Section 5
Understand the development route
The human manual describes a six-part route: conceptual work, FEED, 30%, 60%, 90%, and 100% delivery. These names explain how the character of the work changes. They are not arithmetic measurements, automatic software statuses, or a requirement to restart every phase when maintaining an established project. Enter the verified current position and reopen only decisions whose basis or consequences have changed. Human manual §§1.7, 4.12, 5.11–6 · Root entry
| Phase in the explanatory route | Work emphasized | Useful basis for the next undertaking |
|---|---|---|
| Conceptual | Align intent, understand the product, identify constraints, develop the PRD or appropriate basis document. | Identified accepted direction, clear unresolved questions, and a usable basis for division. |
| FEED | Decompose accepted scope and prepare the project workspace and production contracts. | Stable identities, scope coverage, usable deliverable definitions, and declared coordination. |
| Work toward 30% | Establish the means of execution, declare dependencies, examine coupling, resolve ordering, and construct the first usable objective-relative DAG. | The accepted graph basis, resolved or explicitly held coupling, and an executable route. |
| Work toward 60% | Develop technical details and interfaces through local undertakings; revise the project graph when warranted by scope/decomposition change. | A clearer route to completion with sufficiently developed relationships and recorded design decisions. |
| Work toward 90% | Carry the details into produced deliverables over longer horizons, integrate, reconcile, verify, and account for residual work. | An identified candidate and evidence for concentrated product examination. |
| After 90%, toward 100% and delivery | Move from produced deliverables into concentrated product examination and debugging, then into the organization's 100% publication/delivery pipeline. Testing has also occurred throughout earlier development. | Delivered identity, continuing obligations, recipient information, and the applicable human acts. |
This table is an explanation of the human manual, not a new gate definition. A real project can have uneven maturity: one interface may be settled while another Package still needs design. Do not force all deliverables into the same maturity claim or assume that closing a local undertaking advances the project. Stage gates remain human-managed milestones under the project's own records. SPEC §3.3 · TYPES §5.2
Deliverable lifecycle is a separate axis. The shared sequence is OPEN → INITIALIZED → SEMANTIC_READY → IN_PROGRESS → CHECKING → ISSUED, with the semantic step optional where inapplicable. The state says which production and change-control regime applies; it does not report “60% complete.” Read _STATUS.md and the adopted transition rules, including any project-specific semantics. SPEC §3
Where the revised concordance lifecycle is adopted, IN_PROGRESS remains the honest state while any production obligation is unfulfilled, including one needing a human decision. Entry to CHECKING requires current candidate-bound evidence accounting for all applicable production obligations in the proposed checking scope, a candidate-specific checking basis, and the human declaration freezing the candidate. Compare the Scope of Work, actual outputs, dependencies and required production verification. Closing known graph nodes or deleting a list cannot prove coverage; no separate Remaining list is required. Planned formal review is distinct from unfinished production examination. Earlier pinned Remaining-based criteria continue until their owning adoption. During checking, append evidence to review/run records; required corrections follow the prescribed reversal, and ISSUED changes use governed scope change. SPEC §3.4 · Concordance §4
The practical distinction matters in reports. “Implementation and focused regression checks complete; native recovery witness remains” is a useful assignment result. It is not a declaration that the deliverable is ready for checking. “The PR merged” identifies source integration. It is not professional acceptance or publication. “The graph is complete” concerns the graph's stated undertaking and conditions. Its scope may be much smaller than a project milestone. Chirality change conventions · Construct a local work graph
Delivery likewise follows an actual arrangement, not a universal invented final workflow. Identify the recipient, delivered version, accepted scope, required packaging or transmittal, verification, operational responsibilities, and remaining obligations from the project. Prepare the package before seeking the reserved release or acceptance act. Preserve a prior authorized release as history without inferring authority for another. Human manual, chapter 6 · App development boundaries · Root entry