contract-bound-deliverables

Topics in the source

• Contract-bound deliverables
• 0. Pre-flight: find the owning project, and check who else is writing in it
• 1. Read the acceptance rule before writing a word
• 2. Freeze an evidence packet — one file, the only permitted input
• 3. Draft in parallel from that packet, judge by discipline
• 3b. Adding a model that is not in the frozen registry
• 4. Assemble to the number; never re-prompt for it
• 5. Verify with the contract's own metric, then independently

Use when a brief specifies measurable acceptance — a character/word budget, a citation discipline, a required section numbering — rather than "write something good". The spine is: fix the evidence first, draft in parallel against it, assemble to the number, verify with the contract's own wording, then publish cleanly. Locate the project that already owns the topic before creating one. Search the target repo/workspace for an existing project on the same topic (search on topic keywords, recent commit history, the repo's index/registry) and read its README and plan. Building a parallel tree in a scratch workspace for work a governed repo already owns produces a duplicate that cannot merge cleanly and wastes the entire round. Check for a concurrent writer before editing a shared project. Another agent session may be editing the same files right now. Detect it with find -type f -newermt '-${DELIVERABLEWRITERWINDOWMINUTES:-10} minutes' (files touched during your session that you did not touch) and git status -s (untracked files appearing mid-session that you did not create). A file whose mtime moved but that git status reports clean was rewritten with identical bytes — still evidence of

This is an excerpt. Refer to the complete source and its current requirements.