Axiom¶

Prime #: 647
Origin domain: Mathematics
Subdomain: foundations of mathematics → Mathematics

Core Idea¶

An axiom is a claim a system declines to derive — a starting point accepted without proof so that the rest of the structure can be built on top of it. The defining structural commitment is to mark a stopping place for justification: every derivation chain in a formal system must terminate somewhere, and the axioms are the terminations the system has agreed in advance to honour. The same role appears wherever an inferential, normative, or design system has to bottom out — in mathematics (the foundational postulates of a theory), in logic (admitted formulae and rules of inference), in legal systems (constitutional clauses or jurisdictional first principles), in ethical frameworks (a supreme principle from which obligations are derived), in economic modelling (rationality and transitive preferences), and in software (the contract a component publishes, which callers are entitled to treat as given). What unites these is the structural position of being load-bearing without itself being justified within the system that depends on it.

The pattern is sharper than "an assumption." Three further structural features travel with the axiom role. Independence: a well-designed axiom is not derivable from the others — admitting a redundant axiom does no harm but obscures the structure. Consistency: the set of axioms must not entail a contradiction, since once inconsistent the system collapses and everything becomes derivable. Sufficiency: the axioms together should be strong enough to settle the questions the system was built to answer, and insufficient axioms leave intended results unprovable, forcing the system either to add an axiom or to acknowledge the question as undecided. These three constraints — independence, consistency, sufficiency — are how mature axiom-systems are diagnosed and revised, and they make a recurring pattern of change structurally legible: when a long-undecided question forces a new axiom, the move is not arbitrary but the resolution of a specific blind spot in an incomplete system.

How would you explain it like I'm…

The Bottom Block

When you build with blocks, the very bottom block just sits on the floor — you don't put anything under it, it's where you start. An axiom is like that bottom block for an idea: a starting rule everyone agrees to without asking why. You build all the other ideas on top of it.

Where The Why Stops

When you explain why something is true, you back it up with another reason, and that reason needs a reason too. If that went on forever you could never finish, so every system picks a few starting truths it accepts without proof. Those are axioms. In math, geometry starts with a handful of basic statements, and everything else is built on top of them. The axioms are the floor — you don't build below them, you build up from them.

Accepted Without Proof

An axiom is a claim a system refuses to prove on purpose, because every chain of reasoning has to stop somewhere, and the axioms are the agreed-upon stopping points. This is different from a lucky guess or a wild assumption: good axioms come with rules. They should be independent (you can't derive one from the others), consistent (they never lead to a contradiction), and sufficient (together they're strong enough to answer the questions the system cares about). When a question stays unanswerable for a long time, sometimes the fix is to add a new axiom — not randomly, but to patch a specific gap. The same role shows up in laws (a constitution), ethics (a top principle), and software (the contract a piece of code promises).

An axiom occupies a specific structural position: it is load-bearing for a system without itself being justified inside that system. Every derivation in a formal system must terminate, and axioms are the terminations agreed on in advance — the points where the system declines to ask 'why?' any further. This same role recurs across domains: foundational postulates in a mathematical theory, admitted formulas in logic, constitutional clauses in law, a supreme principle in an ethical framework, rationality assumptions in economics, the published contract of a software component. What unites them is being structurally foundational yet underived. Three constraints discipline a mature axiom set: independence (no axiom follows from the others, so none is redundant clutter), consistency (the set entails no contradiction, since an inconsistent system proves everything and collapses), and sufficiency (the axioms settle the intended questions). These three are also the diagnostic tools for revising axiom systems: when a long-undecided question forces a new axiom, that move is the principled resolution of a blind spot in an incomplete system, not an arbitrary addition.

Structural Signature¶

the inferential or design system — the derivation chains that must terminate — the stipulated, underived terminus accepted without proof — its independence from the other termini — the consistency constraint forbidding contradiction — the sufficiency requirement that the termini settle the intended questions

The pattern is present when each of the following holds:

