Skip to content

Schema-Bounded Blind Spot

Prime #
1162
Origin domain
Epistemology
Subdomain
methodology → Epistemology

Core Idea

A schema-bounded blind spot is the structural pattern in which a reasoning, elicitation, or evaluation process uses a finite schema — a structured list of categories, prompts, questions, fields, parameters, or template slots — to scan an open target space, and items in the target space that fall outside the schema are systematically absent from what the process produces, records, or considers. The absence is not stochastic but structural. The failure is methodological — the schema has no slot for the item — rather than executional (the operators applied the schema badly) or evaluative (the item was generated and judged unimportant). The schema's coverage boundary becomes the boundary of what the process can see, and items beyond it do not appear at all, regardless of their importance.

Three commitments are load-bearing. There is a finite schema: a structured cross-product of categories — forms, questions, prompts, guidewords, checklist items — defining the process's input or output template. There is an open target space: the real space of items that could matter is not coverable by any finite schema, whether because new categories continually emerge, the space is combinatorially large, or rare-but-real items fall outside any practical enumeration. And there is a systematic outside: items that match no schema category are not generated by the schema's normal operation, and their absence has a structural cause (no slot to hold them) rather than an incidental one (sometimes missed).

The pattern is sharply distinct from random oversight or attentional lapse. Its diagnostic property is reproducibility under re-execution: re-running the schema with fresh operators fails in the same places, because the gap lives in the schema, not in the operators. That reproducibility is what makes schema-bounded blind spots immune to "try harder" interventions and responsive only to schema-level change — and it is also the empirical test that distinguishes a methodological gap from a merely executional one.

How would you explain it like I'm…

Not On The List

Imagine you have a checklist of animals to look for at the zoo: lion, zebra, monkey. If you only check your list, you'll never write down the kangaroo, because it isn't on your paper. You didn't miss it by being sloppy — your list just had no spot for it.

No Slot For It

A schema-bounded blind spot is when you use a fixed list of categories — questions, boxes, slots, checklist items — to look at a big open world, and anything that doesn't fit one of your categories just never shows up. It's not that you looked carelessly; it's that your list had no slot to hold that thing. The gap is built into the form itself, not into how you filled it out. The giveaway is that if you hand the same list to a fresh person, they'll miss the exact same things, every time. That's why telling people to 'try harder' doesn't help — only changing the list fixes it.

Checklist Blind Spot

A schema-bounded blind spot is the pattern where a reasoning, survey, or evaluation process uses a finite schema — a structured set of categories, prompts, questions, fields, or template slots — to scan an open target space, and items that fall outside the schema are systematically missing from what the process produces. The absence is structural, not random. The failure is methodological — the schema has no slot for the item — rather than executional (operators applied it badly) or evaluative (the item came up and was judged unimportant). It rests on three things: a finite schema defining the input or output template; an open target space too big or too ever-changing for any finite list to cover; and a systematic outside, where non-matching items never get generated and their absence has a structural cause. Its diagnostic signature is reproducibility under re-execution: re-run the schema with fresh operators and it fails in the same places, because the gap lives in the schema, not the people — which is also the test that separates a methodological gap from a merely careless one.

 

A schema-bounded blind spot is the structural pattern in which a reasoning, elicitation, or evaluation process uses a finite schema — a structured list of categories, prompts, questions, fields, parameters, or template slots — to scan an open target space, and items in the target space that fall outside the schema are systematically absent from what the process produces, records, or considers. The absence is not stochastic but structural. The failure is methodological — the schema has no slot for the item — rather than executional (the operators applied the schema badly) or evaluative (the item was generated and judged unimportant). The schema's coverage boundary becomes the boundary of what the process can see, and items beyond it do not appear at all, regardless of importance. Three commitments are load-bearing: a finite schema (a structured cross-product of categories — forms, questions, prompts, guidewords, checklist items — defining the input or output template); an open target space (the real space of items that could matter is not coverable by any finite schema, whether because new categories continually emerge, the space is combinatorially large, or rare-but-real items fall outside any practical enumeration); and a systematic outside (items matching no category are not generated by the schema's normal operation, their absence having a structural cause rather than an incidental one). The pattern is sharply distinct from random oversight or attentional lapse: its diagnostic property is reproducibility under re-execution — re-running the schema with fresh operators fails in the same places, because the gap lives in the schema, not the operators. That reproducibility is what makes such blind spots immune to 'try harder' interventions and responsive only to schema-level change, and it is also the empirical test distinguishing a methodological gap from a merely executional one.

