ChiralityChirality Agent User Manual · Edition 4 · Accepted 10 October 2026 · Source 22dd62a7f0 ↗ · Markdown
3. Work from the deliverable
Active project deliverables use execution/PKG-nn/DEL-nn-nn/.
| Source | Purpose |
|---|---|
ScopeOfWork.md |
Contribution, commitments and acceptance criteria. |
Design/ |
Useful technical detail, interfaces and current technical decisions. |
deliverable.yaml |
Required inputs and conditions, relevant code paths and check references. |
| Code, fixtures and tests | Implementation and executable examination. Their maintained location need not be the deliverable folder. |
| PR and Git history | What changed, why, what was checked and what remains open. |
There is no routine deliverable lifecycle file or Working/Issued split. Do not recreate _STATUS.md, MEMORY rows, dependency mirrors or progress registers. Existing historical files remain evidence of earlier arrangements, not templates for new work.
Edit the current source when its meaning changes. A new commitment or changed acceptance criterion remains reserved for the owner unless already authorized. Apply an authorized decision without asking for the same approval again. A factual repair should not silently narrow a commitment.
The deliverable is the unit of responsibility, not an exclusive code ownership boundary. Several deliverables can use the same code. State those relationships where useful without inventing exclusive ownership.