Why–What–How
Lead with the risk or business problem, define the result, then show the controlled method.
Ten delivery cases, three honest ways to explain them.
The lens may change for an executive, reader, or operator. The underlying facts, dates, outcomes, and evidence boundaries do not.
This English page is deliberately the case index: every case keeps its claim, outcome, and boundary in one card. The full ten-case narratives live on the Chinese page; the English deep-dive evidence is the controlled-recovery case.
Story
Use tension, decision, and consequence—but never turn an unobserved outcome into a dramatic ending.
5W2H
Make owner, scope, time, place, reason, method, and measured boundary explicit.
Coverage and evidence responsibility
Each case keeps its source facts, measured outcome, and claim boundary while the lens changes how the reader enters the story.
High-risk Git and worktree governance
Value: preserve user assets while restoring a safe continuation point.
Boundary: successful Git recovery did not authorize runtime writes.
Agentic Engineer CV
Value: produce a readable, role-specific two-page artifact.
Evidence: page, link, residual-text, and visual checks.
Simplifying DHF safely
Value: make light work lighter without deleting safety controls.
Evidence: contract, committee review, implementation, and gate.
Commercial positioning
Value: connect one buyer, one service, and bounded proof.
Boundary: strategy evidence did not prove customer adoption.
Private response prototype
Value: test useful interaction while minimizing collected data.
Boundary: local prototype, no production deployment.
Level 2 adapter and rollback
Value: contain partial external writes and restore trustworthy state.
Evidence: failed receipt, native rollback, independent readback.
10/10 still incomplete
Value: prevent self-review confidence from replacing independent proof.
Boundary: blind final remained unresolved when rounds ended.
231 requests are not visitors
Value: avoid treating probes and bot noise as growth.
Boundary: visitor count unavailable when RUM was stale.
Status documentation and browser QA
Value: separate source, runtime, publication, and enforcement claims.
Evidence: focused tests and desktop/375px acceptance.
Moments delivery contract
Value: separate verified event, generated asset, and observed use.
Boundary: repository push did not prove WeChat publication.
Evidence rule: narrative structure can make a case understandable. It cannot increase the evidence level of the case.