0d424c500a
Unify commercial runtime ownership across backend and frontend so platform, experience, and hospitality modules use the shared commercial source of truth. Co-authored-by: Cursor <cursoragent@cursor.com>
2.1 KiB
2.1 KiB
Experience handover — Architecture Freeze (Actions / Access / Embed)
| Field | Value |
|---|---|
| Patch ID | experience-arch-freeze |
| Service | experience (Torbat Pages) |
| Date | 2026-07-27 |
| Kind | Architecture / documentation only — ARCHITECTURE COMPLETE |
| Backend version | Unchanged — 0.11.10.0 |
| Backend phases | 11.0–11.10 remain complete and unmodified |
Summary
Final Experience architecture freeze. In addition to Published Resources / publish_id:
- Published Actions — open registry; Experience binds; owning services execute
- Public Access Model — open strategies; Identity/Payment/Loyalty/Communication own challenges
- Universal Embed — open embed types with security/sizing/theme/analytics contracts
Architecture status: COMPLETE. Ready for frontend implementation phases when registered — not for further architecture redesign.
What changed (docs only)
- published-resource-architecture.md — §§14–18
- ADR-022 — amended decisions 9–15
- Contracts: action registry, public access, embed
- Roadmap / README / snapshot / manifests / glossary / boundaries
What did NOT change
- No
backend/services/experiencecode - No migrations / APIs / frontend
- No breaking contract changes (additive only)
Inheritance for frontend / future implementation
- Design UI against
publish_id, open actions, access strategies, and embed types. - Do not implement Action/Access/Embed engines until a phase is registered.
- Do not put auth/payment/membership logic in Experience UI beyond calling owning services.
- Prior handover: phase-experience-published-resource-arch.md.
Related
- Framework handover: phase-af-experience-arch-freeze.md
- Architecture: published-resource-architecture.md
- Backend complete: phase-11-10.md