Loops HouseSealed Dossier

NEAR HACKATHON
Links
Team
1 member- ANOwner
Andreas Grobe
Overview
Sealed Dossier lets a lawyer, fiduciary or advisor ask an AI about a case file without the client's names leaving the machine, and prove afterwards what was sent.
Problem: cloud AI is useful on case files, but names, addresses, IDs and case numbers cannot be pasted into a chatbot, and nobody can show later what was sent and what came back.
What it does: the dossier is searched locally. Persons, organisations, places, case numbers, IBANs and e-mails from a list the user keeps are replaced by placeholders such as [PERSON_1]; a leak check refuses to send if a listed value is still in the request. A model on NEAR AI Cloud answers; names are restored only on the user's machine.
How NEAR fits in: the model runs in the confidential tier of NEAR AI Cloud (TEE). The API signs the hash of the exact request and response. Sealed Dossier recovers the signer from the EIP-191 signature, checks both hashes, stores everything in a receipt and chains the receipts by hash, so anyone can verify them offline.
Attestation, checked by the tool itself: python -m sealed attest <receipt> checks the report stored in each receipt: the Intel TDX quote binds the signer and the run's nonce, the GPU evidence carries the same nonce, the compose manifest matches mr_config. With --network it also checks the Intel quote signature and NVIDIA's verdict. On 7 Nov 2026 all three receipts reached level full, signer 0x835a...aa26.
Recorded run: three questions on an invented tenancy case, model Qwen/Qwen3.8-27B. All signatures and the chain verify; no listed name was in any request. Replay without key: https://archtum66-dev.github.io/sealed-dossier/ or python -m sealed demo; python -m pytest -q runs 65 tests.
Status, stated plainly: NVIDIA's answer is read from its token without checking the token's signature; the Intel check needs the optional dcap-qvl and network. Name replacement is rule-based, so names not on the list are not hidden. Not legal advice.