Explanatory Overlay Masking Structural Debt¶
Core Idea¶
Explanatory overlay masking structural debt is the pattern in which an artefact carries an avoidable amount of structural confusion — a function with too many responsibilities, a contract with ambiguous operative language, a process with unclear ownership, a chapter with unstable organisation — and rather than restructuring the artefact, its owner adds an explanatory overlay (comments, clarifying clauses, runbooks, FAQs, instructor's notes, README sprawl) that makes the artefact locally readable. The overlay reduces the immediate reader's confusion; it does not retire the underlying structural problem; and its very presence reduces the perceived urgency of the refactor that would. The structural commitment is that informational correction is being used as a substitute for, not a complement to, structural correction, and the substitution is silently corrosive: it buys local legibility at the cost of entrenching the confusion it papers over.
The pattern has five load-bearing parts. There is an artefact carrying structural confusion that could in principle be restructured. There is an explanatory overlay that supplies the missing structure informationally rather than structurally. There is an enforceability gap: the overlay is not statically checkable against the artefact, so it drifts as the artefact changes, falling out of date in a characteristic way. There is a crowding-out mechanism in which the overlay's local readability lowers the felt urgency of the structural fix. And there is a failure mode at scale: the overlay grows faster than the artefact, becomes its own maintenance burden, and eventually contradicts or lags the artefact, producing the worst of both worlds — a confusing artefact and a stale, voluminous overlay. The prime's distinctive content is the recognition that the second and fourth elements are the engine: the overlay is structurally brittle because it is uncheckable, and it is self-perpetuating because it makes the situation just tolerable enough that the structural fix is never scheduled.
How would you explain it like I'm…
A Note On The Mess
Explaining Instead Of Fixing
Comments Papering Over Debt
Structural Signature¶
the artefact carrying avoidable structural confusion — the explanatory overlay supplying the missing structure informationally — the enforceability gap (the overlay is not checkable against the artefact) — the crowding-out mechanism by which local readability lowers felt urgency of the fix — the drift signature as the overlay falls out of date — the at-scale failure where overlay outgrows artefact
A configuration exhibits explanatory overlay masking structural debt when each of the following holds:
- An artefact with structural confusion. Something authored carries an avoidable amount of structural confusion that could in principle be restructured: an over-responsible function, an ambiguous contract, an unclear process, an unstable chapter, a tangled architecture.
- An explanatory overlay. Rather than restructuring, the owner adds informational matter that supplies the missing structure on the side — comments, clarifying clauses, runbooks, FAQs, instructor's notes, README sprawl — making the artefact locally readable.
- An enforceability gap. The overlay is not statically checkable against the artefact; nothing forces the two to agree, distinguishing the human-only surface from the checkable surface (compiler, operative terms, ownership assignment).
- A crowding-out mechanism. The overlay's local readability lowers the felt urgency of the structural fix, so the cheap informational patch substitutes for — rather than complements — the structural correction, foreclosing it.
- A drift signature. Because it is uncheckable, the overlay falls out of date in a characteristic way as the artefact changes; an overlay noticeably older than what it covers is debt being concealed rather than documented.
- An at-scale failure mode. The overlay grows faster than the artefact, becomes its own maintenance burden, and eventually contradicts or lags it — yielding the worst of both worlds: a confusing artefact and a stale, voluminous overlay.
The components compose around a single test — could structure carry this information? — which separates honest documentation (intent, rationale, history, out-of-band constraint, that no structure could carry) from overlay (information structure could carry but does not), and reads the overlay-to-artefact ratio and its trend as a substrate-neutral measure of accumulating structural debt.
What It Is Not¶
- Not
technical_debt. Technical debt is the general deferred-cost of structural shortcuts; this prime is the specific mechanism by which an explanatory overlay masks such debt and crowds out its repair. Debt is the liability; the overlay is the concealment. - Not
traceability. Traceability links artefacts to origins for accountability; this prime is about informational matter substituting for structural fix, whose defining flaw is the enforceability gap — the overlay is uncheckable against the artefact. - Not honest documentation (
provenance). Recording intent, rationale, or history that no structure could carry is virtuous; overlay is information structure could carry but does not. The could-structure-carry-this test separates them. - Not
exaptation. Exaptation is repurposing a feature for a new function; embedding nearness is misleading. This prime is the concealment of unfixed structural confusion by an explanatory layer, not a creative reuse. - Not
indirection. Indirection resolves a reference through a level of pointer as a structural device; the overlay is an uncheckable human-only layer that supplies missing structure informationally, not a structural redirection. - Common misclassification. Treating all thickening documentation as either healthy or as debt. Catch the error with the prime's test — could structure carry this? If yes and it sits in commentary, it is overlay debt; if no structure could carry it (why, history, out-of-band constraint), it is honest documentation worth keeping.
Broad Use¶
- Software engineering: comments compensating for poor naming and mixed-responsibility functions; the "comments" code smell rests precisely on the claim that a section needing an explanatory comment is often a section that should be extracted into a well-named function.
- Legal drafting: clarifying clauses, defined-terms sections, and "for the avoidance of doubt" provisions that grow to compensate for structurally ambiguous operative language.
- Organisational design: process documents, runbooks, and RACI matrices that compensate for unclear ownership; a thick "who-does-what" document is often a signal that the org structure itself is the source of confusion.
- Pedagogy and textbooks: chapter introductions, lecturer's notes, and supplementary glossaries that compensate for material that does not present its own structure; a textbook requiring extensive instructor's notes shifts the clarity burden onto every classroom.
- Engineering documentation: README sprawl and tribal-knowledge wikis that compensate for architectural confusion; onboarding-document size is often inverse to architectural clarity.
- Regulatory guidance and UX: agency FAQs that compensate for ambiguous regulations, and tooltips or onboarding modals that compensate for unintuitive interaction design — "needs a tutorial" is the UX form of the smell.
Clarity¶
Naming the pattern forces attention onto a distinction ordinary language conflates: load-bearing information that sits on the checkable surface of the artefact (the compiler, the operative contract terms, the assigned process owner, the syllabus structure) versus load-bearing information that sits on the human-only surface and depends on the reader actually reading the overlay. Once that distinction is sharp, a routine diagnostic question becomes available: "could this information be migrated onto the checkable surface instead?" The clarifying force is to make the choice between informational and structural correction explicit at the moment it is made, rather than letting the cheaper informational move win by default.
The framing also exposes a recurring and otherwise unresolvable debate. Two reasonable practitioners agree an artefact is locally confusing; one argues for a better explanation, the other for restructuring. The prime supplies the structural argument for restructuring — the explanation does not retire the confusion, drifts under maintenance, and crowds out the fix — without denying the legitimate short-term value of the overlay. A second clarity benefit is the separation of honest documentation (information not derivable from structure: intent, rationale, history, out-of-band constraint) from overlay documentation (information that could be carried by structure but is not). Both look like "documentation"; only the second is the failure mode, and the prime gives a test — could structure carry this? — that tells them apart.
Manages Complexity¶
The pattern manages complexity by making the structural-versus-informational choice a first-class object. Maintaining an artefact and its overlay is a coupled problem, and their drift is the dominant source of latent defect over time; diagnosing a confusing system by asking what is the artefact and what is the overlay, and where is the overlay making the artefact tolerable but harder to fix? converts a diffuse "this is messy" complaint into a tractable question with a defined answer set. The complexity absorbed is the conflation of two maintenance problems — keeping the artefact correct and keeping its commentary current — that compound each other when treated as one.
A second compression is that the intervention catalogue is shared across substrates. The structural fix is always one of a small set: rename (so the identifier carries the meaning the comment carried), decompose (so each piece is small enough to be self-explanatory), decouple (so the informational warning is no longer needed), redraft (so operative language no longer needs clarification), restructure (so organisational confusion no longer needs documentation), or reorganise (so a chapter's narrative carries the clarity its introduction substituted for). These six moves recur in every substrate listed, which means a practitioner who has internalised them in software can apply them to legal drafting or curriculum design without re-deriving the remedy. The prime also supplies a portable metric: the ratio of overlay to artefact is a substrate-neutral diagnostic of accumulating structural debt, and a sharp rise in that ratio is an early-warning signal in any authored-artefact substrate.
Abstract Reasoning¶
The prime trains a reasoner to ask, of any clarifying text, whether the information it carries could in principle be migrated onto the artefact's checkable surface, and if so to treat the text as overlay rather than as honest documentation. It licenses a set of substrate-neutral inferences. The first is the checkable-versus-uncheckable surface distinction: information enforced by the system (the compiler, the operative terms, the ownership assignment) is structurally robust, while information enforced only by the reader's attention is structurally brittle, so the location of load-bearing information predicts its decay. The second is the overlay-drift signature: because the overlay is uncheckable against the artefact, it falls out of date in a characteristic way, and an overlay noticeably older than the artefact it covers is structural debt being concealed rather than documented.
The deeper inference is the crowding-out diagnosis. When an organisation responds to recurring confusion by adding more documentation rather than by restructuring the artefact, it is paying the overlay tax recurrently while deferring the structural fix indefinitely, and the prime predicts that this response is self-perpetuating: each round of overlay makes the situation just tolerable enough that the structural fix is never scheduled. The reasoner is thereby led to read overlay growth as a rate — the ratio of overlay to artefact, and its trend — rather than as a static fact, and to recognise that the cheap informational patch and the expensive structural fix are not complements but substitutes, so that choosing the former forecloses the latter. The prime also supports the converse inference: that some thickening documentation is honest (recording intent, rationale, history, or out-of-band constraint that no structure could carry), and that adding more of this kind is virtuous, so the diagnostic must distinguish the two rather than treating all growth as debt.
Knowledge Transfer¶
The transferable content is the artefact / overlay / enforceability-gap / crowding-out / drift-signature diagnostic together with the shared six-move repair catalogue and the honest-documentation-versus-overlay test. The role mappings are regular across substrates: the artefact is a function, a contract, a process, a chapter, an architecture, a regulation, an interface; the overlay is a comment, a clarifying clause, a runbook, an instructor's note, a README, a guidance document, a tooltip; the checkable surface is the compiler, the operative terms, the ownership assignment, the syllabus, the type system; the drift signature is an overlay noticeably older than the artefact it covers, internal contradictions inside the overlay, and overlay growth outpacing artefact growth.
The transfers are reuses of one diagnostic rather than surface resemblances. The software insight that a section requiring extensive commentary is often a section that should be restructured ports directly to legal drafting: "give the noun a better name," "promote the recital into an operative clause," "split the section" are rename, extract, and decompose in legal vocabulary. The engineering rhythm of refactoring before writing more docs ports to organisational design, where a re-org that retires the need for the RACI matrix dominates a clearer RACI matrix. The SaaS observation that a required onboarding tutorial is evidence of a design problem ports to pedagogy, where a chapter needing extensive instructor's notes is the educational analogue. The regulatory insight that recurring need for guidance documents should trigger amendment rather than substitute for it ports to corporate policy, technical standards, and contract-template maintenance. In every case the load-bearing move is the same: make each overlay clause visible as either honest documentation worth keeping or structural debt awaiting retirement, and resist the cheap informational patch that defers the structural fix indefinitely. What differs across substrates is only the name of the compiler-equivalent that could have carried the information; the structural reasoning is invariant.
Examples¶
Formal/abstract¶
The "comments" code smell in software is the prime's defining instance, and it makes the checkable-versus-uncheckable surface concrete. Consider a function named process that takes a flag argument and is preceded by a twelve-line comment block explaining "if flag is true this validates and persists; if false it only validates; do not call with false during a transaction; the second return value is the error count." The artefact carrying structural confusion is the over-responsible function with a meaningless name and an overloaded signature. The explanatory overlay is the comment block, supplying the missing structure informationally. The enforceability gap is decisive: the compiler checks the code but not the comment, so nothing forces the two to agree. The crowding-out mechanism operates because the comment makes the function locally readable, lowering the felt urgency of the refactor. The drift signature appears predictably: a later developer changes the flag's behaviour but not the comment, and now the overlay is worse than nothing — confidently wrong. The at-scale failure is the file where comments outweigh code and contradict it. The single test resolves the case: could structure carry this information? Yes — rename process to validateAndPersist, split it into two single-responsibility functions, and promote the error count into a typed result. Each fix migrates information from the uncheckable comment onto the checkable surface (the compiler, the names, the types), retiring the overlay rather than maintaining it. Contrast honest documentation — a comment recording why a non-obvious algorithm was chosen — which no structure could carry and which is virtuous to keep. Mapped back: the function is the artefact, the comment block is the overlay, the compiler is the checkable surface, the stale-comment-after-behaviour-change is the drift signature, and rename/decompose/promote are the structural repairs the prime prescribes over thicker commentary.
Applied/industry¶
Two applied instances run the identical diagnostic in non-software substrates. First, organisational design and the RACI matrix: the artefact is an organisation whose ownership of a recurring process is genuinely unclear. Rather than restructuring reporting lines and decision rights, the org adds an explanatory overlay — a thick "who-does-what" RACI document, a runbook, a wiki of tribal knowledge. The enforceability gap is that nothing forces the document to match how decisions actually get made, so it drifts: an overlay describing a reorganised team three quarters ago is debt being concealed, not documented. The crowding-out mechanism is that the document makes the confusion just tolerable enough that the structural fix — clarifying ownership — is never scheduled, and the at-scale failure is a sprawling process-doc library that contradicts itself. The repair is structural: a re-org that retires the need for the RACI matrix dominates a clearer RACI matrix. Second, legal drafting: the artefact is a contract with structurally ambiguous operative language; the overlay is a growing thicket of "for the avoidance of doubt" clauses and defined-terms sections compensating for it. The same six-move catalogue applies in legal vocabulary — rename a noun that the definition struggles to pin down, promote a recital into an operative clause, decompose an overloaded section — and the same test sorts honest from overlay: a clause recording out-of-band negotiated intent is honest, while one clarifying language that could simply be redrafted is debt. In both, the prime supplies the structural argument that resolves the recurring "better explanation versus restructure" debate, and the overlay-to-artefact ratio and its trend is the portable early-warning metric. Mapped back: the org and the contract are artefacts; the RACI doc and the avoidance-of-doubt clauses are overlays; reporting lines and operative terms are the checkable surfaces; and the cross-substrate move is identical — migrate each overlay item onto the checkable surface or recognise it as honest documentation, resisting the cheap informational patch that defers the structural fix.
Structural Tensions¶
T1 — Overlay as Substitute versus Overlay as Complement (sign/direction). The prime's load-bearing claim is that informational correction is being used as a substitute for, not a complement to, structural correction. The tension is that the same overlay can play either role. The characteristic failure mode is the substitution: the comment, clause, or runbook makes the artefact locally readable and thereby forecloses the refactor it should have accompanied. The diagnostic: ask whether the overlay buys time toward a scheduled structural fix or instead of one — an overlay added with no plan to retire the confusion it covers is a substitute, and the cheap patch has won by default against the expensive fix.
T2 — Checkable Surface versus Human-Only Surface (coupling). Load-bearing information can sit on the checkable surface (compiler, operative terms, ownership assignment) or the human-only surface (comments, FAQs) that depends on the reader actually reading it. The tension is between where information lives and how robust it is. The failure mode is putting load-bearing information on the uncheckable surface, where nothing forces it to agree with the artefact. The diagnostic test the prime names: could structure carry this information? If yes and it sits in an overlay, it is brittle by construction — migrate it onto the checkable surface; if no structure could carry it (intent, rationale, history), it is honest documentation and belongs in the overlay.
T3 — Overlay Currency versus Drift (temporal). Because the overlay is uncheckable against the artefact, it drifts as the artefact changes, falling out of date in a characteristic way. The tension is between an overlay that tracks the artefact and one that lags it. The failure mode is the confidently-wrong overlay: a comment describing behaviour the code no longer has, worse than no comment at all. The diagnostic: compare the age and content of the overlay against the artefact — an overlay noticeably older than what it covers, or internally contradictory, is debt being concealed rather than documented, and its staleness is a signal the structural fix was deferred past the artefact's last change.
T4 — Honest Documentation versus Overlay Debt (scopal). Both look like "documentation," but only one is the failure mode: honest documentation records what no structure could carry (intent, rationale, out-of-band constraint), while overlay records what structure could carry but does not. The tension is that growth of the first is virtuous and growth of the second is debt. The failure mode is treating all documentation growth as either healthy or as debt, missing the partition. The diagnostic: apply the could-structure-carry-this? test clause by clause — virtuous thickening (recording why) must be distinguished from corrosive thickening (substituting for structure), because conflating them either prunes useful rationale or licenses unbounded overlay.
T5 — Overlay-to-Artefact Ratio: Static Snapshot versus Trend (scalar). The portable metric is the ratio of overlay to artefact, but its diagnostic value is in the trend, not the snapshot. The tension is between reading the ratio as a fixed fact and reading it as a rate. The failure mode is complacency about a high-but-stable ratio or alarm at a low-but-rapidly-rising one, mis-ranking which artefacts are accruing debt fastest. The diagnostic: track the ratio's trajectory — a sharp rise in overlay growth outpacing artefact growth is the early-warning signal of accumulating structural debt, and the rate of accretion, not the current level, predicts where the at-scale failure (overlay outgrowing and contradicting the artefact) will land first.
T6 — Local Readability versus Global Maintainability (scalar). The overlay genuinely improves local readability for the immediate reader; its cost is borne globally and later, as the coupled artefact-plus-overlay drift becomes the dominant source of latent defect. The tension is between the real short-term value to one reader and the long-term burden on every maintainer. The failure mode is optimising for the local reader's immediate comprehension while entrenching a maintenance liability that compounds across the artefact's life. The diagnostic: weigh the overlay's local clarity benefit against the coupled-maintenance cost it creates — an overlay that makes today's reader comfortable while ensuring tomorrow's maintainer faces a confusing artefact and a stale, voluminous commentary has traded a small local gain for a large global cost.
Structural–Framed Character¶
Explanatory overlay masking structural debt sits on the framed side of the structural–framed spectrum, with an aggregate of 0.5 — right at the framed boundary. There is a genuine relational skeleton (an artefact, an overlay supplying missing structure informationally, an enforceability gap, a crowding-out mechanism), but the prime cannot be stated without human authorship and editorial practice.
The decisive push toward framed is human_practice_bound (1.0): the pattern lives entirely in human-authored artefacts — comments, contracts, runbooks, textbooks, READMEs, guidance documents — and presupposes an author who chose to patch rather than restructure, an editorial culture that tolerates the overlay, and a reader who consumes it. There is no physical or biological substrate where an "explanatory overlay masking structural debt" exists, because nothing authors an overlay and nothing has structural debt absent a maintaining practice. Two further diagnostics carry a half-point. The word "debt," and the framing of overlay as corrosive concealment, carries normative load (evaluative_weight 0.5): the prime judges the substitution as a liability against a standard of good structure. And the vocabulary leans toward software-maintenance and editorial terms — refactor, technical debt, drift, checkable surface (vocab_travels 0.5), so a reader partly translates carrying it to legal drafting or pedagogy. Invoking it also partly IMPORTS a maintenance-discipline framing (import_vs_recognize 0.5). The one structural anchor is institutional_origin (0.0): the artefact/overlay/enforceability-gap relation is definable without rooting in a specific institution. But the dominant human-authorship binding and the normative "debt" load place the prime squarely on the framed side, exactly as the 0.5 aggregate records.
Substrate Independence¶
Explanatory overlay masking structural debt is a moderately substrate-independent prime — composite 3 / 5 on the substrate-independence scale. Its domain breadth sits at 3: the pattern of an informational overlay substituting for a structural fix recurs across software engineering (comments compensating for poor naming), legal drafting ("for the avoidance of doubt" clauses over ambiguous operative language), organisational design (thick RACI documents over unclear ownership), pedagogy (instructor's notes over self-unexplaining material), engineering documentation (README sprawl over architectural confusion), and regulatory guidance and UX (FAQs and tooltips over ambiguous rules and interfaces). These are distinct fields, but every one is a human-authored artifact substrate in which an author adds explanation rather than restructuring the thing explained; there is no physical or biological instance, which is what caps the breadth. Its structural abstraction is 3: the skeleton (an artefact with a structural defect, an overlay that explains around it rather than repairing it) is relational, but it carries an evaluative judgment — the overlay is a "smell" signalling debt — that is not value-neutral. The transfer evidence is the strongest component at 4: the "needs-a-comment / needs-a-tutorial / needs-a-FAQ" diagnostic is demonstrably recognised across the code-smell literature, legal drafting, org design, and UX as the same signal, with concrete named instances in each. The human-artifact ceiling holds the composite at a defensible 3.
- Composite substrate independence — 3 / 5
- Domain breadth — 3 / 5
- Structural abstraction — 3 / 5
- Transfer evidence — 4 / 5
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
-
Explanatory Overlay Masking Structural Debt is a kind of Technical Debt
The file states it outright: "the broad concept this prime sits inside" is technical_debt, and this prime is "a specific mechanism of incurring and, crucially, concealing such debt." technical_debt's own file is consistent (general deferred-cost liability). The differentia is the crowding-out/concealment mechanism — a genuine is-a, not a mere contrast. technical_debt is a real candidate slug; it is also the prime's listed cross-ref. Direction verified (overlay-masking is one species of technical debt). NOT a reparent to exaptation (the 0.923 nearest is a vector artifact, explicitly dismissed in-file).
Path to root: Explanatory Overlay Masking Structural Debt → Technical Debt → Intervention Stack Accretion → Ratchet Effect → Path Dependence → Dependency
Neighborhood in Abstraction Space¶
Explanatory Overlay Masking Structural Debt sits in a sparse region of abstraction space (77th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Cue-Outcome Drift & Silent Failure (18 primes)
Nearest neighbors
- Exaptation — 0.70
- Traceability — 0.70
- Provenance — 0.69
- Reification — 0.69
- Property Rights — 0.69
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
The most consequential confusion is with technical_debt, the broad concept this prime sits inside. Technical debt is the general liability incurred when a structural shortcut is taken to move faster now at the cost of harder maintenance later — any deferred restructuring, regardless of how it is deferred. Explanatory overlay masking structural debt is a specific mechanism of incurring and, crucially, concealing such debt: the structural confusion is left in place and an explanatory layer (comments, clauses, runbooks) is added that makes the artefact locally readable. The invariant that distinguishes them is the crowding-out mechanism: ordinary technical debt is often visible and tracked as a known liability, whereas this prime's overlay actively lowers the felt urgency of the fix, so the debt is not merely deferred but disguised as resolved. A practitioner who files an overlay-masked artefact under generic technical debt will track it as a known cost to be paid down on schedule, missing that the overlay has removed the very pressure that would have scheduled the payment. The prime's contribution is naming the mechanism by which debt becomes self-perpetuating rather than merely outstanding.
A second genuine confusion is with honest documentation, which the prime addresses through provenance as its catalog representative. Recording why a non-obvious algorithm was chosen, what out-of-band constraint a clause encodes, or what historical decision a process reflects is virtuous and irreplaceable — no structure could carry that information, and adding more of it is good. Overlay documentation is its mirror image: information that structure could carry (a better name, a decomposed function, a redrafted clause, clarified ownership) but which is supplied informationally instead. The two look identical on the surface — both are "documentation" that thickens over time — which is exactly why they are confused, and why the prime supplies the discriminating test: could structure carry this? The distinction matters operationally because the remedies are opposite: honest documentation should be preserved and even expanded, while overlay should be retired by migrating its content onto the checkable surface. An analyst who lacks the distinction will either prune useful rationale as if it were debt or license unbounded overlay as if it were documentation.
A third confusion, and the prime's nearest embedding neighbour, is exaptation (similarity 0.92) — almost certainly a vector-space artefact of shared vocabulary about features acquiring new roles, rather than a true structural kinship. Exaptation is the creative repurposing of an existing feature for a function it was not selected for: a structure that turns out to serve a new end, a net gain. Explanatory overlay masking structural debt is the concealment of an unfixed problem: an explanatory layer that papers over confusion the artefact should have shed, a net liability. The two point in opposite evaluative directions — exaptation is opportunity realised, overlay is repair deferred — and share no invariant beyond the loose notion of something serving a role. Treating an overlay as a clever exaptation would be precisely the rationalisation the prime warns against: dressing up the failure to restructure as an inventive reuse.
For a practitioner the through-line is to locate the overlay precisely. Ask whether the situation is generic deferred debt (technical debt, to be tracked and scheduled), virtuous recording of the underivable (honest documentation/provenance, to be kept), creative reuse (exaptation, to be welcomed), or the specific corrosive case this prime names — an uncheckable explanatory layer that makes structural confusion locally tolerable and thereby forecloses the fix. Only the last is debt being concealed rather than merely owed, and only the could-structure-carry-this test reliably tells it apart from its virtuous look-alikes.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.