Start a record
Veritas · database release candidate

Facts. Possible futures. One explainable database.

Veritas stores, queries, validates and reasons over living evidence—from an in-memory graph inside a wallet to durable and active-active peers. It keeps source, inference, uncertainty and imagined change distinct, then exposes how every answer was reached.

Run the public workbench Inspect capability evidence GitHub repository · opens shortly

The repository is opening in the next few days; the announced link may return a not-found page until publication. The engine and its test-backed database capabilities are already in the release candidate; hosted Verifable integration has its own status below.

  • RDF 1.2
  • SPARQL 1.2
  • Location-aware evidence
  • SHACL 1.2
  • OWL 2
  • Many-worlds
  • MCP
Active-active evidence graph 3 peers · no central owner
Peer 01 Wallet local memory
Peer 02 Organisation durable graph
Peer 03 Partner own deployment
Shared semantic substratesame engine · different operating shape Converged
  1. QuerySPARQLencoded graph
  2. ValidateSHACLexact findings
  3. ReasonOWLlabelled inference
  4. ImagineWorldsfork · diff · drop
trace query.plan reasoning.decision storage.verify replication.converged
Engine Release candidate

Integrated linked-data database and standards stack.

Durability Shipped · selectable

Recovers cleanly after interrupted writes.

Replication Implemented · tested

Independent peers can keep working and converge.

For agents Full MCP contract

The packaged stdio reference is one active, local-process binding for evidence operations.

One engine · several operating shapes

The graph goes where responsibility lives.

Veritas does not require every participant to surrender data to one database owner. The same deterministic engine can stay embedded, persist locally, converge between organisations, or reconcile pairwise across a decentralized network.

Available 01 · Embedded

In-memory

Open a mutable database inside a process, service, browser runtime or wallet without changing the query model.

Fast local decisions · tests · short-lived worlds
Selectable 02 · Persistent

Durable

Keep an auditable history and recover cleanly after an interruption.

Local control · recovery · repair
Release candidate 03 · Replicated

Active-active

Let several organisations keep working, then bring their records back into agreement.

Concurrent work · convergence · inspectable outcomes
Release candidate 04 · Peer-to-peer

Decentralized

Exchange changes directly and repair damaged state without handing one party the whole network.

Direct exchange · repair · own deployment
Browser · workstation · local agent

Use the graph where responsibility lives.

Explore locally in the browser, connect the Studio to a Veritas CLI on the same machine, or let a local agent use the CLI's separate MCP tools. The same evidence model can move between those shapes without making a hosted service the owner of the graph.

Runs in browser 01 · No sign-in

WebAssembly Studio

Load a graph, query it and validate shapes on the user's device.

Local binding available 02 · Workstation or server

Studio + local CLI

  • SPARQL query endpoint over GET and POST
  • SPARQL SERVICE federation
  • In-memory or durable graph
Local binding available 03 · Local agents

MCP reference binding

Give an agent bounded query and graph-analysis tools through the same product contract without turning the Studio into an MCP client.

Open the public Workbench ↗
Location-aware evidence

Place belongs in the evidence graph.

A component, project, depot or trade route is not only a label. Veritas can keep place and shape with the evidence, then ask how assets, spaces and routes relate without separating location from identity, provenance or lifecycle history.

  • KeepPlace and shape stay with the evidence
  • AskWhat is within, touching, overlapping or nearby?
  • ConnectLink products to projects, depots and trade routes
  • ReuseCarry location through maintenance and second life
location query place + product evidence 
COMPONENT panel-lot-a
PLACE Aholahti reuse area
RELATIONSHIP within
EVIDENCE geometry + recorded destination
location relationship component:panel-lot-a within · candidate reuse area
Evidence and possibility

Explore possible futures against the same facts.

Explore a possible change in its own world. Ask questions, test the rules and compare the exact difference. Keep the current record intact while an idea is discarded, refined, or prepared as an authorised result.

Each possible world is explicitly marked as a proposal. Current facts retain their own status, making counterfactual reasoning inspectable.

See the imagined reuse journey →
Known now state: 7f3a… canonical graph
Possible world A Reuse eight panels + destination · + proposed event
Possible world B Keep in storage no canonical change
Exact diff + 2 statements − 0 statements SHACL · conforms
Integrity is a behavior

No torn commit becomes truth.

