Capabilities

The layer behind verified context

Restormel is the verified-context layer for AI products — knowledge an agent (or an auditor) can trace to the exact source span. Two capabilities produce it: Keys controls the plane; Connect ingests, verifies, and retrieves.

Control plane

Keys

Governs which model runs, under which policy, with whose credentials — so every step is routed deliberately, and an independent model family is always on the line to check the work.

  • BYOK custody
  • Resolve + routing
  • Policy before spend
  • Fallback chains
Keys overview →

Ingest · Verify · Retrieve

Connect

Turns a corpus into verified context: ingest sources, verify every claim against a bound quote with a cross-model check, then retrieve only what survived — with the trace attached.

  • Evidence binding
  • Cross-model check
  • Quality gate
  • Provenance trace
Restormel Connect →

How Connect produces it

  1. Ingest

    Sources become discrete, checkable claims — nothing is summarised away before it can be verified.

  2. Verify

    Each claim is bound to a verbatim quote and judged by a different model family. No bound, entailed span → never “supported”.

  3. Retrieve

    Strict retrieval returns only supported claims; excluded and uncertain ones are omitted, never blended — every query keeps the trail.

Published quality bar: ≥90% supported · ≤2% unsupported — graphs that miss it fail the gate. See the verified-context contract →

Fits your stack

Compatible with your stack

Restormel

Control layer

Route · ingest · verify

Your product

Grounded agents

Cited answers, your keys

No rip-and-replace — keep Neon, SurrealDB, and your providers.

Coming

Rounding out the workspace

  • Assure

    Testing

    Goal-based acceptance tests for AI behaviour in CI — a verified-context regression fails the build, not production.

  • Visualise

    Graph

    An embeddable canvas that renders the verified graph — provenance and verification state visible in your own app.