AILeash · operator console
The endpoints a browser cannot reach on its own. Your key stays in this tab and is never stored.
Runs the 28-vector battery through your own engine. Every probe is measured against this. Run it first — if it answers, the module can see your live scorer.
Fires the same battery at somebody else's scoring endpoint and compares the two sets of numbers. One request per vector with a gap between them.
Hashes every file, commits one manifest root, seals it with your declaration. Dated evidence of what you held and when.
Fetches a live page and seals the exact bytes served. Pins what the world could see on a given date, which is not the same as what was in the repo.
Every comparison you have run, with its verdict and receipt.
Walks every module on the router and reports what each one exposes, and which routes need a key. If you have forgotten what exists, this is the answer.
A root grant. It must be issued by a human, it must state a purpose, and it must expire. Whoever is named as accepting the risk is the person an incident lands on.
A child can narrow, never widen. Try raising the amount above the parent's and watch it refuse. A child that can delegate again must name its own risk acceptor.
The whole chain is re-derived at this moment, not trusted from when it was issued. Ask for more than the lineage allows and it names the grant and the invariant that broke.
Seals which records will be tested before any data is fetched. Once this runs you cannot choose a kinder sample, and an abandoned plan stays visible forever.
The values from your own live system, against the sample that was already sealed. Fill these honestly - a mismatch is sealed as permanently as a match, and that is the only reason any of it means anything.