5c6a2e78cf
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>
6.3 KiB
6.3 KiB
Phase Handover — AF-Runtime-Read-Policy (Runtime Read Policy Integration)
| Field | Value |
|---|---|
| Phase ID | ai-framework-runtime-read-policy |
| Title | Runtime Read Policy Integration |
| Status | Complete |
| Service(s) | N/A (documentation / process only) |
| Version | Framework runtime-read-1.0 |
| Date | 2026-07-26 |
| ADR(s) | Extends ADR-018, ADR-019 (process; no new ADR) |
Business Analysis Summary
| Item | Detail |
|---|---|
| Capabilities delivered | Authoritative tiered document-loading policy; framework stages defer to Runtime Read Policy instead of unconditional bulk reads |
| Explicit non-goals honored | No business service changes; no completed business phase retrofits; no relocation of docs/ai-framework/ |
Enterprise Phase Discovery Summary (this docs phase)
| Item | Detail |
|---|---|
| Discovery Record location | This handover + runtime-read-policy.md |
| Gaps promoted & closed | Unconditional “read all …” instructions in loop/master-prompt/Discovery → replaced with policy tiers and triggers |
| Exclusions | All business phases and services |
| CRUD-only rejected | N/A (process rule) |
Enhancement Catalog
Authoritative policy document
| Document | Purpose |
|---|---|
| runtime-read-policy.md | ALWAYS READ · READ ONCE PER SERVICE · READ ONLY IF REFERENCED · NEVER AUTO READ; additional load triggers; Discovery input mapping; backward compatibility |
Core execution upgrades
| Document | Enhancement |
|---|---|
| master-prompt.md | Document-loading authority statement; AI rules use policy instead of “read framework + architecture + phase docs” |
| development-loop.md | Stage 1 and Architecture Validation use tiered loading; testing-strategy loaded when referenced |
| enterprise-phase-discovery.md | Discovery Inputs table with load tiers; procedure step 1 uses policy mapping |
Reusable Components
| Component | Location | Reuse notes |
|---|---|---|
| Runtime Read Policy | docs/ai-framework/runtime-read-policy.md |
Every future phase and framework change |
| Discovery input → tier mapping | Same + enterprise-phase-discovery.md | Discovery without bulk reads |
| Additional load triggers | runtime-read-policy.md | Manifest, handover, phase, validation-driven loads |
Public APIs
N/A — documentation/process only.
Events
N/A.
Permissions
N/A.
Extension Points
| Extension point | How to extend | Forbidden uses |
|---|---|---|
| New ALWAYS READ doc | Add to policy + cross-link from loop/master-prompt if normative | Bulk-reading whole directories |
| New Discovery input | Add row with load tier in Discovery + policy mapping | Auto-reading other services’ roadmaps/handovers |
Known Limitations
- Does not retrofit completed business phase prompts or handovers with new load lists.
- Legacy docs outside the three updated files may still contain “read all …” wording; runtime-read-policy.md supersedes those instructions.
- Frontend docs remain out of scope unless the phase scopes frontend work.
Migration Notes
| Item | Detail |
|---|---|
| Alembic revision(s) | N/A |
| Upgrade steps | Agents follow runtime-read-policy.md on next phase entry |
| Breaking changes | None for runtime; reduced default doc fan-out for future phases |
Dependencies
| Dependency | Type | Required for |
|---|---|---|
| AF-Discovery / ADR-019 | Docs | Enterprise Phase Discovery baseline |
| AF-Enterprise / ADR-018 | Docs | Enterprise framework baseline |
Boundary Compliance
- No foreign service ownership implemented
- No business logic duplication
- No cross-DB access
- No future-phase business functionality pulled forward
- No business service code modified
Enterprise Completeness Sign-Off
- Discovery completeness (policy mapping for Discovery inputs)
- Business completeness (framework process)
- Architectural completeness (policy preserves boundary/ADR-on-demand loading)
- Documentation completeness
- Self Audit
Definition of Done
- Runtime Read Policy published as authoritative loader
- master-prompt.md, development-loop.md, enterprise-phase-discovery.md updated
- Backward compatibility documented
- Framework handover complete
- No business code changes
Next Phase Entry
- runtime-read-policy.md — load tiers before any other non-triggered docs
- master-prompt.md · development-loop.md · enterprise-phase-discovery.md
- Prior framework handovers remain valid; load only the latest handover for the current service per policy
- Resume business milestones per next-steps.md when explicitly requested
| Field | Value |
|---|---|
| Recommended next phase | Per next-steps.md (business track) — not started by this phase |
| Blockers for next phase | None from this upgrade |
| Entry checklist | ALWAYS READ tier → READ ONCE PER SERVICE → Discovery with policy mapping → implement promoted gaps only |
Completion Sign-Off
- Runtime Read Policy integrated into master-prompt, development-loop, enterprise-phase-discovery
- Unconditional bulk-read instructions replaced in updated framework docs
- Framework handover complete
- No TODO for claimed deliverables
- No business service modifications