Delivery Harness Framework / DHF Lifecycle Flow
DHF Lifecycle Flow from intake to handoff.
Use this Flow Map after the beginner guide. It shows how delivery-harness-framework selects a governance profile and routes requirements, implementation, verification evidence, review, release, and conditional recovery or handoff.
Lifecycle Flow
Flow Map
Recover / Env / Checkpoint are conditional nodes. Only governed work with a matching escalation signal runs harness_recover.py, harness_env_probe.py, or harness_checkpoint.py; light does not require those helpers.
flowchart TD
Start(["User request enters DHF"])
ProfileDecision{"Does the selected profile require governed recovery?"}
Recover["Governed matching signal only
harness_recover.py"]
Env["Governed matching signal only
harness_env_probe.py"]
Clear{"Are goal, scope,
and acceptance clear?"}
Req["Requirements
planner / req-to-dev
CONTEXT / ADR"]
Plan["Planning
vertical slice / AFK / HITL"]
Dev["Implementation
TDD / ATDD / scoped workers"]
Verify["Verification evidence
command, exit_code,
key_output, timestamp"]
Review["QA / security / review
gstack-qa / gstack-cso / gstack-review"]
Ship["Ship / deploy / canary
gstack-ship / land-and-deploy"]
Docs["Docs release
document-release / doc-updater"]
Handoff["Governed matching signal only
harness_checkpoint.py append"]
Done(["DHF output
route, evidence, next safe task"])
Start --> ProfileDecision
ProfileDecision -- "governed matching signal" --> Recover --> Env --> Clear
ProfileDecision -- "light/standard skip Recover / Env" --> Clear
Clear -- "No" --> Req --> Plan
Clear -- "Yes" --> Plan
Plan --> Dev --> Verify
Verify --> Review --> Ship --> Docs --> Handoff --> Done
Verify --> Handoff
classDef runtime fill:#e9f7f5,stroke:#0f9b8e,color:#17241f;
classDef decision fill:#f0eaff,stroke:#8a4fff,color:#17241f;
classDef build fill:#fbf0dc,stroke:#b26a00,color:#17241f;
classDef verify fill:#eaf6f0,stroke:#12805c,color:#17241f;
classDef ship fill:#faeaf1,stroke:#d13574,color:#17241f;
class Recover,Env,Handoff runtime;
class Clear decision;
class Req,Plan,Dev build;
class Verify,Review,Docs verify;
class Ship ship;
How to read it
Use the map as a gate, not a poster.
1. Recover when escalatedRun full recovery only for a matching governed signal; otherwise read the narrowest task sources.
2. Lock scopeIf acceptance is unclear, route to requirements before planning.
3. Build in slicesDevelopment starts only after the lifecycle stage and owner are clear.
4. Prove; hand off when escalatedVerification is required for artifact claims; checkpoint handoff remains signal-conditional.
Next