Five claims you can test yourself

Type a message, choose the code, then jam or intercept bearers. The sender seals the message under a fresh key, codes the ciphertext into n shards (any k rebuild it), Shamir-shares the key across the same shards, and caps every bearer at k−1 shards. See what the receiver can rebuild and what the interceptor actually learns. Then intercept a second bearer and watch the guarantee end, which is why the end-to-end session layer exists.

Your radio's Ed25519 identity seed is split t-of-n across its formation. Sign with a quorum, take custodians out of range, advance epochs, then let OPFOR capture your radio, coerce the operator, or harvest custodian radios one at a time. Raise SOLO_GRACE_EPOCHS to see the cost of letting isolated nodes keep talking.

One brigade, 72 ticks, an orders group twelve ticks before H-hour. The top trace is what an observer sees of a conventional encrypted net; the bottom is Saelvor at the cover rate you choose. Lower the rate to save bandwidth and watch the price move to latency. Below, two real on-air frames: one carries a fire mission and one is chaff. Tell them apart.

One contact report, sealed once. Each field carries its own policy over clearance attributes; four readers open the same bytes with their own key rings. Build your own reader to try the 2-of-3 release-authority gate. The HUMINT field is invisible rather than redacted: it is indistinguishable from padding.

Left: an intent capsule the aircraft enforces on its own. Move the aircraft on the map, run the mission clock past the time box, or have a captured staff tablet sign the capsule instead of the quorum. Right: the mission ledger. Edit any entry and see the chain break from that point on.