e41ecfad4c
Include Loyalty/Communication/Sports Center backends and registry updates alongside production nginx and compose wiring. Co-authored-by: Cursor <cursoragent@cursor.com>
2.7 KiB
2.7 KiB
Phase Handover
Every implementation phase must deliver this package before completion.
Copy the sections below into the phase document (or attach a phase-specific handover file) and fill every field. Empty sections are only allowed when marked N/A with justification.
Metadata
| Field | Value |
|---|---|
| Phase ID | (from phase-manifest.yaml) |
| Title | |
| Status | Complete |
| Service(s) | |
| Version | |
| Date | |
| ADR(s) |
Reusable Components
List libraries, engines, providers, shared helpers, or patterns introduced for reuse.
| Component | Location | Reuse notes |
|---|---|---|
Public APIs
| Method | Path | Auth / Permission | Notes |
|---|---|---|---|
Link detailed contracts: api-reference.md, services-contracts.md.
Events
| Event type | Domain / Integration | Payload summary | Version |
|---|---|---|---|
Catalog: event-catalog.md. Standards: event-template.md.
Extension Points
Document intentional hooks for future phases (provider protocols, strategy interfaces, feature flags, entitlement keys).
| Extension point | How to extend | Forbidden uses |
|---|---|---|
Known Limitations
Explicit non-goals and temporary constraints (must not be silently omitted).
Migration Notes
| Item | Detail |
|---|---|
| Alembic revision(s) | |
| Upgrade steps | |
| Downgrade support | |
| Data backfill | |
| Breaking changes | None / described |
Dependencies
| Dependency | Type | Required for |
|---|---|---|
| Core / Service / Provider / Docs |
Next Phase Entry
What the next phase must read and assume:
- This handover + phase doc
- Updated module-registry.md / manifests
- Open limitations that become next-phase scope
- Suggested next phase ID from phase-manifest.yaml / next-steps.md
| Field | Value |
|---|---|
| Recommended next phase | |
| Blockers for next phase | |
| Entry checklist |
Completion Sign-Off
- Quality gates passed (quality-gates.md)
- Tests green
- Documentation updated (documentation-template.md)
- Progress / next-steps / registries updated
- No TODO for claimed deliverables
- Self audit completed (development-loop.md)