Specification 1.0 — Constitutional Runtime Governance
The foundational specification for constitutional model, runtime authority, admissibility, evidence, execution gate, consequence, and conformance.
Evidence participates in admissibility.
Evidence is not only the trace left after a runtime decision. It is part of what allows a runtime decision to be constitutionally justified before consequence occurs.
Purpose
This specification defines PMS4U as constitutional runtime governance infrastructure. Its purpose is to establish how authority, admissibility, evidence, execution, and consequence relate at the execution boundary.
The specification is intended to be the primary reference. Technical notes then expand specific parts of the model without replacing the normative structure described here.
Normative Thesis
Evidence is not merely a post-gate audit residue. Evidence participates in admissibility itself. A decision cannot be legitimate unless the runtime can inspect sufficient evidence to justify why the requested transition may occur now.
For that reason, admissibility should be understood as a live evaluation informed by both policy state and evidence. Evidence continues after execution, but it also exists before and during the decision as part of what makes the decision constitutionally defensible.
Constitutional Model
The constitutional model defines authority sources, delegation rules, constraint boundaries, evidence obligations, escalation paths, and consequence ownership outside the runtime verifier itself.
It must remain inspectable independently from the operational runtime so that the verifier does not become the sole author, interpreter, and enforcer of its own legitimacy.
Runtime Authority
Runtime authority is the live check executed immediately before consequence-bearing mutation. It tests whether the requesting actor, system, or delegated process still holds valid authority in the current context.
Runtime authority is not equivalent to access control. Permission may grant system reachability; runtime authority determines whether a specific consequential transition is legitimate now.
Admissibility
Admissibility is the execution-time evaluation that integrates constitutional constraints, runtime authority, current policy state, consequence classification, and evidence sufficiency.
A request may be technically executable and still inadmissible if delegated legitimacy has drifted, evidence is incomplete, consequence ownership is unclear, or policy state no longer supports the transition.
Evidence
Evidence has two roles. First, it feeds the decision: identity context, state proofs, signatures, prior receipts, and verifiable runtime inputs support admissibility evaluation. Second, it preserves continuity after the decision: receipt, hash lineage, replay context, and verification artifacts remain available for audit and reconstruction.
Therefore the model must treat evidence as both a decision input and a continuity output, not only as a post-execution log.
Execution and Consequence
Execution occurs only through the execution gate after admissibility resolves. The gate is the final mechanism that turns a validated request into actual mutation, release, dispatch, commit, or other consequence-bearing effect.
Consequence is where governance becomes real. The system must be able to show why the outcome was allowed, who owned the authority, what evidence existed, and what state survived at the moment of release.
Conformance
Conformance requires that implementations preserve the independence of the constitutional model, runtime revalidation before mutation, evidence continuity, and replayable verification paths.
A system that stores logs after execution but cannot prove admissibility before execution does not conform to this specification.
Core terms
Constitutional Model
The independent governing model that defines authority conditions, permissible transitions, evidence obligations, and consequence ownership before runtime execution is considered.
Runtime Authority
The live verification layer that checks whether a specific actor, system, or delegated process may request a consequence-bearing transition now.
Admissibility
The execution-time determination that authority, constraints, policy state, and evidentiary sufficiency survive immediately before mutation.
Evidence
The runtime material used to justify, bind, and later replay a decision: state snapshots, authority context, receipts, signatures, hashes, and verification context.
Execution Gate
The final boundary that blocks, releases, defers, interrupts, or observes consequence-bearing mutation.
Consequence
The real-world or system-level effect created when a governed transition is committed.
Conformance
The degree to which runtime behavior, evidence continuity, and implementation outputs remain consistent with the constitutional model and specification.
Conceptual flow
Constitutional Model
Defines authority sources, boundaries, delegation, evidence duties, and consequence ownership.
Runtime Authority
Checks whether the live actor or system still holds valid authority for this specific transition.
Admissibility Evaluation
Integrates authority, policy state, consequence class, and evidence sufficiency before mutation.
Evidence + Policy State
Evidence and policy state jointly inform whether execution remains constitutionally defensible now.
Execution Gate
Blocks or releases mutation only after admissibility resolves.
Consequence
Commits the governed real-world or system effect.
Evidence Continuity
Preserves replayable receipts, hashes, signatures, and decision context after the consequence.
Constitutional Model
↓
Runtime Authority
↓
Admissibility Evaluation
↙ ↘
Evidence Policy State
↓
Execution Gate
↓
Consequence
↓
Evidence ContinuityHow technical notes extend the specification
Verifier Integrity
Why the runtime verifier cannot self-legitimate.
Runtime Authority
Why authority is not reducible to static permission.
Admissibility
How execution-time legitimacy is evaluated.
Evidence Continuity
How evidence spans both decision support and post-decision replay.
Execution Gate
How consequence is released only after admissibility survives.
Why this specification matters now
This document gives specialists one stable reference for discussing data model, runtime authority, admissibility, safety integration, evidence continuity, and execution control without depending on isolated posts.
Treat this specification as the normative base. Treat numbered technical notes as focused expansions that sharpen one architectural problem at a time.