Trust Center

Launch truth, not launch theatre.

VEILOS shows the gate state it can prove locally and names the gates it must not fake.

Public archive event Future Obelisk-gated

the organism judges itself: nascentthe proof system, itself alive · zero-token · deterministic

Preflight: red
CSP routes: 68
Registry routes: 240
Evidence source: fresh deploy attestation
Vault status: Unknown
Receipt posture: unknown
Identity assurance: 0

The external witness

An independent runner (the repo's CI) exercises every public probe ~4×/day and goes red the moment this organism dies unwatched — a dead worker cannot confess. Each completed run leaves a counts-only mark here.

Latest witness mark stale

42/43 probes FAILED · 285.4h ago · origin manual-smoke

Window freshness promise: arrive within 13h 285.4h used of 13h · 100%

overdue — the witness has not reported within the promised window

no mark in 285.4h — the witness itself may be down, and this absence is the signal · 0 marks in 7 days

Cleared gates

pending launch review

Remaining gates

fresh canonical release attestation

Checks

measured computed live in this isolate · asserted proven by release preflight / Studio Ops at deploy time, restated here.

Project audience valid

fail attested

build-stamped release vars

Vault status consistent

fail attested

build-stamped release vars

Durable database bound

pass measured

env.DB binding, this isolate

Strict CSP on public pages

pass attested

0 findings at 2026-08-04T21:53:45.293Z

Obelisk approval state valid

fail attested

build-stamped release vars

App release gate valid

fail attested

build-stamped release vars

Realtime rooms cost-gated

pass measured

env.COLLAB_ROOM absent - paid realtime stays gated

Free tier cost-neutral

unknown attested

unknown - no fresh canonical cost-gate evidence

Sovereign identity signed

fail measured

FORGEABLE - SESSION_SECRET unbound; identity is signed with a public-in-source constant. Bind the Worker secret to close this.

Launch route evidence

The registry declares 35 launch probes for this surface family. No measured result travelled with this build — the deploy rail publishes per-route evidence at its next run, and this page will restate it rather than guess. A declared probe is coverage intent, never a verdict.