Did the walls hold, and can you prove it?
1–16 October 2026 · Example Health · 6 scopes · Numbers run to Fri 16 Oct 2026, 14:20 UTC
Did the walls hold?
From 1 to 16 October, no AI agent or user got a note it was not allowed to see. TenWall stopped 7 calls at the wall: it kept notes back from 4 and refused 3.
Record check ✓ VALID
- When
- Today, Fri 16 Oct, 09:00 UTC
- Checked
- 5,462 entries, all 6 scopes
- Where
- On the privacy office's own machine, with ledgerverify
- Against
- Checkpoints the office holds itself, not TenWall's copy
Nothing in the record was changed or removed. Entries written after 09:00 are checked in tomorrow's run.
It only proves what flows through TenWall.
What was stopped
The 7 calls, newest first. Select a call to see its entry as TenWall writes it.
Who reads as agent ← agent ← person: the agent that made the call, then whoever it acts for. Patients appear only as a pseudonym. TenWall never stores note content.
What each agent did, 1–16 Oct
| Agent | Acting for | Calls | Kept back | Refused | Last active (UTC) |
|---|---|---|---|---|---|
| agent:orchestrator | dr.alvarez, dr.brooks | 2,412 | 0 | 1 | 16 Oct 14:19 |
| agent:summariser | dr.alvarez, dr.brooks, through agent:orchestrator | 1,426 | 3 | 1 | 16 Oct 14:18 |
| agent:billing-assistant | j.chen | 933 | 1 | 1 | 16 Oct 13:58 |
| a.patel (no agent) | herself | 733 | 0 | 0 | 16 Oct 12:11 |
| Total | 5,504 | 4 | 3 |
From TenWall's access record: each entry names the agent and who it acts for.
Check it yourself
Check the record
Your privacy office runs ledgerverify on its own machine. It shares no code with TenWall. It checks the record against the checkpoints your office kept.
FETCHED=$(date -u +%Y-%m-%dT%H:%M:%SZ) curl -s -H "X-DAC-Session: $OFFICE_SESSION" 'http://tenwall.internal:8080/memory/ledger' > northside.enc-lena.json ledgerverify -export northside.enc-lena.json -tenant northside.enc-lena -pubkey "$PINNED_KEY" -fetched "$FETCHED" \ -held checkpoints/northside.enc-lena/ -require-held -report lena-check.html # A long record comes in pages: fetch again with ?from=<next_from> and pass each page with its own -export.
Test the walls
The TenWall scan replays 28 leak attempts against a test copy of your store: once straight to the store, once through TenWall.
Our own test on Qdrant 1.19.1, one host. The scan only creates and removes its own scratch collections.
Coming next
- Break-the-glass review: emergency access with a reason, a short time window and review by your office the next day.
- Withheld-by-rule report: every note held back, with the rule behind it.
- By patient and purpose: look up one patient and see every AI access to their notes.
- Telling the clinician's app how many notes were held back, and why.
- Labels at write time, from fields your EHR already sets, such as note type and department.
- Quarterly attestation and per-patient AI access reports for your office.
- Connecting this preview to your hospital's sign-in and the Epic launch. Today both work against a demo sign-in and a demo EHR; Epic's test system is next.