docs: ADR-003 contribution governance + ADR-004 tabula rasa documentation#143
docs: ADR-003 contribution governance + ADR-004 tabula rasa documentation#143scottschreckengaust wants to merge 3 commits into
Conversation
scottschreckengaust
force-pushed
the
feat/bootstrap-adr
branch
from
0174e2a to
010786e
Compare
…tion ADR-003 defines how agents/humans pick up, own, and deliver work: priority evaluation, predecessor validation, cross-reference audit, self-assignment, and issue body as source of truth. ADR-004 defines the documentation standard: zero-context self-sufficiency, progressive disclosure, international English, testable instructions, and the tabula rasa quality test. Refs #134, #135 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
scottschreckengaust
force-pushed
the
feat/adr-003-004
branch
from
daf33f1 to
744492d
Compare
|
|
||
| ### Issue quality bar | ||
|
|
||
| An issue is "ready for work" when a contributor can read the body alone — without comments, related issues, or clarifying questions — and know exactly what to build. |
There was a problem hiding this comment.
should it be "without comments"?
There was a problem hiding this comment.
...or related issues, or replies to clarifying questions?
There was a problem hiding this comment.
Addressed in 6b724e6 — rewrote this section. The body is now described as the "primary directive" rather than exclusively sufficient. Comments, replies, predecessors, and downstream goals all contribute context. The reviewer's job before implementation is to synthesize these sources and surface inconsistencies.
|
|
||
| ### Work-in-progress discipline | ||
|
|
||
| Provide progress signals at checkpoints. If blocked or abandoning, comment and unassign. Do not start multiple issues simultaneously unless explicitly parallelizable. |
There was a problem hiding this comment.
Would serializable work count also due to contextual significance?
There was a problem hiding this comment.
Addressed in 6b724e6 — expanded to allow "serializable work with declared ordering (where context from one directly informs the next)." This covers the case where tasks are technically parallelizable but benefit from sequential execution due to contextual significance.
Address review feedback: - Issue quality bar: body is primary directive, not exclusively sufficient — comments, predecessors, downstream goals all add context - Issue body section: renamed from "source of truth" to "primary directive"; reviewer synthesizes threads with body before implementation - Pre-start review: adds context synthesis step (predecessors, adjacent state, forward-look into downstream) - Work-in-progress: allows serializable work with declared ordering Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 participant
Stack position
PR 3 of 4 for #145 — ADR governance framework
Prior (PR 2 / #133): ADR-002 least-privilege bootstrap decision record
This PR: ADR-003 (governance) + ADR-004 (documentation standard) — the two process foundations
Remaining: ADR-005 through ADR-011 (feedback loop, feature flags, knowledge acquisition, DoD, security posture, error recovery, conflict resolution)
Summary
Two foundational ADRs that everything else depends on:
ADR-003 — Contribution governance:
ADR-004 — Tabula rasa documentation:
Changes
docs/decisions/003-contribution-governance.mddocs/decisions/004-tabula-rasa-documentation.mddocs/src/content/docs/decisions/003-*.mddocs/src/content/docs/decisions/004-*.mdTest plan
astro check— 0 errorsCloses #134
Closes #135
🤖 Generated with Claude Code