Republic Navy readiness and sustainment
DEFENSE615 entities · 1,502 relations · 97 evidence under ontology v1.0.0, scenario clock 2026-10-16T08:00:00Z.
Solutions
A pack is a segment-shaped workspace: its object types, its link types, its action types and one story that a person in that sector can follow end to end without being told to trust the number.
Shipped packs
Numbers below are from the demo journeys in docs/DEMO_GUIDE.md, which the end-to-end suite asserts step by step.
615 entities · 1,502 relations · 97 evidence under ontology v1.0.0, scenario clock 2026-10-16T08:00:00Z.
584 entities · 1,507 relations · 81 evidence under ontology v1.0.1, scenario clock 2026-10-16T08:00:00Z.
Where it fits next
Two sectors are built. The rest are honest about what would have to change before anyone quoted you a delivery date.
Built and demonstrated
This is where the defense pack lives: berths, platforms, missions, readiness capacity and maintenance events, with a margin formula printed on the tile.
Live AIS feed and real port-call history would replace the synthetic arrivals.
Built and demonstrated
The commercial pack models depots, stock, order lines, inbound shipments and transfer lead times, and distinguishes on hand from planned supply.
An ERP extract with order, on-hand and in-transit tables is enough to reproduce the story.
Target sector · not built
Fleet readiness, spool availability and dock scheduling share one shape with what is already modelled: capacity against demand, with a named shortfall.
Would need a classified-data deployment; the POC runs on synthetic records only.
Target sector · not built
Substations, feeders, generation and work orders are entities with locations and dependencies; outage propagation is a traversal, which is the primitive this platform is built on.
Would need a link-type review against your asset registry, plus a historian feed for time series.
Target sector · not built
Pre-positioned stock, routable warehouses and demand across a disrupted network — the timely-versus-late distinction matters more here than anywhere.
Would need lead-time realism per corridor and a donor-visible export of the assumptions.
Target sector · not built
Most stalled twins are visualization projects without a write path. Here a commit is a first-class action with preconditions, a journal and a branch you can compare.
Would need one decision that is worth closing, chosen before any modelling starts.
Getting started
A pack is worth building when there is a decision someone makes weekly from a number they cannot currently explain.
“Which shortfall do I close first, and what does it cost?” is a good one. “A 3D dashboard of everything” is not.
Entities with locations and status, relationships between them, and events over time. CSV or an extract is fine at this stage.
Every tile that will be shown must print its own arithmetic. If we cannot write the subtraction, we do not show the tile.
We build the disruption and its fix as a journey, then assert it end to end before you see a number.
Tell us the decision and we will show you the shortfall moving on screen, with the arithmetic printed next to it.
No matches. Try shortfall, SSE or ontology.