Operations

Network Status

Planned

How status will be reported once there is a network to report on. This page deliberately contains no dashboard, no uptime figure, no node count and no green indicator, because a reassuring display with nothing behind it is worse than no display at all.

Not live

The network is not operating. Nothing on this page reports real activity, and no operational figures are shown, because no verified operational data source exists yet.

Source / verification: Operations model draft; no telemetry source exists
Document version: Not yet assigned
Last reviewed: 19 September 2026

Intended status categories

Planned status categories and how each would be evidenced
Category	What it would report	Evidence required
Acceptance	Whether new entries are being accepted.	Signed observations from validating nodes.
Epoch progression	Whether epochs are closing and snapshots publishing on schedule.	Published snapshot roots with timestamps.
Retention	Whether archive replication meets its obligation.	Retention attestations from custodians.
Read surfaces	Availability of explorer and API surfaces.	Independent probe results.
Governance	Whether authorized decisions are being applied.	Decision records and applied rule versions.

Every category is currently unreportable. None is shown as healthy, degraded or anything else.

Node and network indicators

Aggregate, not per-operator

Planned

Indicators are intended to describe network condition without exposing individual operator infrastructure.

Independently observable

Planned

A status claim should be checkable by a third party. Self-reported health with no external observation is not evidence.

No counts published yet

Documented architecture

Node counts, regions and participation figures appear only when there are nodes and a verified source for the number.

Degradation stated plainly

Planned

Partial function is reported as partial. Unknown is reported as unknown rather than assumed healthy.

Incident and status-history model

Incidents are intended to be recorded with a start time, an impact statement, updates during the event and a closing note describing cause and follow-up. History is retained rather than cleared, so the record cannot be quietly improved after the fact.

Incident history: none, because no system has been in operation.

Version information

Protocol version: Not yet assigned
Node software version: No release exists
Rule-set version: Not yet assigned
Snapshot format version: To be specified

Last-verified semantics

Each reported value is intended to carry the time it was last independently confirmed, not the time the page was rendered. A value older than its expected refresh window is shown as stale rather than current. Where a value has never been verified, it is stated as not verified — which is the case for everything on this page today.

Node architecture Explorer model

Evidence register

Each statement on this page is tracked against a source. A claim without a verified source is never presented as fact.

Claims on this page and the verification state of their sources
Claim	Source type	Verification	Note
Status categories, incident and version model	Operations model draft	Source claimed, not yet verified	Drafted from owner instruction; no operations document supplied.
Uptime, node counts, heights or health state	Telemetry	No source on file	No network, no telemetry, no figures displayed.