Control-plane canary evidence
Inspect signed external evidence for semantics, journeys, and safety boundaries.
The control-plane canary is an external, read-only agent that tests what ENS.Tools responses mean rather than stopping at HTTP availability. Every run produces an immutable Ed25519-signed receipt with assertions, latency, evidence, freshness, and semantic-drift state.
Before you run this workflow
Networks
- No funded transaction network
- External HTTPS against production
Prerequisites
- Pinned Ed25519 public key
- Fresh hourly, daily, or nightly receipt
Wallet permissions
- None; the canary cannot sign or broadcast Ethereum transactions
Expected result
- Signature-verified assertion receipt with evidence, latency, and semantic-drift state
Errors and recovery
- Open or update one drift issue
- Keep production self-healing disabled
- Close the issue only after fresh passing evidence
How to use it
- 1
Choose a suite
Read hourly, daily, or nightly evidence according to the platform behaviour your task depends on.
- 2
Verify provenance and freshness
Require signature.verified, the expected key ID, and a fresh receipt. Missing or stale evidence is not a pass.
- 3
Read semantic assertions
Treat receipt.status=fail as unavailable even when the API returned HTTP 200. Inspect every non-passing assertion and semanticDrift flag.
- 4
Use evidence narrowly
A passing receipt is point-in-time evidence. It does not guarantee future behaviour or grant the canary authority to change production.
- 5
Inspect the source run
Follow the source-run link when you need the external execution context behind a receipt.
Safe operating boundary
Examples
{ "suite": "hourly", "limit": 3 }