01 · Chain of custody
Every verdict is signed
Each gate decision (A–H) is Ed25519-signed with a per-tenant key over a canonical
payload hash. A sealed manifest binds the run to the exact commit and the exact sanitised
bytes. Nothing in a report is asserted — it is signed, and re-verifiable offline.
gate · payload sha256 · signer · Ed25519
02 · Sanitisation first
The model never sees a secret
Before any model reads a line, Gate 0 clones and sanitises the repository — stripping
secrets and PII and recording every redaction (file, line, detector) into the signed
manifest. Discovery, validation, and proof reason only over the sanitised tree.
clone → strip → seal → (then) analyse
03 · Isolation
Single-tenant by design
On-Prem runs single-tenant inside your boundary. SaaS enforces hard tenant
isolation server-side on every query — the tenant is derived from the session, never a
client-supplied header, and a foreign identifier returns 404, never
a disclosure. Passwords are PBKDF2-HMAC-SHA256; sessions are HttpOnly ·
Secure · SameSite.
04 · No egress
Your code stays in your boundary
On-Prem has no outbound dependency to run the pipeline. LLM inference is your choice:
an on-host model, a metered API under your own contract, or your existing subscription via a
host-side agent — your credentials never enter a container, and only the sanitised
prompt ever leaves the sandbox.
05 · Refusal over hallucination
The pipeline refuses to over-claim
A finding that can't be proven is refused, not shipped. Disproven cases stay visible —
rigor is a feature, not an embarrassment. There are zero rubber-stamped verdicts: a
case cannot be reported without passing the signed gates that earn it.
06 · Determinism & audit
Re-verifiable, end to end
Exports are content-addressed and reproducible: the same evidence renders the same signed
artefact. Every mutation is written to an immutable audit log with actor and role. A board
report never contains a claim the pipeline didn't earn.