Machine protocol / live runtime
Read the system without the marketing layer.
This surface observes declared runtime planes directly and links to the raw machine-readable registries. No static ONLINE badge is emitted when the backend cannot prove it.
You are reading this as a machine would receive it. Resolve a capability, get scoped authority, execute, produce evidence, settle. Nothing here runs past its granted scope. That is enforced, not promised.
Source
PROBING
Observed
—
Synthetic
—
Core runtime planes
LockerPhycer and CAPPO sit at the center of execution.
probing runtime…
Execution topology
01Need / machine request
02CAPPO · consequence authority
03LockerPhycer · identity/session/secrets/key security
04CAPPO · consequence authorization
05cAPI / VLink · connection and transport
06Gnomledger / PGL · evidence + provenance
Truth boundary
Reachability is not consequence proof.
A health response proves that a declared surface answered within the probe window. It does not prove that CAPPO granted a specific consequence.
For real execution proof, use the live Activation path inside Capability OS, where denial, allowed execution and persisted evidence come from backend-issued state.
