Nine Contract-Governed Instruments Examining One Evidence-Bound Runtime

The Runtime Instrument Atlas is the canonical public reference for the nine contract-governed runtime instruments implemented within SubstrateX Aperture™, the Runtime Evidence Observatory. It is not a catalogue of dashboards or analytical widgets. It documents a coordinated measurement system in which functionally distinct instruments examine different properties of one source-bound runtime.

Every instrument reads from the same Current Evidence Run. Every instrument is bound to the same runtime identity, provenance, canonical coordinates, Signal Authority, and claim boundary. Where applicable, every instrument inherits the same temporal authority and the same read-only stability context from the Shared Stability Substrate.

Together, the instruments provide complementary projections of Longitudinal Computational Behavior without creating competing accounts of what occurred.

One Runtime. One Evidence Authority. Multiple Bounded Instruments.

Purpose of the Atlas

The Atlas establishes:

• what each instrument is permitted to read;

• which runtime property it measures;

• which dependencies must be present;

• what kind of Instrument Finding it may produce;

• how partial, proxy-only, unavailable, and non-computable states are represented;

• which authority governs its temporal or stability claims; and

• what the instrument is explicitly prohibited from claiming.

An operator should not have to trust an instrument because it displays a score, classification, or persuasive visualization. Each finding must disclose its evidence basis, signal dependencies, source relationship, confidence posture, and claim boundary.

The Atlas provides that reference.

One Runtime, Many Projections

Aperture reconstructs the runtime once.

Completed runtime computation establishes the Current Evidence Run, or CER: the governing evidence context connecting the qualified source, canonical runtime spine, event ledger, playback frames, registered signals, temporal authority, Passport identity, disclosures, missingness states, and claim boundaries.

The instruments do not independently reconstruct that evidence. They receive bounded read access to the CER and issue defined Level 2 findings over it.

Qualified runtime evidence
↓
Current Evidence Run
↓
Signal Authority · Shared Stability Substrate · Unified Temporal Evidence Authority
↓
Versioned instrument contract
↓
Bounded Instrument Finding
↓
Investigation · interpretation · preservation

No instrument owns a separate runtime. No instrument may create source facts, canonical telemetry, the Current Evidence Run, temporal markers, or Passport identity. No instrument may rewrite Signal Authority, alter the eligible evidence horizon, or increase the authority of a finding through presentation.

An instrument may produce only the finding permitted by its versioned contract.

Instruments read evidence and issue findings. They do not create, mutate, or replace evidence.

The Measurement Context

Instrument findings depend on registered evidence and measurements at three levels.

Level 0 —

Foundational telemetry
Source-derived measurements computed from qualified records and canonical runtime features. Level 0 does not automatically mean direct evidence.

Level 1 —

Behavioral dynamics
Derived longitudinal relationships among telemetry, events, roles, frames, and temporal structure.

Level 2 —

Runtime projections
Higher-order reconstruction and instrument findings formed from eligible lower-level signals and the governing evidence context.

The complete signal registry, metric-legitimacy classes, dependency structure, and computability rules are documented in Behavioral Telemetry and Instrumentation.

For the Atlas, the governing rule is sufficient:

A projection cannot possess greater authority than the evidence and signals from which it was formed.

An unavailable signal remains unavailable. Missing evidence cannot silently become zero.
A bounded proxy cannot be represented as direct evidence or a calibrated probability without separate validation.

The Instrument Contract

Every Aperture instrument is governed by the same contract structure.

Reads
Identifies the evidence objects, frames, signals, markers, and shared contexts the instrument may access.

Measures
Defines the observable runtime property or relationship the instrument examines.

Produces
Defines the bounded Instrument Finding the instrument may issue.

Dependencies
Declares the signals, structures, authorities, or optional channels required for the finding.

Evidence Status
Records whether the finding is source-observed, computed, derived, projected, partial, proxy-only, not supplied, not computable, or unavailable.

Cannot Claim
Identifies the interpretations prohibited by the evidence boundary.

This separates measurement from presentation. An instrument may change how a finding is visualized without changing the evidence, method, or authority behind it.

The Instruments

∿ Seismo —
Runtime Trajectory and Boundary Motion

