crenshawdev/cadence

v2.0.0

New issue

The breaking half of the routing reframe, plus the traceability and config-honesty work that rides with it. The user-visible break is one: model.profile's enum values change with no back-compat alias. In scope: the stakes axis (#81, with #63 kept as the trace of how the argument got here), stable IDs on CONTEXT acceptance criteria (#76, the survivor of the rejected #70), the resolved-then-dropped config keys (#78), and #54, which this reframe closes rather than ships. The non-breaking half shipped in v1.5.0 (#74, #64).

No due date

14% Completed

fire(trigger) step 4 is loop-shaped, so reviewers get dispatched serially

#88 opened 2026-07-28 22:08:27 +00:00 by crenshawdev

routing: make the axis stakes, not spend - one question (what happens if this is wrong) driving model, effort, review, and verification

#81 opened 2026-07-28 19:49:18 +00:00 by crenshawdev

review: the same silent config drop as #64 in two more places (triggers.<t>.tier, decision-review report_cost)

#78 opened 2026-07-28 19:22:57 +00:00 by crenshawdev

traceability: give CONTEXT acceptance criteria IDs so an audit can prove every criterion reached the checklist

#76 opened 2026-07-28 19:12:39 +00:00 by crenshawdev

routing: replace the spend ladder with a rigor ladder, deleting the profile matrix, the tier bump, and escalate_effort_variant

#63 opened 2026-07-28 17:41:20 +00:00 by crenshawdev

routing: make per-role tier and effort user-configurable (config layer), persistent across plugin updates

#54 opened 2026-07-24 16:23:34 +00:00 by crenshawdev