TorbatYar/docs/phase-handover/phase-af-discovery.md

Phase Handover — AF-Discovery (Enterprise Phase Discovery Mandate)

Field	Value
Phase ID	ai-framework-discovery
Title	Enterprise Phase Discovery Mandate
Status	Complete
Service(s)	N/A (documentation / process only)
Version	Framework discovery-1.0 (extends ADR-018)
Date	2026-07-26
ADR(s)	ADR-019 (extends ADR-018, ADR-013)

Business Analysis Summary

Item	Detail
Capabilities delivered	Mandatory pre-implementation Discovery so every phase derives complete current-phase responsibility from roadmap + architecture + boundaries + prior handover + live codebase/APIs/domain/events/permissions/aggregates/tests/docs
Explicit non-goals honored	No business feature implementation; no retrofit of completed business phases/code; no future-phase pull-forward

Enterprise Phase Discovery Summary (this docs phase)

Item	Detail
Discovery Record location	This handover + framework docs
Gaps promoted & closed	Missing Discovery process → published; loop/gates/templates updated
Exclusions	All business phases
CRUD-only rejected	Yes (process rule)

Enhancement Catalog

New normative document

Document	Purpose
enterprise-phase-discovery.md	Absolute rules, Discovery Inputs, procedure, Missing Capability Checklist, Discovery Record template, failure policy

ADR

ADR	Decision
ADR-019	Mandatory Enterprise Phase Discovery before Implementation

Core execution upgrades

Document	Enhancement
development-loop.md	Stage 1 = Enterprise Phase Discovery; completion requires closed gaps
quality-gates.md	New Enterprise Phase Discovery gate + sign-off
master-prompt.md	Discovery mandatory; AI rules inventory inputs
README.md	Lifecycle starts with Discovery; index + AF-Discovery handover
definition-of-done.md	Discovery checklist section
mandatory-phase-artifacts.md	Artifact #0 Discovery
enterprise-completeness.md	Discovery completeness dimension
phase-template.md	Full Discovery Record section
phase-handover.md	Discovery summary + Discovery completeness sign-off
prompt-rules.md · cursor-guidelines.md	Discovery automatic; Discovery Order before coding
documentation-template.md	Discovery Record required in phase docs
project-principles.md	Principle 25
docs/README.md · glossary.md · roadmap.md · next-steps.md · progress.md · module-registry.md	Cross-links
phase-manifest.yaml	Phase ai-framework-discovery Complete
ADR index	ADR-019 listed

Reusable Components

Component	Location	Reuse notes
Discovery procedure	docs/ai-framework/enterprise-phase-discovery.md	Every future phase
Missing Capability Checklist	same	Gap analysis
Discovery Record template	same + phase-template	Copy into every phase doc
Discovery quality gate	docs/ai-framework/quality-gates.md	Reviewer checklist

Public APIs

N/A — documentation/process only.

Events

N/A.

Permissions

N/A.

Extension Points

Extension point	How to extend	Forbidden uses
New Discovery input source	Add to Discovery Inputs table + ADR if architectural	Skipping Discovery
New capability class in checklist	Update checklist + DoD/completeness	Using checklist to pull future-phase products

Known Limitations

• Does not retrofit completed business phases with Discovery Records.
• Docs-only phases still require a Discovery Record against documentation/manifests (code may be N/A).
• Does not implement product features.

Migration Notes

Item	Detail
Alembic revision(s)	N/A
Upgrade steps	Next business phase must publish Discovery Record before Implementation
Breaking changes	None for runtime; process bar higher for future phases

Dependencies

Dependency	Type	Required for
ADR-018 / AF-Enterprise	Docs	Enterprise framework baseline
ADR-013 / Phase AF	Docs	Original framework

Boundary Compliance

• No foreign service ownership implemented
• No business logic duplication
• No cross-DB access
• No future-phase business functionality pulled forward

Enterprise Completeness Sign-Off

• Discovery completeness
• Business completeness (framework process)
• Architectural completeness (ADR-019)
• API completeness (N/A — docs)
• Permission completeness (N/A — docs)
• Capability completeness
• Event completeness (N/A — docs)
• Migration completeness (N/A — docs)
• Repository completeness (N/A — docs)
• Validation completeness
• Security completeness
• Performance completeness
• Documentation completeness
• Testing completeness (docs-phase validation)
• Tenant isolation (rules retained)
• Provider abstraction (rules retained)
• Integration completeness (boundary rules)
• Operational readiness (in Discovery checklist)
• Developer experience
• Maintainability
• Self Audit

Definition of Done

• Framework Discovery mandate DoD satisfied for this docs-only phase
• Applicable artifacts delivered
• CRUD-only N/A (no business CRUD)

Next Phase Entry

1. This handover + enterprise-phase-discovery.md
2. ADR-019
3. Resume business milestones per next-steps.md — Discovery runs automatically; do not restate the procedure in the phase prompt
4. Do not start a business phase from this handover unless 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	Run Discovery first; publish Discovery Record; then implement promoted gaps only

Completion Sign-Off

• Quality gates passed (documentation / architecture / cross-reference / template / manifest validation)
• Enterprise Phase Discovery gate defined and satisfied for this docs phase
• Documentation updated
• Progress / next-steps / registries / manifests updated
• No TODO for claimed deliverables
• Self audit completed
• Enterprise Completeness signed off
• Definition of Done satisfied

Related Documents

• Enterprise Phase Discovery
• AI / Enterprise Framework README
• ADR-019
• ADR-018
• Phase Handover AF-Enterprise
• Progress
• Next Steps