Public Reason-Giving Protocol¶
Protocol — instantiates Authority Legitimacy and Consent Foundations
Requires decisions to include reasons, evidence, constraints, and appeal information so authority remains legible.
A Public Reason-Giving Protocol is a standing rule attached to the act of deciding: every binding decision must ship with the reasons behind it — the criteria applied, the evidence weighed, the constraints and tradeoffs that bound it, and how to challenge it. Its defining trait is that it operates on the decision's legibility, not on who may decide or whether they are qualified: it forces an authority to show its work, converting an opaque "because we said so" into an explainable, contestable record. And because it requires the appeal route to be stated on the face of the decision, it also makes the decision reviewable — reasons you can read are reasons you can dispute.
Example¶
A national disability-benefits agency has for years issued denials as a bare rejection code plus a boilerplate sentence. Trust is collapsing, appeals arrive as confused fury, and caseworkers can decide inconsistently because nobody has to justify a call in writing. The agency adopts a reason-giving protocol. Now every adverse decision must state which eligibility criteria were and were not met, cite the specific evidence relied on (the functional assessment, the medical report), name the constraint that bound the outcome, and set out the deadline and steps to appeal.
A denial now reads as a legible argument the claimant can actually engage with — and two things follow. Some denials are quietly withdrawn once a caseworker has to write down a justification that does not hold up. The rest become contestable on their merits, appealed on the specific reason the claimant disputes, rather than experienced as an arbitrary "no."
How it works¶
- Set the trigger. Define which decisions must carry reasons — usually the binding, adverse, or contested ones, not every routine call.
- Require the contents. Criteria, evidence, constraints, tradeoffs, and the route to challenge — a template that makes an omission visible.
- Hold a legibility standard. Reasons written to be understood by the affected party, not only by insiders fluent in the jargon.
- Carve out confidentiality. Expose the reasoning without requiring every confidential detail, so the duty to explain does not collide with legitimate secrecy.
Tuning parameters¶
- Coverage — which decisions must carry reasons. Broad coverage maximizes legibility but burdens routine work; narrow coverage saves effort but leaves opacity exactly where stakes are lower-visibility.
- Depth of reasons — a one-line rationale versus a full reasoned opinion. Depth aids contestation and sharpens the decision but costs time and can invite gaming.
- Confidentiality boundary — how much underlying detail is disclosed. More transparency builds trust; too much can breach privacy, security, or a third party's interest.
- Templating — free-form prose versus structured fields. Structure guarantees completeness and comparability but can degrade reasons into box-ticking.
When it helps, and when it misleads¶
Its strength is that it makes authority legible, and by that alone it does double duty: deciders reason better when they know they must publish, and affected parties gain the raw material to challenge a decision they think is wrong. It is a practical descendant of the idea of public reason — that the exercise of collective power should rest on reasons others could in principle accept.[1]
Its failure mode is reasons theater — post-hoc rationalizations that dress a predetermined outcome in plausible language, or a template so rote that its "reasons" say nothing. The classic misuse is publishing a fluent justification manufactured after the decision to defend it, rather than the reasons that actually drove it — legibility as camouflage. The guarding discipline is to require the reasons to be written before or as the decision is made, to keep the stated appeal route a real one rather than a dead end, and to spot-check whether the published reasons actually predict which decisions go which way.
How it implements the components¶
public_reason_record— the protocol's core product: the criteria, evidence, constraints, and tradeoffs behind each covered decision, recorded and disclosed in a legible form.accountability_and_review_path— by mandating that each decision state how and by when it can be challenged, the protocol makes the review route legible and reachable to the affected party at the moment they need it.
This protocol publishes an account of a decision and its challenge route; it does not itself judge whether the decider is qualified (competence_evidence — that is Credentialing and Peer Review Process) or gather affected parties' input before the decision (voice_channel — that is Participatory Consultation Process).
Related¶
- Instantiates: Authority Legitimacy and Consent Foundations — the protocol supplies the reason-record leg that keeps authority explainable.
- Sibling mechanisms: Charter or Mandate Document · Appeal or Review Forum · Consent Capture and Revocation Workflow · Credentialing and Peer Review Process · Legitimacy Health Dashboard · Participatory Consultation Process · Decision-Rights Matrix
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Public Reason-Giving Protocol operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it requires decisions to include reasons, evidence, constraints, and appeal information so authority remains legible.
Independent corroboration: The frozen evidence defines Public Reason-Giving Protocol as 'Requires decisions to include reasons, evidence, constraints, and appeal information so authority remains legible', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Requiring authority to state evidence, constraints, and appeal information is rooted in legal due process and reasoned decision doctrine.
Related originating lineages:
- Philosophy — Public-reason and legitimacy theory supplied the deeper normative rationale.
- Public Administration & Policy — Administrative practice operationalized standardized decision notices and appeal routing.
Review resolution: Both blind reviewers agree on law_governance as the primary origin. Explicit reconciliation resolves domain_reach_disagreement. The merged alternate lineages retain only domains the reviewers identified as materially formative; domain_reach=universal records later applicability separately from origin breadth.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The protocol and the Appeal or Review Forum both touch the review path, from opposite ends: this protocol states and publishes how a decision may be challenged, making the route legible on the face of every decision; the forum is the venue that actually hears the challenge. A reason-giving protocol without a live forum leaves the appeal route a promise; a forum without published reasons leaves challengers guessing what they are contesting. They are meant to run together.
References¶
[1] Rawls, J. "The Idea of Public Reason Revisited". The University of Chicago Law Review 64(3), 765–807 (1997). Grounds legitimate collective political power in reasons that citizens can reasonably accept. registry ↩