A system that bottoms out. An inferential, normative, or design system derives claims from prior claims, and every derivation chain must terminate somewhere.
A stipulated terminus. Certain claims are accepted without proof within the system — the points at which justification is agreed in advance to stop.
Load-bearing-without-justification. The terminus is depended on by what is built on it, yet is not itself justified inside the system that depends on it; this structural position, not its content, is what makes it an axiom rather than a theorem.
Independence. A well-formed axiom is not derivable from the others; a redundant one does no harm but obscures the structure, and independence proofs proceed by exhibiting models satisfying the rest while differing on it.
Consistency. The set of axioms must not entail a contradiction, since an inconsistent set makes everything derivable and the system collapses.
Sufficiency. The axioms together must be strong enough to settle the questions the system was built to answer; insufficient axioms leave intended results unprovable, forcing addition of an axiom or acknowledgement that the question is undecidable.

These compose so that revision is local: changing a premise propagates downstream automatically, alternative axiom systems are compared by relative strength, and any sufficiently expressive system faces questions it can neither derive nor refute and must escalate or stipulate.

What It Is Not¶

Not an assumption. An assumption is any provisional premise; an axiom is the load-bearing, declined-to-derive terminus of a system, additionally constrained by independence, consistency, and sufficiency. Assumptions can be casual and many; axioms are deliberate and minimal. See assumption.
Not a constraint. A constraint restricts the space of admissible solutions; an axiom is a generative starting point from which the rest of the system is derived. One narrows; the other founds.
Not belief_formation. Belief formation is how an agent arrives at credences from evidence; an axiom is a structural position in a derivation system — accepted without proof so derivations can terminate — not a process of forming or updating belief. See belief_formation.
Not deductive_reasoning. Deduction is the process of deriving conclusions from premises; axioms are the premises at which that process bottoms out. The axiom is what deduction starts from, not the deriving itself.
Not a formal_system as a whole. A formal system is the entire apparatus (symbols, rules, axioms, theorems); the axiom is the specific underived-terminus role within it. The system includes its axioms but is not identical to them.
Common misclassification. Admitting as an axiom something the rest already entails (a redundant axiom that obscures structure) or trying to derive what is genuinely independent. The tell: can the claim be derived from the remaining axioms? If yes it is a theorem in disguise; if no it is a genuine terminus.

Broad Use¶

Mathematics and logic — set theory, the field and group axioms, the postulates of arithmetic, and the axiomatic method itself as the foundational discipline.
Legal and constitutional systems — founding documents and jurisdictional first principles from which case law is derived, amendable only through extraordinary procedures that reflect their load-bearing status.
Ethical frameworks — deontological systems that name their supreme principle, and welfare-maximising systems that take a single criterion as axiomatic and derive policy from it.
Economics — rationality, transitivity, and completeness of preferences as the axioms of choice theory, whose relaxation defines alternative behavioural models.
Software and systems — published contracts, type laws, and maintained invariants that callers are entitled to assume, with violations counting as bugs in the same sense that contradiction is a bug in a logical system.
Scientific modelling — conservation laws and the postulates of a physical theory, each tradition stipulating a small set of axioms and deriving the rest.

Clarity¶

Naming a claim an axiom forces the question of where the system bottoms out. Disputes that look substantive often turn out to be axiom-level: two parties are not disagreeing about the derivation but about the premises, and progress requires admitting which axioms each side is using. In law this is the distinction between interpretation and constitutional dispute; in ethics between an applied disagreement and a foundational one; in mathematics between a conjecture and a foundational question. Locating a disagreement at the axiom level changes what would resolve it — not more derivation, but a decision about premises — and the frame makes that relocation possible.

Axiom-naming also clarifies what a system cannot settle. The dramatic case is the formal result that any sufficiently rich consistent system contains undecidable statements; the pragmatic version is everywhere. An institution that cannot derive an answer from its current axioms must either add an axiom — legislate, amend, stipulate — or accept the question as outside its competence, and confusing these two options is a common pathology of rule-driven systems. The frame separates them cleanly: a question is either decidable from the current axioms, or it is not, and if not, the only honest moves are to extend the axioms or to declare the question beyond the system's reach. Pretending that an undecidable question has a derivable answer is precisely the error that axiom-awareness prevents.

Manages Complexity¶

Axiomatising a domain compresses an unbounded space of claims into a small axiom set plus a derivation procedure. Once the axioms and rules of inference are fixed, the rest of the system is determined, and arguments shift from "what is true?" to "what follows from the axioms?" — a far more tractable question, because it is mechanically decidable in principle. The axioms become the entire conceptual surface area the user must accept; everything else is downstream, and the whole edifice can be reasoned about by reasoning about its base.

