# Phase Manifest

# Registry of implementation phases for TorbatYar.
# Status: planned | in_progress | complete | deferred
# Agents must keep this file aligned with docs/progress.md and docs/roadmap.md.

schema_version: 1
updated: "2026-07-28"
# Payment Pay-Reg complete: Enterprise Payment Platform registration (ADR-020).
# Payment payment-arch complete: licensing, contracts, compatibility (ADR-021).
# AF-Discovery complete: Enterprise Phase Discovery mandate (ADR-019).
# AF-Enterprise complete: Enterprise Development Framework upgrade (ADR-018).
# Hospitality Phase 12.3 complete; 12.4 POS Lite next for Hospitality track.
# Experience 11.2 Component Library complete; next experience-11.3 was completed — next experience-11.4 Template System.
# Experience 11.3 Theme & Layout complete; 11.4 Template System complete; next experience-11.5 Localization, RTL/LTR & Media.
# Delivery Platform registration complete; Phase 10.8 Settlement complete; next delivery-10.9.
# Loyalty Phase 7.6 complete; 7.7 Gift Card Platform next for Loyalty track.

phases:
  - id: core-1
    name: Core Platform
    area: Platform
    status: complete
    dependencies: []
    required_documents:
      - docs/architecture/architecture.md
      - docs/development/project-principles.md
    required_services:
      - core-platform

  - id: identity-2
    name: Identity & Access + SSO
    area: Platform
    status: complete
    dependencies:
      - core-1
    required_documents:
      - docs/architecture/identity-architecture.md
      - docs/architecture/adr/ADR-004.md
    required_services:
      - identity-access
      - core-platform

  - id: otp-tenant-3
    name: OTP Login + Tenant Management
    area: Platform
    status: complete
    dependencies:
      - identity-2
    required_documents:
      - docs/architecture/adr/ADR-005.md
      - docs/architecture/multi-tenant-architecture.md
    required_services:
      - core-platform

  - id: onboarding-4
    name: Tenant Onboarding & Workspace Activation
    area: Platform
    status: complete
    dependencies:
      - otp-tenant-3
    required_documents:
      - docs/architecture/multi-tenant-architecture.md
      - docs/architecture/adr/ADR-008.md
      - docs/architecture/adr/ADR-009.md
    required_services:
      - core-platform
      - identity-access

  - id: docs-architecture-D
    name: Documentation Architecture Consolidation
    area: Platform
    status: complete
    dependencies:
      - onboarding-4
    required_documents:
      - docs/README.md
      - docs/architecture/adr/README.md
    required_services: []

  - id: ai-framework
    name: AI Development Framework
    area: Platform
    status: complete
    dependencies:
      - docs-architecture-D
    required_documents:
      - docs/ai-framework/README.md
      - docs/ai-framework/master-prompt.md
      - docs/ai-framework/development-loop.md
      - docs/ai-framework/quality-gates.md
      - docs/architecture/adr/ADR-013.md
    required_services: []

  - id: ai-framework-enterprise
    name: Enterprise Development Framework Upgrade
    area: Platform
    description: Docs-only upgrade of the AI Development Framework into an Enterprise Development Framework — Definition of Done, mandatory phase artifacts, enterprise completeness, boundary rules, expanded gates/loop/templates. No business feature code. Extends ADR-013 via ADR-018. Does not modify completed business phases or implementations.
    status: complete
    dependencies:
      - ai-framework
    required_previous_phase: ai-framework
    required_documents:
      - docs/ai-framework/README.md
      - docs/ai-framework/definition-of-done.md
      - docs/ai-framework/mandatory-phase-artifacts.md
      - docs/ai-framework/enterprise-completeness.md
      - docs/ai-framework/boundary-rules.md
      - docs/ai-framework/master-prompt.md
      - docs/ai-framework/development-loop.md
      - docs/ai-framework/quality-gates.md
      - docs/ai-framework/phase-template.md
      - docs/ai-framework/phase-handover.md
      - docs/architecture/adr/ADR-018.md
      - docs/phase-handover/phase-af-enterprise.md
    required_services: []
    completion_criteria:
      - DoD, mandatory artifacts, enterprise completeness, and boundary rules documents published
      - Master prompt, development loop, quality gates, templates, prompt/cursor rules updated
      - ADR-018 accepted; ADR index and glossary updated
      - Framework handover complete; no business code changes
      - Backward-compatible path docs/ai-framework/ retained
      - Quality gates for documentation/architecture/manifest validation passed

  - id: ai-framework-discovery
    name: Enterprise Phase Discovery Mandate
    area: Platform
    description: Docs-only framework enhancement — mandatory Enterprise Phase Discovery before every phase implementation. Agents must inventory roadmap, architecture, boundaries, prior handover, codebase, APIs, domain, events, permissions, aggregates, tests, and docs; derive missing current-phase production capabilities; never assume CRUD; never pull future phases or violate boundaries. ADR-019 extends ADR-018. No business feature code.
    status: complete
    dependencies:
      - ai-framework-enterprise
    required_previous_phase: ai-framework-enterprise
    required_documents:
      - docs/ai-framework/enterprise-phase-discovery.md
      - docs/ai-framework/README.md
      - docs/ai-framework/master-prompt.md
      - docs/ai-framework/development-loop.md
      - docs/ai-framework/quality-gates.md
      - docs/ai-framework/phase-template.md
      - docs/ai-framework/phase-handover.md
      - docs/ai-framework/definition-of-done.md
      - docs/architecture/adr/ADR-019.md
      - docs/phase-handover/phase-af-discovery.md
    required_services: []
    completion_criteria:
      - enterprise-phase-discovery.md published with inputs, procedure, checklist, Discovery Record
      - Loop stage 1 is Discovery; quality gates include Discovery gate
      - Phase template/handover/prompt/cursor/DoD/completeness updated
      - ADR-019 accepted; glossary/progress/manifests updated
      - Framework handover complete; no business code changes
      - Quality gates for documentation/architecture/manifest validation passed

  # --- Accounting ---
  - id: accounting-5.1
    name: Accounting Foundation
    area: Accounting
    status: complete
    dependencies:
      - onboarding-4
    required_documents:
      - docs/phases/Accounting/README.md
      - docs/architecture/adr/ADR-010.md
    required_services:
      - accounting

  - id: accounting-5.2
    name: Double-Entry Posting Engine
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.1
    required_documents:
      - docs/phases/Accounting/phase-5.2-double-entry-posting-engine.md
      - docs/architecture/adr/ADR-010.md
    required_services:
      - accounting

  - id: accounting-5.3
    name: General Ledger & Fiscal Management
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.2
    required_documents:
      - docs/phases/Accounting/phase-5.3-general-ledger-fiscal-management.md
    required_services:
      - accounting

  - id: accounting-5.4
    name: Treasury Management
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.3
    required_documents:
      - docs/phases/Accounting/phase-5.4-treasury-management.md
    required_services:
      - accounting

  - id: accounting-5.5
    name: Accounts Receivable & Payable
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.4
    required_documents:
      - docs/phases/Accounting/phase-5.5-accounts-receivable-payable.md
    required_services:
      - accounting

  - id: accounting-5.6
    name: Sales Accounting Integration
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.5
    required_documents:
      - docs/phases/Accounting/phase-5.6-sales-accounting-integration.md
    required_services:
      - accounting

  - id: accounting-5.7
    name: Purchase & Inventory Accounting
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.6
    required_documents:
      - docs/phases/Accounting/phase-5.7-purchase-inventory-accounting-integration.md
    required_services:
      - accounting

  - id: accounting-5.8
    name: Fixed Assets
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.7
    required_documents:
      - docs/phases/Accounting/phase-5.8-fixed-assets-management.md
    required_services:
      - accounting

  - id: accounting-5.9
    name: HCM / Payroll Accounting
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.8
    required_documents:
      - docs/phases/Accounting/phase-5.9-hcm-payroll-accounting.md
    required_services:
      - accounting

  - id: accounting-5.10
    name: Financial Reporting & BI
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.9
    required_documents:
      - docs/phases/Accounting/phase-5.10-financial-reporting-business-intelligence.md
    required_services:
      - accounting

  - id: accounting-5.11
    name: Compliance, Audit & Governance
    area: Accounting
    status: complete
    dependencies:
      - accounting-5.10
    required_documents:
      - docs/phases/Accounting/phase-5.11-enterprise-compliance-audit-governance.md
    required_services:
      - accounting

  - id: accounting-5.12
    name: Accounting AI Assistants
    area: Accounting
    status: planned
    dependencies:
      - accounting-5.11
      - ai-framework
    required_documents:
      - docs/architecture/ai-architecture.md
      - docs/phases/Accounting/README.md
    required_services:
      - accounting

  # --- CRM ---
  - id: crm-6.0
    name: CRM Service Foundation
    area: CRM
    status: complete
    dependencies:
      - onboarding-4
    required_documents:
      - docs/crm-phase-6-0.md
      - docs/phases/CRM/README.md
    required_services:
      - crm

  - id: crm-6.1
    name: CRM Core Business Entities
    area: CRM
    status: complete
    dependencies:
      - crm-6.0
    required_documents:
      - docs/crm-phase-6-1.md
    required_services:
      - crm

  - id: crm-6.2
    name: CRM Sales Process Engine
    area: CRM
    status: complete
    dependencies:
      - crm-6.1
    required_documents:
      - docs/crm-phase-6-2.md
    required_services:
      - crm

  - id: crm-6.3
    name: CRM Sales Collaboration
    area: CRM
    status: complete
    dependencies:
      - crm-6.2
    required_documents:
      - docs/crm-phase-6-3.md
    required_services:
      - crm

  # --- Loyalty ---
  - id: loyalty-7.0
    name: Loyalty Service Foundation
    area: Loyalty
    status: complete
    dependencies:
      - onboarding-4
    required_documents:
      - docs/loyalty-phase-7-0.md
      - docs/architecture/adr/ADR-011.md
      - docs/phases/Loyalty/README.md
    required_services:
      - loyalty

  - id: loyalty-7.1
    name: Membership Engine
    area: Loyalty
    status: complete
    dependencies:
      - loyalty-7.0
      - ai-framework
    required_documents:
      - docs/loyalty-phase-7-1.md
      - docs/phase-handover/phase-7-1.md
      - docs/phases/Loyalty/README.md
      - docs/architecture/adr/ADR-011.md
    required_services:
      - loyalty

  - id: loyalty-7.2
    name: Point Engine
    area: Loyalty
    status: complete
    dependencies:
      - loyalty-7.1
      - ai-framework
    required_documents:
      - docs/loyalty-phase-7-2.md
      - docs/phase-handover/phase-7-2.md
      - docs/phases/Loyalty/README.md
      - docs/architecture/adr/ADR-011.md
      - docs/service-snapshots/loyalty.yaml
    required_services:
      - loyalty

  - id: loyalty-7.3
    name: Rewards Engine
    area: Loyalty
    status: complete
    dependencies:
      - loyalty-7.2
      - ai-framework
    required_documents:
      - docs/loyalty-phase-7-3.md
      - docs/phase-handover/phase-7-3.md
      - docs/phases/Loyalty/README.md
      - docs/architecture/adr/ADR-011.md
      - docs/service-snapshots/loyalty.yaml
    required_services:
      - loyalty

  - id: loyalty-7.4
    name: Campaign Engine
    area: Loyalty
    status: complete
    dependencies:
      - loyalty-7.3
      - ai-framework
    required_documents:
      - docs/loyalty-phase-7-4.md
      - docs/phase-handover/phase-7-4.md
      - docs/service-snapshots/loyalty.yaml
    required_services:
      - loyalty

  - id: loyalty-7.5
    name: Referral Engine
    area: Loyalty
    status: complete
    dependencies:
      - loyalty-7.4
      - ai-framework
    required_documents:
      - docs/loyalty-phase-7-5.md
      - docs/phase-handover/phase-7-5.md
      - docs/service-snapshots/loyalty.yaml
    required_services:
      - loyalty

  - id: loyalty-7.6
    name: Wallet
    area: Loyalty
    status: complete
    dependencies:
      - loyalty-7.5
      - ai-framework
    required_documents:
      - docs/loyalty-phase-7-6.md
      - docs/phase-handover/phase-7-6.md
      - docs/phases/Loyalty/README.md
      - docs/architecture/adr/ADR-011.md
      - docs/service-snapshots/loyalty.yaml
    required_services:
      - loyalty

  - id: loyalty-7.7
    name: Gift Card Platform
    area: Loyalty
    status: planned
    dependencies:
      - loyalty-7.6
    required_documents:
      - docs/phases/Loyalty/README.md
      - docs/ai-framework/phase-template.md
    required_services:
      - loyalty

  - id: loyalty-7.8
    name: Analytics
    area: Loyalty
    status: planned
    dependencies:
      - loyalty-7.7
    required_documents:
      - docs/phases/Loyalty/README.md
    required_services:
      - loyalty

  - id: loyalty-7.9
    name: Public / Partner / Webhook APIs
    area: Loyalty
    status: planned
    dependencies:
      - loyalty-7.8
    required_documents:
      - docs/phases/Loyalty/README.md
    required_services:
      - loyalty

  - id: loyalty-7.10
    name: Final Review
    area: Loyalty
    status: planned
    dependencies:
      - loyalty-7.9
    required_documents:
      - docs/phases/Loyalty/README.md
    required_services:
      - loyalty

  # --- SMS / Communication ---
  - id: communication-8
    name: Enterprise Communication Platform (SMS-first)
    area: SMS
    description: Independent communication-service (SMS MVP). Production Ready — feature-complete for current MVP scope; future channels in communication-roadmap.md only.
    status: complete
    dependencies:
      - onboarding-4
    required_documents:
      - docs/communication-phase-8.md
      - docs/communication-phase-8-audit.md
      - docs/communication-roadmap.md
      - docs/phase-handover/phase-8.md
      - docs/service-snapshots/communication.yaml
      - docs/architecture/adr/ADR-012.md
    required_services:
      - communication
    notes: MVP feature-complete (SMS). No registered 9.x phases. Email/Push/Telegram/WhatsApp/Rubika/Voice remain future roadmap items.

  - id: sms-panel-future
    name: Legacy SMS Panel Scaffold Alignment
    area: SMS
    status: deferred
    dependencies:
      - communication-8
    required_documents:
      - docs/module-registry.md
    required_services:
      - sms_panel
    notes: Prefer Communication service (ADR-012); sms_panel scaffold remains historical/planned alignment only.

  # --- Sports Center (Phase 9.0–9.10) ---
  - id: sports-center-9.0
    name: Sports Center Foundation
    area: Sports Center
    description: Independent sports_center service scaffold, sports_center_db, health/capabilities, permissions sports_center.*, publish-only events, tenant isolation, audit shell.
    status: complete
    dependencies:
      - onboarding-4
      - ai-framework
    required_previous_phase: ai-framework
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
      - docs/architecture/adr/ADR-014.md
      - docs/sports-center-phase-9-0.md
      - docs/phase-handover/phase-9-0.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - sports_center
    completion_criteria:
      - Service scaffold under backend/services/sports_center with API → Service → Repository → Model layering
      - Alembic initial migration for foundation tables only as scoped
      - Health endpoint green; permission tree sports_center.* documented
      - Tenant isolation + architecture + docs tests green
      - Module registry, manifests, progress, handover updated
      - Quality gates passed; no business engines beyond foundation

  - id: sports-center-9.1
    name: Membership Catalog
    area: Sports Center
    description: Membership types, packages, plans, pricing models, age groups, sport categories, membership rules, renewal/freezing/expiration policies, validation, events, APIs.
    status: complete
    dependencies:
      - sports-center-9.0
    required_previous_phase: sports-center-9.0
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
      - docs/architecture/adr/ADR-014.md
      - docs/sports-center-phase-9-1.md
      - docs/phase-handover/phase-9-1.md
      - docs/ai-framework/module-template.md
    required_services:
      - sports_center
    completion_criteria:
      - Membership catalog aggregates implemented with tenant isolation
      - APIs, validators, permissions, events, tests, docs, handover complete
      - No member enrollment / coach / attendance / booking engines

  - id: sports-center-9.2
    name: Member Management
    area: Sports Center
    description: Members, family members, medical information, emergency contacts, membership assignment, cards/QR/digital membership, waivers, documents, attachments, status management.
    status: complete
    dependencies:
      - sports-center-9.1
    required_previous_phase: sports-center-9.1
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
      - docs/phase-handover/phase-9-1.md
      - docs/sports-center-phase-9-2.md
      - docs/phase-handover/phase-9-2.md
      - docs/ai-framework/module-template.md
    required_services:
      - sports_center
    completion_criteria:
      - Member management APIs + validators + tests green
      - Consumes Membership Catalog from 9.1; does not recreate catalog tables
      - No coach/attendance/booking engines yet

  - id: sports-center-9.3
    name: Coach & Staff Management
    area: Sports Center
    description: Coaches, trainers, nutritionists, medical staff, reception, managers, working hours, certificates, skills, payroll refs, availability, permissions.
    status: complete
    dependencies:
      - sports-center-9.2
    required_previous_phase: sports-center-9.2
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
      - docs/ai-framework/module-template.md
    required_services:
      - sports_center
    completion_criteria:
      - Coach and staff modules complete with APIs, permissions, events, tests, docs
      - No attendance devices or booking engine yet

  - id: sports-center-9.4
    name: Scheduling & Booking
    area: Sports Center
    description: Sports classes, sessions, timetables, reservations, capacity, waiting lists, recurring sessions, resource allocation, facilities, equipment reservation, calendar.
    status: complete
    dependencies:
      - sports-center-9.3
    required_previous_phase: sports-center-9.3
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
    required_services:
      - sports_center
    completion_criteria:
      - Booking and scheduling APIs and rules green
      - Tests include conflict/tenant isolation; docs/handover updated

  - id: sports-center-9.5
    name: Attendance & Access Control
    area: Sports Center
    description: Attendance, QR/RFID/barcode/face-ready check-in, manual attendance, entry/exit gates, late arrival, absence, attendance history.
    status: complete
    dependencies:
      - sports-center-9.4
    required_previous_phase: sports-center-9.4
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
    required_services:
      - sports_center
    completion_criteria:
      - Attendance and access control complete with isolation/security tests
      - Vendor adapters remain outside business services

  - id: sports-center-9.6
    name: Training Management
    area: Sports Center
    description: Training programs, exercises, workout plans, goals, measurements, progress tracking, nutrition plans, body composition, assessments, performance records.
    status: complete
    dependencies:
      - sports-center-9.5
    required_previous_phase: sports-center-9.5
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
    required_services:
      - sports_center
    completion_criteria:
      - Training/workout modules complete with APIs, events, tests, docs
      - No competitions module yet

  - id: sports-center-9.7
    name: Competition & Event Management
    area: Sports Center
    description: Competitions, tournaments, matches, teams, groups, registrations, rankings, results, medals, certificates, judges, schedules.
    status: complete
    dependencies:
      - sports-center-9.6
    required_previous_phase: sports-center-9.6
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
    required_services:
      - sports_center
    completion_criteria:
      - Competitions and events modules complete; no payment posting ownership
      - Tests, docs, handover complete

  - id: sports-center-9.8
    name: Financial Integration
    area: Sports Center
    description: Integrate Accounting, CRM, Loyalty, Communication, payments, invoices, subscriptions, discounts, refunds, installments via API/Events only — no business logic duplication.
    status: planned
    dependencies:
      - sports-center-9.7
      - accounting-5.11
      - crm-6.3
      - loyalty-7.0
      - communication-8
    required_previous_phase: sports-center-9.7
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/architecture/adr/ADR-010.md
      - docs/architecture/adr/ADR-011.md
      - docs/architecture/adr/ADR-012.md
      - docs/architecture/adr/ADR-014.md
    required_services:
      - sports_center
      - accounting
      - crm
      - loyalty
      - communication
    completion_criteria:
      - Integrations via API/events only; no journal creation inside Sports Center
      - Tests prove no cross-DB access; docs/contracts updated

  - id: sports-center-9.9
    name: AI & Analytics
    area: Sports Center
    description: Integrate Enterprise AI Platform for recommendations, attendance/retention/churn prediction, workout suggestions, capacity forecasting, dashboards and KPIs — AI optional.
    status: planned
    dependencies:
      - sports-center-9.8
      - ai-framework
    required_previous_phase: sports-center-9.8
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/architecture/ai-architecture.md
      - docs/phases/AI/README.md
    required_services:
      - sports_center
    completion_criteria:
      - Analytics/AI surfaces documented/implemented per scope
      - Core flows work when AI is off
      - Tests and docs complete

  - id: sports-center-9.10
    name: Enterprise Validation
    area: Sports Center
    description: Full AI Framework validation — architecture, security, performance, docs, integration, tenant isolation, migration, API compatibility, dependency checks, self-heal until green.
    status: planned
    dependencies:
      - sports-center-9.9
    required_previous_phase: sports-center-9.9
    required_documents:
      - docs/sports-center-roadmap.md
      - docs/phases/SportsCenter/README.md
      - docs/ai-framework/quality-gates.md
      - docs/ai-framework/phase-handover.md
      - docs/deployment/production.md
    required_services:
      - sports_center
    completion_criteria:
      - All Sports Center quality gates passed
      - Production readiness notes complete
      - Module registry version/phase updated; progress marks 9.10 complete
      - No undocumented public API/event/permission


  # --- Delivery & Fleet Platform (Phase 10.0–10.10) ---
  - id: delivery-reg
    name: Delivery & Fleet Platform Registration
    area: Delivery
    description: Documentation-only registration of independent delivery service, delivery_db, phases 10.0–10.10, ADR-015, module/glossary/boundary updates. No business code.
    status: complete
    dependencies:
      - onboarding-4
      - ai-framework
    required_previous_phase: ai-framework
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
      - docs/architecture/adr/ADR-015.md
      - docs/phase-handover/phase-dp-reg.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - delivery
    completion_criteria:
      - Service registered in service-manifest with delivery_db and delivery.* permissions
      - Phases 10.0–10.10 registered in phase-manifest
      - Module registry, glossary, module-boundaries, ADR-015 updated
      - Progress and next-steps updated; handover complete
      - No business code, models, APIs, or migrations in this phase
      - Quality gates for documentation/architecture/manifest validation passed

  - id: delivery-10.0
    name: Delivery Platform Foundation
    area: Delivery
    description: Independent delivery service scaffold, delivery_db, health/capabilities/metrics, permissions delivery.*, publish-only event shells, tenant isolation, audit/config shells, provider/routing-engine contracts only.
    status: complete
    dependencies:
      - delivery-reg
    required_previous_phase: delivery-reg
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
      - docs/architecture/adr/ADR-015.md
      - docs/phase-handover/phase-dp-reg.md
      - docs/delivery-phase-10-0.md
      - docs/phase-handover/phase-10-0.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - delivery
    completion_criteria:
      - Service scaffold under backend/services/delivery with API → Service → Repository → Model layering
      - Alembic initial migration for foundation tables only as scoped
      - Health, capabilities, metrics endpoints; permission tree delivery.* documented
      - Tenant isolation + architecture + docs tests green
      - No dispatch/routing/tracking engines beyond foundation shells
      - Quality gates passed; handover complete

  - id: delivery-10.1
    name: Driver Management
    area: Delivery
    description: Drivers, profiles, credential refs, status lifecycle, permissions, events, APIs.
    status: complete
    dependencies:
      - delivery-10.0
    required_previous_phase: delivery-10.0
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
      - docs/architecture/adr/ADR-015.md
      - docs/ai-framework/module-template.md
      - docs/delivery-phase-10-1.md
      - docs/phase-handover/phase-10-1.md
    required_services:
      - delivery
    completion_criteria:
      - Driver management APIs + validators + tests green
      - Lifecycle, credentials/documents, outbox, list filter/sort/search
      - No fleet/dispatch/routing engines yet
      - Quality gates passed; handover complete

  - id: delivery-10.2
    name: Fleet & Vehicle Types
    area: Delivery
    description: Fleets, vehicle types catalog, vehicles, assignments shells, permissions, events, APIs.
    status: complete
    dependencies:
      - delivery-10.1
    required_previous_phase: delivery-10.1
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
    required_services:
      - delivery
    completion_criteria:
      - Fleet and vehicle modules complete with tenant isolation tests
      - No dispatch engine yet

  - id: delivery-10.3
    name: Availability, Shifts & Working Zones
    area: Delivery
    description: Driver availability, shift management, working zones, readiness rules.
    status: complete
    dependencies:
      - delivery-10.2
    required_previous_phase: delivery-10.2
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
    required_services:
      - delivery
    completion_criteria:
      - Availability/shift/zone APIs + tests green
      - No dispatch/routing engines yet

  - id: delivery-10.4
    name: Pricing, Capabilities & Bundles
    area: Delivery
    description: Delivery pricing shells, capability flags, capability bundles.
    status: complete
    dependencies:
      - delivery-10.3
    required_previous_phase: delivery-10.3
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
    required_services:
      - delivery
    completion_criteria:
      - Pricing/capabilities/bundles APIs + validators + tests green
      - No settlement posting ownership

  - id: delivery-10.5
    name: Dispatch Engine
    area: Delivery
    description: Dispatch engine, job assignment, dispatcher workflows (API), multi-vertical job refs.
    status: complete
    dependencies:
      - delivery-10.4
    required_previous_phase: delivery-10.4
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
    required_services:
      - delivery
    completion_criteria:
      - Dispatch APIs + isolation/security tests green
      - Verticals interact via API/events only
      - No deep routing optimization yet (10.6)

  - id: delivery-10.6
    name: Routing & Optimization
    area: Delivery
    description: Routing plans, multi pickup, multi drop, optimization strategies, future routing engine adapters.
    status: complete
    dependencies:
      - delivery-10.5
    required_previous_phase: delivery-10.5
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
    required_services:
      - delivery
    completion_criteria:
      - Routing/optimization modules complete; external engines via adapters
      - Tests and docs complete

  - id: delivery-10.7
    name: Tracking & Proof of Delivery
    area: Delivery
    description: Live tracking, journey timeline, proof of delivery, customer tracking APIs.
    status: complete
    dependencies:
      - delivery-10.6
    required_previous_phase: delivery-10.6
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
    required_services:
      - delivery
    completion_criteria:
      - Tracking and POD APIs + tenant isolation tests green
      - Distinct from Communication message delivery tracking

  - id: delivery-10.8
    name: Settlement
    area: Delivery
    description: Driver/merchant settlement intents; post to Accounting via API/Events only — no journal ownership.
    status: complete
    dependencies:
      - delivery-10.7
      - accounting-5.11
    required_previous_phase: delivery-10.7
    required_documents:
      - docs/delivery-roadmap.md
      - docs/architecture/adr/ADR-010.md
      - docs/architecture/adr/ADR-015.md
    required_services:
      - delivery
      - accounting
    completion_criteria:
      - Settlement via Accounting APIs/events only; no cross-DB access
      - Tests prove no journal creation inside Delivery

  - id: delivery-10.9
    name: Merchant Connector & App Surfaces
    area: Delivery
    description: Merchant connector for verticals, notifications via Communication, Driver App and Dispatcher Panel API contracts, customer tracking polish.
    status: planned
    dependencies:
      - delivery-10.8
      - communication-8
    required_previous_phase: delivery-10.8
    required_documents:
      - docs/delivery-roadmap.md
      - docs/architecture/adr/ADR-012.md
      - docs/architecture/adr/ADR-015.md
    required_services:
      - delivery
      - communication
    completion_criteria:
      - Connector + notification client + app API contracts documented/tested
      - No SMS provider ownership; UI remains in frontend

  - id: delivery-10.10
    name: Analytics, AI Ready & Enterprise Validation
    area: Delivery
    description: Fleet analytics shells, AI-ready optional hooks, full AI Framework validation — architecture, security, performance, docs, integration, tenant isolation, migration, API compatibility, self-heal until green.
    status: planned
    dependencies:
      - delivery-10.9
      - ai-framework
    required_previous_phase: delivery-10.9
    required_documents:
      - docs/delivery-roadmap.md
      - docs/phases/Delivery/README.md
      - docs/ai-framework/quality-gates.md
      - docs/ai-framework/phase-handover.md
      - docs/architecture/ai-architecture.md
    required_services:
      - delivery
    completion_criteria:
      - All Delivery quality gates passed
      - Core flows work when AI is off
      - Module registry version/phase updated; progress marks 10.10 complete
      - No undocumented public API/event/permission

  # --- Experience Platform / Torbat Pages (Phase 11.0–11.10) ---
  - id: experience-reg
    name: Experience Platform Registration
    area: Experience
    description: Documentation-only registration of independent experience service, experience_db, phases 11.0–11.10, ADR-016, module/glossary/boundary updates. No business code. Prefer experience over historical website_builder scaffold.
    status: complete
    dependencies:
      - onboarding-4
      - ai-framework
    required_previous_phase: ai-framework
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/architecture/adr/ADR-016.md
      - docs/experience-phase-xp-reg.md
      - docs/phase-handover/phase-xp-reg.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - experience
    completion_criteria:
      - Service registered in service-manifest with experience_db and experience.* permissions
      - Phases 11.0–11.10 registered in phase-manifest
      - Module registry, glossary, module-boundaries, ADR-016 updated
      - Progress and next-steps updated; handover complete
      - No business code, models, APIs, or migrations in this phase
      - Quality gates for documentation/architecture/manifest validation passed

  - id: experience-11.0
    name: Experience Platform Foundation
    area: Experience
    description: Independent experience service scaffold, experience_db, health/capabilities/metrics, permissions experience.*, publish-only event shells, tenant isolation, audit/config shells, provider contracts only.
    status: complete
    dependencies:
      - experience-reg
    required_previous_phase: experience-reg
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/architecture/adr/ADR-016.md
      - docs/phase-handover/phase-xp-reg.md
      - docs/experience-phase-11-0.md
      - docs/phase-handover/phase-11-0.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - experience
    completion_criteria:
      - Service scaffold under backend/services/experience with API → Service → Repository → Model layering
      - Alembic initial migration for foundation tables only as scoped
      - Health, capabilities, metrics endpoints; permission tree experience.* documented
      - Tenant isolation + architecture + docs tests green
      - No page/theme/template engines beyond foundation shells
      - Quality gates passed; handover complete

  - id: experience-11.1
    name: Sites & Page Resources
    area: Experience
    description: Sites, pages as resources, page types (landing, mini site, menu, bio, profile, event, campaign, portfolio, blog, QR, SEO, media, knowledge, …), lifecycle, permissions, events, APIs.
    status: complete
    dependencies:
      - experience-11.0
    required_previous_phase: experience-11.0
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/architecture/adr/ADR-016.md
      - docs/experience-phase-11-1.md
      - docs/phase-handover/phase-11-1.md
      - docs/ai-framework/module-template.md
    required_services:
      - experience
    completion_criteria:
      - Site and page resource APIs + validators + tests green
      - No component versioning / theme / template engines yet

  - id: experience-11.2
    name: Component Library & Versioning
    area: Experience
    description: Versioned components, component versions, composition shells, permissions, events, APIs.
    status: complete
    dependencies:
      - experience-11.1
    required_previous_phase: experience-11.1
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/experience-phase-11-2.md
      - docs/phase-handover/phase-11-2.md
    required_services:
      - experience
    completion_criteria:
      - Component library with immutable versions; tenant isolation tests green
      - No theme/layout engine yet

  - id: experience-11.3
    name: Theme & Layout Engine
    area: Experience
    description: Replaceable themes, dynamic layouts, directionality-ready shells.
    status: complete
    dependencies:
      - experience-11.2
    required_previous_phase: experience-11.2
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/architecture/adr/ADR-008.md
      - docs/experience-phase-11-3.md
      - docs/phase-handover/phase-11-3.md
    required_services:
      - experience
    completion_criteria:
      - Theme and layout APIs + tests green
      - No template catalog engine yet

  - id: experience-11.4
    name: Template System
    area: Experience
    description: Template catalog, instantiation from templates, page-type starter packs.
    status: complete
    dependencies:
      - experience-11.3
    required_previous_phase: experience-11.3
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/experience-phase-11-4.md
      - docs/phase-handover/phase-11-4.md
    required_services:
      - experience
    completion_criteria:
      - Template APIs + validators + tests green
      - No forms/surveys engine yet

  - id: experience-11.5
    name: Localization, RTL/LTR & Media
    area: Experience
    description: Locales, RTL/LTR, media references via Storage only (no binaries in experience_db).
    status: complete
    dependencies:
      - experience-11.4
    required_previous_phase: experience-11.4
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/experience-phase-11-5.md
      - docs/phase-handover/phase-11-5.md
    required_services:
      - experience
    completion_criteria:
      - Localization and media-ref APIs + isolation tests green
      - No form/survey/appointment engines yet

  - id: experience-11.6
    name: Forms, Surveys & Appointments
    area: Experience
    description: Forms, surveys, appointment page shells; submission/booking refs via APIs/events only.
    status: complete
    dependencies:
      - experience-11.5
    required_previous_phase: experience-11.5
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/experience-phase-11-6.md
      - docs/phase-handover/phase-11-6.md
    required_services:
      - experience
    completion_criteria:
      - Forms/surveys/appointment APIs + tests green
      - No deep CRM/scheduling ownership; refs only

  - id: experience-11.7
    name: Publishing, Domains, SEO & PWA
    area: Experience
    description: Publish workflows, custom domain binding refs, SEO metadata/sitemap/robots shells, PWA readiness.
    status: complete
    dependencies:
      - experience-11.6
    required_previous_phase: experience-11.6
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/architecture/adr/ADR-009.md
      - docs/experience-phase-11-7.md
      - docs/phase-handover/phase-11-7.md
    required_services:
      - experience
    completion_criteria:
      - Publishing/SEO/PWA APIs + tests green
      - DNS/SSL edge remains Core/Nginx patterns; Experience stores binding refs

  - id: experience-11.8
    name: Bundles, Licensing & Feature Toggles
    area: Experience
    description: Capability bundles (Mini Site, Menu, Bio Link, …), licensing shells, feature toggles coordinated with Core entitlement.
    status: complete
    dependencies:
      - experience-11.7
    required_previous_phase: experience-11.7
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/experience-phase-11-8.md
      - docs/phase-handover/phase-11-8.md
    required_services:
      - experience
    completion_criteria:
      - Bundles/toggles APIs + validators + tests green
      - No Core plan-engine ownership

  - id: experience-11.9
    name: Consumer Integrations & Widgets
    area: Experience
    description: Consumer connector contracts for Hospitality/Marketplace/Sports/CRM/etc., embeddable widgets, Communication notify client.
    status: complete
    dependencies:
      - experience-11.8
      - communication-8
    required_previous_phase: experience-11.8
    required_documents:
      - docs/experience-roadmap.md
      - docs/architecture/adr/ADR-012.md
      - docs/architecture/adr/ADR-016.md
    required_services:
      - experience
      - communication
    completion_criteria:
      - Connector + widget contracts documented/tested
      - No SMS provider ownership; UI remains in frontend

  - id: experience-11.10
    name: Analytics, AI Content & Enterprise Validation
    area: Experience
    description: Analytics shells, optional AI content hooks, full AI Framework validation — architecture, security, performance, docs, integration, tenant isolation, migration, API compatibility, self-heal until green.
    status: complete
    dependencies:
      - experience-11.9
      - ai-framework
    required_previous_phase: experience-11.9
    required_documents:
      - docs/experience-roadmap.md
      - docs/phases/Experience/README.md
      - docs/ai-framework/quality-gates.md
      - docs/ai-framework/phase-handover.md
      - docs/architecture/ai-architecture.md
    required_services:
      - experience
    completion_criteria:
      - All Experience quality gates passed
      - Core flows work when AI is off
      - Module registry version/phase updated; progress marks 11.10 complete
      - No undocumented public API/event/permission

  - id: platform-published-resource-arch
    name: Platform Published Resource Architecture
    area: Platform
    description: Docs-only architecture patch — Published Resource abstraction, Publish Target Registry contract, standalone Form/Survey/Appointment publish rules, reserved public URL prefixes, cross-service publish_id integration contracts (Payment, Communication, Short Link, QR, Analytics, verticals, future products). ADR-022. No backend, frontend, migration, or API implementation.
    status: complete
    dependencies:
      - experience-11.10
      - ai-framework
    required_previous_phase: experience-11.10
    required_documents:
      - docs/architecture/published-resource-architecture.md
      - docs/architecture/adr/ADR-022.md
      - docs/reference/published-resource-contracts.md
      - docs/experience-roadmap.md
      - docs/phase-handover/phase-af-published-resource-arch.md
      - docs/phase-handover/phase-experience-published-resource-arch.md
    required_services:
      - experience
    completion_criteria:
      - Architecture doc + ADR-022 accepted and indexed
      - Contracts + Experience/framework handovers published
      - Module boundaries, integration architecture, manifests, snapshot updated
      - No business code, migrations, or UI changes
      - Completed Experience phases 11.0–11.10 remain unmodified

  - id: platform-experience-arch-freeze
    name: Experience Architecture Freeze (Actions, Access, Embed)
    area: Platform
    description: Final docs-only architecture freeze — Published Actions (open Action Registry), Public Access Model (open strategies; Experience never owns auth), Universal Embed Architecture (open embed types + security/sizing/theme/analytics contracts). Amends ADR-022 additively. Marks Experience Platform ARCHITECTURE COMPLETE. No backend, frontend, migration, or API implementation.
    status: complete
    dependencies:
      - platform-published-resource-arch
    required_previous_phase: platform-published-resource-arch
    required_documents:
      - docs/architecture/published-resource-architecture.md
      - docs/architecture/adr/ADR-022.md
      - docs/reference/published-action-registry.md
      - docs/reference/public-access-contract.md
      - docs/reference/embed-contract.md
      - docs/reference/published-resource-contracts.md
      - docs/phase-handover/phase-af-experience-arch-freeze.md
      - docs/phase-handover/phase-experience-arch-freeze.md
    required_services:
      - experience
    completion_criteria:
      - Action / Access / Embed contracts published
      - ADR-022 amended additively; architecture marked complete
      - Snapshot, manifests, roadmap, handovers updated
      - Fully backward compatible; no business code or migrations
      - Completed Experience phases 11.0–11.10 remain unmodified

  # --- Experience Frontend (Torbat Pages) — FE-11.0–11.5 STOP ---
  - id: experience-fe-11.0
    name: Experience Frontend Framework
    area: docs/frontend
    description: Hub, PortalShell, AuthGuard, workspace switcher, permissions/capabilities hooks, admin CRUD lists, BFF to :8008, design tokens.
    status: complete
    dependencies:
      - platform-experience-arch-freeze
    required_documents:
      - docs/experience-frontend-roadmap.md
      - frontend/docs/experience-frontend-architecture.md
    required_services:
      - experience
    completion_criteria:
      - frontend/modules/experience scaffolded mirroring Delivery
      - docker-compose EXPERIENCE_* env vars
      - apps catalog experience available

  - id: experience-fe-11.1
    name: Experience Executive Dashboard
    area: docs/frontend
    status: complete
    dependencies:
      - experience-fe-11.0
    required_documents:
      - docs/experience-frontend-roadmap.md
    completion_criteria:
      - Dashboard with API counts, recharts, recent resources, audit slice

  - id: experience-fe-11.2
    name: Experience Workspace & Content UI
    area: docs/frontend
    status: complete
    dependencies:
      - experience-fe-11.1
    completion_criteria:
      - CRUD workspaces/sites/pages/domains/templates; publish-targets provisional publish_id

  - id: experience-fe-11.3
    name: Experience Visual Builder UI
    area: docs/frontend
    status: complete
    dependencies:
      - experience-fe-11.2
    completion_criteria:
      - Page builder with placements; component/theme/layout CRUD; builder not blocked by page_builder flag

  - id: experience-fe-11.4
    name: Experience Forms & Surveys UI
    area: docs/frontend
    status: complete
    dependencies:
      - experience-fe-11.3
    completion_criteria:
      - Form/survey CRUD and builders; no appointment booking UI

  - id: experience-fe-11.5
    name: Experience Publishing & Public UI
    area: docs/frontend
    status: complete
    dependencies:
      - experience-fe-11.4
    required_documents:
      - docs/phase-handover/phase-experience-fe-11-5.md
      - docs/service-snapshots/experience-frontend.yaml
      - frontend/docs/experience-validation-report.md
      - docs/experience-frontend-progress.md
    completion_criteria:
      - Publishing/SEO/PWA CRUD, public preview, analytics refresh, embed snippet, published-actions catalog
      - Design system playground with light/dark, brand, RTL/LTR, charts/maps/tables/timeline/kanban
      - STOP — FE-11.6+ not started

  # --- AI Framework: Project Status Registry ---
  - id: platform-project-status
    name: Permanent Project Status Registry
    area: docs/ai-framework
    description: >
      Creates docs/project-status.yaml + docs/project-status.md as the authoritative
      execution dashboard. First document every phase reads. Updated after every Complete
      phase. Eliminates full-project scans when present. Framework policies updated.
    status: complete
    dependencies:
      - ai-framework
      - ai-framework-enterprise
    required_documents:
      - docs/project-status.yaml
      - docs/project-status.md
      - docs/phase-handover/phase-af-project-status.md
      - docs/ai-framework/runtime-read-policy.md
      - docs/ai-framework/master-prompt.md
      - docs/ai-framework/development-loop.md
      - docs/ai-framework/service-snapshot-policy.md
      - docs/ai-framework/context-cache-policy.md
      - docs/ai-framework/project-index.yaml
      - docs/ai-framework/prompt-rules.md
      - docs/ai-framework/quality-gates.md
    completion_criteria:
      - project-status.yaml contains required global and per-service fields
      - Framework policies require reading project-status first
      - Project Status updated automatically after every completed phase
      - No full project scan required when file exists
      - Framework handover generated; STOP

  - id: platform-project-status-v2
    name: Project Status Execution Dashboard v2
    area: docs/ai-framework
    description: >
      Upgrades project-status to single execution dashboard with deployment_readiness,
      execution_priority, critical_path, depends_on/required_by, completion percents,
      resume_rules, automatic_update_rules. Deprecates next_recommended_phase.
    status: complete
    dependencies:
      - platform-project-status
    required_documents:
      - docs/project-status.yaml
      - docs/project-status.md
      - docs/phase-handover/phase-af-project-status-v2.md
      - docs/ai-framework/runtime-read-policy.md
      - docs/ai-framework/development-loop.md
      - docs/ai-framework/service-snapshot-policy.md
      - docs/ai-framework/quality-gates.md
      - docs/ai-framework/scripts/validate-project-status.mjs
    completion_criteria:
      - schema_version 2 with required dashboard sections
      - next_recommended_phase deprecated and not active
      - validate-project-status.mjs passes
      - Framework docs updated; STOP — no business code

  # --- Hospitality (Phase 12.0+) — Torbat Food ---
  - id: hospitality-12.0
    name: Hospitality Platform Foundation
    area: Hospitality
    description: Independent hospitality service scaffold, hospitality_db, health/capabilities, bundle licensing + feature toggles, venue/menu/table shells, permissions hospitality.*, publish-only events, tenant isolation, audit shell. Commercial product Torbat Food.
    status: complete
    dependencies:
      - onboarding-4
      - ai-framework
    required_previous_phase: ai-framework
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/architecture/adr/ADR-017.md
      - docs/hospitality-phase-12-0.md
      - docs/phase-handover/phase-12-0.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - hospitality
    completion_criteria:
      - Service scaffold under backend/services/hospitality with API → Service → Repository → Model layering
      - Alembic initial migration for foundation tables only as scoped
      - Health + capabilities endpoints; permission tree hospitality.* documented
      - Bundle definitions + tenant bundle activation + feature toggles
      - Tenant isolation + architecture + docs tests green
      - Module registry, manifests, progress, handover updated
      - Quality gates passed; no POS/kitchen/ordering engines

  - id: hospitality-12.1
    name: Digital Menu Catalog
    area: Hospitality
    description: Deep digital menu catalog — modifiers, allergens, availability windows, media refs, multi-language shells.
    status: complete
    dependencies:
      - hospitality-12.0
    required_previous_phase: hospitality-12.0
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-1.md
      - docs/phase-handover/phase-12-1.md
      - docs/ai-framework/module-template.md
    required_services:
      - hospitality
    completion_criteria:
      - Digital menu catalog APIs + validators + tests green
      - No POS / kitchen / ordering engines yet
      - Module registry, manifests, progress, handover updated
      - Quality gates passed

  - id: hospitality-12.2
    name: QR Menu & QR Ordering
    area: Hospitality
    description: QR Menu public surfaces and QR Ordering shells consuming the digital menu catalog.
    status: complete
    dependencies:
      - hospitality-12.1
    required_previous_phase: hospitality-12.1
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-2.md
      - docs/phase-handover/phase-12-2.md
      - docs/ai-framework/module-template.md
    required_services:
      - hospitality
    completion_criteria:
      - QR Menu / Ordering APIs + validators + tests green
      - No POS / kitchen engines yet

  - id: hospitality-12.3
    name: Table Service & Reservations
    area: Hospitality
    description: Reservation, table assignment, service request, and waitlist aggregates for dine-in table service workflows.
    status: complete
    dependencies:
      - hospitality-12.2
    required_previous_phase: hospitality-12.2
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-3.md
      - docs/phase-handover/phase-12-3.md
      - docs/ai-framework/module-template.md
    required_services:
      - hospitality
    completion_criteria:
      - Reservation / table assignment / service request / waitlist APIs + validators + tests green
      - No POS / kitchen / payment engines

  - id: hospitality-12.4
    name: POS Lite
    area: Hospitality
    description: Lightweight point-of-sale shell for small venue formats.
    status: complete
    dependencies:
      - hospitality-12.3
    required_previous_phase: hospitality-12.3
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-4.md
      - docs/phase-handover/phase-12-4.md
    required_services:
      - hospitality
    completion_criteria:
      - POS Lite APIs + validators + tests green

  - id: hospitality-12.5
    name: POS Pro
    area: Hospitality
    description: Full-featured point-of-sale engine for larger venue formats.
    status: complete
    dependencies:
      - hospitality-12.4
    required_previous_phase: hospitality-12.4
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-5.md
      - docs/phase-handover/phase-12-5.md
    required_services:
      - hospitality
    completion_criteria:
      - POS Pro APIs + validators + tests green

  - id: hospitality-12.6
    name: Kitchen
    area: Hospitality
    description: Kitchen display / ticket routing engine consuming POS and ordering sessions.
    status: complete
    dependencies:
      - hospitality-12.5
    required_previous_phase: hospitality-12.5
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-6.md
      - docs/phase-handover/phase-12-6.md
    required_services:
      - hospitality
    completion_criteria:
      - Kitchen ticket APIs + validators + tests green

  - id: hospitality-12.7
    name: Delivery / Accounting / CRM / Loyalty / Communication / Website Connectors
    area: Hospitality
    description: Outbound connector contracts integrating Delivery, Accounting, CRM, Loyalty, Communication, and Website Builder platforms via API/Events only.
    status: complete
    dependencies:
      - hospitality-12.6
    required_previous_phase: hospitality-12.6
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-7.md
      - docs/phase-handover/phase-12-7.md
    required_services:
      - hospitality
    completion_criteria:
      - Connector contracts + tests green; no direct DB coupling

  - id: hospitality-12.8
    name: Analytics
    area: Hospitality
    description: Analytics shells and reporting surfaces for hospitality operations.
    status: complete
    dependencies:
      - hospitality-12.7
    required_previous_phase: hospitality-12.7
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
      - docs/hospitality-phase-12-8.md
      - docs/phase-handover/phase-12-8.md
    required_services:
      - hospitality
    completion_criteria:
      - Analytics APIs + tests green

  - id: hospitality-12.9
    name: AI Assistant
    area: Hospitality
    description: AI assistant contracts for hospitality operations (optional, contract-only).
    status: planned
    dependencies:
      - hospitality-12.8
    required_previous_phase: hospitality-12.8
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
    required_services:
      - hospitality
    completion_criteria:
      - AI assistant contracts + tests green

  - id: hospitality-12.10
    name: Enterprise Validation
    area: Hospitality
    description: Final enterprise-grade validation pass across the Hospitality Platform prior to GA.
    status: planned
    dependencies:
      - hospitality-12.9
    required_previous_phase: hospitality-12.9
    required_documents:
      - docs/hospitality-roadmap.md
      - docs/phases/Hospitality/README.md
    required_services:
      - hospitality
    completion_criteria:
      - Full quality gate suite green across all Hospitality phases

  # --- Payment Platform (Phase 14.0–14.10) — Torbat Pay ---
  # Note: manifest IDs payment-14.x are distinct from beauty-business-14.x (Torbat Beauty).
  - id: payment-reg
    name: Payment Platform Registration
    area: Payment
    description: Documentation-only registration of independent payment service, payment_db, phases payment-14.0–payment-14.10, ADR-020, module/glossary/boundary updates. BYO-PSP and Torbat Pay Merchant modes. No business code.
    status: complete
    dependencies:
      - onboarding-4
      - ai-framework
    required_previous_phase: ai-framework
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/README.md
      - docs/architecture/adr/ADR-020.md
      - docs/payment-phase-pay-reg.md
      - docs/phase-handover/phase-pay-reg.md
      - docs/ai-framework/service-template.md
      - docs/ai-framework/phase-template.md
    required_services:
      - payment
    completion_criteria:
      - Service registered in service-manifest with payment_db and payment.* permissions
      - Phases payment-14.0–payment-14.10 registered in phase-manifest
      - Module registry, project index, ADR-020 updated
      - Service snapshot and handover complete
      - Progress and next-steps updated
      - No business code, models, APIs, or migrations in this phase
      - Quality gates for documentation/architecture/manifest validation passed

  - id: payment-arch
    name: Payment Architecture Prerequisites
    area: Payment
    description: Docs-only — finalize licensing (L1/L2/L3), bundle isolation, provider assignment, versioned integration contracts (PaymentIntent, Checkout, Callback, Settlement, future Refund/Split/Subscription/Wallet/Installment), service compatibility matrix, permission tree, event catalog. ADR-021. No business code; no existing service modifications.
    status: complete
    dependencies:
      - payment-reg
    required_previous_phase: payment-reg
    required_documents:
      - docs/payment-roadmap.md
      - docs/reference/payment-contracts.md
      - docs/architecture/adr/ADR-021.md
      - docs/architecture/module-boundaries.md
      - docs/reference/event-catalog.md
      - docs/reference/services-contracts.md
      - docs/phase-handover/phase-pay-arch.md
    required_services:
      - payment
    completion_criteria:
      - ADR-021 accepted; payment-contracts.md published with all v1 contract schemas
      - Compatibility verified for Core, Identity, Tenant, Accounting, CRM, Communication, Hospitality, Delivery, Sports Center, Marketplace
      - Module boundaries, event catalog, services-contracts, authorization updated
      - Roadmap and phase 14.0 doc updated with bundle/toggle/assignment prerequisites
      - Service snapshot regenerated; handover complete
      - No business code; no modifications to existing services

  - id: payment-14.0
    name: Payment Foundation
    area: Payment
    description: Independent payment service scaffold, payment_db, health/capabilities/metrics, permissions payment.*, publish-only event shells, tenant isolation, audit/config shells, PSP adapter protocol stubs only.
    implementation_priority: HIGH
    status: complete
    dependencies:
      - payment-reg
      - payment-arch
    required_previous_phase: payment-arch
    required_documents:
      - docs/payment-roadmap.md
      - docs/reference/payment-contracts.md
      - docs/phases/Payment/README.md
      - docs/phases/Payment/phase-14-0-payment-foundation.md
      - docs/architecture/adr/ADR-020.md
      - docs/architecture/adr/ADR-021.md
      - docs/phase-handover/phase-pay-arch.md
      - docs/ai-framework/service-template.md
    required_services:
      - payment
    completion_criteria:
      - Service scaffold under backend/services/payment with API → Service → Repository → Model layering
      - Alembic initial migration for foundation tables only as scoped
      - Health, capabilities, metrics endpoints; permission tree payment.* documented
      - Tenant isolation + architecture + docs tests green
      - No PSP connections, payment requests, callbacks, or ledger engines

  - id: payment-14.1
    name: PSP Management
    area: Payment
    description: BYO-PSP connections (ZarinPal, IDPay, NextPay, Pay.ir, Mellat, Parsian, Saman, …), credential vault refs, routing priority, health checks, adapter registry.
    implementation_priority: HIGH
    status: complete
    dependencies:
      - payment-14.0
    required_previous_phase: payment-14.0
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-1-psp-management.md
      - docs/architecture/adr/ADR-020.md
    required_services:
      - payment
    completion_criteria:
      - PSP connection APIs + test/suspend + routing policy + adapter stubs green
      - Secret redaction and tenant isolation tests green
      - No payment capture yet

  - id: payment-14.2
    name: Merchant Accounts
    area: Payment
    description: Torbat Pay Merchant (facilitator) sub-merchant account shells, settlement profiles, compliance refs, lifecycle.
    implementation_priority: HIGH
    status: complete
    dependencies:
      - payment-14.1
    required_previous_phase: payment-14.1
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-2-merchant-accounts.md
    required_services:
      - payment
    completion_criteria:
      - Merchant account CRUD + lifecycle APIs + tests green
      - Facilitator mode flag on workspace documented
      - No payment requests yet

  - id: payment-14.3
    name: Payment Requests
    area: Payment
    description: Idempotent payment request initiation for vertical refs; redirect/token payloads via PSP adapters.
    implementation_priority: HIGH
    status: complete
    dependencies:
      - payment-14.2
    required_previous_phase: payment-14.2
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-3-payment-requests.md
    required_services:
      - payment
    completion_criteria:
      - Payment request APIs + idempotency + state machine + mock initiate green
      - No callback verification or ledger finality yet

  - id: payment-14.4
    name: Callback & Verification
    area: Payment
    description: PSP callback ingestion, signature verification, verify API reconcile, request paid/failed transitions.
    implementation_priority: HIGH
    status: complete
    dependencies:
      - payment-14.3
    required_previous_phase: payment-14.3
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-4-callback-verification.md
    required_services:
      - payment
    completion_criteria:
      - Callback routes + verify retry + replay protection tests green
      - payment.request.paid events published

  - id: payment-14.5
    name: Transaction Ledger
    area: Payment
    description: Immutable append-only payment transaction ledger linked to verified requests — distinct from Accounting journals.
    implementation_priority: HIGH
    status: complete
    dependencies:
      - payment-14.4
    required_previous_phase: payment-14.4
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-5-transaction-ledger.md
      - docs/architecture/adr/ADR-010.md
    required_services:
      - payment
    completion_criteria:
      - Ledger immutability + transaction query APIs + tests green
      - HIGH priority MVP path 14.0–14.5 complete
      - No Accounting journal creation inside Payment

  - id: payment-14.6
    name: Refunds & Reversals
    area: Payment
    description: Full/partial refunds via PSP adapters; ledger reversal entries; Communication notify hooks.
    implementation_priority: LATER
    status: planned
    dependencies:
      - payment-14.5
      - communication-8
    required_previous_phase: payment-14.5
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-6-refunds-reversals.md
      - docs/architecture/adr/ADR-012.md
    required_services:
      - payment
      - communication
    completion_criteria:
      - Refund APIs + reversal ledger + idempotency tests green

  - id: payment-14.7
    name: Split Payments & Facilitator Settlement
    area: Payment
    description: Multi-party split allocations; settlement batch shells; marketplace/facilitator ready.
    implementation_priority: LATER
    status: planned
    dependencies:
      - payment-14.5
      - payment-14.2
    required_previous_phase: payment-14.5
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-7-split-settlement.md
    required_services:
      - payment
    completion_criteria:
      - Split rules + settlement batch intents + allocation math tests green

  - id: payment-14.8
    name: Vertical Connectors & Checkout Contracts
    area: Payment
    description: Versioned connector contracts for Hospitality, Marketplace, Sports, Experience, CRM, Healthcare, Beauty, Delivery, Automation, future services.
    implementation_priority: LATER
    status: planned
    dependencies:
      - payment-14.5
    required_previous_phase: payment-14.5
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-8-vertical-connectors.md
    required_services:
      - payment
    completion_criteria:
      - Checkout session + connector registration APIs + mock vertical connectors documented/tested

  - id: payment-14.9
    name: Reconciliation & Accounting Integration
    area: Payment
    description: PSP settlement reconciliation; Accounting posting intents via API/events only — no journal ownership.
    implementation_priority: LATER
    status: planned
    dependencies:
      - payment-14.5
      - accounting-5.11
    required_previous_phase: payment-14.5
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-9-reconciliation.md
      - docs/architecture/adr/ADR-010.md
    required_services:
      - payment
      - accounting
    completion_criteria:
      - Reconciliation run + accounting intent events; no cross-DB access; no local journals

  - id: payment-14.10
    name: Analytics, Fraud Shells & Enterprise Validation
    area: Payment
    description: Payment analytics snapshots, optional fraud rule hooks, full AI Framework validation — architecture, security, performance, docs, integration, tenant isolation, self-heal until green.
    implementation_priority: LATER
    status: planned
    dependencies:
      - payment-14.9
      - ai-framework
    required_previous_phase: payment-14.9
    required_documents:
      - docs/payment-roadmap.md
      - docs/phases/Payment/phase-14-10-enterprise-validation.md
      - docs/ai-framework/quality-gates.md
      - docs/architecture/ai-architecture.md
    required_services:
      - payment
    completion_criteria:
      - All Payment quality gates passed
      - Core flows work when fraud hooks off
      - Module registry version/phase updated; progress marks payment-14.10 complete
      - No undocumented public API/event/permission

  # Historical alias — superseded by hospitality-12.0
  - id: restaurant-foundation
    name: Restaurant / Cafe Foundation (superseded)
    area: Restaurant
    status: complete
    notes: Superseded by hospitality-12.0 (Hospitality Platform / Torbat Food). Kept for manifest continuity.
    dependencies:
      - onboarding-4
      - ai-framework
    required_documents:
      - docs/hospitality-phase-12-0.md
      - docs/phases/Restaurant/README.md
    required_services:
      - hospitality

  # --- Marketplace / Ecommerce ---
  - id: ecommerce-foundation
    name: Ecommerce Foundation
    area: Marketplace
    status: planned
    dependencies:
      - onboarding-4
      - ai-framework
    required_documents:
      - docs/phases/Marketplace/README.md
    required_services:
      - ecommerce

  - id: marketplace-foundation
    name: Marketplace Foundation
    area: Marketplace
    status: planned
    dependencies:
      - ecommerce-foundation
      - ai-framework
    required_documents:
      - docs/phases/Marketplace/README.md
    required_services:
      - marketplace

  # --- Automation ---
  - id: automation-foundation
    name: Automation Engine Foundation
    area: Automation
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/phases/Automation/README.md
      - docs/architecture/event-driven-architecture.md
    required_services:
      - automation

  # --- Academy ---
  - id: academy-foundation
    name: Academy Foundation
    area: Academy
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/phases/Future/README.md
      - docs/ai-framework/service-template.md
    required_services:
      - academy

  # --- Clinic ---
  - id: clinic-foundation
    name: Clinic / Healthcare Foundation
    area: Clinic
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/phases/Future/README.md
      - docs/ai-framework/service-template.md
    required_services:
      - clinic

  # --- Hotel ---
  - id: hotel-foundation
    name: Hotel Foundation
    area: Hotel
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/phases/Future/README.md
      - docs/ai-framework/service-template.md
    required_services:
      - hotel

  # --- Tourism ---
  - id: tourism-foundation
    name: Tourism Foundation
    area: Tourism
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/phases/Future/README.md
      - docs/ai-framework/service-template.md
    required_services:
      - tourism

  # --- Product AI ---
  - id: ai-assistant-foundation
    name: AI Assistant Foundation
    area: AI
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/architecture/ai-architecture.md
      - docs/phases/AI/README.md
      - docs/ai-framework/service-template.md
    required_services:
      - ai_assistant

  # --- Commercial Platform Foundation (docs / architecture only) ---
  - id: commercial-foundation
    name: Business Platform Foundation (Commercial)
    area: Platform
    description: >
      Docs-only commercial foundation — Business Bundle architecture, Pricing Catalog,
      Subscription/License/Entitlement contracts, Business Type catalog, rule-based
      Recommendation contracts, Activation event pipeline, Admin portal screen specs,
      canonical catalog SoT, cross-service compatibility. ADR-023. No engines, migrations,
      APIs, DB, customer portals, or future product foundations.
    status: complete
    dependencies:
      - onboarding-4
      - payment-arch
      - platform-experience-arch-freeze
      - platform-published-resource-arch
    required_documents:
      - docs/architecture/adr/ADR-023.md
      - docs/architecture/commercial-platform-architecture.md
      - docs/reference/business-bundle-contracts.md
      - docs/reference/business-bundles.md
      - docs/reference/business-bundles.catalog.yaml
      - docs/reference/pricing-catalog.md
      - docs/reference/subscription-contracts.md
      - docs/reference/license-entitlement-contracts.md
      - docs/reference/business-type-catalog.md
      - docs/reference/recommendation-contracts.md
      - docs/reference/activation-flow-contracts.md
      - docs/reference/commercial-admin-portal-spec.md
      - docs/reference/commercial-compatibility-matrix.md
      - docs/commercial-platform-foundation-report.md
      - docs/phase-handover/phase-commercial-foundation.md
      - docs/service-snapshots/commercial-foundation.yaml
    required_services:
      - core-platform
    completion_criteria:
      - ADR-023 accepted; commercial architecture + all Part 1–10 contracts published
      - Canonical bundle catalog (md + yaml); FE marked non-SoT
      - Compatibility validated for Payment, Accounting, Identity, Experience, CRM, Communication, Delivery, Hospitality, Healthcare, Sports, Loyalty
      - project-status, progress, next-steps, handover, framework snapshot updated
      - No backend/migrations/APIs/DB; no Payment 14.6+, Experience FE-11.6+, QR/Links/Booking/Marketplace/Credit
    notes: Product Integration Wave 1 UX remains; commercial truth moves to docs/YAML.

  # --- Future Services ---
  - id: future-services
    name: Future Services Portfolio
    area: Future Services
    status: planned
    dependencies:
      - ai-framework
    required_documents:
      - docs/phases/Future/README.md
      - docs/roadmap.md
    required_services: []
    notes: Catch-all for live_chat, smart_messenger, notification, file_storage, link_shortener, historical website_builder scaffold, and unlisted future modules. Prefer experience (ADR-016) for page/site work.