What is a twin

The primitive in full: what it is, why the graph cannot do without one at every edge, and the properties that make it different from the thing the industry sells under the same name. Everything on this page is quoted from the cluster of briefs written on 26 June 2026 and the primitives they settled into.

1. The definition

"a digital twin is, in essence, a system that has properties, behaviours, functions, and inputs and outputs, and we can define all of those."

That is the whole definition, and it is deliberately small. What makes it useful is its generality:

"we can make a digital twin out of anything: an organisation, an element, a mail system, an inbox, a person, a behaviour, an event, an action, external factors like weather, even luck."

Non-determinism is included rather than excluded: "the fact that in the real world they are not deterministic, or maybe random, we can capture that." Uncertainty is something the twin models. It is not something that defeats it.

2. The doorway role

These graphs refuse properties. The rule, stated on graphs.sgit.ai, is that "properties do not have meaning, they are just words; we capture meaning through connectivity." That is a strong position, and it creates an obvious problem at the graph's edge: if meaning is connectivity, where does connectivity stop?

"the power of the twin is that we always arrive at the twin, so the edges and the peaks and the endpoints of the graph continue into the twin, and then ideally into reality."

Every terminal node is a twin, and the twin is "the doorway from the model to the real system." This is not a stylistic preference. It is why the grounding ladder puts Twin at the bottom:

Measure := an observation of the node it measures, grounded on a Twin

and why the established edge grammar ends where it does: "the connection from any node to a twin and onward to reality is connected_to." A graph with no twins at its edges is a graph that stops at words.

3. Connectedness is a fact, and therefore a measure

"whether we can continue to reality is a measurable fact, it is connected or it is not."

Where it is not connected, because there is no API, no connector, or the work simply has not been done, the state is not silence. It is recorded:

"a place to represent an air gap that is understood and tracked: this has no API, this is updated manually once a week."

A tracked air gap is a first-class object. It is the difference between a model that quietly implies coverage it does not have and one that can be asked, and answer honestly, how far it actually reaches. The July extension turns that into the most distinctive idea available here, which is set out in full on the discipline page.

4. The discipline of reality

The rule that separates this from threat modelling, and the reason the primitive is worth the constraint it imposes:

"in this model, everything has to be relevant, everything has to be a fact, everything has to exist, because it is based on reality. It forces the discipline: either we have evidence and it exists, or we do not."

No speculative risks. No hypothetical persons or systems. "the graph never fills with potential, out-of-context risks that become pollution." The constraint is the source of the power rather than a limitation on it, and it is worth its own page: the discipline of reality →

5. Structure: fractal, stacking, seam-aligned

"digital twins that are fractal and can go from the bottom up, little twins, digital twins of digital twins, with natural abstraction layers, where in reality there are handovers or movements between two different systems."

The second half of that sentence is the part that does work. Abstraction layers here are not chosen for tidiness. They sit at the real seams, where one real system hands over to another, which means the model's structure is evidence about the world rather than a modelling convention.

And twins stack: "a twin of MFA, a twin of the solution, then the real solution, which adds abstraction and isolation." The consuming system "only ever sees a twin, so it works in an enterprise way from the first moment, and onboarding becomes describing what you have, which builds the digital twin of the organisation."

6. Twins as actors

"every action that updates the graph, including accepting a risk, is performed by a twin, the acceptor is the twin acting as the CEO or the CFO, connected either to a human or to an agent acting on that human's behalf, with the agent creating the actions, documenting its reasoning and why it chose one option over another, and carrying a persona."

Twins are not only modelled. They act. And because "the graph is ultimately a set of changes, there is a pipeline for changes, which are fundamentally graph transformations," every acceptance and every update becomes an attributable transformation performed by a named twin with a documented reason. That is the audit trail the risk sites need, produced structurally rather than assembled afterwards. Twins as actors, in full →

7. Twins make risk testable

"these also let us simulate, write unit tests, integration tests, simulations, plans, and analysis, use static analysis and visualisations and rules, the same techniques we use with software."

This is the claim with the most upside and the least evidence. The argument is straightforward: software engineering has forty years of technique for reasoning about systems it can run, and organisational risk has almost none, because there was never anything to run it against. A twin is something to run it against. What exists today is the AWS engine, which is unit-tested Python producing typed objects. What does not exist is any of the simulation layer. The simulation layer, labelled as design →

And the practical entry point, which is also the honest warning: "start with one simple mapping and see how big it gets, because even one specific use case can become massive once you capture all the elements." That sentence contains an open question the corpus never answers, which is when a twin is finished. Question 5 →

Sources

This page is drawn from the 26 June 2026 cluster (twin of anything, dimensions, discipline of reality, simulation testing; the integration layer, tracked air gaps, the agent twin; the 2FA demo, twins as actors, IssueFS, the change pipeline) and the 28 June ontology brief that fixed the grounding ladder. All quotations are the project lead's own words, retained verbatim including their punctuation. The documents →