The verification matrix.

• Exposes an ARCHANGEL/v0 signed status surface at monarch.xinus.one/health.
• Promotes to MEASURED · LIVE on signature verification against the operator pubkey.

Monarch is the one node a browser can directly verify. The card couples local CID derivation against the node's signed /health payload, verified with the published ed25519 pubkey.

• Registered in the fleet manifest as valkyrie.nexinus.net (5.78.148.244).
• Does not currently expose a CORS-readable health JSON.

Valkyrie is probed with an opaque HEAD request against valkyrie.nexinus.net. Opaque success means the origin answered; it does not prove application health, only that the host is reachable from the browser's network path.

• Reserved vertex for the Alpha triangle.
• Activates when an operator pins a signed status JSON to IPFS and its CID is written into this manifest.

Helsinki Vertex describes a topology intent. Promotion to LIVE requires a real IPFS CID resolving to an ARCHANGEL/v0 signed envelope; no probe runs until then.

• Sovereign witness surface for Earth's electromagnetic substrate.
• Configured to resolve its signed status via IPFS content-addressed payload rather than a REST /health.
• Falls back to opaque HEAD only if IPFS resolution fails.
• Bound to the 7D unity CID — any change here re-hashes the unification certificate.

Resonate-Earth couples the bitcoin substrate (work / pressure / density) to the planetary substrate (resonance / coherence). Its signed status envelope is expected to live at a pinned IPFS CID; the browser resolves through public gateways with signature verification against the node pubkey.

• Holds the operator key for fleet liveness stamps.
• Not directly reachable from the public web by design; participates via signed receipts.

Tesseract-A is held in operator custody. Its existence is asserted by signed receipts surfaced elsewhere in the fleet, not by a public endpoint here.

• Reserved vertex for the Beta triangle.
• Activates once a signed-status JSON is pinned; the browser will resolve it via IPFS gateway.

Beta IPFS Vertex has no HTTPS surface by design. Its liveness depends entirely on a content-addressed signed envelope; no CID pinned means no probe attempted.