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>
3.3 KiB
ADR-019: Mandatory Enterprise Phase Discovery
| Field | Value |
|---|---|
| Status | Accepted |
| Date | 2026-07-26 |
| Deciders | Platform Architecture |
| Supersedes | — |
| Superseded by | — |
| Extends | ADR-018, ADR-013 |
Context
ADR-018 made enterprise production readiness the default via Definition of Done, mandatory artifacts, completeness verification, and boundary rules. Agents could still begin implementation from a thin phase brief and under-derive scope—shipping CRUD-shaped work while missing policies, events, list UX, ops surfaces, or other current-phase responsibilities that already existed partially in the codebase or roadmap.
The Framework needs an explicit, mandatory Enterprise Phase Discovery stage that inspects roadmap, architecture, boundaries, prior handover, and the live codebase/APIs/domain/events/permissions/tests/docs before coding, then promotes every missing current-phase production capability into Scope.
This ADR does not implement business features and does not retrofit completed business phases.
Decision
- Adopt Enterprise Phase Discovery as a mandatory stage before Implementation for every phase.
- Discovery MUST use the full input set: Current Roadmap, Current Architecture, Service Boundaries, Previous Phase Handover, Existing Codebase, Existing APIs, Existing Domain Model, Existing Events, Existing Permissions, Existing Aggregates, Existing Tests, Existing Documentation.
- Discovery MUST derive every missing production-ready capability for the current phase and MUST NOT assume CRUD is sufficient.
- Missing current-phase capabilities automatically become implementation work before Complete.
- Discovery MUST NOT pull future-phase responsibilities, violate service boundaries, or duplicate another service.
- A Discovery Record is required in the phase document; quality gates and Definition of Done fail without it (implementation phases).
- Framework loop, gates, templates, master prompt, and Cursor guidelines are updated accordingly.
Consequences
Positive
- Phase responsibility is evidence-based (docs + code), not prompt-guessed
- Gaps are closed inside the phase instead of deferred as TODOs
- Boundary and anti-duplication checks happen before code is written
Negative
- Slightly longer pre-implementation analysis (intentional)
Neutral
- Docs-only phases still produce a Discovery Record against documentation/manifests
- ADR-013 and ADR-018 remain Accepted; this ADR extends them
Alternatives Considered
- Rely only on mandatory-artifact checklists without codebase inventory — rejected (misses drift vs existing code)
- Optional discovery “when unclear” — rejected (agents skip under time pressure)
- Expand every phase prompt with full discovery instructions — rejected (framework is single source of truth)