agent-fabric
Overview

The Veridex Agent Fabric

The only TypeScript agent runtime that gives you safe, stateful, long-context autonomy without the framework magic.

Veridex is a TypeScript-first agent runtime designed around a single thesis: every consequential thing an agent does must be typed, gated, observable, and resumable. We didn't add safety as a feature; we built the loop around it.

Why another agent framework?

Every team building agents in production hits the same wall:

PainWhere it bitesWhat competitors doWhat Veridex does
The framework rewrites prompts behind your backDebugging is impossibleLangChain/LangGraph mutate state in reducersEvent-sourced loop β€” every transition is a typed event you can read (ADR-0049)
Long conversations degradeQuality cliff after ~30k tokensBuffer + summarise on overflowStrict effective window VeV_e with per-section budgets and homeostatic compression (ADR-0050)
"Memory" is just transcript replayCost bloat, staleness, driftVector store as a toolFour tiers + reconciler β€” promotion, decay, conflict resolution (ADR-0051)
Tools are functions with API keysTPA, prompt injection, traversal"Trust the developer"Typed contracts + sandbox + safety classes (ADR-0052)
No human-in-the-loop without rewritingTreasury, healthcare, legalExternal workflow engineApprovals + checkpoint/resume as a first-class loop primitive (ADR-0054)
"Ship on vibes"Production regressionsManual prompt evalStateful eval harness with golden traces and red-team corpus (ADR-0062)

What you get

  • @veridex/agents β€” the core runtime: tools, policy, memory, checkpoints, transports, evals. Zero magic; one well-documented loop.
  • @veridex/agents-react β€” focused hooks: useRun, useApprovals, useTrace, useContextHealth, useMemory, useSkills, useBudget.
  • @veridex/agents-adapters β€” incremental migration from LangChain, LangGraph, OpenAI Agents SDK, OpenAPI, PydanticAI.
  • @veridex/agents-openclaw β€” OpenClaw / Pi-style context files and skills.
  • @veridex/agents-control-plane β€” multi-tenancy, policy packs, approval workflows, durable trace storage.
  • @veridex/agent-security β€” framework-agnostic security gateway, packs (injection, tool poisoning, secrets, endpoint allowlist, budget, shell safety, handoff), and adapters for LangChain and CrewAI.
  • @veridex/agents-treasury β€” money-movement capability layer: idempotency, ceilings, time-lock, sanctions, signed evidence bundles, red-team eval suite.

Quick comparison

DimensionVeridexLangChain / LangGraphOpenAI Agents SDKMastra
Event-sourced loopβœ… first-class❌ opaque reducers❌ black boxpartial
Strict context budget VeV_eβœ… enforced per-turn❌ overflow β†’ summarise❌ raw window❌
Tiered memory + reconcilerβœ… 4 tiers, lifecyclepartial (vector add-on)❌ minimalpartial
Tool sandbox + safety classesβœ… default❌❌partial
Policy engineβœ… priority-ordered rules❌ ad-hoc❌partial
Human approvals + checkpoint/resumeβœ… first-classbolt-on❌partial
Signed audit / evidence bundlesβœ… HMAC + Ed25519❌❌❌
Stateful eval + red-team corpusβœ… built-inexternalexternalpartial
Multi-tenant control planeβœ… opt-in packageexternal❌❌

Start here

  1. Quick Start β€” five minutes to a production-shaped agent.
  2. Context Compilation β€” the engine that keeps long-running agents coherent.
  3. Tools β€” typed contracts and safety classes.
  4. Policy β€” priority-ordered, replayable rules.
  5. Approvals β€” humans in the loop, durably.

First principles, not framework magic

Every choice in this docs site is derived from a concrete failure mode of existing frameworks and a concrete piece of research. We cite both. If you ever wonder "why is Veridex doing it this way?", click through to the relevant ADR.