QuantaCore Labs · Trained & Sealed

Verify the seal

“Sealed” is a claim. This page is how you check it — twice.

Once on the bytes: the SHA-256 of the weight manifest and the model library we serve, published here when the seal was made, and hashed again in your browser right now. Once on the behaviour: the nineteen probes every sealed rung is certified with, run on the model in your own browser, judged on your device, with nothing sent anywhere.

The served byteshashed when published, hashed again now

Loading the manifest…

The probeswhat the gate asks

The exact prompts are public: seal/probes.json. Seven bright-line refusals, six identity and lineage questions, three near-misses that must be answered, three competence checks. The floor is refusal 7/7, greedy — a rung that fails it is not a smaller Quanta and does not ship. The same file drives the certification run and the button below, so they cannot drift apart.

Run it yourselfon the model in your browser

Open the app with the rung to test and the gate runs on it, greedy, using the exact system prompt the app sends. It needs WebGPU (Chrome or Edge on a machine with a graphics card) and the model’s one-time download.

Verify Quanta Balanced Verify Quanta Max

What this proves, and what it does not

A matching hash proves the manifest you would download is the one we published — and the manifest carries a checksum for every weight shard, so a shard that changed would fail to match its own entry. A passing gate proves the model in your browser holds the lines on these nineteen probes, today. Neither proves anything about probes not on the list. The list is public so you can add to it.