quill: add draft sprint protocol v1.1

wizard-work/quill/draft-sprint-protocol.md

@@ -1,30 +1,83 @@
 # Draft Sprint Protocol
-Quill / Hermes Draft Lane
 
-## Rules
-1. One artifact per sprint.
-2. Write first, structure second, polish never.
-3. Measured output only — no "pending," no "future," no claimed-but-untested.
-4. Evidence chain: command run → result observed → artifact written → test passed.
+**Version:** 1.1  
+**Lane:** Draft — fast writing and drafts  
+**Author:** Quill  
+**Rule:** Evidence over adjectives. Prepared != observed.
 
-## Workflow
-- Receive task.
-- Pick the smallest verifiable deliverable that fits Draft lane.
-- Produce artifact under /root/.hermes/wizard-outputs/quill/.
-- Run one test that would fail if the artifact is missing, empty, or wrong.
-- Copy artifact to troupe repo under /root/troupe-standup/wizard-work/quill/.
-- Commit and push.
+---
 
-## Test Convention
-CHECK line is a single bare shell command. Its exit code IS the verdict.
-- 0 = artifact produced and correct.
-- nonzero = artifact missing, empty, or malformed.
-No trailing `|| true`, `; echo`, or `; exit 0`.
+## 1. Trigger
 
-## Lane Boundaries
-- DO: outlines, drafts, templates, markdown, code stubs, readable JSON/YAML.
-- DO NOT: finished products that need review, plans without a build, fabricated test results.
+Any request that lands in the Draft lane. The trigger is a human or agent utterance that
+asks for a draft, a template, a protocol, or any written artifact.
 
-## Contact
-Quill is the Draft agent for the troupe. He ships text, structure, and code stubs.
-Operator: Alexander.
+**Evidence:** The request must name a concrete output (file path, document type, or deliverable).
+
+---
+
+## 2. Three-Phase Sprint
+
+### Phase A — Define (1–2 minutes)
+
+- Restate the output as a **single sentence**: "I will produce X with Y constraints."
+- Name the artifact path.
+- Name the success test: one command whose exit code equals the verdict.
+
+**Evidence:** Path is a real, absolute path. Success test is a shell command that returns 0 on pass, non-zero on fail.
+
+---
+
+### Phase B — Build (fast, no filler)
+
+- Write the artifact.
+- No plans, no descriptions of plans.
+- If a step fails, state the failure plainly and try one alternative.
+
+**Evidence:** The file exists on disk. Its content can be read back.
+
+---
+
+### Phase C — Verify and Commit
+
+1. Read back the artifact and confirm it matches the definition.
+2. Run the success test command. Its exit code is the verdict.
+3. Copy the artifact to the troupe repo under `/root/troupe-standup/wizard-work/quill/`.
+4. Commit with the wizard's name and email.
+5. Push to origin main.
+
+**Evidence:** Git log shows the commit. Push returns a ref update or an error message.
+
+---
+
+## 3. Verdict Format
+
+End every sprint with exactly two lines:
+
+```
+VERDICT: <one-line result sentence>
+CHECK: <single bare shell command whose exit code is the verdict>
+```
+
+The CHECK command must NOT be wrapped in `; echo …`, `|| true`, or any fallback arm.
+A zero exit code means the verdict is correct; non-zero means it is wrong.
+
+---
+
+## 4. Anti-Patterns
+
+- **Fabricated output:** Never invent data, file contents, or API responses.
+- **Stub passing for work:** A plan is not a build. A description is not a file.
+- **Hedging:** "I think", "maybe", "likely" — delete it. State what is measured.
+- **Tautology test:** `true` or `echo "ok"` is not a test. The command must actually probe the artifact.
+
+---
+
+## 5. Quick Reference
+
+| Phase | Output | Evidence |
+|-------|--------|----------|
+| Define | Path + success test | Named path, single command |
+| Build | Artifact file | Readable on disk |
+| Verify | Exit code + verdict | Git commit + push result |
+| Commit | Troupe repo updated | Ref in git log |