Why a Living Digital Twin?

The Federal Frontier Ontology (FFO) is a TypeDB knowledge graph that serves as the world model for the Federal Frontier Platform — continuously updated, queryable infrastructure state that makes AI agents operate instead of guess.

Why a Living Digital Twin?

The Federal Frontier Ontology (FFO) is a TypeDB knowledge graph that serves as the world model for the Federal Frontier Platform. It is not a CMDB, not a data warehouse, and not a config file. It is a continuously updated, queryable representation of infrastructure state, relationships, and operational history.

The Problem with Static Context

AI agents need to know what they’re operating on. The naive approach is to give them a config file — a topology document, a CLAUDE.md, a README that describes the environment. This works for ten minutes. The moment a new node is provisioned, a pod is rescheduled, or a volume is resized, the file is wrong.

An agent operating against a stale topology document is not an autonomous agent. It is a script with a language model bolted on.

FFO Is Live

Scout agents continuously poll Systems of Record and write current state to FFO. When the Dispatch Controller receives an alert, it queries FFO at dispatch time — not at build time, not at boot time, at dispatch time — and injects current infrastructure context into the agent’s prompt.

The agent knows:

  • The resource’s current state and recent history
  • Its relationships to upstream and downstream dependencies
  • Previous remediation outcomes for the same resource
  • The resource’s classification level and authorized remediation scope

This is why FFO is architecturally non-negotiable. An agent without live context is guessing. An agent with FFO context is operating.

FFO Is a Write-Back Store

Agents don’t just read from FFO. After every remediation, Wrangler writes the outcome back: what happened, what was done, whether it worked, confidence score. Over time, FFO accumulates operational history that makes future agents faster and more accurate for the same infrastructure patterns.

What FFO Stores

FFO stores relationships and operational state — not raw data. Enterprise data stays in systems of record (ServiceNow, vCenter, Splunk). FFO stores the meaning: this VM is hosted on this ESXi host, this host has had three OSD failures in the last 30 days, this Ceph pool is at 94% capacity, this resource is classified IL4.