n0rds3c.dev / lab

The lab

Run actions through the same kind of rules Vault AI uses, watch the trail build, then follow one request through the whole path. Nothing here talks to a server. The chain hash is SHA-256 in your browser.

Prefer the walkthrough? Follow the audit path ↓

01audit simulator

Every action leaves a row

Pick an action, flip a condition, press enter. The rules live in lab.json and match top to bottom.

audit · tenant a1f30 events

no actions yet. pick one above, flip a toggle, press enter.

chain hash · sha-256 over the last 8 rowsin memory only

02the audit path

Where a request stops

UI, API guardrail, tenant check, human gate, signed export. Toggle a failure and watch where it stops.

a second tenant shows upa foreign document in the result set the model is confident and wronghigh certainty, bad answer an integration bypasses the UIdirect API call

UI

pass

API guardrail

pass

Tenant check

pass

Human gate

pass

Signed export

pass

what broke

Early guardrails lived in the UI. The first integration that bypassed the UI proved they had to move into the API layer, where they now sit next to the tenant checks.

what i'd do differently

Design the audit model before the first feature, not after the first customer asked for it. Every later system was easier because the trail already existed.

Vault AI case study The note behind it

03github

last public event, read from now.json · the full dashboard