Core system
VaultCrux
The trust plane: verification, attestation and privacy machinery
VaultCrux is the trust plane of the CueCrux platform: the verification machinery, the attestation pipeline, and the credibility surfaces (this site and the benchmark spine) whose one job is to make every other part of the stack checkable. The name once covered a hosted private-RAG product; that product was retired when the platform consolidated on the Crux Engine, and what remains under the name is the part of the system an auditor touches first.
Receipt verification is the core of it. CROWN receipts are Ed25519-signed with the signature bound to both the receipt id and the payload hash, sealed into BLAKE3-chained segments, and verifiable entirely offline with corecruxctl: no network, no account, no trust in this website. The verifier rejects malleable signatures and small-order keys, and committed conformance vectors (expected digests for store and replay) keep the Python and TypeScript SDKs verifiable against the Rust core rather than merely compatible with it.
Release attestation extends the same discipline to the software itself. Every published build carries cosign keyless signatures, a CycloneDX SBOM and SLSA3 provenance, and the export, offline-verify, tamper-reject cycle runs as a release-blocking CI gate: a build that fails to catch tampering never ships.
Privacy is enforced by construction rather than policy. Reserved-prefix facts (passports, sessions, operational state) are forced private at the store level and seeded unconditionally at daemon boot, so an operator who configures nothing still gets tenant isolation. Private facts never leave the machine. Scoped forget with dry-run makes GDPR Article 17 erasure auditable: see exactly what would be deleted, then delete it, and the deletion leaves a receipt while the content does not. The local-first posture is contractual: you cannot pay the platform to park your data, and paid enrichment is processed in flight and returned to your store, never held.
It surfaces as vaultcrux.com, the /security and /benchmarks pages, and the verifier tooling that ships in every daemon. If the rest of the platform is the machine, VaultCrux is the part that lets you check the machine without believing anyone.
