Evidence-aware · action-led · yours to direct

Make work move. See it converge.

Chat for the first move. Flows and Offices for the next. SpiderMesh when bounded work needs to travel, return, and be reviewed.

5security layers
2nodes per work unit
10+weighted tags per memory
1,024MB scratch cap per node
The position

Verityasksyoutotrustamechanismratherthanapromise.Atenantfilterthatfailsclosed.Adigestthateithermatchesordoesnot.Aplanlimittheserversettlesagainstaverifiedidentity.

01 · SpiderMesh

SpiderMesh routes work you can inspect

Choose a bounded task, route it across available workers, then review the output. Verity keeps the next action visible instead of treating a model reply as the final word.

  • redundancy-2
  • sybil-pair guard
  • temp-0 / seed-7
  • digest equality
How consensus works
WORK UNITOWNER AOWNER Bnodenodedigest A == digest BVERIFIED
02 · Recall

Memory that funnels instead of dumping

Each memory is tagged from five lanes (entity, intent, domain, temporal, lexical) and every tag carries a computed importance.

Recall matches tags first, drops weak-only overlap, then scores only what survived. A per-tenant registry aliases near-duplicates and bridges siblings, so asking about AI reaches the memory filed under large language model.

  • 5 lanes
  • 10+ tags per memory
  • alias + bridge registry
  • O(matched tags)
Read the funnel
entity0.75intent0.70domain0.55temporal0.40lexical0.20FUNNELscore survivors, keep top-kweak-onlyoverlapdropped
03 · Flows and offices

Flows that diverge, offices that keep going

A conductor plans, workers run in parallel, an inspector converges the result.

Offices are standing teams. They checkpoint their state to a file, fire on a cron lease, and resume where they stopped.

Both run on the four Verity model tiers or on whichever providers you have configured. The models stay yours.

  • conductor / worker / inspector
  • STATE.md checkpoints
  • Redis cron lease
Open a flow
conductorworkerworkerworkerworkerinspector
Security by construction

Isolation is a shape the code takes, not a rule someone remembers.

  1. L1EdgeStrict CSP and sanitisation at the boundary.
  2. L2GatewayJWT verified against the issuer's keys; per-user rate limits.
  3. L3IdentityTenant identity travels as gRPC metadata, never as a request field.
  4. L4BrainUntrusted text is wrapped before it can influence a model.
  5. L5DataA mandatory tenant filter in the Rust core, fail-closed, covered by CI.
All five layers, with the code that enforces them

Deploy it. Read it. Argue with it.

Verity is source-available and runs on your own hardware. Start in the browser, or clone it and point it at your models.