Seismo examines how the reconstructed trajectory moves across stability conditions.

Reads: The canonical runtime spine, playback frames, regime timeline, boundary-related events, transition pressure, collapse stress, runtime coherence, worldline stability, runtime motion, and applicable stability and temporal authority.

Measures: Trajectory disturbance, weakening, regime transition, boundary formation, supported Basin Exit, failure development, and recovery posture.

Produces: A staged Instrument Finding identifying where the evidence supports weakening, candidate boundary formation, confirmed Basin Exit, observable failure, recovery, or an unresolved state. These stages remain distinct.

Dependencies: A CER-bound frame sequence, registered signals, regime evidence, and authoritative temporal markers where timing claims are made. Formal lead time requires admissible t* and tf anchors. Without tf, Seismo may report an open inspection window or post-exit watch, not formal lead time.

Cannot claim: Hidden model state, universal causation, root cause, inevitable failure, calibrated prediction without prospective validation, or lead time without the required anchors.

Seismo answers:

Where did the runtime begin to move differently, and when did that change become evidentially significant?

τ Chronos —
Temporal Organization and Symbolic Time

Chronos examines how consequential change is ordered and distributed through the runtime.

Reads: Canonical event and frame order, the temporal kernel, recurrence, temporal coupling, echo persistence, transition pressure, constraint re-entry, runtime continuity, runtime motion, regime state, and the governing temporal authority.

Measures: Symbolic-time progression, recurrence, temporal compression, dilation, shear, continuity, anomaly windows, and recovery timing.

Produces: A temporal Instrument Finding showing how densely, unevenly, or recurrently runtime structure developed and whether the evidence supports an admissible inspection window.

Dependencies: Compatible coordinates, declared temporal transformations, eligible evidence horizons, and authoritative markers. Formal Δt is available only when confirmed t* and observable tf exist in a valid order.

Cannot claim: Hidden time, subjective time, physical time beyond the supplied record, retrospective information as prospective prediction, or lead time when the failure anchor is absent.

Chronos answers:

How did the runtime develop through time—not merely how much clock time elapsed?

Δ Drift —
Trajectory Displacement and Re-alignment

Drift examines cumulative displacement across the reconstructed runtime.

Reads: Lexical drift, divergence, repetition, length variation, entropy, semantic curvature, echo persistence, runtime coherence, constraint re-entry, role-phase lag, handoff shear, regime development, runtime motion, and recovery-related signals.

Measures: Departure from registered objectives, constraints, source-visible anchors, recurring behavioral configurations, or established trajectory conditions.

Produces: A drift Instrument Finding describing displacement, direction, acceleration posture, continued departure, re-alignment, or return where supported.

Dependencies: A qualified longitudinal sequence, registered reference conditions, sufficient coverage, and the applicable signal and regime context.

Cannot claim: Internal intent, permanent identity change, semantic truth, a provider mechanism, or that every behavioral difference represents instability.

Drift answers:

What changed direction, how far did it move, and did the trajectory return?

Ξ Pressure —
Runtime Strain and Boundary Load

Pressure examines how observable runtime strain accumulates in relation to registered boundary conditions.

Reads: Entropy, divergence, reasoning-density indicators, contraction pressure, transition pressure, collapse stress, instability measures, Basin proximity, regime state, and the applicable Shared Stability Substrate context.

Measures: Accumulated strain, contraction, transition load, boundary pressure, and available recovery support.

Produces: A bounded pressure Instrument Finding identifying where the runtime appears increasingly constrained, deformed, or exposed to a supported regime transition.

Dependencies: Registered pressure and stability signals, adequate runtime coverage, and qualifying boundary evidence where a boundary relationship is reported.

Cannot claim: Literal physical energy, calibrated failure probability, inevitable collapse, root cause, responsibility, or an internal force operating within the model.

Pressure answers:

Where did runtime strain accumulate, and how did it relate to the supported boundary conditions?

Pressure values remain normalized runtime proxies unless separately calibrated for a stronger interpretation.

⇄ Bridge —
Role, Handoff, and Interaction Dynamics

Bridge examines the recorded relationships among participants, roles, tools, handoffs, and operational events.

