Architecture
From ontology to evidence-based AI outcome
How a policy, a decision and the code that implements it become one governed graph, how the loop reasons through it, how a gate stands between intent and action, and how every decision leaves a record a stranger can verify.
How to read it
Eight layers, one tag per node, a source for every fact
The layers read from the bottom up. Sources and ontology sit at the bottom: documents, policies, decisions, codebases and regulatory text enter one graph as typed nodes with explicit relationships. Above them the knowledge graph substrate keeps that graph as persistent typed state, retrieval finds the right passage by the structure of the regulation, the reasoning loop runs ANCHOR, ACTIVATE, GENERATE, VALIDATE and COMMIT through the graph, the control layer stands between intent and action, and the evidence layer turns every attested decision into a record. The products and services sit on top of that, and at the very top is what the board, auditor or regulator receives: a TRACE score report, an evidence pack and a 90-day roadmap. Click a band to zoom into a layer and a node to open its facts; the walkthrough takes the same path in twelve steps.
Every node carries one state tag, and the tag says what the node is today. hosted: runs on our infrastructure in AWS Frankfurt (TraceGov.ai, the TRACE score report and the evidence pack it produces). shipped: a delivered framework or deliverable, such as FrictionMelt or the 90-day roadmap. source-available: code you can read and run from the GraQle repository or PyPI under its licence; it is not open source. design disclosure: a published design, not shipped code; the seven hard gates and the determinism record are in this state. service: work we do with you, from the free AI Quick Scan to the two-week proof of concept. published: a paper or report with a DOI. A dashed outline marks a pluggable slot, where the panel lists the alternatives that can take that place. The “shipped only” switch fades every design disclosure so you can see what runs today.
Every fact in the panel links to the README, a paper DOI or a page on this site. Nothing in the explorer is a new claim: where a node rests on a published design rather than running code, the node says so, and the facts behind each node name the file or the DOI they come from, so you can check the work rather than take our word for it.
See it on one of your own decisions
Pick a decision your organisation already makes with AI and, in 45 minutes, we will show you where it sits in this picture and what you could hand over today.
No sales deck. 45 minutes. Free.