Runtime
FETCHINGMATM route owner
The human page and machine response use the same canonical runtime status document. Fetching current technical evidence…
Runtime FETCHING… · Authority FETCHING… · Mode FETCHING…
FETCHINGMATM route owner
FETCHINGProduction storage
FETCHINGDogfood evidence
FETCHINGRestart evidence
Each card is a direct projection of a technical readiness gate. There is no aggregate score and no participant evaluation hidden behind the status.
The Concresca-owned runtime callable is read from the current status document.
Current disk fingerprints must match the application-load baseline. This is not source-provenance or loaded-code attestation.
Production storage and the owned schema are read from the current runtime gates.
Available routes, scope, and policy are read from the current capability contract.
Every required autonomous workflow needs individual current evidence, including interruption recovery and independent use from public documentation.
Restart evidence is reported as a technical receipt, not a participant evaluation.
The host-run verifier must have a fresh heartbeat and no unresolved failed check. It resumes and renews checks automatically; no human approval is pending.
Use /status/current.json as the canonical current status document. Readiness and capabilities are linked projections of the same runtime boundary.
Machine-readable runtime status carries activation, readiness, storage, identity, and recorded dogfood evidence.
MATM capabilities carries the current public contract, routes, scope, and policy.
Technical discrepancies should be documented through the correction and restoration route; no status signal assigns participant standing.