# 05 — Boundaries and licensing

## 1. Licensing

**This site's content is CC BY 4.0**, consistent with the network; stamp every markdown document and gate with `licence-audit.py --check`. Code quoted (the S3 container, the AWS engine) is **Apache-2.0** — retain the notice.

**One source needs a provenance note:** the Service Twin brief is *"converted from a document produced in a voice session with a different assistant, restructured into the corpus format."* The corpus records that honestly; the site should carry the same note where it quotes that material, and its companion market-research file is marked *"as supplied"* — treat its external claims as unverified until checked.

## 2. Do not publish

- `library/alchemist/materials/` — the whole tree.
- `team/roles/grc/reviews/02/19/` — names a private individual with signature blocks. **Note:** the 2FA scenario the twins demo builds on originates in that incident — publish the *scenario* as the corpus's own worked example (it already does this), never the underlying named acceptance records.
- The Service Twin **market research** (5,142 w) — external, "as supplied", may name vendors and market figures. Extract with per-claim verification; do not republish wholesale.
- The hyperscaler-consumption brief (23 Jul) — check for named-vendor positioning before quoting beyond the twins-abstraction section.

## 3. Network boundaries

| Site | Relationship |
|---|---|
| **`twins.sgit.ai`** | Owns the primitive: definition, discipline, actors, the broker, the naming ruling |
| `risks.` / `standards.` | Own the grounding ladder and the regulation graph; **this site owns the `Twin` rung and the hooks/coverage idea** — each states the other in three lines |
| `nhi.` | Owns the identity-twin visualisation play; links here for the primitive |
| `sg-compute.` | Ships the S3 container and the vault specs; this site explains why it is a twin |
| `graphs.` | Owns meaning-through-connectivity; this site owns what happens at the graph's edge |
| `skills.` | The naming-drift lesson is shared — cross-link the two exhibits |
| riskmandate.ai | Commercial; references, is not referenced |

## 4. House style

Quote the lead's own words for every claim — the 26 June cluster is written for exactly this reuse · label every section `[built]` / `[primitive]` / `[designed]` · the "even luck" list stays verbatim, it is the most memorable sentence in the cluster · -ise, no em-dashes.

---

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