Document type: system
Table of Contents
This page defines the system document type — one entry in the
document types taxonomy. The general contract every document follows
(frontmatter, state, linking, tags) lives on the taxonomy page; this
page carries only what is specific to system.
1. Contract
- Implements
- loading. See
Regulatory Functions. A
system is role-shaped: it describes a named role and lists the
operational skills,
recipes, and pre-reads that role uses. Think of it as the priming
context an LLM session loads when it takes on that role — "you are S2
orchestrator, here is what you do, here is what you do not do, here
are the skills available to you." Compare with
skillbelow, which is task-shaped. - Folder
doc/systems/- Level
crossor a specific level.- How to create
- system codegen is not yet wired into
compass add(nosystemtype yet); for now, copy an existing system document underdoc/systems/and adjust the frontmatter and sections. - (no term)
- Not stateful — no TODO.
- Required sections
* Purpose— one paragraph: what this role is for.* Operates at— which system level(s); link to cybernetic levels.* Inputs— what this role consumes (documents, signals).* Outputs— what this role produces.* Pre-reads— documents that must be loaded into context before the role can act. The contract docs go here.* Skills— id-links to the skills this role invokes.* Recipes— id-links to the recipes this role exercises.* Boundaries— what this role explicitly does not do, and which other System picks it up instead.