Structural Signature

the finite schema (an enumeration of category-slots) — the open target space it is asked to scan — the schema's image (the coverable subset) — the systematic outside (items matching no slot) — the absence-at-the-boundary — the reproducibility invariant under re-execution

The pattern holds whenever these components co-occur:

  • The finite schema (role). A structured, enumerable instrument — a cross-product of categories, prompts, guidewords, fields, or checklist items — that defines what the process can generate, record, or consider.
  • The open target space (role). The real space of items that could matter, which no finite enumeration covers, whether because new categories emerge, the space is combinatorially large, or rare items fall outside any practical list.
  • The scanning relation. The process applies the schema to the target space, producing output only for items that map to some slot.
  • The systematic outside (invariant). Items matching no schema category are absent from the output by construction, not by chance — their absence has a structural cause (no slot to hold them).
  • The reproducibility test (invariant). Re-execution with fresh operators fails in the same places, because the gap lives in the schema, not the operators — the empirical signature distinguishing a methodological gap from an executional one.
  • The meta-applicability closure. The schema cataloguing types of this failure is itself schema-bounded, so the pattern includes itself within its own scope.

The components compose into the signature: a finite instrument scanning an open world yields principled, reproducible blindness exactly at the schema's coverage boundary.

What It Is Not

  • Not schema. A schema is the instrument — a structured enumeration of slots; the blind spot is the systematic absence at its coverage boundary. The prime is not the schema but the structural consequence of applying any finite schema to an open target.
  • Not bias. Bias is a directional distortion of what the process does see; the blind spot is what the process cannot see at all, for structural reasons. Debiasing adjusts the weighting of in-schema output and leaves the boundary gap untouched.
  • Not selection_bias. Selection bias skews an included sample relative to a population; here items outside the schema are not merely under-sampled — they are uncoverable by construction, absent because no slot can hold them, not because the sampling under-weighted them.
  • Not overfitting. Overfitting is a model tracking noise in its training data; the blind spot is principled blindness to items the schema never enumerated, an under-coverage of the target space rather than an over-fit to a sample.
  • Not mere execution failure. The pattern's signature test is reproducibility: re-execution by fresh operators hits the same gap. A one-off oversight that a more careful operator would catch is executional, not the methodological blind spot the prime names.
  • Not bounded_rationality. Bounded rationality is a limit on an agent's computation and search; the blind spot is a property of the instrument the agent wields — the gap reproduces even with unbounded effort, because it lives in the schema, not the searcher.
  • Common misclassification. Filing a methodological gap as "the team should have thought harder." If a fresh team re-running the schema misses in the same places, the failure is in the schema's coverage boundary, not in operator diligence — and "try harder" guarantees the gap reproduces.

Broad Use

  • Process safety. HAZOP studies cross a fixed set of guidewords with process parameters; hazards not articulable in guideword-by-parameter form — software faults, cyber-physical interactions, novel operator behaviours — sit outside the schema and are systematically missed.
  • Cybersecurity threat modelling. STRIDE enumerates six threat categories; supply-chain compromise, prompt injection, and side-channel attacks fall outside its coverage, and alternative schemas have different gaps.
  • Clinical differential diagnosis. The trained differential enumerates expected conditions; rare diseases, atypical presentations, and conditions outside the clinician's register fall off the list, a failure the literature calls premature closure.
  • Audit checklists. SOX, ISO 27001, and SOC 2 audits scan a fixed control list; novel or out-of-scope control failures escape, and firms compete partly on schema breadth.
  • Peer review and risk registers. A reviewer's rubric does not enumerate the specific flaw a manuscript carries; a national risk register under-enumerates a pandemic of a particular configuration even when "pandemic" is nominally on the list.
  • Form-based intake and surveys. Immigration forms, benefit applications, and closed-form survey instruments bound what can be captured; the "other" field is a partial, structurally deprioritised complement.

Clarity

