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

Source changed 2026-10-14 19:58:00 UTC · snapshot created 2026-10-14 19:58:38 UTC · last check 2026-10-15 04:45:08 UTC

C.40.OI:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWhy it failsRepair
“Develop in X” as the inquiryIt names a subject area or solution without a question worth investigating.Name the subject, local question, horizon, protections and first useful result; identify the receiving use when investigating a proposed contribution.
Full goal required before discoveryIt suppresses useful exploration when the problem is still provisional.Permit an explicit hypothesis, but bind effort and the question that would qualify or reject it.
Uncertainty sets the budgetA large unknown attracts an expensive study even when its results cannot improve the present use.Compare attainable answers and whole burden with a sufficient current answer or smaller inquiry; stop at the result this use needs.
One cross-holder development mechanismIt imports human, organizational, technical, epistemic, or evolutionary assumptions across unlike subjects.Recover the exact subject and return substantive claims to its direct owner.
Inquiry as engagement authorizationPermission to explore is treated as authority to advise or intervene.Keep inquiry permission, advising admissibility, choice authority, and implementation authority separate.
Horizon by convenienceTime is shortened or extended to favor one candidate.Declare the horizon before comparison and reopen when it changes.
Protected conditions added lateCandidate momentum hides safety, continuity, workload, privacy, or option losses.State protections before search or selection.
Publication order as workflowReaders use every pattern in numeric order.Start at the first missing result and stop when the receiving use is served.