Skip to content

Category Boundary Audit

Audit the boundary of a category to reveal hidden assumptions, exclusions, edge cases, and consequences before the category is trusted for action.

The Diagnostic Story

Symptom: A category everyone uses as if it were obvious is producing different outcomes in different hands. Borderline cases are handled inconsistently across teams or over time, and nobody can explain why. Some actors are silently excluded from processes, benefits, or visibility that the category label was supposed to grant them. An edge case finally surfaces and reveals that the boundary was never as settled as it seemed.

Pivot: Turn the category boundary into an explicit object of examination: name it, map who is included and excluded and on what criteria, test the hard cases, and surface the assumptions the boundary encodes. Then decide deliberately whether to preserve, revise, split, merge, exception-handle, or retire the line.

Resolution: Inclusion and exclusion become accountable because criteria are explicit, purpose-bound, and open to inspection. Misclassification harm drops because edge cases are handled through declared rules rather than ad hoc judgment. The category remains useful while the assumptions it carries are no longer hidden.

Reach for this when you hear…

[public health] “We keep fighting about whether this patient population counts as 'high-risk' because no one ever wrote down what the category actually means.”

[data engineering] “Three teams are using the same 'active user' definition in the same dashboard and they are all computing it differently from the same events table.”

[policy administration] “Half our appeals are about whether someone falls inside or outside this eligibility boundary — a boundary that was drawn twenty years ago for a completely different program.”

Mechanisms / Implementations

  • Boundary Critique Review (boundary_critique_review): This is a method implementation of the archetype.
  • Eligibility Audit (eligibility_audit): This is a procedure implementation of the archetype.
  • Taxonomy Review (taxonomy_review): This is a procedure implementation of the archetype.
  • Classification Fairness Review (classification_fairness_review): This is a test_or_assessment implementation of the archetype.
  • Edge-Case Analysis (edge_case_analysis): This is a method implementation of the archetype.
  • Ontology Audit (ontology_audit): This is a procedure implementation of the archetype.
  • Category Governance Record (category_governance_record): This is a document implementation of the archetype.
  • Appeals Case Review (appeals_case_review): This is a workflow implementation of the archetype.
  • Appeals Case Review
  • Boundary Critique Review

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (3)

Also references 5 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Eligibility Boundary Audit · domain variant · recognized

Audits eligibility criteria for access, benefits, rights, duties, responsibilities, or exemptions.

Classification Boundary Fairness Audit · assessment variant · recognized

Audits classification thresholds or category boundaries for systematic unfairness, invisibility, or error distribution.

Identity Category Boundary Audit · sensitive domain variant · candidate

Audits identity-related category boundaries to avoid rigid essence claims, erasure, forced classification, or harmful exclusion.

Edge-Case Boundary Stress Test · method variant · likely subtype

Uses strategically chosen borderline cases to test whether a category boundary is coherent, justified, and resilient.