Files
wyndham-ARR/.project-docs/50-evidence/topics/2026-07-30-arr2-programmatic-pipeline.md
2026-07-31 15:11:42 +08:00

33 lines
1.6 KiB
Markdown

# ARR2.0 Programmatic Pipeline Evidence
## Scope
Independent workspace `/Users/chillishark/Desktop/ARR2.0`; source workspace remained read-only.
## Implementation Evidence
- Active Web composition imports PostgreSQL, OSS, local processor and generic ingestion only.
- Compose contains one application service and no MCP port/domain/service or Agent secrets.
- Root requirements do not install Agent integration or MCP packages.
- Old callback route returns 404 and health has no Agent readiness field.
- All ARR-managed OSS objects use private object ACLs.
## Behavioral Evidence
- Real success fixture: 5 source records, 3 retained records, four committed artifacts, active Finance version.
- Real pricing failure fixture: result + structured + exception artifacts, recorded terminal failure, no active version.
- PostgreSQL fake-cursor tests verify running and infrastructure-failure transitions plus failure outbox SQL.
- Daily download test materializes the committed object and rejects a descriptor hash mismatch.
## Verification Snapshot
- Focused Web/download/programmatic/trace/OSS/deployment suite: 25 passed.
- Focused ingestion PostgreSQL/programmatic suite: 13 passed.
- Final full discovery: 282 passed-or-skipped in 125.8 seconds, with 0 failures/errors and 9 explained skips (3 private
booking fixtures intentionally not bundled; 6 optional XLSX renderer/tool checks).
## Remaining External Verification
Docker/Caddy and a real test database/OSS deployment are not available in this workspace. One controlled no-PII server
vertical slice is still required before production rollout.