TorbatYar/docs/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

133 lines
5.5 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Project Status — TorbatYar Single Execution Dashboard (v2)
**Authoritative machine file:** [`project-status.yaml`](project-status.yaml)
This is the **first document** every AI implementation run must read. When it exists, agents must **not** full-scan the repository or inspect unrelated services.
| Field | Value |
| --- | --- |
| Schema | **2** |
| Project version | `0.14.9-hospitality-frontend-production-validation` |
| Last updated | 2026-07-28 |
| Last completed phase | `hospitality-frontend-production-validation` |
**Commercial foundation:** **ARCHITECTURE COMPLETE** (`commercial.v1.2`).
**Commercial runtime FE:** **CERTIFIED**.
**Commercial runtime backend:** **COMPLETE**.
**Commercial runtime adoption:** **ADOPTED**.
**Commercial cleanup:** **CERTIFIED** / **SOLE_SOT** — score **98** — Remaining Legacy **0** — [certification](commercial-runtime-final-certification.md).
**Platform UX:** **CERTIFIED_PRODUCTION_UX** — score **98**.
**Hospitality FE:** **CERTIFIED** — score **98** — [certification](hospitality-final-certification.md) · [validation](hospitality-production-validation.md).
**Next remaining (critical path):** Payment Backend MVP `14.614.10` · Hospitality backend `12.9`/`12.10` · Experience FE `11.6+`.
**Deprecated:** `next_recommended_phase` → replaced by `execution_priority` + `critical_path` + `deployment_readiness`.
---
## Resume rules (every execution)
1. Read `docs/project-status.yaml` **FIRST**.
2. Never inspect unrelated services.
3. Never scan the repository for completed work.
4. Determine remaining work **exclusively** from this file.
5. Load only documents required by [Runtime Read Policy](ai-framework/runtime-read-policy.md) for the active service.
6. Execute higher `execution_priority` before lower.
7. Follow `critical_path` order for commercial-release sequencing.
---
## Critical path (first commercial release)
Ordered remaining milestones:
1. **Payment Backend MVP**`payment-14.6``payment-14.10`
2. **Payment Frontend**
3. **Experience Frontend** — Publish Registry `experience-fe-11.6+`
4. **Restaurant Production**`hospitality-12.9``12.10`
5. **Driver Production**`delivery-10.2``10.10`
6. **Medical Booking**
7. **Booking**
8. **Short Links**
9. **QR**
10. **Digital Card**
---
## Execution priority
| Bucket | Phases |
| --- | --- |
| **critical** | `payment-14.6``14.10`, `payment-frontend`, `hospitality-12.9``12.10` |
| **high** | `delivery-10.2``10.10`, `experience-fe-11.6`, `communication-frontend-complete` |
| **medium** | `loyalty-7.7``7.10`, `sports-center-9.8``9.10`, `accounting-5.12` |
| **low** | Identity / CRM / Healthcare / Beauty frontend polish |
| **future** | Ecommerce, Marketplace, Automation, Academy, Clinic, Hotel, Tourism, AI, SMS Panel, Short Links, QR, Digital Card, Booking, Notification, File Storage, Live Chat, Messenger |
---
## Global statistics
| Metric | Value |
| --- | --- |
| Number of services | 27 |
| Completed services | 6 |
| In progress | 7 |
| Planned / scaffolded | 14 |
| Backend completion | ~48% |
| Frontend completion | ~22% |
| Overall completion | ~35% |
| Critical path remaining | 10 |
---
## Deployment readiness
Official indicator per service:
```yaml
deployment_readiness:
backend: NOT_STARTED | IN_PROGRESS | COMPLETE
frontend: NOT_STARTED | IN_PROGRESS | COMPLETE
database: NOT_STARTED | IN_PROGRESS | COMPLETE
api: NOT_STARTED | IN_PROGRESS | COMPLETE
tests: NOT_STARTED | IN_PROGRESS | COMPLETE
documentation: NOT_STARTED | IN_PROGRESS | COMPLETE
production_ready: NOT_STARTED | IN_PROGRESS | COMPLETE
```
---
## Service completion (canonical)
| Service | Completed | Remaining | BE% | FE% | Overall% | Prod ready |
| --- | --- | --- | --- | --- | --- | --- |
| Core | onboarding-4 | — | 100 | 100 | 100 | COMPLETE |
| Identity | identity-2 | FE polish | 100 | 70 | 85 | COMPLETE |
| Accounting | 5.11 | 5.12 | 92 | 40 | 66 | IN_PROGRESS |
| CRM | 6.3 | FE polish | 100 | 55 | 78 | COMPLETE |
| Loyalty | 7.6 | 7.77.10 | 60 | 0 | 30 | IN_PROGRESS |
| Communication | 8 | FE complete | 100 | 65 | 82 | COMPLETE |
| Sports Center | 9.7 | 9.89.10 | 70 | 0 | 35 | IN_PROGRESS |
| Delivery | 10.1 | 10.210.10 | 18 | 25 | 22 | IN_PROGRESS |
| Experience | FE-11.5 | FE-11.6+ | 100 | 83 | 92 | IN_PROGRESS |
| Hospitality | 12.8 | 12.912.10 | 80 | 100 | 90 | FE READY / BE IN_PROGRESS |
| Healthcare | 13-7 | FE polish | 100 | 55 | 78 | COMPLETE |
| Beauty | 14-7 | FE polish | 100 | 55 | 78 | COMPLETE |
| Payment | 14.5 | 14.614.10 + FE | 50 | 0 | 25 | IN_PROGRESS |
| Future products | — | foundations | 05 | 0 | 02 | NOT_STARTED |
## Dependency graph
Use `depends_on` / `required_by` on each service row — do not derive by scanning code.
## Automatic updates
After every Complete phase, update: completed/remaining phases, deployment readiness, percentages, critical path, execution priorities, service completion, timestamps. No manual editing when following the Documentation Update stage.
## Framework refs
[Runtime Read Policy](ai-framework/runtime-read-policy.md) · [Context Cache](ai-framework/context-cache-policy.md) · [Service Snapshot](ai-framework/service-snapshot-policy.md) · [Development Loop](ai-framework/development-loop.md) · [Master Prompt](ai-framework/master-prompt.md)
Handover: [phase-af-project-status-v2.md](phase-handover/phase-af-project-status-v2.md)