Evidence enters once and is governed for the life of the asset — so the record built while a tunnel is driven is the twin its operator inherits at handover, not a set of files somebody has to reconcile.
One identity, one validated context, and every application a team is entitled to.
Delivery, Operations and Maintenance — each independently deployable and named for the phase of the asset's life it serves. A team sees the one it is entitled to, on the projects it belongs to.
Connect, Data, State, Data Services, Spatial, Ontology, Intelligence, Models, Actions and Govern. Each is a published contract before it is an implementation.
Shared contracts, a bitemporal record, provenance on every reading, and every decision bound to the model version that justified it.
X-Twin carries three senses at once. The mathematical unknown x, apt for a discipline whose dominant unknown is the ground itself. The established X‑ convention of technology naming. And xuán tóng (玄同), from Laozi's Dao De Jing — usually rendered “mystical unity” — denoting the dissolution of the boundary between observer and world, which is what a digital twin attempts in engineering terms.
Each states its job in one line, and each names the stage it has actually reached. We publish the stage because a capability list without one tells a reader nothing they can plan against.
| Capability | What it does | Stage |
|---|---|---|
| Connect | Bring reality in. Edge, IoT, files and enterprise adapters, with an idempotent push-admission contract | Extending |
| Data | Preserve the evidence. Time series, events, relations, spatial and raw payloads | Delivered |
| State | Know what is true now. Validated current state with quality, freshness and as-of query | Delivered |
| Data Services | History, bulk extract and governed export, kept off the state path | Extending |
| Spatial | See it in context. BIM, GIS, tiles, point clouds and live overlays | Delivered |
| Ontology | Understand what it means. Identity, relationships, spatial context and provenance | Delivered |
| Intelligence | Predict what comes next. Physics, machine learning, diagnosis and scenario analysis | Delivered |
| Models | Version and approve how predictions are made | Extending |
| Actions | Turn decisions into controlled action. Approval gate, adapters and the decision ledger | Extending |
| Govern | Control who can do what, how long it is kept, and prove both | Delivered |
Built, exercised by an automated test, and demonstrable today.
The contract is delivered and proven against a working application, and is being carried across the remaining ones. The engineering question is answered; what remains is reach.
The contract is defined, version-controlled and ready to build against. X-Twin declares its interfaces before it implements them.
Four commitments that are enforced by the code rather than promised in a document.
Entitlement runs four gates — scope, lifecycle phase, deployment, and what an application is cleared to hold. The portal hides what a user may not open, but hiding is convenience: editing an identifier in a URL changes nothing, because the URL is never an input to the decision.
Two clocks on every reading, so you can ask what was known at the time as well as what is true now. Evidence is append-only, submissions are idempotent, and a decision is bound by reference to the model version that justified it.
A suspicious reading is admitted and flagged, not discarded — a reading that vanishes is one nobody can investigate. Late and backfilled data is normal on a real site and is classified rather than refused.
A work order asks a person, who keeps the right to refuse. Moving a real control value is a different act, and it requires an adapter the asset owner has deliberately authorised, with their own interlocks intact. A twin that can open a valve because a model crossed a threshold is a hazard, not a feature.
Almost nothing in the platform is about tunnels. The evidence loop, the gates, the governance and the edges are sector-neutral; what is sector-specific is vocabulary — and vocabulary is a file, not a fork.
Drives, bores, lining rings, station boxes, cross passages and surface receptors. Ground movement, face pressure, volume loss and the damage categories a building is assessed against.
Spans, piers, bearings and expansion joints. Deflection, crack width, chloride ingress, and the movement that reveals a seized bearing before anything else does.
Trunk mains, pump stations and reservoirs. Pressure, flow, disinfection residual, and the losses that reveal a leak before anyone sees water at the surface.
Sectors share a term only when they mean the same thing by it. Two sectors that disagree about the unit of a shared measurement are refused rather than reconciled — which is what keeps a single word from quietly meaning two things across a client's estate.
X-Twin is a working platform at demonstrator and early-pilot stage, developed with Monash University. We would rather tell you that plainly than have you discover it in week three.
The governed contracts, the entitlement model, the bitemporal record, the physics and federated machine-learning intelligence, the scenario engine, the disclosure and retention policy, and a certification kit a third party can run against their own application before asking to be registered.
No client system is connected to the action gateway in this environment, and the ledger says so rather than reporting work the platform did not cause. Enterprise identity, production ingest at scale and the remaining application integrations are specified and in progress.
If you are planning a tunnel, operating an estate, or building software that should sit on a governed twin, we would like to hear what you are trying to do.
Partner applications reach platform data through published contracts and are certified before registration. Ask us for the conformance kit and the domain-pack specification.