docs(adr): ADR 0029 - strict-omission destruction model #211
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!211
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-207-adr-strict-omission"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Pins the destruction-safety model as a decision record: a madtea surface (MCP tool or CLI command) never carries an operation that can destroy unrecoverable work or data. Destruction is offered only when madtea machine-proves nothing is lost (content-verified prune, force-with-lease push, merged-only branch delete); refusals name the tool the user already holds (raw git, forge web UI), never a runnable madtea incantation. Includes the per-operation classification table that #208/#209 implement, and records the reversal of the one-day-old elicitation-gate design with the two findings that sank it (fail-open on non-elicitation clients; refusal text recommending the bypass).
Also scopes the ADR-citation guard to its actual audience: runtime-facing strings (errors, prompts, help bodies, tool descriptions) state their why in plain language; source code and docs may cite ADRs directly. docs/ leaves the guard's scan surface, and the new docs-only Domain.Intro seam lets a reference page name its governing ADR without the citation ever reaching the shipped help body.
Closes #207