Map the case to SAFE evidence.

A useful case map does not merely label a story. It identifies what was specified, who authorized the action, which facts were observed, and how the system recovered from failure.

S · Specification

The write set, target documents, required structure, completion condition, and rollback expectation were explicit.

A · Authorization

External writes required a scoped grant; recovery facts did not automatically authorize retry.

F · Facts

The failed receipt, actual changed sections, independent readback, and fresh verification bounded the completion claim.

E · Error-recovery

Mutation stopped, native history restored known state, readback confirmed restoration, and execution resumed only after fresh authority.

Ten-case control index

01 · Worktree governance

S/A fix ownership and allowed Git actions; F/E preserve recovery anchors and verified restoration.

02 · CV artifact

S fixes the two-page output and preserved source; F checks rendering and residual text.

03 · DHF simplification

S fixes scope and acceptance; A/F require independent review and fresh gates.

04 · Commercial positioning

S limits the decision to one offer; F separates fact, inference, and assumption.

05 · Local prototype

S bounds the experiment; A keeps local learning separate from production authority.

06 · ShipQ rollback

A requires a scoped write grant; F/E preserve mismatch evidence, restore, and read back.

07 · Committee review

S fixes the rubric; A/F use an independent blind gate and retain failed scores.

08 · Traffic analysis

S defines visitor evidence; F separates RUM, HTTP noise, and unavailable data.

09 · Public status

S separates status layers; A/F keep local verification distinct from publication.

10 · Moments delivery

S defines the artifact contract; A/F separate repository delivery from social use.

Claim-to-evidence map

ClaimRequired evidenceBoundary
The plan was safeExact targets, scope, completion and rollback contractDesign intent only
The implementation workedFresh checks and artifact readbackDoes not prove production
The failure was containedFailed receipt, stopped writes, restored state, independent readbackDoes not authorize retry
The customer received valueObserved customer outcome attributable to the workflowCase mechanics alone are insufficient
Evidence rule: SAFE labels organize the facts. They do not upgrade the evidence level of those facts.