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.0 KiB
2.0 KiB
Experience handover — Published Resource Architecture
| Field | Value |
|---|---|
| Patch ID | experience-published-resource-arch |
| Service | experience (Torbat Pages) |
| Date | 2026-07-27 |
| Kind | Architecture / documentation only |
| Backend version | Unchanged — 0.11.10.0 |
| Backend phases | 11.0–11.10 remain complete and unmodified |
Summary
Experience adopts the platform Published Resource model (ADR-022). Public surfaces authored in Experience will eventually map to Publish Target Registry entries. Forms, Surveys, and Appointment shells are architecturally independent of Site/Page (optional binding only). Cross-service attachments use publish_id, not Experience internal ids.
What changed (docs only)
- experience-roadmap.md — Published Resource section + reserved URL patterns + future products
- phases/Experience/README.md — architecture status note
- service-snapshots/experience.yaml — architecture ADRs / limitations / open todos
- Module boundaries + contracts + ADR index
What did NOT change
- No
backend/services/experiencecode - No migrations
- No new REST endpoints
- No frontend module
- No alteration of completed phase docs 11.0–11.10 deliverables
Inheritance for future Experience work
- Any new public surface design MUST plan for
publish_id. - Form / Survey / Appointment UX MUST allow standalone publish.
- Payment / Communication / Link / QR / Analytics integrations MUST cite
publish_idonly. - Do not implement registry storage until a phase is registered in phase-manifest.yaml.
Related
- Platform handover: phase-af-published-resource-arch.md
- Architecture: published-resource-architecture.md
- Prior backend handover: phase-11-10.md