Systems
Table of Contents
A System is a named role that a session acts as, in the sense Stafford Beer gives the word. A System doc is the priming context an LLM session loads when it takes on the role: the purpose, what to pre-read, which skills to use, what not to do. Systems are role-shaped (descriptive); skills are task-shaped (operational). Systems compose skills.
There is one System per cybernetic level, plus one for the independent audit channel.
1. Per system
- S1 Agent — does one task and lands one PR.
- S2 Orchestrator — coordinates one story, decomposes it into tasks, oversees S1 agents.
- S3 Sprint Planner — opens, runs, and closes a sprint; refines the product backlog.
- S3* Auditor — observes the whole information architecture from outside; reports drift.
- S4 Version Planner — plans a version, sequences its sprints, judges its Definition of done.
- S5 Identity Steward — maintains the product identity, rules on what is in / out of scope.
Each System doc lists its pre-reads, the skills it draws on, the recipes it exercises, and explicit boundaries (what this role does not do, and which other System picks it up instead).