Engineering Lifecycle at a Glance¶
Purpose¶
This page explains how the Engineering Stages fit together.
The stages are not paperwork. They are a sequence of engineering questions that progressively reduce uncertainty and produce evidence.
Lifecycle phases¶
Orientation
ES-100 prepares the team to use the platform, understand the journey, and recognize readiness gates.
Framing
ES-101–ES-103 define the vision, requirements, constraints, planning assumptions, work breakdown, and risks.
Architecture and Design
ES-104–ES-106 establish architecture, detailed design, guardrails, implementation readiness, and verification expectations.
Construction and Verification
ES-107–ES-110 guide AI-assisted implementation, code review, integration, testing, verification, and release readiness.
Operations
ES-111–ES-113 prepare operation, deploy within approved scope, monitor behavior, and preserve operational evidence.
Learning and Stewardship
ES-114 converts operational evidence into lessons, backlog items, ownership, and next-cycle direction.
Stage flow¶
ES-100 Orientation
↓
ES-101 Vision and Problem Definition
↓
ES-102 Requirements and Constraints
↓
ES-103 Planning and Work Breakdown
↓
ES-104 Architecture and Technical Approach
↓
ES-105 Detailed Design
↓
ES-106 Implementation Readiness
↓
ES-107 AI-Assisted Implementation
↓
ES-108 Code Review and Integration
↓
ES-109 Testing and Verification
↓
ES-110 Release Readiness
↓
ES-111 Operational Readiness
↓
ES-112 Deployment and Transition
↓
ES-113 Operations and Monitoring
↓
ES-114 Post-Release Learning and Stewardship
↓
Next Engineering Cycle
What moves forward¶
Every stage produces evidence that becomes input to later stages. In a cloned Starter Kit project, that evidence should be stored in docs/project-workspace/.
| Earlier Evidence | Later Use |
|---|---|
| Vision evidence | Requirements, planning, release scope |
| Requirements evidence | Architecture, design, tests, release judgment |
| Architecture evidence | Design, implementation, guardrails |
| Testing evidence | Release readiness |
| Deployment evidence | Operations and monitoring |
| Monitoring evidence | Stewardship and next cycle |
Evidence location¶
The Engineering Stages explain the work. The project workspace stores the evidence.
docs/engineering/ stage guidance
docs/template-library/ reusable templates
docs/examples/ reference examples
docs/project-workspace/ completed project evidence
Do not treat the lifecycle as a checklist to finish quickly. The goal is better engineering judgment, not faster paperwork.
The lifecycle is a confidence-building system: each stage makes later decisions less speculative.