the-system # The System The System gives a Pi project a lightweight place for its mission, plans, decisions, and implementation progress. Use it when work needs shared direction and visible human approval instead of an unstructured stream of prompts. ![the-system demo: init, phase, spec, plan, human approval, exec with board update, doctor, all from /system](assets/demo.gif) ## Start here Run `/system init MYPROJECT` in the project you want to govern. Pi shows what it will create or update and asks for approval before changing files. Restart Pi to load the new project's guidance. Then run `/system phase` to establish the current working phase, or `/system research ` to begin exploring a problem. ```text /system research How should we support offline imports? ``` Each lifecycle command starts a new Pi turn with your instructions and current project status. Run `/system spec ` to define what must be true. Run `/system plan ` to prepare a plan, then review and explicitly approve it. Run `/system exec ` to carry out approved work. Stages do not automatically advance, so you choose each next step. Enable Pi's `codemode` or `tool_search` so Pi can discover deferred System tools without first activating a lifecycle stage. ## Keep track of work Run `/system board` to open the project board and review or change tracked progress. Specs appear in one column with nested plans, unfinished first and most recently modified first within each group. Click a document ID to copy it, or click **EXEC** to start `/system exec ` in the current idle Pi session. Click **EDIT** to open a document in your configured editor, using the same opener as `/system edit `. Use **DROP** to exclude a spec, plan, or issue without marking it done; **RESTORE** returns it to todo or open. Dropped items appear last and do not count as active work. Dropping a spec leaves its plans unchanged; dropped plans do not block spec completion. Plan approval remains separate from completion; toggle draft or approved in the document's metadata. Run `/system assess` to ask Pi for evidence-backed progress proposals, then review them in the board. Run `/system doctor` when you want to check System files without changing them. Run `/system book` to browse the project dossier, `/system view ` to jump to a document within it, or `/system board` for its board page. All three commands share one authenticated localhost application per project, which closes when the Pi session shuts down or reloads. Pages follow project changes automatically, retaining the current location, scroll position, and search text when refreshed. Keep the opening URL private: it grants browser access to the book and its actions. Treat authored HTML and visual assets as trusted project content, not isolated previews. Scripts in authored HTML or previews share book origin and can invoke authenticated actions, so only trusted project content is safe. The System stores its material in `.system/` within your project. It may ask for approval before creating core documents, changing the current phase, editing an approved plan, or changing governed files. Review those prompts before accepting them. [Installation](../../README.md#install) ## Reference ### Commands | Command | Purpose | | --- | --- | | `/system` | The System project governance |