This is also the discipline that lets one substitute alternative axiom systems and compare them. Dropping or replacing a single postulate yields a different but internally coherent system, and the change is local — confined to the axioms — while its consequences propagate downstream automatically. The complexity-management payoff is twofold: the axioms bound what must be taken on faith to a small set, and they localise the site of revision, so that exploring an alternative system means changing a premise rather than rebuilding the whole structure. A reasoner who holds the axiom pattern in mind knows where to push to change a system's conclusions — at its premises — and knows that the rest will follow, which converts the daunting prospect of revising a large body of derived results into the manageable task of revising its base.

Abstract Reasoning¶

Recognising the axiom pattern enables several reasoning moves. Relative-strength calibration: showing that one system can derive another's axioms, or vice versa, calibrates their strength without checking every result. Independence proofs: demonstrating that an axiom does not follow from the others — by exhibiting models that satisfy the others while differing on it — is a structural move that ports from mathematics to law (showing a clause is not implied by the rest) and to contract design (showing two requirements are independent if implementations satisfy any combination of them). Conservative extension: adding axioms that prove new results only about new terms, leaving the old fragment unchanged, is a structural pattern reused in modular software, legal supplementation, and theory revision.

A further move is reasoning about decidability and incompleteness: any system rich enough to encode arithmetic is either inconsistent or incomplete, and the structural consequence — that some questions in the domain cannot be answered from within the system — is a reusable insight for institutional design, warning that any sufficiently expressive rule system will face cases it cannot adjudicate from within and must either escalate or stipulate a new rule. Each of these inferences follows from the axiom's structural role — load-bearing, independent, consistency-constrained, sufficiency-tested — rather than from any particular substrate, which is why the pattern is purely structural: it carries no evaluative weight, no institutional binding, and its vocabulary travels across mathematics, law, software, and ethics essentially unmodified.

Knowledge Transfer¶

The transfers are clean and structural, because the axiom's role — a stipulated, load-bearing, underived terminus — is the same wherever a system must bottom out, and the three diagnostics travel with it. Independence diagnostics into institutional design: the mathematician's question "is this axiom needed?" transfers as the constitutional question "is this clause derivable from another?", so that pruning derivable clauses tightens the system while preserving genuinely independent ones is what makes amendment appropriately hard. Consistency-as-collapse into governance: the logical principle that a contradiction makes everything derivable transfers as the governance insight that mutually contradictory mandates do not merely create conflict but make any decision defensible from the rules, which is a recipe for arbitrary power — a structural warning that the consistency constraint is not a formal nicety but a guard against unbounded discretion.

The pattern ports further. The incompleteness limit into rule-system design: the structural fact that sufficiently powerful systems have undecidable questions transfers as the heuristic that any rich-enough rule system will have cases it cannot adjudicate from within, and must either escalate or stipulate. Sufficiency analysis into contract design: the question "do these axioms decide the results we care about?" transfers to "does this contract expose enough invariants for callers to do their jobs?", both being structural-completeness audits. The transferable core is the role itself: in any inferential, normative, or design system, identify the claims the system declines to derive, test them for independence, consistency, and sufficiency, and recognise that where a load-bearing premise is genuinely independent, multiple coherent systems exist and the choice between them is principled rather than derivable. That core does real work in mathematics, logic, law, ethics, economics, and software with no translation of vocabulary required, which is what makes the axiom one of the catalogue's cleanly structural foundational patterns — a formal role recognised, not imported, wherever justification must stop.

Examples¶

Formal/abstract¶

