Category Governance Record¶
Document — instantiates Category Boundary Audit
A living record of a category's criteria, rationale, decision authority, and revision history, so its boundary can be maintained accountably instead of drifting in silence.
Category Governance Record is the audit's memory made durable. It is the artifact — not an act of analysis — that holds a category's operational criteria, the purpose those criteria serve, who has authority to change them, when they are reviewed, and a dated history of every revision and its rationale. Its defining property is that it makes drift visible: a category maintained only in people's heads changes silently as each new decider brings a slightly different reading, and no one can say when or why the boundary moved. A governance record fixes a single source of truth against which the current line, its owner, and its lineage can always be checked, and it turns every future change from a hallway consensus into a recorded, attributable decision.
Example¶
A software company's incident process classifies outages by severity: P0 for a total customer-facing outage down through P3 for cosmetic issues. In practice "P0" means different things to different on-call engineers — some page the whole company for a degraded region, others hesitate to escalate a genuine outage — producing both false alarms and dangerous under-response. A Category Governance Record is created for the severity scheme. It records the operational criteria for each level, the purpose (right-size the response to the real blast radius), the owner (the SRE lead who can change the definitions), a quarterly review cadence, a log of the borderline incidents and how they were ultimately classified, and a version history with dates and rationales for each change.
The payoff shows up the next time it is contested. An engineer argues a partial outage "was really a P1"; instead of relitigating from scratch, the team consults the record, sees the current rule, its owner, and the reasoning behind the last revision, and — if the rule genuinely no longer fits — proposes a change through the record, which captures the new decision and its author. The boundary stops drifting because every move it makes is now written down and attributable.
How it works¶
- Template the fields. Capture purpose, inclusion criteria, exclusion criteria, decision authority, review trigger and cadence, a log of decided edge cases, and a version history.
- Attribute every change. Record each revision with a date, a rationale, and the person who approved it, so the boundary's movement is always traceable.
- Serve as single source of truth. Make downstream systems and deciders reference the record rather than their own recollection.
- Reconcile periodically. On the review cadence, check the written record against how the category is actually being applied, and close any gap.
Unlike the analytic siblings, the record does not find what is wrong with a boundary — it stores the criteria and the decisions others produce, so they persist and stay accountable.
Tuning parameters¶
- Field granularity — how much the record captures, from a one-line definition to a full dossier with edge-case log and rationale. More is accountable but heavier to maintain.
- Version-control rigor — how strictly changes are dated, attributed, and approved. High rigor prevents silent drift but adds process to every revision.
- Authority centralization — whether one owner controls the definition or many can edit it. Central ownership keeps the boundary coherent; distributed editing keeps it current but risks fragmentation.
- Review cadence — how often the record is reconciled with practice. Too rare and it rots; too frequent and it churns without adding accuracy.
When it helps, and when it misleads¶
Its strength is ending unaccountable drift: it gives a contested category an owner, an audit trail, and a way to onboard new deciders into the same line rather than a personal reinterpretation.
Its central failure mode is document rot — the record and the real practice diverge until the artifact describes a category no one actually applies, giving a false sense of governance precisely where governance has lapsed. A classic misuse is the write-once record that is created for a compliance checkbox and never updated. The guarding discipline is to tie every record update to an actual decision and to reconcile the record against practice on a fixed cadence, in the spirit of authority control[n1] — the boundary is governed only if its written definition and its lived use are kept in sync.
How it implements the components¶
Category Governance Record realizes the documentation and governance face of the archetype — the components that make a boundary persist accountably:
boundary_authority_record— its defining content: who owns the category, the review cadence, and the dated, attributed revision history.boundary_purpose_statement— records the purpose the criteria are meant to serve, so future revisions can be judged against it.boundary_revision_decision— captures each decision to preserve, clarify, or change the boundary, with its rationale and author.inclusion_ruleandexclusion_rule— stores the operational positive and negative criteria as the canonical, referenceable definition.
It does not gather and work a corpus of hard cases (edge_case_register) — that diagnostic is Edge-Case Analysis; nor does it run the reconsideration workflow for a contested case (appeal_or_exception_path), which is Appeals Case Review.
Related¶
- Instantiates: Category Boundary Audit — provides the durable record that keeps an audited boundary accountable over time.
- Consumes: Eligibility Audit and Edge-Case Analysis — the record stores the criteria and decisions these analytic mechanisms produce.
- Sibling mechanisms: Boundary Critique Review · Eligibility Audit · Taxonomy Review · Classification Fairness Review · Edge-Case Analysis · Ontology Audit · Appeals Case Review
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: A living record of a category's criteria, rationale, decision authority, and revision history, so its boundary can be maintained accountably instead of drifting in silence, making its operative form a durable record, ledger, register, or trace whose value depends on preserving actual state or history.
Independent corroboration: The frozen evidence defines Category Governance Record as 'A living record of a category's criteria, rationale, decision authority, and revision history, so its boundary can be maintained accountably instead of drifting in silence', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Authority-control practice established canonical category records with criteria, ownership, cross-references, and revision history.
Review resolution: Library and information science are primary because authority control established canonical category records with maintained criteria, responsibility, cross-references, and change history. Legal governance and data-schema management are applications of that record pattern rather than required co-origins here.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Authority control is the library-science practice of maintaining a single authoritative record for a name or subject heading — its established form, cross-references, and change history — so that a category is used consistently across a catalog and over time. It is the discipline this mechanism generalizes: a boundary is only governed if its canonical definition is recorded and kept in sync with use. ↩