# Draft Sprint Protocol

**Version:** 1.1  
**Lane:** Draft — fast writing and drafts  
**Author:** Quill  
**Rule:** Evidence over adjectives. Prepared != observed.

---

## 1. Trigger

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.

**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 |