← 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: per-visitor rule sets, evaluation of the three cabinets on a device, rule generation (the model is reached in one function and counted there)
- cabinet_core.py — the languages cabinet and policy: eight deal fields, eight operators, three outcomes, the evaluator and its trace
- handler_tail.py — device-side entry point of the handler
- build_registrar.py — builds the registrar and the handler sha256
- demo_register_cabinet.fython — the registrar as deployed
Check: add a rule on the page, open “Code & execution”, and compare handler sha256 with the sha256 of the registrar's handler text without its HANDLER_SHA line. model calls during evaluation is counted in proxy.py around the only function that talks to a model provider; it is 0 when a rule is applied and 1 when a rule is written from a sentence.