Stakeholder Category Review¶
Participatory review — instantiates Implicit Bias in Knowledge Structure
Convenes maintainers and affected users around concrete categories to adjudicate changes together, producing either revisions or a recorded reason they were declined.
A Stakeholder Category Review is a decision forum: it puts the people who maintain a structure and the people affected by it in the same room, around specific categories and cases, and requires them to jointly reach an outcome — a change made, or an explicit, recorded reason a proposed change was not made. Its defining feature is adjudication with accountability. Unlike a listening exercise, it is empowered to alter the structure, and unlike a maintainer's private edit, it obligates the maintainers to answer the affected parties on the record. Its irreducible product is the dissent record: proof of what was proposed, what was decided, and — when input was set aside — why. It exists so that affected input cannot be gathered and then quietly ignored, and so that a decision to keep a category becomes a defended choice rather than a default.
Example¶
A city's 311 service-request system routes every citizen report through a fixed category list that determines which department responds and how fast. Residents in older neighborhoods complain that their issues vanish. A Stakeholder Category Review convenes the 311 taxonomy owners, dispatchers from three departments, and a panel of residents and community organizers around the actual category list. They work concrete cases. "Illegal dumping" routes to Sanitation, but dumping on a vacant lot is Code Enforcement's job, so those reports bounce and die. There is no category for a chronic problem — only one-off incidents — so a block reporting the same flooding for years generates a fresh, low-priority ticket each time. "Noise" collapses a nightclub, a barking dog, and industrial machinery into one queue with one response time.
The forum traces each category to its dispatch consequence, then decides together. It adopts a cross-cutting "recurring issue" flag (a revision), splits "noise" by source (a revision), and — after the departments explain a real dispatch constraint — declines to merge the two dumping categories, recording that decision and the residents' continued objection in a dissent record. The value is not that residents were heard; it is that every proposal now has a visible disposition, and the one that went against them is on paper with a reason, not lost in a maintainer's inbox.
How it works¶
The review is defined by joint adjudication and recorded disposition:
- Seat both sides with standing. Maintainers and affected users at one table, each able to put proposals and objections on the record — not a consultation the maintainers later summarize alone.
- Work concrete categories and cases. Anchor every discussion in a specific category and real cases, tracing each to the downstream decision it drives, so the argument is about effects, not abstractions.
- Reach a disposition on every proposal. Each proposed change ends adopted, deferred, or declined — never merely "noted."
- Record dissent on the declines. When a proposal is set aside, log what it was, who wanted it, and the stated reason, so the decision is accountable and revisitable.
Tuning parameters¶
- Power balance at the table — how much standing affected users hold relative to maintainers. Too little and it decays into consultation; parity is what makes the dissent record meaningful rather than decorative.
- Proposal scope per session — a few categories deeply or the whole structure. Depth reaches real dispositions; breadth generates proposals faster than the forum can adjudicate them.
- Disposition bar — how much evidence a proposal needs before adoption. A low bar risks category instability; a high one lets the status quo win by inertia.
- Dissent visibility — whether dissent records stay internal or are published to participants. Publishing raises accountability and the cost of a bad decline; it also raises the stakes of convening at all.
When it helps, and when it misleads¶
Its strength is that it converts affected input into decisions with a paper trail. It is the mechanism that answers the archetype's hardest failure — input gathered and ignored — by making every proposal end in a recorded disposition, so a maintainer who overrides the affected has to say why, in writing, to their faces.
Its failure mode is participation without power, the middle rungs of Sherry Arnstein's ladder of citizen participation, where consultation and placation simulate involvement while real decisions stay upstream.[n1] The classic misuse is a forum whose "dissent record" is written solely by the maintainers, quietly reframing every override as a reasonable tradeoff. The guarding discipline is structural: affected participants must hold real standing over dispositions, and the dissent record must capture their words, not the maintainer's paraphrase — otherwise the review is Arnstein's placation wearing a governance costume.
How it implements the components¶
The review fills the adjudication-and-accountability components:
downstream_consequence_trace— every category on the table is tied to the concrete decision it drives, so the forum argues over effects rather than preferences.revision_proposal— proposals for change are jointly authored and each carries to an explicit adopted/deferred/declined disposition.dissent_record— declined proposals and unresolved objections are logged with who proposed them and why they were set aside, in the affected parties' own terms.
It does not run the up-front self-recognition audit that gathers whether affected people can see themselves in the categories (stakeholder_perspective_set, category_audit) — that evidence comes from inclusive_classification_review.md — and it does not preserve longitudinal continuity across the changes it adopts (legacy_category_history), which is category_revision_log.md.
Related¶
- Instantiates: Implicit Bias in Knowledge Structure — the review is the archetype's accountable decision forum for contested category changes.
- Consumes: Inclusive Classification Review supplies the self-recognition evidence the forum adjudicates.
- Sibling mechanisms: Bias Review Checklist · Taxonomy Bias Audit · Boundary Critique Session · Category Impact Assessment · Category Revision Log · Excluded Case Sampling · Ontology Critique Workshop · Red-Team Schema Review
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Stakeholder Category Review operates by jointly evaluates category evidence and records a supported maintenance or change disposition. That concrete deployed or enacted form is Assessment, Review & Assurance under the frozen taxonomy.
Nearest alternative: Decision, Gate & Allocation — Although Decision, Gate & Allocation can support this mechanism, the frozen evidence makes its operative form the act that jointly evaluates category evidence and records a supported maintenance or change disposition; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Jointly revising categories is participatory classification governance.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: convenes maintainers and affected users around concrete categories to adjudicate changes together, producing either revisions or a recorded reason they were declined.
- Law & Governance — Recorded dispositions support fairness.
- Organizational & Management Science — Maintainers and users negotiate operational meaning.
- Sociology & Anthropology — Sociology and anthropological study of institutions and social relations supplies a parallel or contributing lineage for the mechanism's defining operation: convenes maintainers and affected users around concrete categories to adjudicate changes together, producing either revisions or a recorded reason they were declined.
- Ethics of Technology & AI Governance — Technology ethics and ai governance supplies a parallel or contributing lineage for the mechanism's defining operation: convenes maintainers and affected users around concrete categories to adjudicate changes together, producing either revisions or a recorded reason they were declined.
Review resolution: The blind reviewers agree that library_information_science is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
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] Sherry Arnstein's "A Ladder of Citizen Participation" distinguishes genuine citizen power from its counterfeits — "informing," "consultation," and "placation" — where participation is staged but decision authority never actually transfers. It is the standing diagnostic for whether a stakeholder forum holds real power over dispositions or merely simulates it. ↩