← back to the demo
Server source
Everything the browser talks to, published so the claims can be read, not believed. Secrets come from the server environment; none are in these files.
- README.md — what each file does and how to check the handler hash and the model-call count yourself
- proxy.py — the only server process: render cache, handler re-registration per device, block generation (the model is reached in one function and counted there)
- block_core.py — the block language: seven types, text-only fields, escaping, both renderers (v1 editorial, v2 compact dark), the laws
- handler_tail.py — device-side entry point of the HTML handlers v1 and v2 (one renderer, two looks, chosen by a constant)
- handler_text.py — handler v3, written separately: the same documents rendered as plain text; shares only the grammar
- build_registrar.py — builds both registrars and the handler sha256
- demo_register_block_v1.fython, demo_register_block_v2.fython, demo_register_block_v3.fython — the registrars as deployed
Check: render through the page, open “Code & execution”, and compare handler sha256 with the sha256 of the registrar's handler text without its HANDLER_SHA line (build_registrar.py shows the exact computation). model calls during this render is counted in proxy.py around the only function that talks to a model provider.