Keep the model in step.
Connect approved systems through event feeds or scheduled updates. Preserve time, provenance and version history. Show stale, missing and conflicting information, so an old model never silently passes for the present.
Living operational counterparts that connect what is observed, what is modelled and what could change.
Polydeuces
Sovereign digital twins
An evolving model of services, assets, resources and dependencies. Keep it connected to authorised evidence. Rehearse change, inspect the assumptions and compare the model with reality.
Open the government demo (French)Bring in authorised evidence. Preserve its origin, time and quality. Make gaps visible.
Trace an aircraft disruption to service commitments and cost. Set a service target and spending limit, test a further delay, and inspect public weather and FAA airport context.
Try the private-operations demo In English · fictional operations, public weather and airport data · calculated role briefingsExplore healthcare access, territorial planning and flood resilience through official Luxembourg data. Inspect the evidence and test explicit assumptions.
Explore the government workspace In French · official public data + a separate fictional labLiving operational counterparts that connect what is observed, what is modelled and what could change.
Connect approved systems through event feeds or scheduled updates. Preserve time, provenance and version history. Show stale, missing and conflicting information, so an old model never silently passes for the present.
Connect services, assets, resources, obligations and dependencies in an inspectable operational model. Distinguish observed facts, inferred relationships and assumptions. Domain owners can challenge and correct the representation.
Use Icarus to branch a versioned twin into bounded scenarios. Couple validated operational, statistical or physical models where appropriate. Compare cascading effects, competing explanations and uncertainty before committing resources.
Compare expected behaviour with observed outcomes. Detect drift, investigate disagreement and propose revisions. Test and approve a new model version before it informs operations; preserve the evidence behind the change.
Our frontier is a federation of institutional twins: services, municipalities and infrastructure working across approved interfaces. Each participant governs its data, model and permissions. Shared scenarios depend on explicit agreements and compatible models.
Let authorised teams inspect a scenario, select a response and track its consequences. Solon governs model and tool access. Separate scenario exploration from operational execution, with approvals, source links and a recoverable decision history.
Start with one institution, one decision and a bounded system. Define the authoritative sources, update cadence, model boundaries, permitted processing and operators. Extend to additional services or partners only when the interfaces, authority and evidence support it.
Agree freshness and coverage requirements; replay historical events; compare model behaviour with observations and existing methods. Evaluate sensitivity, uncertainty, failure modes and expert acceptance. The model must also show where it cannot support a decision.
If demand, staffing or a procedure changes, where could pressure move next?
How could heat, flooding or an infrastructure outage affect the services that depend on it?
What happens to services when beds, staff, equipment or supplies become constrained?
Which linked obligation or asset could turn a local disruption into a wider constraint?
Follow one illustrative example from a supplier update to a decision a person can explain and approve.
A supplier reports a two-day delay. Eridanos brings that update together with stock records and customer orders, preserving the source and time of each record.
Ariadne links the delayed part to the orders that need it, their deadlines and the warehouses holding alternatives. This is the shared model of how the operation works.
Polydeuces brings the connected model into a digital twin: which orders are exposed, what stock is available and when the picture was last updated. Missing information stays visible.
Icarus tests waiting, moving stock or using another supplier against agreed costs, deadlines and capacity. The team can compare the options and see the assumptions behind them.
A planner asks Solon which response meets the deadline. It explains the comparison using permitted evidence and tools. The planner approves any proposed action before it reaches an operational system.
Polydeuces is the operational workspace. It can bring together the connected data of Eridanos, the relationships of Ariadne, the scenarios of Icarus and the governed AI assistance of Solon. We select and build the capabilities your use case needs.
An illustrative workflow, not a live client deployment. Integrations, access controls, models and approval steps are agreed and validated for each project.One service first. Connected institutions next.
Our ambition is a network of sovereign twins that can rehearse shared futures while each institution retains control over its data, models and decisions.
Polydeuces maintains the evolving counterpart. Icarus explores its possible futures. Ariadne structures its meaning. Solon governs the use of AI. Eridanos connects the evidence.
Proposed capability. Illustrative animation with synthetic relationships. Each twin is scoped, developed and validated with the institution.
Start with a scenario and the systems involved. An initial conversation does not require confidential data.