Category Boundary Audit¶
Boundary audit — instantiates Meta-Symbolic Rule Reflection
Tests a category system at its edges — running the borderline, excluded, and anomalous cases against each line to find where the boundary itself, not the classifier's judgment, is drawn wrong.
A Category Boundary Audit takes a working classification system and stress-tests it at its edges, feeding the borderline, excluded, and anomalous cases across each category line to find where the boundary — not the person doing the classifying — is drawn wrong. Its defining move is that it holds the categories fixed and interrogates the line between them: it does not ask "was this case sorted correctly?" but "does the place we put this line force cases onto the wrong side no matter how carefully anyone judges?" That keeps it diagnostic. It is the mechanism that turns a vague sense that "we keep arguing about the same kinds of cases" into a documented map of exactly which distinctions are failing and how.
Example¶
A large platform's Trust & Safety team keeps re-litigating the same reports: a barbed reply to a public figure, a pile-on that is individually polite, a reclaimed slur used by an in-group. Each gets classified as "harassment" or "criticism" by a different reviewer, and appeals pile up. Rather than retrain reviewers, the team runs a boundary audit. They pull fifty of the most-appealed cases — the ones that sit right on the harassment / criticism line — and map the current rule: harassment requires a "targeted attack on an individual." Then they push each edge case against that definition. The pile-on exposes that "targeted" assumes a single actor; the reclaimed slur exposes that the rule reads the word, not the speaker's relationship to it; the criticism-of-a-public-figure case exposes that "individual" quietly erases the power asymmetry.
The output is not a rewritten policy but a finding: a documented inventory of the boundary failures, each tagged with the assumption it breaks, plus a one-level-up judgment that the harassment line is being asked to carry three distinctions it cannot hold at once. That finding is what tells the policy owners the problem is the boundary, and hands the redesign to the mechanism that actually rewrites it.
How it works¶
- Fix the categories, probe the line. The audit deliberately does not propose new categories; it treats the existing scheme as the object under test and only manipulates which cases it confronts.
- Sample from the margin, not the center. Cases are drawn from the ambiguous, appealed, "miscellaneous"-bucket, and workaround population — the places where the boundary is actually load-bearing — never the easy central exemplars.
- Attribute each failure to an assumption. For every case that lands wrong, the audit names the embedded assumption the boundary makes (single actor, stable identity, one primary cause) rather than just recording a disagreement.
- Judge the line, not the case. It closes with a one-level-up verdict on whether the boundary is salvageable, overloaded, or mis-placed — the input a redesign consumes.
Tuning parameters¶
- Margin width — how far from the center you sample; only truly ambiguous cases, or a wider band. Wider surfaces more failures but dilutes the signal with genuinely easy calls.
- Case sourcing — appeals, reviewer disagreements, "other" buckets, or adversarial constructed cases. Real appeals are credible; constructed cases probe boundaries no live case has hit yet.
- Attribution depth — stop at "this case fails" or push to the specific assumption behind the failure. Deeper attribution is more useful to a redesign but slower.
- Verdict threshold — how many boundary failures of a given type count as "the line is wrong" versus normal edge noise; set it low and every category looks broken.
When it helps, and when it misleads¶
Its strength is separating a classifier problem from a category problem — the difference between "reviewers need training" and "no reviewer can get this right because the line is in the wrong place." Concentrating on the margin is efficient: boundaries reveal their flaws exactly where cases cluster against them, which is why edge cases keep the critique grounded instead of abstract.
It misleads when the margin is mistaken for the whole. Every category has some vague border — the classic sorites problem is that a boundary can be fuzzy without being wrong[n1] — and an audit that treats all vagueness as a defect will condemn a scheme that is working fine for the ninety percent it was built to sort. The classic misuse is auditing only the loudest appeals and concluding the entire taxonomy is broken from a handful of pathological cases. The guarding discipline is to test the boundary against normal cases too, and to require a pattern of same-type failures — not one dramatic case — before ruling the line wrong.
How it implements the components¶
symbol_system_map— it names the specific categories and the definitions of the lines between them as the fixed object under test.edge_case_and_blind_spot_inventory— its core artifact: the documented set of borderline, excluded, and anomalous cases, each tagged with the boundary it breaks.meta_level_critique— it closes with a one-level-up verdict on whether the boundary itself should be trusted, not on whether a given case was sorted right.
It does not write the new scheme — it produces neither a revision_proposal nor the validation_and_governance that adopts one; that is Taxonomy Redesign Workshop. Nor does it run cases through a proposed framework to trace downstream_consequence_trace — that is Edge-Case Walkthrough.
Related¶
- Instantiates: Meta-Symbolic Rule Reflection — it supplies the diagnostic finding that a category boundary, not its application, is generating the recurring problem.
- Sibling mechanisms: Edge-Case Walkthrough · Taxonomy Redesign Workshop · Ontology Revision Session · Language / Rule Critique · Governance Rule Review · Model-Class Revision · Paradigm Review · Meta-Cognitive Reflection Prompt · Versioned Schema Change
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Tests a category system at its edges — running the borderline, excluded, and anomalous cases against each line to find where the boundary itself, not the classifier's judgment, is drawn wrong, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Category Boundary Audit as 'Tests a category system at its edges — running the borderline, excluded, and anomalous cases against each line to find where the boundary itself, not the classifier's judgment, is drawn wrong', 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: Philosophy of vagueness and the sorites tradition supply systematic attention to borderline cases and the distinction between indeterminate and misplaced boundaries.
Related originating lineages:
- Cognitive Science — Prototype and graded-membership research explains why category edges need not behave as crisp necessary-and-sufficient rules.
- Library & Information Science — Classification practice supplies the governed category system whose excluded and anomalous cases are tested.
Review resolution: Philosophy is primary because edge cases, necessary and sufficient conditions, and sorites problems test whether a category boundary is coherent. Library classification and cognitive categorization supply operational and prototype-based tests, so the generalized audit is a cross-disciplinary synthesis.
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] The sorites paradox (from the Greek for "heap") — removing one grain from a heap leaves a heap, yet repeated the boundary between "heap" and "not-heap" dissolves. Its lesson for classification is that a vague border is not the same as a wrongly-placed one; boundaries can be indeterminate at the margin and still be useful, so vagueness alone is not evidence a category is broken. ↩