# 06 — Site Architecture

## The house pattern

Copy `pki.sgit.ai`; add the `/llms-full.txt` it lacks. And note this site's particular duty: **its subject is the artefact type agents load** — so `/llms.txt` self-sufficiency and the markdown twin are acceptance criteria, and the catalogue must be machine-readable before it is pretty.

---

## Page by page

### `/` — the front page
The thesis in one line — *"skills are software packages… the same way we have npm and pip, we need a way to manage skills like that"* — then the honest split: **8 shipped, 60,782 words of theory, one green cell in the lifecycle table.** Then the diverging-duplicate exhibit in two sentences.

### `/catalogue/` — **build first**
The 8 skills, **generated from their SKILL.md frontmatter** (`skills__catalogue.json` is the seed). Per skill: name, trigger summary, word count, repo, version (once versions exist), and the do-NOT-use clause surfaced as a first-class field. This page is the registry v0 the thesis calls for.

### `/authoring/`
`02__` §§2 and 4 — the five conventions and the three governance rules. **The page a visitor can use the same day**, and the only page whose content is fully `[S]`.

### `/thesis/`
`03__` — the package claim, the lifecycle table with its one green cell, intent-over-capability, and the five-step roadmap.

### `/graph/`
`03__` §§3–4 — the projection paradigm, typed primitives, the forking ecosystem. **Banner: design, not shipped.** Every current skill is the static photograph the page criticises.

### `/identity/`
`05__` — the permission set principle, units of execution, the OAuth critique, and the one-field frontmatter proposal.

### `/economy/`
`04__` — base vaults, the cascade, Tessl, scoring-on-provenance, the OWASP case, the conference signal.

### `/shipped/`
The lifecycle table unsoftened · the duplicate · zero declared permissions · zero evals · no registry · the Feb 2026 review trio as the precedent-and-lapse.

### `/network/`, `/admin/`
House pattern; build order published unresolved.

---

## What must be generated

The catalogue (from frontmatter) · the lifecycle table's skill column (from the repos) · all word counts. The `use-sg-playwright` divergence should be **measured on every build** — the day the two copies match, the exhibit becomes a resolution story, which is even better.

---

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