P0007 (accept + execute): spec DoD convention — 5–7 agent-observable behaviors

[klappy]

What this PR does

Combined acceptance + execution of promotion P0007 — adds a spec-shape constraint to Definition of Done.

Acceptance (1 file)

• docs/promotions/P0007-dod-as-agent-observable-behaviors.md
  • promotion_status: proposed → accepted
  • Tags array "proposed" → "accepted"
  • Status section header → accepted (2026-05-05)
  • Review Notes filled

Execution (1 file, +37 lines)

• canon/constraints/definition-of-done.md — new section before the project-status marker ## ✅ Status:
  • ## Spec DoD Convention — Agent-Observable Behaviors
  • Format constraint: 5–7 entries in the form "<consumer> can <action> and observe <outcome>"
  • Allowed examples (consumer-observable)
  • Disallowed examples (implementation milestones — SessionDO class lands at..., wrangler.toml updated..., All tests pass)
  • Failure mode: spec readers don't know what they get; fresh-validators can't verify
  • Receipt: PTXprint v1.2 §9 with PR Add Anti-Cache Lying constraint and content-addressed storage implementation #30 validator confirmation

How this complements P0001

	Runtime	Spec
P0001	Completion claims need artifacts	—
P0007	—	DoD must be expressed in observable terms so artifacts can verify it

Both touch canon/constraints/definition-of-done.md but at different locations (P0001 → ## Operating Constraints + ## Failure Modes; P0007 → new appended section). They auto-merge cleanly regardless of merge order.

Position in the 8-proposal sweep

#	ID	Status
1	P0009	PR #167
2	P0001	PR #168
3	P0008	PR #169
4	P0007	this PR
5	P0006	next — vodka boundary enumeration
6-8	P0003, P0004, P0005	queued (these create new docs, larger surface)

DoD

• Proposal frontmatter promotion_status flipped
• Review Notes filled
• Canon edit text matches P0007 §"Proposed Language" verbatim
• Insertion placed in a sensible location (before the project-status marker)
• No other canon docs touched

---

Note

Low Risk
Low risk: documentation-only updates that clarify spec-writing conventions without changing runtime behavior or requiring migration.

Overview
Introduces a new Spec DoD convention in canon/constraints/definition-of-done.md requiring spec Definition of Done sections to be phrased as 5–7 consumer/agent-observable behaviors (with a fixed sentence format, allowed/disallowed examples, and rationale/receipts).

Updates docs/promotions/P0007-dod-as-agent-observable-behaviors.md to accepted status (tags/frontmatter), and fills in the acceptance record (date and reviewer decision).

^{Reviewed by Cursor Bugbot for commit 49d9ba0. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

Canon Quality — oddkit_audit ✅

No dead klappy:// references or legacy link patterns found in writings/. 39 files scanned.

_{Spec: klappy://docs/oddkit/specs/oddkit-audit · Workflow: .github/workflows/canon-quality.yml · Run: #41}