Naming the schema-bounded blind spot separates three failure modes that look identical after the fact: evaluation failure (we saw the item and judged it unimportant), execution failure (we used the schema sloppily), and methodological failure (the schema has no slot for the item). The three call for different fixes. Evaluation failure responds to better judgement criteria; execution failure responds to training and rigour; methodological failure responds only to schema-level change — extend the schema, replace it, union it with a complementary schema, or pair it with an unstructured complement. Treating a methodological failure as an execution failure — "be more careful next time" — guarantees the gap reproduces.

The clarity move also surfaces a diagnostic asymmetry. After a miss, the schema's defenders typically attribute it to execution failure, because methodological failure implicates the schema itself and threatens institutional commitment to it. The structural fact cuts through the attribution dispute: re-execution by new operators will hit the same gap if the failure is methodological, and will not if it is merely executional. The reproducibility test converts a question that is usually settled by organisational politics into one that can be settled by experiment.

Manages Complexity

The pattern compresses a sprawling family of "we should have caught that" failures under a single diagnosis: a finite schema applied to an open space yields systematic absence at the schema boundary. Once the diagnosis is made, the intervention space partitions into five complementary moves, each with its own cost profile. Extend the schema with more categories — always available, cumulative, eventually unwieldy, and never closing the boundary. Triangulate schemas — union multiple schemas for more coverage at the cost of duplication and diminishing returns. Rotate the operators — prior-driven gaps differ across people, giving cheap coverage variance without touching the underlying boundary. Pair with an unstructured complement — an open-ended red-team or "consider the opposite" exercise, structurally the highest-leverage move and the hardest to enforce procedurally. Revisit the schema on a schedule — letting accumulated learning enter it and tracking its drift against a changing target.

The same five-fold catalogue recurs across HAZOP, threat modelling, audit, differential diagnosis, and risk-register work. Practitioners in each substrate have re-invented some subset under local names; the structural pattern is what lets them recognise the full family and import the moves they are missing from neighbouring fields rather than rediscovering them.

Abstract Reasoning

The schema-bounded blind spot is the practical manifestation of a deeper structural fact: any finite enumeration of a categorical target space omits items the enumeration does not name. The schema is finite, the target space is open, and the schema's image in that space is a proper subset its operations cannot escape using only its own resources. There is a Gödelian rhyme: just as no finite axiom schema proves all true statements of arithmetic, no finite question schema surfaces all relevant items of an open domain. The pattern is the methodological analogue of an incompleteness result, and recognising the analogy clarifies why the gap is principled rather than a sign of carelessness.

The pattern also connects cleanly to coverage in formal methods: a test suite is a schema, the program's input space is the target, and uncovered inputs are the blind spot. Mutation testing, fuzzing, and property-based testing are structurally different responses — extending the schema, pairing it with an unstructured complement, and rotating the generator — and the intervention families recur with the same commitments. There is even a self-referential sharpening: the schema used to catalogue types of methodological failure is itself schema-bounded, so the catalogue of failure types is itself incomplete. This is not paradoxical; it simply marks the pattern as meta-applicable, including itself within its own scope.

Knowledge Transfer

Because the pattern is a relation between a finite schema and an open space, its diagnostic and its repairs travel intact across substrates that share nothing else. The guideword-by-parameter cross-product of HAZOP maps directly onto the category-by-asset cross-product of STRIDE, carrying the same coverage-gap diagnostic — a class of hazards or threats not articulable in the schema's form is systematically missed — and the same extend/triangulate/complement catalogue with the same cost structure. The cognitive-science finding that clinicians close on the differential available rather than the differential needed maps onto auditors closing on the checklist available rather than the control gaps present; the training-driven schema produces the same failure shape in both.

Two transfers are especially load-bearing. The first is the unstructured-complement intervention: across substrates, supplementing a structured schema with an open-ended red-team, free-form addendum, or consider-the-opposite exercise is the only move that addresses the boundary itself rather than merely extending or rotating the schema, and Tetlock's "consider the opposite," chaos engineering, and security red-teaming are recognisably the same intervention in different clothes. The second is the reproducibility diagnostic: "if the same gap recurs when new operators apply the schema, the gap is methodological, not executional" is a portable calibration check that distinguishes the two failure modes in any substrate. A practitioner who has learned to suspect the schema rather than the operator in one field carries that suspicion, and the full repair catalogue, into every other field where a finite instrument is asked to scan an open world.

Examples

Formal/abstract

