The network
This site is one of several that carry one argument between them. Each is a separate repository, a separate domain and a separate release history — and each is built from the same three pieces: a commissioning brief published in full, a static site written from it, and the validate → tag → deploy pipeline that gates every release.
What is shared is machinery, not content. One stylesheet
(assets/site.css), one nav component, one pipeline shape, one release
discipline — copied deliberately rather than packaged, so any site can diverge
without asking permission. What is not shared is a single word of argument:
each site is written from its own documents.
This site's place in it
The unit here is the team, not the agent. Every site in the network is named for its unit — this one for the thing the industry keeps skipping.
# the memory network, by layer sgit.ai the product, the CLI, the vault layer skills.sgit.ai what a role can do — capabilities, SKILL.md teams.sgit.ai how roles are composed into a team wardley-maps.sgit.ai Pioneers–Settlers–Town Planners itself
The deconfliction rule
The seam, decided in the commissioning pack: a skill is a capability. A role is a boundary. A team is a routing table. Enforced by the entry format rather than by good intentions:
This site owns
- The
ROLE.mdformat, measured, with the falsifiable-claim recommendation. - The roster — nineteen roles, their claims, their exclusions, where each exists.
- The topologies — Explorer/Villager/Town Planner as staffed roles, and the handback rule.
- The comms protocol — how roles address each other, never what a message bus would do instead.
The sibling owns
SKILL.md, skill lifecycle and description-as-trigger — skills.sgit.ai.- Pioneers–Settlers–Town Planners itself, the evolution axes — wardley-maps.sgit.ai.
- Issues-as-files, the
.issues/tree — issues-fs.sgit.ai. - Coding conventions the Dev role follows — coding.sgit.ai.
The rule in one sentence: this site owns composition. Anything about the work itself belongs to the site that owns that work.
The sibling sites
| Site | Owns | Relation to this site |
|---|---|---|
| sgit.ai | The parent project: the zero-knowledge vault layer, the shipped CLI, the demos and the catalogue — and the network index that lists every site here | Parent |
| skills.sgit.ai | Capability:
SKILL.md, the skill lifecycle, description-as-trigger — reserved and
unpublished as of this pack's measurement | The nearest seam. Where this site names a role's tools, it links out rather than duplicating what a skill does |
| wardley-maps.sgit.ai | Mapping: evolution axes, situational awareness, Pioneers–Settlers–Town Planners itself | Owns the model. This site owns only the staffing of PST as three agent teams |
| issues-fs.sgit.ai | Issues as files, the general argument for a versioned tree over a database | This site makes the narrower version for inter-agent comms specifically, and links out rather than restating |
| coding.sgit.ai | How software actually gets written here: five languages, the rules, measured compliance | The Dev role's own conventions live there, not here |
| nfrs.sgit.ai | CI, testing and documentation as measurable properties | Owns the properties; this site owns only which roles are accountable for them |
| pki.sgit.ai | Vault keys and
sgit mechanics | No overlap beyond the prohibition as it appears inside a role file. This site's structure was copied from this house pattern |
| threat-modeling.sgit.ai | Threat modelling as a method | Only that AppSec is the role that does it |
| risks.sgit.ai | Accepted risks, named acceptors and mitigations | Shares the falsifiable-statement discipline this site's Central Claim recommendation runs on |
What every site in the network runs
The same three jobs, in the same order, gated the same way — described in full on this site's engineering page:
validate ──▶ tag-release ──▶ deploy # a failure in any job stops the ones after it; the live site is never # replaced by a release that did not pass its own checks
The differences between sites are the checks each one adds, and the addition is
always the site's own subject made executable. pki.sgit.ai
bans key-shaped strings anywhere in the tree because it documents key discipline. This
site adds the roster-is-the-data check — every tally on every page recomputed
independently from data/roster.json — because a role count typed by a
person is the first thing that goes stale.
Licence
Every page of this site, llms.txt and llms-full.txt are released under CC BY 4.0. Attribution: Dinis Cruz, with AI co-authorship (Claude, Anthropic).
Pioneers–Settlers–Town Planners is not covered by that. It is Simon Wardley's model, published by him under CC BY-SA — named, credited, linked to wardley-maps.sgit.ai and to his own material, never reproduced. This site's contribution is the staffing of PST as three agent teams, which is original; the model is not.