# 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](../architecture/adr/ADR-022.md)). 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](../experience-roadmap.md) — Published Resource section + reserved URL patterns + future products
- [phases/Experience/README.md](../phases/Experience/README.md) — architecture status note
- [service-snapshots/experience.yaml](../service-snapshots/experience.yaml) — architecture ADRs / limitations / open todos
- Module boundaries + contracts + ADR index

## What did NOT change

- No `backend/services/experience` code
- 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

1. Any new public surface design MUST plan for `publish_id`.
2. Form / Survey / Appointment UX MUST allow standalone publish.
3. Payment / Communication / Link / QR / Analytics integrations MUST cite `publish_id` only.
4. Do not implement registry storage until a phase is registered in [phase-manifest.yaml](../ai-framework/phase-manifest.yaml).

## Related

- Platform handover: [phase-af-published-resource-arch.md](phase-af-published-resource-arch.md)
- Architecture: [published-resource-architecture.md](../architecture/published-resource-architecture.md)
- Prior backend handover: [phase-11-10.md](phase-11-10.md)
