Register all active platform services and base features in core DB so admin can manage them, add delivery/hospitality/sports-center backend phases, update apps catalog and production deploy tooling. Co-authored-by: Cursor <cursoragent@cursor.com>
30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
# Future Phases
|
|
|
|
Catch-all for capabilities not yet given a dedicated phase folder.
|
|
|
|
## Candidates
|
|
|
|
- Subscription & Entitlement as independent service
|
|
- Real message bus
|
|
- DNS/TXT custom domain verification
|
|
- Payment gateway integration
|
|
- Advanced permission trees & member invites
|
|
- File storage + S3 provider
|
|
- Website builder (historical; prefer Experience / Torbat Pages), live chat, SMS panel, link shortener, notification (see module registry)
|
|
- Experience Platform (registered — see [phases/Experience](../Experience/README.md))
|
|
|
|
## Rules
|
|
|
|
1. Promote a topic to its own `docs/phases/<Name>/` when active planning starts.
|
|
2. Use [ai-framework/phase-template.md](../../ai-framework/phase-template.md) (or short [phase-template.md](../../templates/phase-template.md)).
|
|
3. Follow [AI Development Framework](../../ai-framework/README.md) for implementation.
|
|
4. Update [roadmap.md](../../roadmap.md) and [module-registry.md](../../module-registry.md) in the same change.
|
|
|
|
## Related Documents
|
|
|
|
- [Roadmap](../../roadmap.md)
|
|
- [Next Steps](../../next-steps.md)
|
|
- [Progress](../../progress.md)
|
|
- [AI Framework](../../ai-framework/README.md)
|
|
- [Phase Manifest](../../ai-framework/phase-manifest.yaml)
|