Software test coverage is the cleanest formal instance. The finite schema is the test suite: a concrete enumeration of input cases, each a slot the program is exercised against. The open target space is the program's full input domain — combinatorially vast, effectively unbounded for any non-trivial program. The scanning relation runs the suite over the program, producing a verdict only for inputs that some test covers. The systematic outside is the set of uncovered inputs: a bug reachable only by an input no test names is not "sometimes missed," it is invisible to the suite by construction, and re-running the same suite never finds it — the reproducibility invariant in its sharpest form. The five-fold repair catalogue maps onto distinct testing technologies: extend the schema (add hand-written cases), triangulate (union unit, integration, and property tests), rotate the operators (different engineers write tests with different prior-driven gaps), pair with an unstructured complement (fuzzing and chaos engineering, which generate inputs no schema names), and revisit on a schedule (mutation testing to detect schema drift against a changing codebase). The Gödelian rhyme is exact: just as no finite axiom schema proves every arithmetic truth, no finite test schema certifies every input — and the catalogue of coverage criteria itself is schema-bounded, the meta-applicability closure made concrete. Mapped back: the test suite is the finite schema, the input domain is the open target, uncovered inputs are the systematic outside, and fuzzing is the unstructured complement that alone acts on the boundary rather than merely extending the schema.

Applied/industry

Cybersecurity threat modelling with STRIDE is the applied worked case. The finite schema is STRIDE's six categories — Spoofing, Tampering, Repudiation, Information disclosure, Denial of service, Elevation of privilege — crossed with the system's data-flow diagram to generate candidate threats. The open target space is the real space of ways an adversary can compromise the system, which no six-category enumeration covers. The systematic outside is structural and nameable in advance: supply-chain compromise, prompt injection against an embedded language model, and timing side-channels are not threats STRIDE evaluated and dismissed — they are threats it has no slot to articulate, so a fresh team re-running STRIDE on the same architecture misses them in the same places, which is exactly the reproducibility test that flags the gap as methodological rather than executional. The diagnostic asymmetry plays out organisationally: after a supply-chain breach, STRIDE's defenders attribute the miss to sloppy execution ("the team should have thought harder") because conceding a methodological gap implicates the framework the security program is built on. The repair is the unstructured complement — an open-ended red-team exercise charged with "find a compromise STRIDE cannot name" — supplemented by triangulating a second schema (such as an attack-tree or kill-chain model) whose coverage boundary differs. The identical structure recurs in HAZOP process-safety studies (guideword-by-parameter cross-product missing cyber-physical hazards) and in clinical differential diagnosis (the trained differential missing the rare presentation, a failure the literature names premature closure), giving a third and fourth genuine domain. Mapped back: STRIDE's six categories are the finite schema, the adversary's real option space is the open target, supply-chain and prompt-injection attacks are the systematic outside, and the red-team is the boundary-addressing complement the five-fold catalogue prescribes.

Structural Tensions

T1 — Coverage Breadth versus Schema Usability (scalar). The pattern's first repair is "extend the schema," and there is no point at which extension closes the open boundary — yet each added category raises the cost of applying the schema at all. A 200-guideword HAZOP or a 40-category threat taxonomy becomes so heavy that operators skim, and the very breadth meant to close gaps creates execution failure inside the slots that exist. The failure mode is treating coverage as monotonically good and bloating the schema until completion within it collapses. Diagnostic: ask whether marginal new slots are actually scanned with the same rigor as the original core, or merely listed.

T2 — Methodological versus Executional Attribution (measurement). The prime's signature test — re-execution by fresh operators hits the same gap — distinguishes a schema flaw from operator sloppiness. But the test presupposes you can rerun cleanly with truly independent operators who share no training lineage. When all available reviewers were trained on the same schema, their "independent" reruns inherit the same blind spot, and a methodological gap masquerades as confirmed coverage. The failure mode is reading a reproduced pass as evidence the schema is complete when it only shows shared blindness. Diagnostic: ask whether the re-executors' priors are genuinely uncorrelated with the schema's lineage.

