Skip to content

R3 — Odyssey UAT (Phoenix firm-order memo, productionized)

The Odyssey implementation of the Phoenix firm-order memo: the same memo, driven by real Phoenix + EFS connectors, deployed into Odyssey's sovereignty environment with SSO auth. This is the productionization release — distinct from the Phoenix walkthrough already shipped in the framework demo.

Two tiers — don't conflate them

Phoenix walkthrough (shipped) Odyssey implementation (R3, this release)
What The memo as a seeded DocGen template, runnable in the demo The memo wired to live Phoenix + EFS systems, deployed for Odyssey UAT
Data Local MCP server serving a sample deal store Real Phoenix pricing/cat-modeling + EFS approval integrations
Where docs/solutions/odyssey/, docgen/src/docgen/fixtures/phoenix.py, mcp_servers/phoenix.py this folder (r3-prd.md, r3-tdd.md)
Status ✅ implemented + tested (P1–P3 deterministic == gold; P4/P5 LLM) 📋 planned — see the STALE banner below
Tracking framework epics (composition, gaps) + Phoenix-seed epic (GH #90) R3 release [E-release-3]

The walkthrough is the genericity proof (Phoenix configured purely from framework primitives — no Phoenix engine code). R3 replaces only the faked connector with real integrations + adds the deployment/auth/eval surface.

Source documents

All Phoenix inputs (the client spec, sample data, generators, the gold memos, the mockup) are catalogued in ../../reference/README.md. Start with ../../explanation/phoenix-uc2-analysis.md (requirements + the framework gap analysis that became R2 features G1–G4).

Documents in this release

  • r3-prd.md — product requirements (⚠ STALE — written against the pre-2026-05-26 R1 architecture; client-discovery content valid, framework assumptions need revalidation before R3 starts).
  • r3-tdd.md — technical design (⚠ same staleness caveat; Odyssey-specific tables / routes / approval-detection algorithm stay valid).

Cross-references