Framework
"Bug Links" Is Not "Bugs"
A sprint trend moved 102 to 103 and was read as one new defect. The snapshot held 103 link references against 76 unique bug keys, and the week's worst defect counted four times.
More posts
Framework
The Design Document Describes a Proof of Concept That Died
Two design pages described a migration lock built from fields, a permission, metadata, triggers and an LWC that exist nowhere in the org. The deployed solution had different names and no page at all.
Framework
Reconcile the Coverage Claim Against the Org
A developer declared 41 orchestration scenarios and 38 item definitions covered and unit tests passed. A query found the clause on 40 of the 41, and the missing one gated billing.
Framework
Prove Uniformity by Query, Spend Execution on the Outliers
A scope of 78 configuration records became six to eight test cases — because all 84 instances of the gate clause were byte-identical, and the query that proved it also found the exceptions.
Framework
A Static Finding Is a Candidate. One Run Prices It.
A configuration diff flagged one orchestration scenario as an uncovered billing exposure. One executed order turned it into a cosmetic mismatch — every item definition beneath the plan carried the gate anyway.
Framework
Grade the Defect on Detectability, Not on Recoverability
The undo worked perfectly — cancel the order, raise a replacement, everything normal. The finding stayed High, because every orchestration item ended Skipped and nobody would ever know to invoke the remedy.
Field Notes
One Rule, Two Entry Conditions
The acceptance criteria required two flags. All 84 deployed orchestration clauses checked one. The validation rule checked both. The defect exists only in the state where they disagree.
Field Notes
Passing the Outer Layer Is Evidence About the Outer Layer
The same rule was enforced in four stacked layers, so the user in the story could never reach the layer the story delivered. Reaching it meant building the cart unlocked, then setting the flag, then submitting.
Framework
The Gate That Also Disables the Undo
The same gate that let an order commit and skipped its provisioning also sat on the rollback plan. The compensating action was suppressed with its parent, and the orphaned Contract became permanent.
Framework
A Condition Is Not a Gate Until You Enumerate the Entry Routes
A suppression clause on scenario entry conditions left eighteen item definitions across six plans ungated by construction, because nine item definitions spawn plans by lookup and never pass through a scenario at all.