Repository navigation
Reserve graveyard and enforce disposition-bearing retirement #28
Description
Activity
🔗 Related PRs
#1 - [codex] refresh METHOD signposts and legend structure [merged]
#5 - Shape release workflow and user migration docs [merged]
#18 - Land 0030-0033 repo-truth and MCP debt fixes [merged]
#20 - Add backlog notes for agent-first planning and review workflow [merged]
#21 - Align test taxonomy fixtures with live legends [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Migrated from Method backlog
This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.
Source backlog:
docs/method/backlog/bad-code/PROCESS_reserve-graveyard-and-enforce-retirement-disposition.mdOriginal lane:
bad-codeOriginal legend:
PROCESSOriginal priority:
highOriginal backlog card
Reserve graveyard and enforce disposition-bearing retirement
Source:
docs/audits/004-graveyard-lifecycle-semantics-audit.mdMETHOD currently lets
graveyardact like a live backlog lane in somesurfaces, while docs also say graveyard entries can include work
"completed indirectly by a broader cycle." This blurs completion and
retirement and can train agents to move completed cards into graveyard.
Fix the docs and tool validation so completed work is represented by a
closed cycle packet, while graveyard movement is reserved for explicit
retirement with a disposition tombstone.
Problem
docs/method/graveyard/README.mdsays a backlog item can enter thegraveyard when it was completed indirectly by a broader cycle.
graveyardis accepted by lane normalization as a live backlog lane.method backlog move --to graveyard, MCPmethod_backlog_move, andGitHub closed-issue sync can move backlog items without the
disposition contract enforced by
method retire.Desired Outcome
done. The completion artifact is the retro and witness packet.
no-longer-live proposals.
original proposal under a tombstone.