# 07 — 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`.

**The shipped SKILL.md files are part of Apache-2.0 repos.** Quoting them at length is fine with the notice retained; do not imply they carry the site's CC BY licence. If the site republishes full skills as downloadable artefacts (a reasonable move for a registry v0), publish them under the repo licence, stated per skill.

## 2. Do not publish

- `library/alchemist/materials/` — the whole tree (the skills-revenue material near it is fine; the investor framing is not).
- `team/roles/grc/reviews/02/19/` — names a private individual.
- `team/humans/dinis_cruz/briefs/06/08/…tls-ssl-cybersecurity-skills-landscape.md` — **names a private individual as a commercial target.** The skills-landscape *task* inside it is safe in isolation; the surrounding brief is not. (Same ruling as the wardley pack.)
- The Tessl brief is publishable as analysis, but **check it for private conversation detail before quoting** — it records a live commercial discussion. Publish the pattern, not the negotiation.
- The Feb 2026 threat-model trio: publish the *fact* of the reviews and their structure; **check the threat model itself for live findings** before publishing content.

## 3. Network boundaries

| Site | Owns | This site |
|---|---|---|
| **`skills.sgit.ai`** | The skills thesis, the catalogue, authoring, the skill economy, skills+identity | — |
| `wardley-maps.sgit.ai` | **The skill lifecycle** (Explorer→Town Planner, English-to-code, the token-spend line) | Three lines and a link |
| `open-source.sgit.ai` | The OWASP monetisation thread, fork economics, the villagers argument | Owns the skills *mechanism*; links for the arguments |
| `graphs.sgit.ai` | Meaning through connectivity, G³ | Owns the *application* of graphs to skills |
| `coding.sgit.ai` | Code conventions, `/for-agents/` | The skills-describe-intent claim is the same argument from the other side; cross-link |
| `standards.sgit.ai` | Vault-as-substrate, the subset method | Base vaults are that architecture applied to skills |
| `llms.sgit.ai` | `sg.llm.*`, the chat pane | Source of the when-not-to-make-a-skill decision; that site owns the capability |
| `sgit.ai` | Vaults, the catalogue | Base vaults live there physically |

## 4. House style

Every catalogue entry generated, never hand-written · the divergence measured per build · `[S]` / `[D]` / `[E]` labels on every page section · quote the lead's own words for every thesis claim (the briefs are written for exactly this reuse) · -ise, no em-dashes.

---

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