Controls and live evidence
11 of 13 controls operating right now, 2 partly in place. Each reading below is taken live (refreshed every minute), not copied from a report. Markdown · JSON
| Control | What it does | Live evidence | Can support |
|---|---|---|---|
RS-LED-1 | Append-only, hash-chained, signed ledger Every recorded check, approval and action is hash-chained, sealed into Ed25519-signed Merkle blocks, and never edited or deleted. | Operating Chain re-verified at read: valid. 15,103 entries in 3,820 blocks. Issuer key key_41eb7b6d1b11968a. Verify the whole ledger · Verify a record | SOC 2 CC7.2, PI1.4 ISO 27001 A.5.33, A.8.15, A.8.24 ISO 42001 A.6.2.8 EU AI Act Art. 12, Art. 19, Art. 26(6) NIST AI RMF MANAGE 4.1 |
RS-LED-2 | Public timestamp anchoring Block fingerprints are published to the Bitcoin blockchain through OpenTimestamps, so history cannot be quietly rewritten afterward. | Operating Anchoring ok; confirmed through block 3,790. Anchor proofs | SOC 2 PI1.4 ISO 27001 A.5.33, A.8.24 |
RS-LED-3 | Independent witness co-signing (finality) Unaffiliated operators co-sign block heads; entries in witnessed, anchored blocks are final, settled by parties other than the service. | Partly in place Confirmed unaffiliated witnesses: 0 of 2 required. Until the quorum is met, records reach "anchored", not "final". Witnesses | SOC 2 PI1.4 ISO 27001 A.5.33 |
RS-KEY-1 | Signing-key succession by threshold A signing-key change takes effect only through a sealed plan naming three successor keys, a public challenge window, and two of three successors signing. | Partly in place Rule live: 2 of 3 successors, with a timelocked challenge window. Plan state: none announced. Status | SOC 2 CC6.1 ISO 27001 A.5.17, A.8.24 |
RS-CHG-1 | Recorded releases with automatic rollback Every release is recorded on the ledger with its commit; each new build is judged by a smoke battery and rolled back automatically on a confirmed regression. | Operating 123 releases recorded in the last 30 days. Current build verdict: pass; 19 builds judged. Release record | SOC 2 CC8.1 ISO 27001 A.8.32 |
RS-INC-1 | Self-filed incidents Failing checks file sealed incident records automatically, with exceptions-only paging, so an unattended system reports its own faults. | Operating Sealing ok; storage ok; webhooks ok. Status and history | SOC 2 CC7.3, CC7.4 ISO 27001 A.5.24, A.5.25, A.5.26 |
RS-ACC-1 | Every operator action is public Each use of operator power is sealed on the public ledger as an operator action (operation and a path hash). Delegated read keys can read, never change. | Operating 10 operator actions sealed in the last 30 days. Operator actions | SOC 2 CC6.1, CC6.3 ISO 27001 A.5.15, A.8.15 |
RS-ABU-1 | Scanner tripwires, adaptive limits and proof-of-work Scanner probes and wrong operator credentials are recorded by category against hashed networks; flagged networks must solve proof-of-work to register; abusive accounts are quarantined with an appeal path. | Operating 22 tripwire events in the last 24 hours (categories and hashed networks only). Security | SOC 2 CC6.6, CC7.2 ISO 27001 A.8.16 |
RS-MNY-1 | Fees in shadow mode behind circuit breakers Fees are computed and sealed but never executed until arbitration readiness and an explicit operator decision; per-transaction and daily caps trip an automatic pause. | Operating Fee mode: shadow. Circuit breaker: closed. Money status · Pricing | SOC 2 PI1.2 ISO 27001 A.8.32 |
RS-PRV-1 | Public records pass anonymity checks before sealing Public-facing records stage privately and pass schema, lint, anonymity and drift checks before they seal; public surfaces show aggregates only. | Operating Checks: schema, lint, anonymity, drift. Staged now: 0. Privacy | SOC 2 C1.1, P4.1 ISO 27001 A.5.34, A.8.11 |
RS-OPS-1 | Supervision evidence a customer can hand over Workspaces record agent actions with durable receipts, evaluate policies on a schedule, route exceptions to human review, send signed alerts to the customer's systems, and issue signed, hash-chained weekly statements a reviewer can verify without an account. | Operating Available to every workspace. Live workspaces: 0; signed statements issued: 0; active alert endpoints: 0. Operations | EU AI Act Art. 12, Art. 14, Art. 26(5), Art. 26(6) ISO 42001 A.6.2.6, A.6.2.8 NIST AI RMF MANAGE 4.1 SOC 2 CC7.2 |
RS-AVL-1 | Durable storage and replicated checkpoints Records are kept on durable storage; signed checkpoints of the ledger head are replicated beside the database and published daily. | Operating Storage ok. Daily snapshot published. Ledger snapshot | SOC 2 A1.2 ISO 27001 A.8.13, A.8.14 |
RS-VUL-1 | Vulnerability disclosure A published security contact and disclosure policy; security changes are recorded and dated. | Operating security.txt published; security changes listed. security.txt · Security changes | SOC 2 CC7.1 ISO 27001 A.8.8 |
Gaps, stated plainly
- Independent witness quorum: 0 of 2. Two unaffiliated operators confirm and co-sign block heads; records then reach the final rung.
- Designated successor keys: none announced. The owner announces a sealed plan naming three successor keys.
- Third-party attestation: None held. An independent auditor issues a report. Until then, every control here is evidenced by its live reading, not by an attestation.
What this page does not claim
- No SOC 2 report, ISO/IEC 27001 or ISO/IEC 42001 certificate, or third-party audit opinion is held or implied.
- Framework references show where a control can support a customer's own evidence. They are the service's mapping, not a determination that any requirement is met.
- Records prove what was submitted and when, and that it has not changed since. They do not prove that a self-reported action actually happened.
- Nothing here is legal advice.
Checked 2026-11-06T03:49:59.664Z.