TorbatYar/docs/ai-framework/phase-handover.md
Mortezakoohjani e41ecfad4c Sync platform docs, infra, and module services with Accounting integration.
Include Loyalty/Communication/Sports Center backends and registry updates alongside production nginx and compose wiring.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-25 22:35:23 +03:30

104 lines
2.7 KiB
Markdown

# 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](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](../reference/api-reference.md), [services-contracts.md](../reference/services-contracts.md).
## Events
| Event type | Domain / Integration | Payload summary | Version |
| --- | --- | --- | --- |
| | | | |
Catalog: [event-catalog.md](../reference/event-catalog.md). Standards: [event-template.md](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:
1. This handover + phase doc
2. Updated [module-registry.md](../module-registry.md) / manifests
3. Open limitations that become next-phase scope
4. Suggested next phase ID from [phase-manifest.yaml](phase-manifest.yaml) / [next-steps.md](../next-steps.md)
| Field | Value |
| --- | --- |
| Recommended next phase | |
| Blockers for next phase | |
| Entry checklist | |
## Completion Sign-Off
- [ ] Quality gates passed ([quality-gates.md](quality-gates.md))
- [ ] Tests green
- [ ] Documentation updated ([documentation-template.md](documentation-template.md))
- [ ] Progress / next-steps / registries updated
- [ ] No TODO for claimed deliverables
- [ ] Self audit completed ([development-loop.md](development-loop.md))
## Related Documents
- [Phase Template](phase-template.md)
- [Development Loop](development-loop.md)
- [Module Registry](../module-registry.md)
- [Progress](../progress.md)
- [Next Steps](../next-steps.md)