# 04 — Site Architecture

## The house pattern

Copy `pki.sgit.ai`; add the `/llms-full.txt` it lacks. This site's particular character: **it is a reference site for a primitive** — the shape the grounding ladder already has, where other sites state the idea in three lines and link here. Keep it small and canonical rather than broad.

## Page by page

**`/`** — the definition and the contrast in 300 words: *a system with properties, behaviours, functions, inputs and outputs* — an **interface to reality, not a simulation of it** — with the doorway sentence and the "even luck" list. Then the honest ratio: one working twin, two established primitives, a large designed layer.

**`/what-is-a-twin/`** — `01__` in full. Definition, doorway, connectedness-as-fact, discipline of reality, fractal/stacking/seams, actors, testability.

**`/discipline/`** — the discipline of reality and the tracked air gap, with the coverage-measure extension. **The most distinctive page** — nothing else in the digital-twin literature says *"either we have evidence and it exists, or we do not."*

**`/built/`** — `02__` §§1–2. The S3 container as the worked proof (with the boto3 sentence as the headline), the AWS twins, the primitives. Link the sg-compute pack's delivery evidence.

**`/applications/`** — the map from `02__` §3: nine applications, each three paragraphs and a link to its owner site.

**`/actors/`** — twins as actors, personas, documented reasoning, the change pipeline — and the composition with the execution broker from `03__` §4.3.

**`/broker/`** — `03__` §§1–2: the execution broker, the boundary it closes, the two costs. Under its function-name, with the naming note.

**`/naming/`** — `03__` §4. Short, honest, and cross-linked to the skills pack's diverging-duplicate exhibit.

**`/simulation/`** — the world-model layer, labelled design, with the 2FA demo as milestone one.

**`/shipped/`** — the built/designed table from `00__` §4, unsoftened.

**`/network/`, `/admin/`** — house pattern; build order published unresolved.

## What must be generated

The application map's link targets · the built/designed table · all word counts. And one check worth automating: **grep the estate for new uses of "twin"** per build — the Service Twin collision happened once and will happen again; a name-watch is this site's equivalent of the licence audit.

---

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