OBSERVATION BOUNDARY

Signed observations

Observation records are separate from publication and service status. Static output never asserts a current chain state; the monitor route reports a result only after its bounded verification contract succeeds.

Open current monitor Read the claim records

CURRENT CAPABILITY RECORDS

Read-only and evidence-bound

Chain 978 and Chain N521 have independent records. The N521 record remains unavailable until its gateway and public verification key are independently configured.

observation

Chain 978 bounded observation

reference-implementation · limited-preview

Bounded read-only Chain 978 observation adapter with public verification metadata and fail-closed states.

Lifecycle: active
Owner: operations
Review date: 2026-07-14
Claims: claim.observation.signed-read-only, claim.observation.observed-block-label

Limitation: A signed bounded observation is not contract safety, bytecode identity, reserve state, finality, or deployment correctness.

Non-claim: The endpoint does not accept transactions, forward public RPC, or expose private mesh details.

Promotion gate: Require configured signed observation inputs, key metadata, durable continuity controls, and scoped operational evidence before any maturity increase.

observation

Chain N521 bounded observation

research · not-available

Public boundary for a future bounded Chain N521 observation, designed to report awaiting state when independent evidence is absent.

Lifecycle: active
Owner: operations
Review date: 2026-07-14
Claims: claim.observation.n521-awaiting

Limitation: No liveness claim is made until an independent gateway and public verification key are configured.

Non-claim: A waiting or unavailable UI state is not a simulated live head or a claim of chain availability.

Promotion gate: Require independent signed observation evidence, public verification metadata, and an accepted bounded gateway configuration before availability changes.

EXPLICIT NON-CLAIMS

An observation is not authorization

A signed observation does not prove contract safety, bytecode identity, reserve state, finality, deployment correctness, chain availability, or production approval.

It does not accept transactions, forward public RPC, expose private mesh information, or replace a local policy decision.