Euclid's parallel postulate is the historically decisive worked instance, and it exhibits independence, consistency, and sufficiency in action. The inferential system is plane geometry; the derivation chains that must terminate are the proofs of theorems; the stipulated, underived terminus is the set of five postulates Euclid accepts without proof. Four of them are intuitively immediate, but the fifth — that through a point not on a line there is exactly one parallel — is more complex, and for two millennia mathematicians tried to derive it from the other four, suspecting it was a redundant theorem rather than a genuine axiom. The independence question is exactly what those attempts were probing, and the resolution was structural: nineteenth-century work exhibited consistent models (hyperbolic geometry, where many parallels exist; elliptic geometry, where none do) that satisfy the other four postulates while differing on the fifth. Exhibiting such models is the canonical independence proof — it shows the fifth postulate is load-bearing and not derivable, so it is a real axiom, not a theorem in disguise. The consistency constraint is respected because each alternative geometry is internally non-contradictory; the sufficiency question is what each axiom set settles — Euclidean geometry decides the angle-sum of a triangle (exactly 180°), while the hyperbolic axiom set decides it differently (less than 180°). The structural lesson the prime makes legible: where a load-bearing premise is genuinely independent, multiple coherent systems exist, and the choice between them is principled rather than derivable — Euclidean geometry is not "more true," it is one consistent stipulation among several, each appropriate to a different space.

Mapped back: Plane geometry is the system, the proofs are the derivation chains, the five postulates are the stipulated termini, the failed two-thousand-year derivation attempts probed the parallel postulate's independence, and the non-Euclidean models are the independence proof — the axiom's role, with independence and sufficiency operating end-to-end.

Applied/industry¶

A software library's published API contract instantiates the axiom role in systems design. The inferential or design system is the ecosystem of code that depends on the library; the derivation chains are the call graphs by which client code achieves its results, each ultimately resting on the library's behaviour. The stipulated, underived terminus is the published contract — the documented signatures, type laws, and maintained invariants that callers are entitled to treat as given without re-deriving or re-verifying them. This is the load-bearing-without-justification position exactly: a caller does not prove that the library's sort function returns sorted output, it assumes it as an axiom of its own reasoning, and a violation of that contract is a bug in precisely the sense that a contradiction is a bug in a logical system. The three diagnostics transfer directly. Independence: the API designer asks "is this guarantee derivable from the others, or genuinely separate?" — pruning derivable promises tightens the contract while keeping the genuinely independent ones, the same move as removing a redundant axiom. Consistency: mutually contradictory guarantees (two methods that promise incompatible orderings of the same data) are catastrophic in the same way an inconsistent axiom set is — they make the library's behaviour unpredictable and "anything defensible," the contract-design analogue of a contradiction making everything derivable. Sufficiency: the completeness audit asks "does this contract expose enough invariants for callers to do their jobs?" — an insufficient API leaves intended client results unachievable, forcing the designer either to add a guarantee or to acknowledge the use-case as out of scope. The same role governs a constitution's foundational clauses (load-bearing, amendable only by extraordinary procedure that reflects their status, with mutually contradictory mandates making any decision defensible — a recipe for arbitrary power) and an ethical framework's supreme principle, from which obligations are derived.

Mapped back: The dependent codebase is the system, the call graphs are the derivation chains, the published API contract is the stipulated terminus callers treat as given, and the independence-consistency-sufficiency audit of the contract is the axiom-system diagnostic — the formal role recognised in systems design without translation.

Structural Tensions¶

T1 — Axiom versus Theorem (scopal). An axiom's defining mark is its structural position — load-bearing yet underived within the system — not its content; the same claim can be an axiom in one system and a theorem in another. The boundary is whether the claim is derivable from the others. The characteristic failure is admitting as an axiom something the rest already entails (a redundant axiom that obscures structure) or trying to derive what is genuinely independent (the two-thousand-year failed effort to prove the parallel postulate). Diagnostic: can the claim be derived from the remaining axioms? If yes it is a theorem masquerading as an axiom; if no it is a genuine, load-bearing terminus.

T2 — Independence versus Redundancy (measurement). A well-formed axiom is not derivable from the others; a redundant one does no logical harm but hides the system's true structure. The boundary is independence. The failure mode is treating a bloated axiom set as a clean foundation, where derivable "axioms" disguise which premises actually carry the weight — and pruning them is exactly what tightens a constitution or an API contract. Diagnostic: exhibit a model satisfying the other axioms but differing on this one (independence) or show it follows from them (redundancy). Only independence proofs, not intuition, settle which premises are foundational.

T3 — Consistency versus Collapse (limit). The axiom set must not entail a contradiction, because an inconsistent set makes everything derivable and the system collapses — in governance, mutually contradictory mandates make any decision defensible, a recipe for arbitrary power. The boundary is consistency. The failure mode is accumulating individually-reasonable axioms (or rules, or contract guarantees) whose conjunction is contradictory, after which the system proves anything and its discipline evaporates. Diagnostic: is there any model satisfying all axioms at once? If none exists the set is inconsistent, and the apparent richness is actually total collapse, not strength.

