Degradation proof: Rig disabled reduces coverage, never correctness (Slice 5 exit) #19
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Meta/Campaign
Meta/Epic
Meta/Session
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Curated
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Scope/Campaign
Status/Abandoned
Status/Blocked
Status/Conflicted
Status/In Progress
Status/In Review
Status/Need Grooming
Status/Need More Info
Status/Ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#31 Slice 5 — targeted Rig extraction
Ting/CurryComb
Reference
Ting/CurryComb#19
Loading…
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?
Proposal
CI proof of the Slice 5 exit: with Rig disabled or unavailable, every decision made without it is still correct; only model-derived coverage disappears (§Failure behavior: LLM unavailable).
Tasks
Requirement scenario
GIVEN the Slice 3 goldens, WHEN Slice 5 runs with Rig off, THEN all rule-derived digests match and no failure-mode effect is emitted.
Degradation proof: Rig disabled reduces coverage, never correctness (Slice 5 exit)
State:
open· Labels: Kind/Testing · Comments: 0Rendered by CurryComb slice 1 projection v1. The body will be replaced by rule-derived content in Slice 3.