cad-context: ADR-worthiness test as a decision-promotion filter #26
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence#26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Source: skills-analysis session, 2026-07-18 (comparison against Matt Pocock's
domain-modeling).cad-contextrecords phase decisions (D-01,D-02, …) and carries them forward / resurfaces them via builtin recall. But every decision is treated equally — there's no filter separating load-bearing decisions from throwaway ones, so recall competes trivial and durable decisions for attention.Borrow the sharp three-part ADR-worthiness test as a promotion criterion (NOT a new ADR artifact tree):
A decision is durable when all three hold:
Approach:
cadence-core/workflows/context.md: mark decisions that pass all three as durable/carried-forward; the rest stay phase-local.docs/adr/tree, no glossary/ubiquitous-language import (Cadence'sCONTEXT.mdis already a decisions+criteria doc, not a glossary — different artifact, same filename; don't collide).Benefit: the decisions worth remembering resurface when relevant; trivial ones don't clutter recall. Cheapest item in the v1.2.0 scope.
Scoped for v1.2.0.
Delivered in v1.2.0 (DEC-01).
cad-contextnow marks a decision durable only when it passes a three-part filter (hard-to-reverse, surprising-without-context, and the result of a real trade-off). Durable decisions are written under a## Durable decisionsheading and resurface via recall; phase-local decisions stay under## Decisions, and legacy CONTEXT.md files resurface unchanged. Shipped in #34, tag v1.2.0.