T4 — Sufficiency versus Undecidability (limit). The axioms must be strong enough to settle the intended questions, yet any sufficiently expressive consistent system contains statements it can neither prove nor refute — so strengthening to decide more eventually meets an incompleteness wall. The boundary is between insufficiency and undecidability. The failure mode is pretending an undecidable question has a derivable answer, forcing a verdict the axioms do not support, rather than honestly extending the axioms or declaring the question out of reach. Diagnostic: is the unanswered question decidable-but-not-yet-derived (add reasoning), insufficiently-axiomatised (add an axiom), or genuinely undecidable (escalate or stipulate)? Conflating these is the pathology axiom-awareness prevents.

T5 — Stipulation versus Discovery (sign/direction). Where a load-bearing premise is genuinely independent, multiple coherent systems exist and the choice between them is stipulated, not discovered — Euclidean geometry is one consistent choice among several, not the "true" one. The boundary is between what the system fixes by convention and what it derives. The failure mode is treating a stipulated axiom as a discovered truth, foreclosing the alternative consistent systems a different stipulation would open. Diagnostic: is this premise forced by the others (discovered) or a free choice among independent alternatives (stipulated)? Independent premises are principled choices, and mistaking them for necessities hides the design space.

T6 — Local Revision versus Downstream Propagation (coupling). The axiom's payoff is that revision is local — change a premise and the consequences propagate downstream automatically — but this same coupling means an innocent-looking change to a load-bearing axiom silently invalidates everything built on it. The boundary is the dependency from base to derived results. The failure mode is editing a foundational premise (a constitutional clause, an API invariant) as if it were a leaf, not seeing that the whole edifice resting on it shifts. Diagnostic: how much of the derived structure depends on this premise? The more load-bearing the axiom, the wider the automatic propagation, so revision must trace the downstream consequences, not just the local change.

Structural–Framed Character¶

Axiom sits at the structural pole of the structural–framed spectrum — aggregate 0.1, with four diagnostics at zero and one residual half-mark. It is very nearly a paradigm structural prime: the pattern is a pure formal-logical role, a claim a system declines to derive — load-bearing yet underived within the system that depends on it — subject to independence, consistency, and sufficiency. What makes it an axiom is its structural position, not its content, and that position is recognised across mathematics, logic, law, ethics, economics, and software essentially unmodified.

Four diagnostics read fully structural. Evaluative_weight is 0: an axiom carries no inherent approval — non-Euclidean geometry's parallel-denying axiom is adopted as a stipulation, not endorsed, and the role is value-neutral. Institutional_origin is 0 because the pattern is a formal-logical regularity (every derivation chain must terminate somewhere), not a construct bound to any human institution, even though particular axiom-systems live inside institutions like constitutions. Human_practice_bound is 0 because the underived-terminus role appears wherever any inferential or design system bottoms out — including software API contracts that callers treat as given, with no human practice required for the structural position to obtain. Import_vs_recognize is 0 because invoking it is recognition: identify the claims a system declines to derive and test them for independence, consistency, and sufficiency — no interpretive frame is imported, the terminus is simply located. The single residual score is vocab_travels at 0.5, and even that is generous: the words — axiom, postulate, independence, consistency, sufficiency — travel cleanly across law, software, and ethics, but the half-mark records that the term still reads most natively in a mathematical-logical register. The four zeros and the bare formal role keep it firmly structural; only that faint vocabulary accent lifts the aggregate to 0.1, exactly as the frontmatter records.

Substrate Independence¶

