Evidence-aware · action-led · yours to direct

Make work move. See it converge.

Chat for the first move. Flows and Offices for the next. Verity model delivery keeps the work moving with its operating and evidence rules intact.

5security layers
4connected work surfaces
10+weighted tags per memory
1operating policy
The position

Verityasksyoutotrustamechanismratherthanapromise.Atenantfilterthatfailsclosed.Anevidencerecordyoucaninspect.Aplanlimittheserversettlesagainstaverifiedidentity.

01 · Model delivery

A model path you can inspect

Choose a Verity tier, shape the effort, and keep the next action visible. Verity carries its operating and evidence rules with the work instead of treating a model reply as the final word.

  • Verity tiers
  • effort control
  • operating policy
  • evidence rules
Read model delivery
entity0.75intent0.70domain0.55temporal0.40lexical0.20FUNNELscore survivors, keep top-kweak-onlyoverlapdropped
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

A clear brief, a small team, durable work

A lead plans, team members work in parallel, and a checker reviews before the result is combined.

Offices are standing teams. Give each team a manager, members, a checker, and a scoped team space. Add routines only when the work needs them.

Each role can use the model that fits the job, while Verity keeps the team’s context visible and bounded.

  • lead / member / checker
  • checkpointed runs
  • optional routines
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.