Fenrua Status

loading Loading

Request started; verified status not yet available.

Reference definition · Retry: Retry after the configured refresh interval.

success Success

Source responded and supplied evidence within the freshness window.

Reference definition · Retry: Next check follows normal cadence.

partial Partial

Some required evidence is present but one or more declared checks remain incomplete.

Reference definition · Retry: Retry with scoped confidence.

stale Stale

Last evidence is older than the freshness policy.

Reference definition · Retry: Retry and keep previous value labelled stale.

failure Failure

Source failed or returned invalid evidence.

Reference definition · Retry: Retry with backoff and fail closed for decisions.

paused Paused

Source is intentionally paused.

Reference definition · Retry: No automatic retry until pause is lifted.

maintenance Maintenance

Source is undergoing maintenance.

Reference definition · Retry: Retry after the published maintenance window.

STATUS PLANE BOUNDARIES

What each status can and cannot mean

Publication, service, dependency, observation, incident, and maintenance status remain separate. This page does not publish uptime or an SLO because the required measured service history is not available.

01

Publication status

Static release commits, artifact manifests, and release verification records.

Open related record

02

Platform service health

Only measured deployed services belong here. No unmeasured specification is presented as health.

Open related record

03

Dependency health

Only a measured dependency can receive a current state. The public source currently publishes no generic dependency-health dashboard.

Open related record

04

Signed external observation status

Bounded signed observation state is visible only after its independent verification contract succeeds.

Open related record

05

Security incident status

No public incident history is fabricated. Private security reporting has its own scoped handling boundary.

Open related record

06

Maintenance and change status

Release and rollback changes are controlled through source-bound records and owner-authorised hosting actions.

Open related record

LIVE SIGNED OBSERVATIONS

Current public monitor

Each chain row is populated only from the bounded public observation endpoint. “Last signed observation” is that chain’s signed observation time, not an activation event or release-build time.

Checking the bounded public monitor. No current chain state is asserted until a signed observation is returned.

Mobile view is optimised for record-by-record inspection. Monitor rows preserve exact UTC observation times, signed sequence, and freshness scope.

Public monitor	Current public state	Last signed observation	Signed sequence	Observed block	Evidence basis	Freshness	Scope limitation
Chain 978 observation Bounded public observation	Checking	Checking for a signed public observation.	Not yet verified	Not yet verified	Public monitor pending	Awaiting monitor response	A current observation is not activation history, contract assurance, bytecode identity, reserve proof, deployment assurance, or a safety guarantee.
Chain N521 observation Bounded public observation	Checking	Checking for a signed public observation.	Not yet verified	Not yet verified	Public monitor pending	Awaiting monitor response	A current observation is not activation history, contract assurance, bytecode identity, reserve proof, deployment assurance, or a safety guarantee.

STATIC RELEASE RECORDS

Public release inventory

These are static publication records, not runtime monitors. They intentionally have no per-row event timestamp; use the current release manifest for source-commit and artifact-hash evidence.

Static release records are not live checks. Their validation scope and limitations remain visible without implying a current event.

Release record	Publication state	Maturity	Public artifact	Evidence basis	Validation scope	Current limitation	Next evidence gate
Homepage	Published	Routing surface	index.html	Static release artifact	static route validation	Live chain observations remain separate read-only public telemetry.	Browser viewport matrix
Architecture	Published	Specification	/architecture	Static release artifact	static route validation	Architecture is descriptive, not a deployed control plane.	Independent architecture review
Kernel	Published	Specification/reference mix	/kernel	Static release artifact	static route validation	Primitive maturity varies by row.	Per-primitive evidence expansion
Utilities	Published	Catalogue	/utilities	Static release artifact	static route validation	No fake live utility service is claimed.	SDK or CLI evidence
Research registry	Published	Evidence surface	/research	Static release artifact	static route validation	Dedicated pages expose current reproduction limits.	Independent reproduction
Verify examples	Partial	Prototype foundation	/verify	Fixture corpus	fixture corpus validation	No hosted verifier or upload model exists.	Real verifier implementation
Developer quick start	Published	Reproducibility guide	/developers	Static release artifact	clean checkout report	Node 24 required.	Tagged release reproduction
Toolchain registry	Published	Read-only release evidence	data/toolchain-registry.json	Frozen registry input	registry validation	Version capture is not security proof.	New frozen evidence bundle
Evidence registry	Published	Evidence surface	/evidence	Static release artifact	static route validation	Evidence provenance is scoped to public artifacts.	External evidence review
Commercial boundary statement	Published	Research and technology services	/docs/ACCESS_ONLY_COMMERCIAL_BOUNDARY.md	Public operating statement	public boundary and company-identity validation	The public site is an information and service-discovery surface; commercial services may be separately contracted and paid.	Capability-specific interface records if a self-service feature is introduced
Public repository	Published	Source surface	https://github.com/Fenrua-Labs-Pty-Ltd/fenrua-web	Release provenance	git provenance	Repository state changes after each deployment.	Tagged release
Schema set	Published	Specification	/docs/	Static specification set	example corpus validation	Schemas are examples/specifications, not a hosted validator.	Schema validator package