Ontology Audit¶
Procedure — instantiates Category Boundary Audit
Checks whether a category and its boundary still cohere with the wider domain model of entities, relations, and contexts it is supposed to live inside.
Ontology Audit looks outward from a category to the whole model of the world it belongs to. It asks not "is this line fair?" or "does this scheme browse well?" but a consistency question: does this category still cohere with everything else we say exists in the domain, and with how those things relate? A category does not float free — it sits inside a web of other entities, of is-a and part-of relations, of contexts and revision rules — and it can quietly fall out of step with that web when the domain grows or new entities are discovered. Its defining move is to test the boundary for contradiction with the broader ontology: a category that once fit can become incoherent not because any single case is misjudged but because keeping the old line would force the whole model to say inconsistent things.
Example¶
For most of a century, "planet" was a stable category in the model of the solar system. Then trans-Neptunian discoveries — Eris among them, comparable in size to Pluto — strained it. An Ontology Audit of "planet" is exactly what the field faced: keep the old boundary and the domain model must admit a growing, open-ended list of planets on the same footing as Earth and Jupiter; hold the count at nine and the boundary contradicts its own criteria, since the newly found bodies satisfy whatever made Pluto qualify. The category had fallen out of coherence with the broader ontology of solar-system objects — asteroids, comets, and the newly populous Kuiper belt.
The resolution was a boundary revision that restored coherence rather than a verdict on Pluto alone: the International Astronomical Union's 2006 definition[1] added the relational criterion that a planet must have "cleared its orbital neighborhood," and split off a new sibling entity, dwarf planet, to hold Pluto and Eris consistently. The outcome is what an ontology audit aims at — a category whose boundary once again fits the entities and relations around it, at the cost of a deliberate, purpose-checked redefinition.
How it works¶
- Place the category in the model. Locate it among the domain's other entities and the relations — is-a, part-of, mutually-exclusive-with — that connect them.
- Test for coherence. Check whether the boundary contradicts sibling entities, leaves gaps in coverage, or forces the model into an open-ended or inconsistent commitment.
- Re-check the purpose against the model. Ask whether the category's purpose still matches what the broader model is for, or whether the domain has moved on.
- Locate the contradiction. Name precisely where the current line and the ontology disagree.
- Recommend a coherence-restoring revision. Redefine, split off a new entity, merge, or relocate the category so the whole model is consistent again.
Unlike Taxonomy Review, which works on the internal shape of one scheme, Ontology Audit tests a category's external fit with the entire domain model.
Tuning parameters¶
- Ontology scope — how much of the surrounding model is brought into the check, from a few neighboring categories to the whole domain. Wider scope catches deeper contradictions but is far heavier.
- Relation coverage — which relation types are tested (is-a, part-of, exclusivity, dependency). Checking more relations finds more incoherence but multiplies the work.
- Realism versus pragmatism — whether the audit seeks a philosophically clean model or one that merely serves downstream use well enough. Purity can over-engineer; pragmatism can leave latent contradictions.
- Legacy-compatibility weight — how much established usage and downstream systems constrain the revision, trading coherence against disruption.
When it helps, and when it misleads¶
Its strength is keeping categories coherent as a domain grows, catching the contradictions that appear when new entities strain an old boundary — the failures that are invisible from inside any single category.
Its failure mode is ontological over-engineering: reclassifying for the elegance of the model at the expense of people who use the old categories every day, or sliding into interminable definitional debate ("but what is a planet, really?") that produces coherence and no value. A classic misuse is premature formalization — locking a clean ontology before the domain is understood well enough to warrant it. The guarding discipline is to bind every revision to the category's purpose and its downstream use, and to keep the audit's ontological commitment[n1] honest — revising the model to fit what the domain must actually account for, not the reverse.
How it implements the components¶
Ontology Audit realizes the coherence face of the archetype — the components that test a category against the wider model and decide its fit:
category_under_audit— takes the category as an entity within a larger domain model, not as a standalone line.category_boundary— tests the boundary for contradiction with sibling entities and the relations that bind them.boundary_purpose_statement— re-checks whether the category's purpose still matches what the broader model is for.boundary_revision_decision— issues the coherence-restoring redefine, split, merge, or relocate.
It does not assemble and work a corpus of hard cases (edge_case_register) — that is Edge-Case Analysis; nor does it record the category's owner and version history (boundary_authority_record), which is Category Governance Record.
Related¶
- Instantiates: Category Boundary Audit — supplies the check that a category still coheres with the domain model the audit sits inside.
- Consumes: Taxonomy Review — an ontology audit often builds on a scheme's structural map before testing its external fit.
- Sibling mechanisms: Boundary Critique Review · Eligibility Audit · Taxonomy Review · Classification Fairness Review · Edge-Case Analysis · Category Governance Record · Appeals Case Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Ontology Audit operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it checks whether a category and its boundary still cohere with the wider domain model of entities, relations, and contexts it is supposed to live inside.
Independent corroboration: The frozen evidence defines Ontology Audit as 'Checks whether a category and its boundary still cohere with the wider domain model of entities, relations, and contexts it is supposed to live inside', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Ontology Audit is most directly rooted in philosophy's traditions of conceptual analysis, ontology, logic, epistemology, and normative reasoning. The lineage fits its defining practice: Checks whether a category and its boundary still cohere with the wider domain model of entities, relations, and contexts it is supposed to live inside.
Related originating lineages:
- Computer Science & Software Engineering — Ontology Audit also draws materially on computer science and software engineering's formal and practical treatment of computation, interfaces, data, and reliable systems, which shaped this mechanism rather than merely adopting it as an application.
- Library & Information Science — Ontology Audit also draws materially on library and information science's traditions of classification, metadata, retrieval, preservation, and archival stewardship, which shaped this mechanism rather than merely adopting it as an application.
Review resolution: Both independent reviews agree on primary origin philosophy; reconciliation resolves reported_ambiguity, alternate_origin_disagreement. Formative alternate lineages retained: computer_science, library_information_science. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis records how the formative lineages relate. Confidence is conservatively reconciled to medium, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Attribution caveat: The named audit is a modern operational form spanning philosophical ontology and knowledge engineering.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Ontological commitment (Quine, "On What There Is") — the claim that adopting a theory or model commits you to the existence of the entities it must quantify over. It disciplines an ontology audit toward revising categories to account for what the domain genuinely contains, rather than trimming reality to fit a tidy scheme. ↩
References¶
[1] The International Astronomical Union's 2006 Resolution B5 defined a "planet" by three conditions — orbiting the Sun, being in hydrostatic equilibrium (roughly round), and having "cleared the neighbourhood" around its orbit — and introduced "dwarf planet" for bodies meeting the first two but not the third. It is a real, widely known instance of redefining a category to restore consistency with a broader model of the domain. registry ↩