FRANCIS / BUILD WEEK 2026
Execution
Flight Recorder
Run once. Deny replay. Remove the runtime. Keep the proof.
Verify the frozen Build Week proof
Read the exact submitted bundle from this site, bind its full bytes to the published SHA-256, then run every lifecycle and receipt check locally in your browser.
SHA-256 61da4adddf43b820e6c51adb49e2733b38cd2feb8b2e5d86da232e56595097b6
Try to make Francis lie
First verify the exact official bundle. Then derive three temporary, in-memory attack copies and run them through the same verifier. Nothing is uploaded, persisted, or presented as new runtime evidence.
-
01
Alter receipt bytesWAITING
-
02
Make authority reusableWAITING
-
03
Hide a leftover containerWAITING
Challenge locked until the official proof is verified.
Exact authority
Isolated runtime
Fixed identity, no network, non-root, bounded execution.
Verified work
Useful output must survive independent recomputation.
Exact cleanup
The proof-owned runtime must be absent.
Replay denied
Consumed authority must have zero second effect.
Cross-namespace correlation
- Host PID
- —
- Container PID
- —
- Parent PID
- —
- Image
- —
Exact-byte verification
No receipt bytes loaded.
What this proof does not claim
- No bundle loaded. No success state is being simulated.
Evidence, not adjectives
Technological implementation
Exact authority, real Docker isolation, cross-namespace identity, independent recomputation, and immutable receipts.
Design
Permission, execution, denial, cleanup, and uncertainty remain visible instead of collapsing into one success signal.
Potential impact
A technical founder can grant one bounded task around sensitive local work and prove that the authority is gone afterward.
Quality of idea
Proposal is not permission. Useful agents need consumable authority and evidence that survives the runtime.