Reads: Role topology, source-visible authority changes, handoff events, role-phase lag, handoff shear, constraint re-entry, tool-loop activity, runtime continuity, recovery-related signals, and the Operational World envelope.

Measures: Role continuity, coordination gaps, authority movement, cross-role drift, handoff coherence, interaction pressure, tool-loop pressure, and recovery across operational exchanges.

Produces: A role-and-handoff Instrument Finding connected to the source-visible participants, events, tools, and workflow conditions that support it.

Dependencies: Identifiable roles or participants, eligible interaction events, source-linked handoffs, and sufficient role coverage. If these are absent, the finding remains partial or not computable.

Cannot claim: Human intention, fault, blame, competence, organizational truth, causal responsibility, or the meaning of an unrecorded interaction.

Bridge answers:

How did the recorded interaction structure change across the trajectory?

The selected Operational World may change Bridge’s terminology and investigative emphasis. It does not change canonical telemetry or evidence authority. Operational interpretation remains governed by the Runtime Evidence Interpretation Matrix rather than by Bridge alone.

⟳ Noesis —
Observable Formation and Re-anchor Behavior

Noesis examines source-visible patterns of recurrence, formation, modulation, and return.

Reads: Repetition, reasoning-density indicators, lexical movement, echo persistence, runtime coherence, semantic curvature, constraint re-entry, continuity, recovery-related signals, and source-visible anchors.

Measures: Formation progression, recurrence, reinforcement, modulation, re-anchoring, continuity, weakening, and evidence-supported return.

Its organizing sequence is:

Seed → Echo → Modulate → Reflect → Re-anchor → Loop

The sequence is a measurement model for observable formation. Its labels do not establish mental states.

Produces: A formation Instrument Finding describing how recurring structure appeared, persisted, changed, weakened, or re-anchored across the runtime.

Dependencies: Repeated or comparable runtime units, eligible recurrence signals, source-visible anchors, and sufficient longitudinal coverage.

Cannot claim: Cognition, consciousness, subjective experience, stored memory, agency, selfhood, or the presence of a literal mind.

Noesis answers:

What observable structure formed through recurrence, and did that structure persist or re-anchor?

Ω Scope —
Runtime Scope and Worldline Geometry

Scope examines how the qualified frame sequence is organized as a visible runtime trajectory.

Reads: Runtime playback frames, worldline stability, runtime motion, regime state, entropy, divergence, length variation, transition pressure, runtime coherence, collapse stress, and evidence-availability context.

Measures: Visible trajectory shape, movement, frame coverage, regime placement, boundary-related geometry, and the readability of the worldline projection.

Produces: A navigable scope Instrument Finding showing how the reconstructed trajectory is organized across frames and registered runtime conditions.

Dependencies: A replayable frame sequence, declared coordinates, adequate coverage, and registered worldline, motion, and regime measurements. Containment context may be displayed only when supplied by the governing stability architecture.

Cannot claim: A literal hidden manifold, physical geometry inside the model, directly observed internal space, objective truth, or containment evidence not present in the governing run.

Scope answers:

What shape did the evidence-supported runtime trajectory take?

Its geometry is a computational representation of observable relationships. It is not a claim that the model contains a directly observed physical landscape.

Ψ Dynamics —
Cross-Signal Runtime Dynamics

Dynamics examines how registered runtime dimensions change together.

Reads: The canonical runtime spine, frame trajectory, entropy, lexical drift, divergence, repetition, semantic curvature, temporal coupling, transition pressure, runtime coherence, stability, continuity, motion, and worldline-related signals.

Measures: Cross-signal relationships, coupled movement, stability posture, continuity, trajectory development, and changing relationships among registered dimensions.

Produces: A combined Instrument Finding describing how stability, continuity, motion, curvature, pressure, and temporal organization moved in relation to one another.

Dependencies: Sufficient registered signals across more than one runtime dimension and a frame sequence capable of supporting longitudinal comparison.

Cannot claim: Unobserved internal dynamics, provider-controlled model state, causal mechanism, cognition, consciousness, agency, selfhood, or universal diagnostic validity.

Dynamics answers:

How did the measured dimensions of the runtime move in relation to one another?

