# twins.sgit.ai — brief pack

**For:** the agent commissioned to build `twins.sgit.ai`
**From:** Dinis Cruz, via the SG/Send Librarian
**Version:** v0.33.62 · 24 August 2026
**Licence:** CC BY 4.0 — see `LICENSE.md`

---

## What this is

The digital-twin work: **148 files, 11 dedicated briefs, ~28,000 words**, anchored by the 26 June 2026 cluster (`digital-twins-and-world-models/`) — plus one working implementation and one naming collision the corpus flags itself.

**This is a reference site for a primitive**, the shape the grounding ladder already has: five other sites depend on the twin idea and should state it in three lines and link here.

---

## The thesis — not the industry's digital twin

> *"a digital twin is, in essence, **a system that has properties, behaviours, functions, and inputs and outputs**"* — of anything: *"an organisation, an inbox, a person, a behaviour, an event, external factors like weather, **even luck**."*

An **interface to reality, not a simulation of it**:

> *"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**."*

With the two ideas that make it distinctive: **connectedness is a measurable fact** (*"it is connected or it is not"* — unconnected twins are tracked air gaps, and over a legal instrument they become a computable coverage measure), and **the discipline of reality** (*"either we have evidence and it exists, or we do not"* — no speculative risks polluting the graph).

---

## Read in this order

| File | Words | What it does |
|---|---:|---|
| **`00__BRIEF.md`** | 1.3k | **Start here.** The thesis, the four original ideas, built vs designed, the naming collision, the build order |
| **`01__the-twin-primitive.md`** | 0.9k | The full primitive: definition, doorway, coverage, discipline, fractal structure, **twins as actors**, testability |
| `02__built-and-applied.md` | 0.7k | The S3 container as the worked proof, the AWS twins, and the nine-application map with owner sites |
| **`03__the-service-twin-and-the-collision.md`** | 0.7k | The execution broker, the boundary it closes, its two costs — and **the naming ruling** |
| `04__site-architecture.md` | 0.4k | Page by page; the name-watch check |
| `05__boundaries-and-licensing.md` | 0.4k | Provenance notes, do-not-publish, network boundaries |
| `07__gaps-and-open-questions.md` | 0.7k | 6 build-fresh items, 5 open questions, 5 tensions |
| `09__source-manifest.csv` | 15 rows | Every source, tiered 0–3, **every path verified on disk** |

---

## The three things worth your attention

**1. One twin works, and it is the right one.** The S3-compatible vault container — *"code using boto3 believes it is talking to real S3"*, backends swappable, **the consuming code unchanged**. That demonstrates the whole claim: a twin here is a drop-in interface, not a dashboard. Everything else is primitive (established) or design (labelled).

**2. The corpus caught its own naming collision — resolve it before page one.** The 19 August "Service Twin" is an execution broker that *holds credentials*, which is the opposite security property from the corpus twin, and the conversion review says so: *"the name collides, because twin already means something specific in this corpus."* `03__` rules: **twin keeps its corpus meaning; the broker is presented by its function** — and the two compose: the twin carries the persona and reasoning, the broker carries the credential and enforcement. The collision itself becomes the `/naming/` page, cross-linked to the skills pack's diverging-duplicate exhibit.

**3. The cheapest high-value artefact is one number.** The coverage measure — provisions of the AI Act whose hooks have no twin attached — is fully specified and has never been computed. Running it once makes `/discipline/` concrete and hands `standards.sgit.ai` a number it wants too.

**One tension to hold rather than resolve:** the broker *"becomes the highest-value target in the estate… which inverts the catastrophic failure property the rest of the architecture depends on."* The corpus states the cost and does not decide. Publish it as the open architectural fork it is.

---

## House pattern

Copy `pki.sgit.ai`, add `/llms-full.txt` — and keep this site **small and canonical**: it owns the primitive, the applications live elsewhere. Add the name-watch grep per build.

---

This file is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).