The brief pack: what it is and how to read it
Summary
The front door of the pack that commissioned this site. It states the corpus behind the material (148 files mentioning digital twins, eleven twin-named briefs, roughly 28,000 dedicated words anchored by a cluster written on 26 June 2026), sets the reading order across the eight documents, and names the three things the commissioning agent should pay most attention to: that exactly one twin works and it happens to be the right one, that the corpus caught its own naming collision and the site must resolve it before page one, and that the cheapest high-value artefact available is a single number nobody has computed. It also fixes the house pattern (copy pki.sgit.ai, add the llms-full.txt it lacks, keep the site small and canonical) and adds the name-watch as a per-build check.
Key concepts
- The twin primitive — a system with properties, behaviours, functions, inputs and outputs
- Interface, not simulation — the contrast the site leads with
- The naming collision — flagged by the corpus, ruled on here
- The coverage measure — one number, fully specified, never run
Key ideas
- This is a reference site for a primitive: five other sites depend on the twin idea and should state it in three lines and link here.
- One twin works and it is the right one, because a drop-in interface is the claim, and boto3 cannot tell the difference.
- The collision must be resolved before page one, because a site cannot use a word that means two opposite things.
- The cheapest high-value artefact is one number: provisions of a legal instrument whose hooks have no twin attached.
- One tension to hold rather than resolve: the broker becomes the highest-value target in the estate, and the corpus does not decide.
On this site
Sets the shape of the whole site: the build order on the open questions page, the small-and-canonical scope on the network page, and the name-watch in the release gate.