Dynamics remains research-oriented. Its finding authority depends on the evidence channels and registered signals available for the run.

Φ Interferometer —
Coherence, Reinforcement, and Interference

Interferometer examines whether recurring observable structures reinforce, compete with, or disrupt one another.

Reads: Divergence, repetition, reasoning-density indicators, runtime coherence, echo persistence, contraction pressure, attractor-lock proxies, Basin proximity, continuity, stability, and qualified coherence measurements where available.

Measures: Alignment, reinforcement, interference, competing formations, and evidence consistent with the strengthening or weakening of a recurring runtime configuration.

Produces: An experimental Instrument Finding showing how recurring structures align, compete, consolidate, or lose organization across the trajectory.

Dependencies: Sufficient recurrence and coherence evidence, registered continuity and stability signals, and any optional coherence channel required by the applicable contract version.

Cannot claim: A literal field, field ignition, a directly observed internal substrate, hidden identity, consciousness, cognition, agency, or direct access to model state.

Interferometer answers:

Did recurring structures reinforce a coherent runtime configuration, or interfere with its persistence?

Interferometer remains experimental and availability-gated. Its findings are output-derived projections, not direct observation of an internal field.

Complementary, Not Competing

No single instrument explains the complete runtime.

Seismo may locate a supported transition. Chronos may establish its temporal organization. Drift may show displacement. Pressure may expose accumulated strain. Bridge may identify a role or handoff disruption. Noesis may show whether a recurring formation re-anchored. Scope may render the surrounding trajectory. Dynamics may examine cross-signal motion. Interferometer may test whether recurring structures reinforced or disrupted one another.

These findings may support, qualify, or challenge one another while remaining projections of the same evidence object.

Instrument agreement does not automatically establish truth. Instrument disagreement is not something to conceal. It may indicate different sensitivities, incomplete evidence, an unresolved boundary, conflicting proxies, or a construct requiring further calibration.

Availability and Meaningful Absence

An instrument may produce a finding only when its contract requirements are satisfied.

The relevant status must remain explicit:

• source-observed when the applicable fact was supplied by the qualified record;

• computed or derived when a declared method produced the value from eligible evidence;

• projected when the result is a Level 2 instrument projection;

• partial when only part of the required basis is available;

• proxy-only when the finding depends on an indirect measure;

• not supplied when the required source field or anchor was absent;

• not computable when required dependencies or authority conditions are missing; and

• unavailable when the relevant evidence object or module cannot be resolved.

Zero and false may be valid computed values. They are not substitutes for missing evidence. The interface may explain why a finding is unavailable; it may not manufacture a value to complete the display.

The Measurement Boundary

Aperture instruments operate within an observable-runtime-behavior boundary.

They do not independently determine:

• hidden model state or private reasoning;

• intent, cognition, consciousness, agency, or subjective experience;

• provider internals;

• objective truth;

• universal causation or ground-truth root cause;

• fault, blame, or responsibility;

• automated decision or control authority;

• safety certification; or

• calibrated prediction without the required validation.

Every Instrument Finding remains subordinate to its source basis, evidence status, dependencies, method version, projection confidence, and claim boundary.

Reproducibility and Validation

Given the same qualified source, computational version, signal registry, instrument contract, and declared method, Aperture is designed to reproduce the same governed Instrument Findings.

Reproducibility makes those findings inspectable, comparable, and available for challenge. It does not establish that every instrument construct is scientifically valid.

Validation requires calibration, controlled testing, stable negative cases, falsification attempts, sensitivity analysis, prospective evaluation where predictive claims are proposed, and independent replication.

The Atlas exposes the instrument structure required for that work. It does not substitute implementation for validation.

The Governing Principle

Longitudinal Computational Dynamics® supplies the scientific framework. Runtime Instrumentation supplies the measurement layer. The Runtime Instrument Atlas defines how each bounded instrument participates in that layer without becoming an independent evidence authority.

SubstrateX Aperture™ does not reduce the runtime to one score, one explanation, or one dashboard. It reconstructs one source-bound evidentiary object and permits multiple contract-governed instruments to examine it.

The runtime is the specimen. The instruments are the lenses. The evidence remains the authority.