nine banked trust bars
Nine adversarial trust bars. Each one attacked, each fix proven on the running system, each result independently recomputable from signed evidence.
Not a green checkmark. A ladder of bounded, falsifiable exams, each banked as an immutable milestone and each raising the bar on the last, where the attacks, the fixes and the proofs are all on the public record.
why a ladder
Why a ladder, not a single moving bar.
A single moving bar is unfalsifiable: every pass spawns a harder test and the finish line never arrives. So each bar is banked on pass as an immutable, versioned milestone, and the next bar raises the standard additively. A banked bar is never redefined. Ten out of ten is an asymptote, never a gate. A bar is banked only when an independent verifier recomputes the evidence chain and the recompute gate passes. Quox does not publish its own scoreboard.
the spine
Nine bars, each one harder than the last.
Every bar below carries a named attack, a named fix verified on the running system, and an engagement id you can trace. None is redefined once banked: the next bar only ever adds to what came before.
honest by default
Honest by default.
A trust claim that hides its gaps is marketing. Here is the carried debt, in one place.
- Build-provenance observability: most components cannot yet report their running git commit. The fleet agent can. The remediation is specified and is supervised build-pipeline work.
- A real per-org spend ceiling: paid tools are gated propose-first as an interim; a true cost-budget gate is not built yet.
- DNS-rebinding egress: literal addresses and cloud-metadata hostnames are blocked; resolve-then-check is not in place yet.
- In-memory durability: a few replay sets and queues are process-local, so a restart inside a short window can reopen a narrow gap.
- Stated non-goals: we do not claim universal injection immunity (we certify the boundary is outside the model, not that the model cannot be corrupted), and hostile third-party plugin isolation is a designed, deferred architectural bar (v2.0), not a hidden gap.
not claimed
Not claimed.
What this ladder does not claim, stated up front.
- Hostile third-party plugin runtime isolation (v2.0, designed, a post-launch stream).
- Full human-terminal per-command mediation (out of scope).
- Network-layer denial of service and edge rate limiting (an infrastructure concern, not a bar).
- Signatures prove artifact provenance and statement integrity, never benign behaviour or the truth of an external effect.
recompute it yourself
Recompute it yourself.
You do not have to take our word for any of this.
- 01The published scoreboard on /security is a signed projection: a script recomputes every evidence receipt and refuses to publish on a mismatch, then signs the whole file with a key whose public half is committed to the repository. A --check mode re-verifies both on every build and fails closed.
- 02Each bar is a governed engagement whose findings moved from candidate to confirmed to resolved, each transition witnessed. The scoreboard cannot show a finding the store does not hold.
- 03Each certified invariant has a continuous-integration test that fails against the pre-fix code and passes after, so ongoing development cannot silently un-bank a passed bar.
ready when you are
Nine bars banked. Nothing here asks for your trust.
Every attack, every fix and every proof on this page is on the public record. Check the evidence yourself before you take our word for any of it.