TorbatYar/docs/phase-handover/phase-experience-arch-freeze.md
Mortezakoohjani 0d424c500a feat(platform): complete commercial runtime consolidation
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>
2026-07-29 11:11:53 +03:30

47 lines
2.1 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# 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.011.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](../architecture/published-resource-architecture.md) — §§1418
- [ADR-022](../architecture/adr/ADR-022.md) — amended decisions 915
- Contracts: action registry, public access, embed
- Roadmap / README / snapshot / manifests / glossary / boundaries
## What did NOT change
- No `backend/services/experience` code
- No migrations / APIs / frontend
- No breaking contract changes (additive only)
## Inheritance for frontend / future implementation
1. Design UI against `publish_id`, open actions, access strategies, and embed types.
2. Do not implement Action/Access/Embed engines until a phase is registered.
3. Do not put auth/payment/membership logic in Experience UI beyond calling owning services.
4. Prior handover: [phase-experience-published-resource-arch.md](phase-experience-published-resource-arch.md).
## Related
- Framework handover: [phase-af-experience-arch-freeze.md](phase-af-experience-arch-freeze.md)
- Architecture: [published-resource-architecture.md](../architecture/published-resource-architecture.md)
- Backend complete: [phase-11-10.md](phase-11-10.md)