Realis Structural Standard
Public criteria for decision admissibility under pressure
Who set the terms of that ask? Who bears the consequence if the decision proves wrong? Is the evidence behind it traceable and testable? Where those questions resolve, the decision can proceed on its own merits. Where they stay open, or where their answers place the ask outside what can be structurally admitted, the Realis Structural Standard is the criteria set that makes the basis of the decision inspectable.
An equation, encountered for the first time, appears as a formula to apply. With deeper study it becomes a definition, then an expression of a conserved quantity. At the deepest level it resolves into something else: a statement about what responses a system can produce given its constraints. It is the response produced when a system obeys certain conditions.
Institutional behavior follows the same structure. Stated rules and observed outcomes sit downstream of the constraint conditions that determine which decisions can form, which authority can act, and which actions can propagate once taken.
The standard is built at that level.
The formal basis is set out in LAC-001: Load Admission Constraint →
The standard applies where the institution has the capacity to read its own state. Where that capacity is degraded, self-assessment produces a record of the institution's internal coherence, distinct from a compliance claim under this standard. The diagnostic instruments that determine whether valid self-assessment is available are part of the lab's corpus. Adoption proceeds whether the institution is still internally coherent or has already crossed a degradation threshold; the integration work differs by starting condition, specified in RSS-001-N4.
Under sustained load, internal authority erodes before failure registers. Decisions made under that condition require an external reference point. The Realis Structural Standard sets out criteria a decision can be held against, and the conditions under which authority to act may already have degraded past self-correction. Realis does not certify adopters; conformance is self-declared against the published criteria and made inspectable. The institution still determines what action it takes. Where admission fails and the ask is acted on anyway, correction does not stay available for later: the parties who committed to the decision become the surface that defends it, and admitting the error falls on the same parties whose acknowledgment correction would require. The structural account of why correction becomes resistant after the fact is set out in CLC-001 — Commitment-Locked Correction Resistance.
This standard applies when a decision must be made and the basis for that decision falls outside what the system can verify on its own.
The requesting party must either supply a decision basis that meets the published criteria, or proceed on a record showing they acted without one.
What the standard covers
Six structural functions must remain active for an institution to sustain valid decision authority under pressure. The standard names what each requires and the point at which each has failed. The standard sits at a layer upstream of existing compliance regimes, decision admissibility under load, that those regimes do not themselves specify.
If any one fails, the decision basis is unresolvable. One failure is sufficient.
These six functions are set out in RST-100. They sit at the applied-standards layer (RST), derived from the stability constraints named in Institutional Physics, which determine whether admissible decision states can exist.
What integration looks like
The standard defines what a compliant decision requires. Integration is the work the institution does to meet it. An institution working within a published, self-assessed, publicly inspectable standard presents a different evidentiary position than one that has produced no such record.
Problems surface earlier. Concerns reach someone with authority to act before commitments lock in. A discrepancy noticed in week two does not have to wait until the quarterly review to be heard.
Verification tests whether the process still applies. Review asks whether the procedure still matches current conditions, not only whether the paperwork is internally consistent.
Action pauses when information is incomplete. Decision-making slows under uncertainty because acting without confirmation costs more than waiting. The pause is treated as the responsible action, not as weakness.
Memory stays usable. Six months after a decision, the reasoning behind it is still accessible. The record was maintained at a depth that supports reconstruction.
Reconstruction is possible. When something goes wrong, the institution can identify the actual sequence of decisions and information flow. Trace continuity persists. Responsibility can be assigned.
The full integration architecture is specified in RSS-001-N4 — Integration Architecture.
Operation outside the admissibility envelope has its own structural specification. RST-150 — Operational States Under Constraint specifies the architecture of legitimate operation when admissibility is partial, lost, or in recovery. RST-160 — Structural Function Survivability Under Asymmetric Conditions specifies what survives when the institutional functions required for honest classification have degraded under asymmetric load.
How compliance works
There is no external certification layer. Compliance is self-assessed against public criteria.
The claim is inspectable. Anyone can read the criteria, examine the institution's documented basis, and evaluate whether the claim is supported. Validity rests on whether the structural conditions are met, independent of who issues the claim.
Realis Institute issues no approvals. The standard defines what makes a decision structurally valid, and locates integrity in the inspectability of the basis.
The architectural reason the standard refuses an external certification body is set out in VG-001 — Verification Geometry, which specifies the four-position structure (inspectability, certification, ratification, adjudication) through which any standard becomes operative.
The architectural conditions distinguishing substantive compliance from compliance theater under adversarial pressure are set out in RST-170 — Compliance Theater and Adversarial Inspectability. The note specifies the five structural signatures by which performative compliance becomes detectable, the four architectural requirements for adversarial inspectability (substrate inspection, negative-space inspection, structurally independent reviewers, inspection of inspection itself), and the seven inspection surfaces (published criteria, documented basis, operational record, externalized trace, public registry, field-initiated revision, external review) whose conjunctive operation produces the architecture's resilience.
Compliance proceeds through two instruments.
Reality Contact Assessment (RCA-FC-001). Institutions evaluating whether a decision basis can be verified should begin here before applying the compliance criteria. Download →
RST Compliance Assessment and Declaration (RSS-CA-001). Institutions conducting a compliance assessment against this standard should use this instrument. Declarations may be pilot-bounded, domain-bounded, or institution-wide; pilot-bounded is the default entry point. Download →
The full architecture is specified in three supporting notes.
RSS-001-N5 — Adoption Pathway and the Threshold of Working Understanding. The structural process by which an institution passes from interested to declared, and the practitioner-level threshold the standard requires.
RSS-001-N3 — Invocation, Verification, and Loss of Conformance. The architecture governing standing to invoke, verification surface, and loss of conformance.
RSS-001-N4 — Integration Architecture. The architecture governing integration of this standard into institutional operation.
Institutions formally evaluating adoption may begin with RSS-001-N5 and contact Realis Institute to discuss any pathway questions that arise at the boundary of working understanding. The Implementation Guide sets out the adoption sequence step by step, routing to the documents that handle each phase. Researchers, practitioners, and individuals exploring the framework should begin with the Publications page and the Corpus by Concept.
What This Standard Does
Here is the honest answer to the question most people arrive with: what good is this if no one in charge will listen?
This standard will not make leadership listen. It will not reverse a bad decision, protect you from retaliation, or save an institution that has already decided to look away. Those things take power this standard does not have, and we will not pretend otherwise.
What it does is simpler, and more useful than it sounds.
Normally, pressure changes the institution. Someone powerful demands action, and leadership decides whether to comply.
Under this standard, the order changes. The demand itself has to be examined before leadership can claim the decision rests on a proper basis.
That is the whole mechanism. Before the institution acts, it has to answer plain questions, on the record.
Before acting, the institution must answer:
Who is asking?
What authority supports the request?
What evidence supports it?
Who bears the consequence if it is wrong?
If we proceed without a sufficient basis, are we willing to record that we did?
The pressure does not disappear. But it can no longer travel in a straight line from "someone is angry" to "someone is punished." It has to pass through those questions first.
That interruption is the point. It puts the burden on the people exercising authority, where it belongs, instead of on the person who has to object after the damage is done. Think about how institutions usually fail: pressure arrives, the institution acts fast to make it stop, and only later does anyone ask whether there was ever a real basis. By then the people who saw it coming are alone, trying to prove it after the fact. This standard moves that question to before the decision, when it can still change something.
It also leaves a record, made at the time, that anyone can later inspect: faculty, students, trustees, the press, a court, an accreditor. Years later, when people ask whether anyone could have known, the answer is no longer lost to memory.
When It Helps, and When It Doesn't
This standard has force in one situation: when someone, somewhere, will eventually look.
It works the way a building code works. A building code does not stand at the site and stop you. It is a public rule that inspectors, courts, and other builders measure the work against later. That is what gives it force, long before any law requires it. Good builders follow it because they know they will be measured against it the moment something fails.
This standard is the same. Its force comes from the people who can check a claim against the published rule: regulators, accreditors, courts, the press, professional peers, the other side of a future dispute. Where those people are watching, the standard holds, even though no one is forced to adopt it.
So before adopting it, ask one question: in our world, who would ever look?
A university under public scrutiny. A hospital facing a crisis. A research body bracing for funding pressure. A firm expecting investigation. These institutions live under exactly that kind of watching, and for them this standard is worth the work.
If the honest answer is that no one will ever look, the standard cannot supply the watching itself, and adopting it would be a gesture, not a protection. We would rather tell you that plainly than sell you something that will not hold.
The standards series
Decision Admissibility (RSS-001 Family)
RSS-001 — Criteria and Compliance Requirements →
Distills the full compliance criteria into a single reference document. Defines what a compliant decision requires, what a non-compliant state means, and what conditions create an unresolved decision basis.
RSS-001-N1 — Constraint Independence, Deficit Typology, and Falsifiability →
Specifies the operational conditions under which RSS-001's compliance criteria are satisfied for decision systems whose outputs are produced by an optimization process. Defines constraint independence as a lifecycle condition and establishes a falsifiability test for compliance claims.
RSS-001-N2 — Deficit Resolution and User Input →
Specifies the conditions under which external input resolves a detected deficit. Distinguishes resolution, which alters the decision basis, from override, which leaves the deficit in place.
RSS-001-N2-WE1 — Worked Example: Operator Override Under Urgency →
Traces the verification sequence of RSS-001-N2 through a single operations scenario. Demonstrates that authority cannot override the structural floor.
RSS-001-N3 — Invocation, Verification, and Loss of Conformance →
Specifies the architectural conditions governing how a declaration under this standard is established, examined, and lost. Defines standing to invoke, the four-surface verification architecture, and the structural conditions under which a declaration becomes void.
RSS-001-N4 — Integration Architecture →
Specifies what integration of this standard requires of an institution. Identifies five observable behaviors in an integrated institution, three structural supports that must be protected, the distinction between protective and dysfunctional friction, and the difference between pre-threshold adjustment and post-threshold reconstruction.
RSS-001-N5 — Adoption Pathway and the Threshold of Working Understanding →
Specifies how an institution passes from interested to declared. Defines working understanding as the practitioner-level threshold the standard requires of a declaring entity, distinct from expertise, certainty, and credentialing. Specifies the five-phase adoption sequence and the four pathways available when working understanding reaches its boundary.
Handoff Integrity
RSS-002 — Handoff Integrity Requirements →
Specifies the minimum conditions any transfer of responsibility must satisfy. Identifies the six failure modes that produce handoff failure and defines minimum requirements at every transfer boundary.
Intervention Selection (RSS-003 Family)
RSS-003 — Intervention Point Selection Requirements →
Identifies the conditions required to select a viable intervention point in a degraded system. Identifies three selection criteria and establishes a structured scan procedure.
RSS-003-N1 — Entry Is Not Where the Fire Is →
Distinguishes urgency from admissibility in entry selection at civic scale. Applies gate logic to entry selection under degraded conditions.
For legal and policy teams
It is written for a legal environment that is still forming. The standard is staged to be useful as that environment arrives, rather than claiming a settled legal standing it does not yet have.
Realis Institute leaves legal outcomes to the courts and regulators that adjudicate them. The standard defines structural admissibility.
An institution working under this standard can proceed through pressure, record deviation when compliance fails the criteria, and preserve the basis for review.
The Threshold
The threshold a decision must clear to be sound is this: verifiable evidence, traceable authority, and preserved capacity for correction if the decision proves wrong.
The full criteria — thresholds, the Fourteen Load-Bearing Commitments, and the RST Compliance Checklist — are defined in the RST Field Manual.