morteza/TorbatYar
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
0d424c500a
TorbatYar/docs/phase-handover/phase-af-project-status.md
Mortezakoohjani 0d424c500a feat(platform): complete commercial runtime consolidation 
Unify commercial runtime ownership across backend and frontend so platform, experience, and hospitality modules use the shared commercial source of truth.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-29 11:11:53 +03:30

2.2 KiB
Raw Blame History

Phase Handover — Platform Project Status Registry

Workstream: AI Development Framework (docs-only)
Phase ID: platform-project-status
Date: 2026-07-27
Status: Complete

Objective

Create a permanent project status registry that is the first document every implementation phase reads, eliminating full-project scans when present.

Delivered

Artifacts

Required fields (YAML)

  • project_version, last_updated, last_completed_phase, next_recommended_phase
  • Per-service: name, backend/frontend status, latest phases, roadmap last phase, architecture/backend/frontend/production flags, snapshot, handover, remaining phases, blockers, dependencies
  • global_statistics with service counts and completion percentages

Framework updates

  • master-prompt.md — read project-status first
  • runtime-read-policy.md — execution entry step 0 / ALWAYS READ
  • context-cache-policy.md — always reload project-status
  • development-loop.md — Discovery + Documentation Update + Completion
  • service-snapshot-policy.md — regenerate project-status after phase Complete
  • project-index.yaml — execution_order + shared_references
  • prompt-rules.md — rules for status registry
  • quality-gates.md — Project Status gate
  • README.md — reading order
  • phase-manifest.yaml — phase registered complete

Rules encoded

  1. At the beginning of every execution, read project-status.yaml first.
  2. If it exists, do not inspect unrelated services / full-project scan.
  3. Use it to determine exactly what remains.
  4. After every completed phase, update project-status.yaml (and .md) automatically.
  5. Full reconstruction only when the file is missing or invalid.

Out of scope

  • No business service code changes
  • No snapshot content regeneration beyond status registry itself
  • No next product phase implementation

Next

Superseded by phase-af-project-status-v2.md (schema v2 — critical_path / execution_priority / deployment_readiness).

STOP