T3 — Finite Schema versus Genuinely Open Target (scopal). The pattern asserts the target space is open — uncoverable by any finite enumeration. But some target spaces are effectively closed (a fixed protocol's message types, a bounded combinatorial form), and there the "blind spot" is removable, not principled. Competing with combinatorial_explosion, the question is whether the outside is infinite-in-principle or merely large-and-unenumerated. The failure mode is invoking Gödelian inevitability to excuse a gap that a tractable exhaustive schema would have closed. Diagnostic: ask whether the target space admits a finite generating grammar, in which case incompleteness is a choice not a theorem.

T4 — Stable Schema versus Drifting Target (temporal). The pattern treats the schema as a fixed instrument and the gap as a static boundary, but the target space moves: new attack classes, new failure modes, new disease presentations appear over time. A schema that was complete-enough at adoption silently develops fresh blind spots as the world changes, with no internal alarm. The failure mode is certifying a schema once and trusting it indefinitely, so the gap grows precisely where recent change concentrated. Diagnostic: ask when the schema was last revised against observed misses, and whether its drift is tracked against a changing target rather than assumed frozen.

T5 — Structured Schema versus Unstructured Complement (coupling). The catalogue's highest-leverage move — pair the schema with an open-ended red-team — is the only one acting on the boundary itself, but it trades away exactly what made the schema valuable: auditability, repeatability, and procedural enforceability. An unstructured complement that finds the unnamed threat cannot be made a checklist item without re-bounding it. The failure mode is either refusing the complement (because it cannot be proceduralized) or proceduralizing it (which collapses it back into a bounded schema with its own outside). Diagnostic: ask whether the complement is being preserved as genuinely open or quietly converted into more slots.

T6 — Schema Image versus Selection Among Schemas (scopal). Triangulating multiple schemas widens coverage, but the choice of which schemas to union is itself a schema-bounded act: the meta-schema for picking complementary frameworks has its own outside, so two schemas with correlated boundaries leave a shared gap untouched while creating an illusion of breadth. The failure mode is unioning frameworks that share a lineage (all built on the same threat model) and counting their overlap as defense-in-depth. Diagnostic: ask whether the triangulated schemas have demonstrably different coverage boundaries, or merely different vocabularies over the same image.

Structural–Framed Character

Schema-bounded blind spot sits on the structural side of the middle of the structural–framed spectrum — a mixed-structural prime (aggregate 0.4). At its core it is a set-theoretic relation: a finite enumeration (the schema's image) cast over an open target space leaves a systematic outside, an absence at the coverage boundary that reproduces under re-execution. That is a theorem about finite instruments scanning open worlds, with a Gödelian rhyme made explicit in the entry — and nothing in it presupposes a human field. It carries zero inherent evaluative weight (a blind spot is value-neutral; whether it matters depends entirely on what falls outside), which is precisely why the diagnostic transfers untouched from test coverage to threat models to differential diagnosis.

What keeps it from the pure-structural pole is that two diagnostics read mid. Its load-bearing examples cluster in human and institutional reasoning practices — HAZOP studies, STRIDE threat modelling, audit checklists, peer review, clinical differentials — so it is partly institutional-origin (0.5) and partly human-practice-bound (0.5): the canonical instances are deliberative processes run by operators against a methodology, and the signature reproducibility test ("fresh operators hit the same gap") is framed around human re-execution. Yet the same diagnostics also have a clean formal reading: a test suite over a program's input domain instantiates the pattern in a substrate with no human practice at all, which is exactly why the criteria are scored as partial rather than full. Vocabulary travels at 0.5 — "finite schema," "open target," "systematic outside" are portable, but seeing the gap takes the small interpretive move of distinguishing methodological from executional failure. The aggregate of 0.4 captures this honestly: a genuinely structural skeleton whose home register is human inquiry, sitting just structural-of-center rather than at the pure end where feedback lives.

Substrate Independence

Schema-bounded blind spot is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth is wide: the finite-schema-scans-open-target failure recurs with the same structural force across process-safety HAZOP studies, STRIDE cybersecurity threat modelling, clinical differential diagnosis, SOX/ISO/SOC audit checklists, peer review and national risk registers, and form-based intake — and, crucially, in a substrate with no human practice at all, software test coverage, where the suite is the schema and uncovered inputs are the systematic outside. Its structural abstraction is high: the core is a set-theoretic relation — a finite enumeration cast over an open target space leaves a principled, reproducible absence at the coverage boundary — sharpened by an explicit Gödelian rhyme (no finite axiom schema proves every arithmetic truth) that strips out any domain-specific commitment and makes the pattern value-neutral. Transfer evidence is concrete and documented: the guideword-by-parameter cross-product of HAZOP maps directly onto the category-by-asset cross-product of STRIDE carrying the same coverage-gap diagnostic, the unstructured-complement repair appears as Tetlock's "consider the opposite," chaos engineering, and security red-teaming as recognisably one move, and the reproducibility test ("fresh operators hit the same gap") is a portable calibration check. What pins it at 4 rather than 5 is that its home register and signature test are framed around human deliberative re-execution; the formal test-coverage reading exists but the canonical instances cluster in human inquiry, so the structural skeleton is genuine but partly anchored to practice.

  • Composite substrate independence — 4 / 5
  • Domain breadth — 4 / 5
  • Structural abstraction — 4 / 5
  • Transfer evidence — 4 / 5

Relationships to Other Primes

One-hop neighborhood: parents above, mutual partners to the right, children below.Schema-BoundedBlind Spotcomposition: SchemaSchema

Parents (1) — more general patterns this builds on

  • Schema-Bounded Blind Spot presupposes Schema

    The file: parent-to-CONSEQUENCE relationship — the prime is the invariant property of applying any finite schema to an open target (the systematic absence at the coverage boundary). Presupposes schema as the instrument. The 0.967 nearest is schema — the instrument this is a consequence OF, NOT identity and NOT a reparent.

Path to root: Schema-Bounded Blind Spot → Schema → Abstraction

Neighborhood in Abstraction Space

Schema-Bounded Blind Spot sits in a moderately populated region (42nd percentile for distinctiveness): it has near-neighbors but no dense thicket of synonyms.

Family — Ordering, Sequencing & Dependency (12 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-06-14

Not to Be Confused With

The closest and most dangerous confusion is with schema itself, the embedding-nearest neighbour at similarity 0.97. The relationship is parent-to-consequence, not synonymy. A schema is the categorising instrument: a structured cross-product of slots that a process applies to classify, elicit, or evaluate. The schema-bounded blind spot is not that instrument but the invariant property of using any finite instance of it against an open target — the principled, reproducible absence at the schema's image boundary. One could hold the schema entirely fixed and correctly instantiated and the blind spot would still be present, because it is a theorem about finite enumeration over open spaces, not a defect of any particular schema. The practitioner who collapses the two reaches for "improve the schema" as if a better instrument closed the boundary, when the prime's whole content is that no finite schema closes it — the only boundary-acting move is to pair the schema with an unstructured complement.

A second genuine confusion is with bias. Both name a systematic, not random, defect in a reasoning process, and both are corrected at the process level rather than by exhorting individuals. But they sit on opposite sides of the access boundary. Bias is a distortion of what the process does register — a directional skew in the weighting, interpretation, or scoring of items that are inside the schema's image. The blind spot is the absence of items outside the image entirely. The distinction is exactly the bias-versus-occlusion split: bias is corrected by adjusting how in-coverage content is handled (re-weight, calibrate, debias the rater), whereas the blind spot is corrected only by extending coverage (a new schema, a complementary red-team). Conflating them leads to the error of debiasing a process toward content its schema could never have generated — polishing the handling of what is seen while whole regions remain structurally invisible.

A third confusion worth drawing is with selection_bias. Both involve a population the process fails to fully cover, and both produce confident conclusions from an incomplete picture. The difference is whether the missing items were samplable in principle. Selection bias arises when a sampling mechanism systematically under-includes parts of a population that could have been included — the fix is to model or repair the selection mechanism. The schema-bounded blind spot arises when items fall outside the schema's expressive range — there is no slot that could hold them, so no amount of better sampling within the schema reaches them. The reproducibility test discriminates the two: selection bias can shift when the sampling changes, while the blind spot reproduces under any re-execution that shares the schema's lineage.

For a practitioner these distinctions decide where to spend effort. If the defect is schema-level instrument design, refine the instrument; if it is bias, recalibrate the handling of seen items; if it is selection_bias, fix the sampling mechanism; and if it is the schema-bounded blind spot, accept that extension never closes the boundary and invest in the unstructured complement — the one move that acts on the coverage edge rather than within it. Misreading a methodological blind spot as any of its three neighbours sends the repair to a layer that leaves the gap exactly where it was.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.