Veritas protects the boundary between what was fully committed and what was only partly written. Recovery and repair return named outcomes and structured evidence; an unrecoverable gap is fenced and reported, never silently served as a good answer.

  1. 01
    Reject incomplete writes

    After an interruption, Veritas keeps the last intact state instead of treating a partial write as truth.

  2. 02
    Keep snapshots coherent

    Concurrent persistence across graphs publishes one coherent snapshot rather than a mixture of two moments.

  3. 03
    Preserve a known-good state

    A new state becomes visible only when it is complete—not as a mixture of old and new.

  4. 04
    Repair—or stop clearly

    Recover locally, reconcile with a peer, or report what is missing and stop.

Explain the engine, not only the answer

The database can show its work.

Veritas can show how a question was answered, which reasoning was applied, what storage was accepted and how peers came back into agreement. Operators, developers and agents can inspect the path instead of receiving an unexplained result.

Performance Fast by structure, measurable by design Dated, reproducible benchmarks publish with the source release.
Trace streamcorrelation 04f…
  1. Questionplan selected
  2. Evidencerecords considered
  3. Reasoningdecision explained
  4. Storageintact state accepted
  5. Peersrecords converged

Illustrative presentation · event families and fields are engine-derived

Governed operations for agents

Connect Verifable through MCP.

A Verifable operation keeps the same full contract when exposed through MCP: operation identity, authority and represented principal, policy, permitted view, result, trace and retained record. Local stdio and hosted Streamable HTTP are bindings of that contract, with their active composition stated separately. The hosted OAuth reference is implemented and integration-tested in Verifable.Server, including a governed Product Passport read; named-origin activation and external partner proof are separate states.

Full product contract

Evidence and product operations

  • Understand evidenceQuery, inspect, validate, reason and analyse governed records.
  • Work with productsRead permitted views, prepare changes and append accountable lifecycle events.
  • Return proofBind principal, agent, policy, trace and retained operation record.
Binding and deployment

The hosted reference is implemented.

  • Local stdio referenceAvailable for bounded graph questions and analytics.
  • Hosted Streamable HTTP referenceImplemented and integration-tested in Verifable.Server.
  • OAuth resource gateTenant, resource identity and mcp.tools scope are enforced.
  • Governed passport readproduct_passport_get derives caller, tenant and disclosure tier from the validated token, applies the permitted view and writes trace-linked action evidence.
  • Full product contractRepresented authority, per-operation policy, permitted disclosure and retained operation evidence stay together wherever a governed product operation is bound.
  • This public originNo MCP endpoint URL or accepted partner result is published here.

The server binding exists; its public URL is withheld until trust.verifable.eu is deployed and monitored.

Runnable reference binding · stdio

Connect a client to an installed CLI or local build.

Replace the DLL path with the absolute path to your local CLI build. The outer mcpServers object is a common client configuration shape, not part of the MCP protocol.

Download exact capability note
Hosted reference binding · implemented
Endpoint shape
POST /mcp/{segment}
Discovery
/.well-known/oauth-protected-resource/mcp/{segment}
Protocol
Current 2026-07-28 stateless requests and legacy 2025-11-25 initialization.
Authorization
Tenant issuer, MCP resource identity and mcp.tools scope.
Tools
resolve_did, sparql_query, public dpp_chain_walk and governed product_passport_get.
Passport argument
productId only; caller, tenant and tier come from the validated token.
Passport disclosure
Where tenant policy allows the dpp.stakeholder scope, it receives the full signed credential; other grants receive a masked public projection with restricted fields absent and proof removed.
Passport evidence
The MCP and HTTP reads share one typed operation. Every served or refused read records dpp.passport.read; the returned traceId joins the result to decision and action evidence.
What the local reference records
Result
The MCP client receives the engine output as text.
Runtime log
The local host writes process logs to stderr; the client or operator decides whether to retain them.
Call history
The stdio adapter does not add server-side retention; the local client or process host chooses what to keep.
Receipt
These read-only local graph calls do not create a business-operation receipt. Separately, the hosted product_passport_get operation writes retained, trace-linked action evidence.

This downloadable entry exercises the local stdio reference; it does not define the ceiling of the MCP product contract. Hosted server binding, public-origin activation and external partner evidence are recorded separately. For the local binding, every query or analysis receives filesystem paths chosen by the client. Grant it only files the agent may read, and treat returned error text separately: these three local reference tools return failures as text rather than MCP isError.

Start with the public workbench

Query, inspect and validate a real graph.

Ask a question, inspect source-position RDF diagnostics and validate a graph with SHACL. The same Veritas engine can then travel from an in-browser workspace to local, durable and replicated deployments.

Open Veritas Workbench