Axiom is a near-maximally substrate-independent prime — composite 5 / 5 on the substrate-independence scale, with both domain breadth and structural abstraction at the ceiling. The pattern is a pure formal-logical role — a claim a system declines to derive, load-bearing yet underived within the system that depends on it, subject to independence, consistency, and sufficiency — and what makes it an axiom is its structural position, not its content, so it is recognised essentially unmodified wherever an inferential, normative, or design system must bottom out: mathematical and logical postulates, constitutional first principles, ethical supreme principles, the rationality-and-transitivity axioms of choice theory, and software API contracts that callers are entitled to treat as given. That last case crosses the physical/practice line — the underived-terminus role obtains in a published contract with no human practice required for the structural position to hold — and the diagnostics (independence proofs, consistency-as-collapse, the incompleteness limit, sufficiency audits) transfer with the role into institutional design and contract design. The transfer-evidence sub-score sits at 4 rather than 5 only because the concrete cross-domain instances, while real and varied, are documented somewhat less exhaustively than the formal role itself; a faint mathematical-logical accent on the vocabulary is the sole residue, and even that travels cleanly, which is why the composite still reads 5.

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

Relationships to Other Primes¶

Parents (1) — more general patterns this builds on

Axiom is a kind of Epistemic Mode Of A Proposition

The file: axiom is another single mode (foundationally-true-within-a-system, do-not-refute-from-within). One value of the mode dimension. Clean child.

Path to root: Axiom → Epistemic Mode Of A Proposition

Neighborhood in Abstraction Space¶

Axiom sits among the more crowded primes in the catalog (11^th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Formal Methods & Idealized Models (31 primes)

Nearest neighbors

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

Not to Be Confused With¶

The closest confusion is with the broader notion of an assumption, and the difference is the discipline that an axiom carries. Any provisional premise taken on for the sake of argument is an assumption; assumptions can be casual, numerous, tacit, and untested. An axiom is the deliberately chosen, load-bearing terminus of a derivation system, and it is held to three further constraints that ordinary assumptions are not: independence (it is not derivable from the other axioms), consistency (the set entails no contradiction), and sufficiency (the axioms together settle the intended questions). The structural marker is the conjunction of being depended-on by everything built above it and being subject to the independence-consistency-sufficiency diagnostics by which mature axiom-systems are revised. An assumption can be added or dropped with little ceremony; an axiom's change propagates automatically through every derived result, which is why constitutional clauses and API contracts are amendable only by extraordinary procedure. Treating an axiom as a casual assumption invites editing a foundational premise as if it were a leaf (the prime's T6); treating every assumption as an axiom over-formalises provisional premises that never carried the system's weight.

A second genuine confusion is with belief_formation, the embedding-nearest prime. Belief formation is the epistemic process by which an agent arrives at and updates credences from evidence — a matter of justification, confidence, and revision in light of new data. An axiom is a structural role in a derivation system: a claim the system declines to derive, accepted without proof precisely so that derivation chains can terminate. The two are orthogonal. An axiom need not be believed at all — non-Euclidean geometry's parallel-denying axiom is adopted as a stipulation to explore a consistent alternative, not because anyone forms the belief that no parallels exist; and an agent forms beliefs about countless things that play no axiomatic role in any system. The distinction matters because it separates two kinds of "starting point": the psychological starting point of an agent's credences (belief formation) and the logical starting point of a system's derivations (axiom). Conflating them imports questions of evidence and justification into what is really a question of stipulation and structural position — Euclidean geometry's axioms are not "more justified beliefs," they are one consistent stipulation among several.

A third worth drawing is against deductive_reasoning. Deduction is the process of deriving conclusions that follow necessarily from premises; an axiom is what the process starts from. The relationship is that deduction operates on axioms (and prior theorems) to produce new theorems, so the axiom is the input and the derivation the activity. Identifying the axiom with the reasoning conflates the foundation with the building done on it: a system can hold the same axioms while admitting different rules of inference, and the same deductive machinery can run on different axiom sets. Recognising the axiom as the terminus of justification — the place where deriving stops — is exactly what distinguishes it from the deriving itself, and it is what makes the incompleteness and undecidability results legible (some statements cannot be reached by deduction from the axioms, however sound the reasoning, so the system must extend its axioms or declare the question beyond reach).

For a practitioner the distinctions decide what kind of move is in play. Confusing an axiom with an assumption strips away the independence-consistency-sufficiency discipline and the load-bearing propagation; confusing it with belief_formation imports justification where stipulation is operating; and confusing it with deductive_reasoning mistakes the foundation for the activity built on it. Asking "is this claim the place the system declines to derive, held to independence-consistency-sufficiency?" is what identifies a genuine axiom among its neighbours.

Solution Archetypes¶

No catalogued solution archetypes reference this prime yet.