Intent starts as a spec
A registered specification gives planning a durable source of truth. It captures the desired outcome and constraints before the task becomes an implementation request.
Answer page
What a Human-Agent-Contract looks like in a real repository
A Human-Agent-Contract is a chain of versioned repository artifacts from intent through validation evidence and acceptance.
Direct answer
In a real repository, a Human-Agent-Contract is not a policy document. It is the linked set of files that states intent, scoped work, validation, changed paths, and acceptance: a spec, planning artifacts, task definition, implementation summary, and reconciliation.
Practical guidance
Make the next review decision easier.
A task makes the boundary operational
The task definition names the objective, target paths, and validation. It gives a coding agent a clear contract while leaving human judgment available for ambiguity.
Evidence closes the loop
The implementation summary and reconciliation show what happened and whether acceptance criteria are met. Those artifacts support code review, handoff, and future changes.
Verified demo evidence
A public CLI result, not a completion claim.
This command and result are from the website’s checked-in synthetic repository demo. Substitute your own repository paths and validation command when you apply the workflow.
$ day-shift reconciliation build --milestone-overview <milestone-overview>
reconciliation_status: completedAuthorship and sources
Trace this guidance to maintained product evidence.
- Maintainer
- Tianna McCoy ↗Day Shift maintainer; responsible for the repository-native workflow and release evidence referenced here.
- Last updated
- Tested Day Shift
- v0.1.24
Keep exploring
Follow the next question, not a generic funnel.
What Is a Human-Agent-Contract?
Plain-language explanation of the Human-Agent-Contract: explicit intent, scope, validation, evidence, and reconciliation for coding-agent work.
Read nextDay Shift with Codex or Claude Code
What belongs in versioned repository artifacts when coding assistants do the implementation work.
Read nextA Practical Coding-Agent Handoff Checklist
A practical checklist for handing work to a coding agent and receiving reviewable implementation evidence back.
Read nextFind your answer
Have we answered your question?
Search the answer pages, concept, comparisons, demo, and FAQ without leaving the site.
Search by a problem, workflow step, or tool boundary.