Principles — ORP v3.0

Foundational Rules

The Four Invariants

These axioms are non-negotiable constraints on every ORP-governed execution. All runtime variants, evaluation schemas, and recovery protocols must preserve them.

Signal > Narrative

Data provenance accuracy parameters must never be modified to achieve cleaner linguistic fluency profiles. Raw signal integrity supersedes presentation quality at every stage.

Recoverability > Completion

Graceful, safe diagnostic degradation sequences are systematically favored over forced operational processing continuity. A clean halt is better than a corrupt output.

Epistemic Isolation

Maintains strict separate processing access blocks across execution segments to avoid logic contamination errors. No cross-node context mutation is permitted.

Observable Drift

Every occurrence of operational decay must map explicitly to visible σ² telemetry metrics for diagnostic visibility. Invisible drift is treated as a governance failure.

Provenance Preservation

Traceability as a Hard Requirement

Provenance is not an optional metadata layer — it is a first-class governance object in ORP.

Provenance Enforcement Mandates

No Summarization of Anomalies: Context history must be logged explicitly without summarizing away anomalous tokens. Every deviation from nominal must remain visible in the provenance chain.
σ² Telemetry Binding: Every occurrence of operational decay must map explicitly to visible σ² telemetry metrics. Decay without a telemetry entry is a protocol violation.
Coherence Camouflage Rejection: Outputs that appear coherent while hiding underlying degradation are treated as high-severity failures. Signal accuracy supersedes surface fluency.
Chain Integrity on Output: The provenance chain is sealed at the Output State (Step 08) and made available to downstream consumers. Sealed chains may not be retroactively modified.

Governance-First Axioms