Route
Restormel Keys
route: production-default
primary → openai / gpt-4o-mini
fallback → anthropic / claude-3-5
policy: cost-cap-passRestormel · Connect
The context layer
your auditors can read
Restormel Connect is the control plane for verified context — provenance-traced, quality-gated knowledge that agents in regulated domains can actually be held accountable to. Every claim your agents receive carries the evidence it was bound against, the verdict record, and a trace your compliance team can export.
Why did the agent say that?
That question is the one regulators, compliance teams, and cautious buyers actually ask. Connect answers it structurally, not after the fact.
1 · Claim
The agent receives a supported claim in its context.
The state is not asserted — it means Layer-1 binding passed (quote + offsets + source hash)
and the cross-model entailment judge agreed.
2 · Citation
The claim envelope carries evidence[]: the verbatim quote,
character offsets, and a SHA-256 of the exact source version it was bound against.
Open the cited source and check the quote yourself.
3 · Trace export
Follow trace_ref on any claim to the retrieval's full audit
record: the query, the verification policy in force, every considered claim with its state and
reason for inclusion or exclusion. Export as JSON for your audit file.
Full walkthrough: the verified-claim envelope and auditing a claim yourself.
Provenance-traced context
Every claim served to an agent carries verification state, bound evidence quotes with character offsets and source-version hash, judge attribution, and a trace link. An auditor can walk from an AI output back to the exact source passage in four steps.
Quality-gated knowledge graph
The ingest pipeline runs extraction → validation → remediation with fail-safe gates at every step. Omitted verdicts default to the review queue — never to a pass. The graph clears a published bar (≥ 90% supported, ≤ 2% unsupported) or it surfaces the shortfall.
Cross-model verification
The model family that validates a claim is deliberately different from the one that extracted it. The same-model control affirmed unseen claims 66.7% of the time; the cross-model configuration: 0%. That asymmetry is why cross-model routing is the product default.
Use case · regulated domains
The audit trail your compliance team needs
Legal research tools, clinical decision support, and financial-analysis copilots share one requirement: when the AI says something, a qualified person must be able to check why it said it. Connect makes that check mechanical rather than aspirational.
- Legal
- Case law and regulatory corpus ingested with claim-level provenance traces. Every cited passage carries the source document version it was bound against — counsel can verify the quote in seconds, not hours.
- Pharma / clinical
- Trial data and clinical guidelines with verification state per claim. Unsupported or contradicted statements are excluded from agent context, not blended in. The exclusion log is part of the trace — auditors see what was withheld and why.
- Finance
- Earnings, filings, and research reports gated to the published quality bar. The trust scorecard
(
GET /connect/v1/graph/scorecard) shows the current verification coverage and G2 breakdown at any time — not only after an ingest run.
Pair with Restormel Keys for BYOK on every ingest stage, Restormel Graph to visualise the knowledge graph in your app, and Restormel Testing to assure agent behaviour in CI.
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.
Connect
Restormel Connect
graph: 847 ideas · 2.1k edges
explorer → 94% claims supported
connect.search → context pack
MCP: @restormel/mcp + rk_ gateway key
BYO Surreal — graph stays yours