Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 22:51:26 UTC · snapshot created 2026-11-18 22:54:45 UTC · last check 2026-11-18 23:20:20 UTC

OPS.5:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternFailureRepair
top card means startRank substitutes for authority and permission.Record admission, permission, starter, and start conditions separately.
everything is “in progress”Hidden starts erase residual demand and overload the operation.Apply an explicit-start limit and give every item a disposition.
availability implies capacityA free slot, worker, rig, tool, or model is treated as a complete capability and access result.Recover the exact performer, resource relation, capability, permission, and configuration.
choose-first option setAn artificial score replaces mandatory conditions or direct rules.Use the direct branch; compare only genuine admissible alternatives.
admission by artifactTicket creation, assignment, plan, model output, or code generation becomes “Work started”.Establish whether Work occurred from independent performance evidence; decide admission and permission before the prospective start.
rejection without returnDemand silently disappears or repeatedly re-enters.Keep the reason, residual identity, owner, and retry condition.
local rule claims the systemOne start limit becomes a universal WIP, queue, capacity, or constraint Method.Bound the result and return wider policy questions.