GLASS BOXExplainable AI
Architecture
Power Consultancy
Everything below is generated from ontology.schema.ttl at page load, the same frozen file every engine reads, not a slide redrawn by hand. Three clusters, 14 classes, 17 relations, then the real instances Story A, B, and C actually loaded, snapping onto that schema, and the one append-only table they all live in. Build it schema-first, then pick any story to watch it walk this exact graph.
This is the actual data model behind the whole demo: a graph of 14 classes and 17 relations, with real project records loaded into it. Each of the five demo stories is nothing more than a different walk across this one graph. Below is what each story asks, what it proves, and how to read the shorthand you will see on screen, so the animation itself can stay clean.
| prj_… | a project. prj_core = Core Banking Modernization, prj_aml = AML upgrade. |
| m_… | a milestone. m_204 = Payments Integration Go-Live. |
| t_… | a task. t_130 = Sanctions Screening on the AML project. |
| p_… | a person. p_09 = Ahmed, p_14 = Sarah, p_20 / p_21 = contractors. |
| sk_… | a skill. sk_int = Payment Gateway Integration, the scarce one. |
| a_… | an approval gate. a_88 = Vendor Security Gate. |
| r_… | a risk. r_12 = vendor delivery capacity strained. |
| cr_… | a cost rate. cr_int_contractor = QAR 260/hr. |
| valid_time | when a fact became true in the world. |
| tx_time | when the system actually learned it. The two never mix. |
Every instance above resolves down to rows here. Nothing is ever overwritten, only appended. valid_time is when a fact became true in the world, tx_time is when the twin actually learned it, and Story C's whole proof lives in the one row where those two clocks disagree.
Seven layers, one rule: truth flows up from the feeds, language sits on top, and provenance wraps every layer in between. Toggle between a guided tour of each layer's honest v0 tech pick, and a live walk of any of the five stories' actual data, each one a different real path traced through every layer that computes it.
Project Intelligence gives engineering and capital project owners a single, full-stack view of a project's actual state, surfacing schedule risk, cost drift, and delivery signals from raw field data up through natural-language answers, with every claim traceable back to the source event that produced it. Built on an open source, self-hostable stack, so the system runs entirely inside your own infrastructure rather than a vendor's cloud. The interactive reference below is a real architecture walkthrough, not a mockup: every layer, tool, and data path shown is what actually runs in production. The data model itself, the 14 classes, 17 relations, and all five stories walking one graph, is animated at the top of this page: press "Run full simulation" for the whole thing end to end.
Every tool below is open source and self hostable, the sovereignty story from the architecture brief made concrete. This is not the honest v0 shortlist from the layer cards above, it is the fuller real world stack, including the event sourcing and streaming infrastructure a production deployment would actually run. Click any node for what it does and how you would run it. Choose a story above to watch that story's own path physically traverse the pipeline, each of the five stories lights a different, real route through the same tools.
Currently showing: Story A. When two consecutive lit nodes show no connecting line between them, they are parallel, independent sources converging at the next node, not a broken traversal.
All five stories, A through E, are fully specified and fully built: the claim, the entities, the engine path, the cross feed reconciliation, the distractor, and the fingerprint, all implemented and running against the live digital twin. Each story was built and stress-tested end to end, twice, with identical output, before engine code for the next story began, in the order A, E, C, B, D. That discipline, prove one path before starting the next, is why every number in this deck traces to a live row rather than a mockup.