// 00MITHRIL Console · Ontology Runtime · Lualdi Advisors

MITHRIL·

Ontology · Cited · Approval-Gated

The ontology layer for industries where hallucination is not an option.

Where conventional enterprise software treats data as rows and documents, MITHRIL treats it as a structured world — every asset, process, regulation, relationship, and operational state declared in a single unified ontology that frontier AI models can query, cite, and reason over with precision.

// 01Doctrine

Records are flat.
The world is not.

Most enterprise AI systems treat your business as text to be retrieved and rephrased. MITHRIL treats it as a world to be reasoned about — physical assets, operational states, regulatory obligations, and the relationships between them, declared once and queryable forever. The result is an AI layer that doesn't guess. It computes against the same operational reality your engineers and operators already work in.

// PRINCIPLE 01

Grounded

Every answer is anchored to a node in the ontology — a tag, a record, a sensor stream, a regulation clause. There is no "from the model's general knowledge." If MITHRIL says it, MITHRIL can point at the row, the document, the timestamp.

Citation · Source Node
// PRINCIPLE 02

Traceable

Reasoning is recorded, not just results. The data pulled, the prompt issued, the model that answered, the math performed — every step is reproducible. An auditor can replay the answer. A regulator can verify it. A successor operator can trust it.

Provenance · End-to-End
// PRINCIPLE 03

Approval-Gated

MITHRIL proposes. Operators approve. No write reaches a system of record — no work order, no dispatch instruction, no batch release, no procurement — without an explicit human signature on the proposed action. Agentic, never autonomous.

Human · In the Write Path
// 02Deployment Theaters

Operationally complex.
Safety-critical. Audit-bound.

MITHRIL is built for the industries where a wrong answer carries weight — physical, financial, regulatory, human. Six ontology packs ship today, each modeling the operational world of its theater down to the asset, the obligation, and the dependency.

Semi-submersible drilling rig Frame 14:32 · T01 61.4°N · 1.8°E · North Sea
// THEATER 01Live

Oil & Gas

Maps the interdependencies between well integrity, maintenance schedules, regulatory compliance, and crew logistics across upstream and offshore platforms.

WellsMaintenanceHSECrew
Open-pit mining quarry Frame 09:18 · T02 22.7°S · 117.8°E · Pilbara
// THEATER 02Live

Geological Mining

Encodes orebody models, extraction sequences, environmental obligations, and downstream supply chains into one queryable structure across open-pit and underground operations.

OrebodyExtractionEnvironmentalSupply
Pharmaceutical clean room Frame 03:42 · T03 47.5°N · 7.5°E · Basel
// THEATER 03Live

Pharmaceutical Mfg

Holds the declarative structure of batch records, quality checkpoints, supply chain provenance, and compliance obligations across GMP and regulatory regimes.

BatchQCProvenanceGxP
Fighter aircraft in flight Frame 22:07 · T04 34.9°N · 117.8°W · Edwards
// THEATER 04Live

Defense & Aerospace

Encodes the relationships between mission readiness, parts traceability, airworthiness directives, and program constraints across platforms and sustainment.

ReadinessPartsADsProgram
High voltage transmission tower Frame 14:32 · T05 40.4°N · 3.7°W · Iberian Grid
// THEATER 05Live

Electric Power

Models generation assets, grid topology, dispatch protocols, and regulatory exposure in real time — across transmission, distribution, and wholesale market participation.

GenerationTopologyDispatchMarkets
Cargo container ship Frame 18:55 · T06 1.2°N · 103.8°E · Singapore Strait
// THEATER 06Live

Maritime Operations

Vessel state, route plans, port calls, cargo manifests, charter terms, and regulatory exposure modeled as one ontology spanning the fleet, the voyage, and the cargo.

VesselVoyageCargoCompliance
// 03Live Example · Electric Power Theater

There's margin hiding in your operation. MITHRIL finds it.

A real query against a real grid ontology, replayed below. MITHRIL doesn't search the web — it reasons over your live data, and tells you what to do. Every answer is reproducible: the data, the prompt, the model, the math.

MITHRIL · Electric Power · ES Grid
Session 0x7F · Live
// Operator Query
Top 3 cheapest hours tomorrow?
// 01 PullDay-ahead OMIE prices · 24 nodes · 2026.05.13
// 02 FrameCluster by hour · rank ascending · top 3
// 03 GroundCross-check renewable forecast · solar 16,956 MW peak
// 04 ComputeΔ vs 24h avg over 100 MWh load profile
Answer · Cited · Reproducible
// Rank 03
Wed · 12:00
€80.46
// Rank 01
Wed · 14:00
€77.33
// Rank 02
Wed · 13:00
€78.48
Savings · Cheapest 3h vs 24h Avg
€4,681
37% Discount · 100 MWh
REPRODUCIBLE · Data · Prompt · Model · Math Reply T+412ms
// 04The Runtime Loop

Every MITHRIL run follows the same three steps.

01

Ontology Declared

Your operational world — assets, processes, obligations, relationships — is encoded once into the MITHRIL ontology. Pulled from your existing systems of record, normalized, and kept in sync. The ontology becomes the single source of operational truth.

02

AI Reasons & Cites

Frontier models query the ontology — never the open web, never the model's general memory. Every answer carries the source nodes, the reasoning trace, and the exact prompt-and-model fingerprint that produced it.

03

Operator Approves

Proposed actions queue for explicit human sign-off before any write touches a system of record. The operator stays in command. MITHRIL is the strongest possible co-pilot, never the captain.

// 05MITHRIL — Frequently Asked

Direct answers.

How is MITHRIL different from RAG or a vector database?
RAG retrieves text. MITHRIL reasons over a declared world. The ontology encodes assets, processes, regulations, and relationships as first-class entities — not as documents to be embedded and rephrased. The result is reasoning that compiles against your operational reality, not search results.
Which frontier models does MITHRIL use?
MITHRIL is model-agnostic by design. The choice of underlying reasoning model is made per-theater and per-query, driven by latency, cost, security posture, and what the answer needs to cite. Specific model selection is part of the engagement scope and is not disclosed publicly. Sensitive deployments can be served entirely by self-hosted open-weight models inside the client's perimeter.
Why approval-gated writes?
Because the cost of a wrong autonomous write — a misdispatched crew, a mis-released batch, a wrong work order — is higher than the cost of a human signature. MITHRIL is designed for operations where hallucination is not an option. Agentic, never autonomous.
How is MITHRIL deployed?
On-premises, private cloud, or air-gapped. The ontology and the reasoning runtime live inside client infrastructure. External model calls (where used) traverse named, logged egress with prompt and citation auditing.
How long does an ontology pack take to stand up?
First operational query inside 6–10 weeks for a scoped theater. Full pack maturity — every asset, regulation, and dependency wired — takes one to two quarters of focused engineering with the client's domain experts.
//Console Access

For the operators who must defend the decision —
to the auditor, the regulator, the engineer who comes next.

Onboarding by referral & mandate · Console issued per theater