# Kakurega Repository: https://github.com/xaorao/kakurega (README.md, docs/JUDGES.md, docs/FEATURES.md, docs/LIMITS.md). Demo video: https://x.com/prateekhh/status/2121602960840888480 A private AI workspace. A security layer outside the model decides what may leave the user's computer; a release is signed, and whoever receives it can check it offline. Working prototype on macOS and Linux; NEAR on testnet. ## Check it without installing anything (do X, see Y) - Open /proof/ : the page asks NEAR's public RPC six questions about the contract kakurega-registry-1ba6b2.testnet and compares the answers. Expect "All 6 checks match". - The same claims as data: /proof.json (each claim with the exact RPC request to POST and the answer to expect). - Open /verify/ and drop /sample/review.kkg on it. Expect "Valid", 20 answers each signed by Qwen/Qwen3.8-27B's own key, the signed claims, and what the check does not establish. Nothing is uploaded. - Open /#see : a replay of the real review that produced that capsule; the last step verifies it in the browser, then refuses it after one byte is changed. - Open /break/ : the same secret detector runs in the browser on text you write with a made-up secret in it, and says whether the secret would get past it. Expect "Held." for "A key in a settings file" and "Got through." for "A password in plain words" (a stated limit). A secret that gets through can be reported as a public GitHub issue (label break-it); the page shows the signed leak benchmark's numbers (0 of 126 known shapes and 10 of 42 other secrets reached the model) and the live count of reports, which counts a report as got through only once the maintainer labels it so. Nothing typed is sent. - Open /try/ : a secret detector (WebAssembly) and NEAR AI Cloud's client run in the browser. It withholds lines that hold keys, checks the model's hardware proof, sends the rest encrypted and checks the model's signature. Needs free tries to be on, or the visitor's own NEAR AI key. ## What NEAR does here - NEAR AI Cloud: the model runs in confidential hardware; each answer is signed by a key the hardware proof vouches for; the product checks proof and signature before showing an answer. - A registry contract on NEAR testnet records who registered a capsule and that its model signatures verified, and hands a model's Intel TDX quote to NEAR's own verifier contract. - An order holds payment for a review and releases it when a capsule signed by the reviewer key the order names is registered for it by the reviewer, before the order's deadline. An order can also require that every model key in the capsule has an up-to-date hardware record made after the order opened; the sample order did. ## Limits, stated by the project - Testnet only. A prototype, not a finished product. One sample capsule; small real counts. - A valid capsule shows who signed which bytes. It does not show that a finding is true or that no other defect exists. - The repository's README has "do X, see Y" steps from a terminal; `scripts/judge` runs the no-key checks in one command; docs/FEATURES.md has the state of every feature and docs/LIMITS.md the full list of limits.