MWS Sentinel Loop draft-reilly-mws-00 §7.9–7.10 Operator: Reilly Protocol Suite --:--:-- UTC
Autonomous Web Healing — Live Attestation Ledger
Agents continuously verify, archive, and repair the web's record across six permanence layers. Every line below reduces to an independently checkable fact. Spec: draft-reilly-mws · draft-reilly-cogsov
CONNECTING… APPEND-ONLY · REPAIRS NEVER REWRITE HISTORY
L0
Live Web
L1
Triple FP
L2
Bitcoin/OTS
L3
DOI/Zenodo
L4
IPFS
L5
Web Archive
artifacts under watch
verifications passed (24h)
drift events recorded
repairs performed
latest anchored BTC block
next sentinel pass
Demo mode. This is simulated Sentinel activity, generated per §7.9–7.10 semantics so the ledger can be seen live. To connect the real pipeline, serve GET /api/sentinel/state and GET /api/sentinel/events?after=<iso> from the REM Protocol agent (JSON contract documented at the top of this file's script) and set CONFIG.ENDPOINT. The badge switches to LIVE automatically on first successful fetch.

7.9SENTINEL LOOP — LIVE LEDGER

Append-only. Fingerprint re-verification, anchor re-verification, resolution checks, drift detection, and Stage-10 repairs, as they happen.

UTCSTAGEARTIFACTLAYERRESULT

8ATTESTED CORPUS

Each artifact's layer coverage and most recent full verification.

ARTIFACTSHA-256L1–L5LAST VERIFIED

9VERIFY IT YOURSELF

No claim on this page requires trusting the operator. Pick any artifact:

1  Fetch it from a fallback layer and hash it — sha256sum <artifact> — the digest matches the ledger or it doesn't.

2  Check its Bitcoin anchor — ots verify <artifact>.ots — the proof verifies against the chain or it doesn't.

3  Resolve its DOI at zenodo.org/search?q=reilly and its draft record at datatracker.ietf.org — it resolves or it doesn't.

Independent operators: the cross-verification procedure is specified in draft-reilly-mws §10.2. Run it against this corpus and publish your records.