A claim is not born binding. It becomes binding when the institution's proper authority decides to enforce it. This sidebar traces the pathway from tentative observation to binding rule and identifies the points where appeals and exits must be built in.
The governing principle: no claim may acquire binding force without a defined appeals pathway, and no claim may be enforced without the person subject to enforcement being able to verify that the claim was made with proper authority.
This is not leniency. It is due process encoded as structure.
The Four States of Institutional Claims
When your institution observes a problem and decides to act, the claim travels through four states. At each state, different evidence is required, different authorities are involved, and different exit pathways must be available.
State 1: Hypothesis
What is happening: Someone — individual, team, department — notices something appears to be true. A pattern in the data. A repeated problem. An observed behavior. The claim is tentative.
Authority level: Observation. No authority yet.
Enforcement: None. The claim is not yet enforced. People are not required to respond to it or defend themselves against it.
Evidence standard: Observation and pattern description. Low rigor.
Exit mechanism: Anyone observing the same phenomenon can question the observation. The claim can be dropped if newer data contradicts it.
Key structural rule: At this stage, the claim is reportable, not actionable. Do not discipline based on a hypothesis. Do not assign action based on a hypothesis. Do not make decisions that affect people based on a hypothesis. When an institution violates this rule, it turns tentative observation into retaliation before evidence has been gathered.
State 2: Scoped Finding
What is happening: The institution designates someone — investigator, auditor, researcher — to examine the hypothesis more rigorously. The scope is defined: what specifically are we looking at, by what method, with what data? The findings are preliminary but documented.
Authority level: Investigator authority, delegated by charter.
Enforcement: None yet. The person affected by the finding has a right to respond, to provide their own data, to question the method. This is not an accusation. It is a preliminary report.
Evidence standard: Defined methodology, documented data, stated assumptions, identified gaps. Medium rigor.
Exit mechanism: The person whose work is being studied can request a review of the methodology, an opportunity to provide additional data, a clarification of what the finding does not claim, and extension of the investigation if new information emerges. The investigator must respond in writing.
Key structural rule: At this stage, the finding must be contestable. The person affected must be able to say "I dispute this finding" and have the dispute documented and reviewed. When an institution skips this stage and moves directly from hypothesis to action, it prevents the person affected from defending themselves with data.
State 3: Decision Recommendation
What is happening: Based on the scoped findings, the investigator or a committee with investigator input makes a recommendation: given these findings, what should the institution do? This is still not a binding rule. It is a recommendation for action. But it is authoritative — it comes from someone with delegated authority to interpret findings.
Authority level: Decision authority, specified in charter.
Enforcement: Recommended, not yet enforced. The institution may act on the recommendation, ask for more information, or reject it. But if the institution acts on a recommendation, it must do so deliberately and on record.
Evidence standard: Finding plus logic chain. Reasoning is made explicit: if we do X, we expect to see Y, and here is why. Assumptions are stated.
Exit mechanism: The person affected, and any other stakeholder, can appeal the recommendation on three grounds: the finding is wrong (return to State 2 for re-examination), the logic is wrong (the finding is correct but the recommendation does not follow), or the recommendation imposes disproportionate cost (ask for alternative approaches). Appeals go to [Authority], which must respond in writing within [timeframe].
Key structural rule: At this stage, the recommendation must be reviewable. An appeal must be possible without retaliation. When an institution treats a recommendation as binding before review, it removes the ability to say no.
State 4: Binding Rule
What is happening: The institution has decided to enforce a change to policy, procedure, or practice. The decision is made by proper authority as defined in the charter, documented in writing, and goes into effect on a defined date.
Authority level: Authority delegated by charter to make binding decisions — specific role or committee.
Enforcement: Full enforcement. The institution may now hold people accountable for compliance with this rule.
Evidence standard: Charter authority, decision record, stated effective date, and training or communication plan.
Exit mechanism: After the binding rule takes effect, people subject to the rule can appeal on three grounds: proper notice was not given (must be resolved before enforcement), the rule violates the charter (escalates to charter authority), or compliance is impossible (if applicable, process exit as defined in charter). Appeals must not prevent the rule from operating, but they must be recorded and reviewed. If an appeal reveals the rule violates the charter, the rule is suspended pending charter-level decision.
Key structural rule: At this stage, a binding rule may be enforced. But enforcement without evidence that due process was followed is itself a violation.
The Critical Transition: Hypothesis to Binding Rule
Most institutional corruption happens not because people intentionally abuse power, but because the process skips states.
A process that jumps from hypothesis to binding rule in days eliminates every exit, every appeal, every chance to contest. By the time the person realizes they are being judged, they are already being enforced against. A process that takes the time to move through the states — gathering evidence, allowing review, documenting exceptions — moves slowly but holds together.
The structural safeguard: write the timeframe and process into the charter. Not "we will investigate thoroughly" (vague; enforcement can happen whenever convenient), but specific timelines: hypotheses investigated within a defined period by designated auditor, findings provided to the affected person within a defined period, response window specified, recommendation timeline named, appeal deadline set, and decision binding only after the appeal window closes. When you write the timeline, you make yourself accountable to it.
Building Exit Pathways
For each claim your institution might make binding, identify:
Hypothesis stage exit: If someone disputes the observation, the institution will listen, gather more data, or drop the claim.
Finding stage exit: If someone disputes the finding, they can request method review, data review, or independent audit.
Recommendation stage exit: If someone disputes the recommendation, they can appeal to [Authority]. The appeal must be answered in writing within [timeframe].
Rule stage exit: If someone cannot comply with this rule, they can request an exception, appeal to charter authority, or exit the process.
If you cannot define an exit at any stage, you have not yet built due process.
Integration Points
- Institutional charter (2.3C.1-1): The charter specifies which role has authority to move a claim from hypothesis to scoped finding, from finding to recommendation, and from recommendation to binding rule.
- Culture as feedback (2.3C.1-3): Narrative accountability creates the public record of how claims moved through the four states, which is how you audit whether due process was followed.
- Accountability ladder (2.3C.1): The ladder specifies who can appeal and to whom when judgment hardens without proper process.
- Incident response runbook (2.3C.4-2): When judgment hardens incorrectly — binding rule made without proper evidence — the runbook specifies how to stop enforcement, investigate, and restore.
Change Log
- 18 Aug 26 — Replaced "coercive"/"coercion" language with "binding" throughout, to match the four-state model's own terminology, and revised the "Critical Transition" section's description of how process failures happen.
- 19 Mar 26 — Removed a redundant type label from the title and replaced the subtitle with a descriptive one. Standardized heading and text capitalization and formatting throughout. Corrected two cross-reference errors: a mislabeled sidebar reference and a mislabeled section number for the incident response runbook. Rewrote the "Critical Transition" section as prose instead of a list.
- 17 Mar 26 — Initial publication.