vaultcrux.com · the technology behind cuecrux
Everything this platform claims is written down in one document and indexed as one corpus. You can read it front to back, or you can put a question straight to it and get the passages that answer it, with the gaps named.
Read
One document in 132 chapters and eight parts: what enters the corpus, how it is ranked, what the receipts prove, and what you have to run to make any of it happen. Start at the top and you have read the platform.
Start readingDiscover
The machine-room view. Each subsystem has its own explainer, engine, event substrate, daemon, receipts, corpus, mapping to real crates, real endpoints and benchmarks with a named corpus.
Open the mapTrails
Trails do not duplicate the chapters, they sequence them. Ground an agent, answer a compliance review, stand up private team RAG, extend the daemon. Progress is written by reading.
Pick a trailAsk
Retrieval over the same chapters, with the scores shown. Ranked passages, a computed coverage figure, the gaps named out loud, and every sentence cited back to the chapter it came from.
Ask a questionThat is the whole design, and it is the one claim worth checking first. A receipt binds the corpus snapshot, the ranked passage ids and the lane flags under one detached signature. Verification never contacts VaultCrux.
Read Receipt Verification
