Delivery Harness Framework / DHF Public Guide
From ambiguous requests
to verifiable delivery.
DHF gives agents the right, fresh, authorized context at the right delivery stage, then closes the work with checkable evidence.
Core Context Supply Chain
Give information only when the work needs it
Start with this simplified flow to see how information enters a task. Open Context Engineering for the full rules and mappings.
- Trusted SourcesStart from durable, attributable facts.
- Session BearingRecover stage, ownership, and the next safe task.
- Just-in-time ShapingLoad only what the current risk and stage require.
- Permission DecisionTurn phase, scope, and authority into allow or block.
- Execution FeedbackRecord what actually happened.
- Checkpoint / RecoveryPreserve a trustworthy restart point.
Learn the Framework
Follow the system in five steps
Start with purpose, remember the system, then understand context, lifecycle timing, and permission.
Choose by Goal
Take the shortest useful path
Each path contains only the pages needed for that goal.
I am learning DHF for the first timeUnderstand the purpose and conceptual model.
I am integrating DHF into an engineering workflowFollow the lifecycle, permission rules, and operational owner.
I am checking implementation status and evidenceKeep source, runtime, publication, and enforcement separate.
Status Boundary
One proof surface, four independent states
Architecture Status owns current dates, parity evidence, publication status, and adoption evidence. Concept pages link to it instead of copying proof.
Independent State
Repository source
What the tracked implementation contains.
Independent State
Local runtime
What fresh parity evidence proves active.
Independent State
Public documentation
What readers can reach on the site.
Independent State
Production enforcement
What production evidence proves enforced.