C.26:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Symptom | Repair |
|---|---|---|
| Quantum-like as prestige word | The case is only complex, uncertain, nonlinear, discrete, or hard to measure. | Use ordinary FPF patterns. Admit QL only with a declared cue and payoff. |
| Precautionary suppression | QL wording is rejected because it is unusual without testing the claimed contextual-model obstruction. | Recover the exact claim and apply its ordinary subject patterns. Retain QL-lite only if a named contextual-model obstruction survives and changes the admissible inference or action. If that comparison is unavailable, keep the proposed QL use unresolved; absence of a named ordinary pattern alone does not activate it. |
| Physical overread | The text sounds as if organizations, services, or teams are physically quantum systems. | Cite inherited QL-NQ; rewrite the claim as mathematical or representational. |
| Passive dashboard | A metric or score is used as a neutral fact after its publication or operational use changed behavior. | Use measurement and evidence patterns and, if needed, C.26.1. |
| Faithful-copy export | A survey, report, API response, or context map is treated as the live state itself. | Use bridge/export loss, C.26.2, or ordinary publication patterns. |
| Speed or compression slogan | A shortcut is called fast, cheaper, linear, low-bit, symbolic, or compressed without a declared claim. | Write the speed, compression, or linearity claim declaration: baseline representation and cost, changed representation, mechanism, claimed gain, loss budget or error budget, ordinary alternatives, evidence source or formal source, and reopen trigger. Keep the coarsening card only for the representation shortcut itself. |
| Hidden search problem | The option menu is frame-bound, but the text tries to solve it by naming QL. | Use QL only as a suspicion cue; apply search patterns to generation and regime movement. |
| Cell-like service jump | A service or access bearer is called cell-like because it has a boundary or internal state. | Use A.6.P:4.11a to recover only the boundary, controlled-exchange, state, viability, behavior, coupling, resource, invariant, repair, or continuity claim the current decision needs, then use that claim’s subject pattern. Do not assemble the possibilities as one service bundle. Retain the analogy only for a residual QL issue that changes the decision. |
Near-miss taxonomy:
| Near miss | Why not QL by itself |
|---|---|
| Feedback loop | Ordinary dynamics/control unless admissible reading, export, or comparison is affected. |
| Metric gaming | Ordinary metric/incentive problem unless measurement publication changes the state reading. |
| Uncertainty | Ordinary epistemic uncertainty unless an exact probe/model frame, comparison frame, or effective reference scheme changes variable identity or comparison law and one named contextual-model obstruction remains. |
| Complexity | Ordinary complexity unless shortcut, export, or probe issue remains. |
| Compression | A.6.3.CSC, A.6.3.RT, modeling, or implementation pattern first; QL only for state-representation residue. |
| DDD bounded-context cue | Direct boundary, local-sense, work, and model-use subject patterns first; the label does not identify a universal object or activate QL. Retain C.26 only when a named probe, order, comparison, or export obstruction changes the admissible inference. |
| Low-bit or quantized implementation | Engineering representation first; not QL because it is “quantized”. |
| Collective behavior | A.15, distributed cognition, routines, and evidence patterns first; QL only for low-recoverability state-reading residue. |
C.26:8.1 - Cluster conformance scenarios
Use these as quick applicability tests. A good C.26 use leaves one practical output.
| Scenario | Expected route | Avoid | Expected output |
|---|---|---|---|
| Dashboard readiness improves because teams optimize the displayed metric. | C.16 / A.15 first; C.26.1 only if the output is reused as a passive readiness read after state-shaping publication. | Treating the dashboard value as release evidence by itself. | Redesign metric publication or add independent work traces before release use. |
| Workshop “discovers” a boundary but also creates alignment and local meaning. | A.6 / A.15 first; C.26.1 for false pre-probe discovery reading. | Exporting the workshop result as a timeless domain fact. | Record window, participants, carriers, unresolved rivals, and bridge/export limits. |
| API read warms cache and changes downstream timing. | Interface semantics, A.6, and C.16 first; C.26.1 if the read result is reused as passive state export. | Saying the API read simply copied state. | Mark the read as non-neutral for that timing window or redesign the read path. |
| Two service health reports use different measurement frames. | C.16 / F.9 first; C.26 only if no admissible shared comparison frame remains. | Averaging the scores as one posterior-looking value. | Name the frame difference and either build an admissible comparison route or stop comparison. |
| Team survey says “aligned”, but incident behavior contradicts it. | A.10 / A.15 / B.3 first; C.26.2 if coordinated work traces support a low-recoverability distributed-state reading. | Treating survey output as the team state. | State a low-recoverability carrier/window-bound reading and the rival explanations. |
| Market “expects” a feature because many actors change behavior. | Declare bearer/traces; ordinary market, incentive, and evidence explanation first; C.26.2 only for residual low-recoverability state reading. | Inventing a market mind. | Name actor traces, window, rivals, and a behavior-based reading bounded by those traces. |
| Latency is green while support load and customer promise degrade. | C.25 / C.16 first; C.26.3 for multi-characteristic envelope regulation under disturbance when a candidate intervention, boundary condition, adaptation cost, or failure mode matters. Retain C.26 / QL only when the residual contextual-model obstruction condition holds. | Calling one green metric viability. | Add envelope variables, actuators, costs, and failure mode. |
| Summary compresses an architecture decision for executives. | A.6.3.CSC first; no QL unless a state-representation shortcut has QL residue. | Treating the summary as full architecture state. | Use for orientation only; return to source for release or design lock. |
| Diagram translates the same system into graph form. | A.6.3.RT first; no QL unless incompatible representation, probe, or export cue remains. | Calling any diagram a QL state model. | Declare representation-scheme change, reasoning-medium change, and source tether. |
| Low-bit model approximates expensive simulation. | Modeling, approximation, compression, or implementation pattern first; QL only if the shortcut claim depends on QL state, probe, or frame admissibility. | Treating low-bit or linear form as QL activation. | Name baseline, shortcut, loss budget or error budget, ordinary alternatives, and reopen trigger. |
| Assurance load is raised because a QL explanation is published, reused or written formally. | Identify the receiving conclusion and what support it needs under :12b. | Making a fuller record without resolving a consequential question. | Reuse the adequate account; add only the missing mathematical, empirical or assurance contribution needed for the new use. |
| Author claims QL is faster or better than a classical method. | Require baseline, metric, mechanism, evidence or formal argument, loss/use declaration, ordinary alternatives, and reopen trigger. | Accepting superiority rhetoric. | Either write the claim declaration or remove the speed/superiority claim. |
QL findings can also inform design options to test under the ordinary subject patterns:
| Problem | QL-inspired design option |
|---|---|
| Dashboard changes behavior destructively. | Delay publication, split private and public metrics, add independent sampling, or publish confidence and loss boundaries. |
| Workshop creates alignment but masquerades as discovery. | Record pre-workshop hypotheses, post-workshop commitments, and created boundary meaning separately. |
| API read disturbs state. | Add non-mutating read, shadow read, sampling window, idempotence declaration, or separate observation channel. |
| Metrics in two contexts are not comparable. | Build a bridge or coupling record or stop comparison. |
| Summary is overused as source. | Add admissible-use label and return-to-source trigger. |
| Viability scalar hides damage. | Build envelope variables and actuators; add a failure-mode sensor. |
C.26:8.2 - AI and LLM work-cycle route examples
LLM-mediated work cycles often create the same representational mistakes C.26 repairs: false passive read, false faithful summary, false shared comparison frame, and shortcut without loss/use declaration.
| AI case | Route |
|---|---|
| LLM summary of an architecture record | A.6.3.CSC, A.6.3.RT, and A.10 first; C.26 coarsening only if a state-representation shortcut is being overused. |
| Prompted model evaluation changes model or prompt behavior | C.16 / B.3 first; C.26.1 only if the eval output is treated as a passive model-state read. |
| Agent work cycle “discovers” requirements | A.15 / A.10 / A.6 first; C.26.1 only if the interaction created the requirement framing. |
| Synthetic personas “represent market state” | A.10 / B.3 first; C.26.2 only if a low-recoverability state-reading claim is carefully bounded with non-admissible use visible. |