// 05b · Run the real engine
Don't take our word for it. Run the code.
The console above is scripted, for speed. This one is not. It loads HouseCommand's actual permission engine — the same Python that ships in the repository — into your browser and executes it on every command you type. No server, no model, no edits. The SHA-256 of each file is computed here and linked to the exact blob on GitHub, so you can confirm byte-for-byte that the code deciding below is the code we publish.
ENGINE MANIFEST · SHA-256 computed in your browser
COMPILING ENGINE…
~1,500 lines of the enforcement path — permissions, router, audit,
delegations, identity, health, state — with zero third-party imports. It runs the same in this
tab as it does on the estate.
OPERATOR
CLOCK
21:30
// the engine is compiling. one moment — this runs entirely in your browser.
PENDING CONFIRMATION
none
DECISIONS: 0
Standing consent
grant a certificate; matching AI proposals execute under your identity — no token ever reaches the model
At 21:30, the night-locking and night-arming windows are open. Grant one, then propose a lock as the AI.
Two proofs you can run
the safety case as an experiment, not a claim
Vigilance, one week
A week of routine night-time proposals, with and without three standing certificates. Watch the interruptions collapse.
Adversarial fuzz
Random operators, forged and stolen tokens, hostile houses, unknown verbs — thrown at the real engine in your browser. Five invariants, checked on every one.