shiyuyun/wyndham-ARR
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ad3d9878c5aa8d956339ef6871322000e694f5ca
wyndham-ARR/.project-docs/20-architecture/system-overview.md
Wyndham ARR ad3d9878c5 fix: enable XML processing in container entry
2026-07-29 18:34:03 +08:00

2.4 KiB
Raw Blame History

System Overview

Current Architecture

The ARR system accepts an Opera XML upload, stores the private source artifact, invokes an Agent for deterministic processing, validates the returned structured result, and commits accepted Finance facts to PostgreSQL. Downstream analytics and report programs consume those committed facts. The accepted target flow automatically triggers monthly processing after the commit; the current manual monthly UI/API remains a known implementation gap.

Main Components

Component Responsibility Notes
arr_web XML upload, job status, controlled downloads and business APIs The existing manual monthly-generation request is not the accepted primary flow.
SuperAgent + deterministic processing skill Convert XML to the approved structured result Must not decide user-facing report parameters.
arr_mcp / ingestion service Independently validate/replay and atomically commit accepted structured results Automatic downstream trigger begins only after commit success.
PostgreSQL Finance facts Authoritative current and retained daily facts Source of truth for downstream reports.
monthly_reports Generate monthly XLSX from committed database facts Internal month/cutoff inputs are allowed; TOTAL PRICE must be an XLSX formula.
channel_analytics / company_reports Additional read/report consumers Must not change the monthly-report trigger contract.
Caddy + Compose deployment boundary Terminate HTTPS, authenticate Web users, keep Web/MCP ports internal and start the explicit processing profile MCP still performs its own bearer check and DNS-rebinding Host validation.

Important Boundaries

  • XML processing and Finance fact validation happen before the monthly-report trigger.
  • The user-facing upload workflow does not collect monthly report year, month, or cutoff date.
  • Monthly processing reads validated database facts rather than repeating Agent business logic.
  • Database total_price may support validation, but the exported TOTAL PRICE cell must remain a formula.
  • Container deployment enables XML processing through both the Dockerfile default Web CMD and the explicit Compose command, and still requires processing_ready=true; direct source CLI execution remains default-closed.

Related Decisions

Last Updated

2026-07-29