HistoryHelp:SystemViewPro

Up to 100 versions are kept, as small diffs with a full copy every 10th. Restore makes a new version with the old text: nothing is lost.

version 5current 2026-10-05 11:43 UTC View Text
version 4diff 2026-09-30 09:41 UTC View Text

What version 5 changed
---
-tags: help, system
+tags: help, system, inherited
order: 30
description: the full view on pro and master: spec, design, implementation and tests side by side
…
version 3diff 2026-09-29 03:14 UTC View Text

What version 4 changed
---
tags: help, system
+order: 30
+description: the full view on pro and master: spec, design, implementation and tests side by side
---
# Help: the full system view
…
version 2diff 2026-09-28 17:12 UTC View Text

What version 3 changed
…
**Behind the scenes.** The server keeps a small index, built once per topic version: one row per section and code, which topic has it at each level, and a hash. Your browser builds the page from it and asks for a section's text only when you open it. The page checks for changes every few seconds and, with auto-scroll on, walks you through what changed. Links like `/system?show=^vault-3` open straight to a behaviour.

+**Components** (`/components`, a Toolbox tile) shows the same sections as cards, one per functional area: where it is in the spec, design, implementation and tests, what's missing, and the project's domain; `GET /api/v2/system` gives the same as JSON, for your AI.
+
**Related:** the Feature list (`/features`) reads the same index per behaviour; [[Help:Pipeline]] for how work moves.
version 1diff 2026-09-28 13:28 UTC View Text

What version 2 changed
…
**Where each column comes from.**
- **Sections** are the ids on the headings (`{#vault}`) and the behaviour codes on spec lines (`^vault-3`); the same id in every document lines them up.
-- **Spec and Design** are the topics tagged for them (and a project's **Features** topic, from when it was hero or creator); **implementation** topics (pick one at the top) say where each part is built; **Tests** lists the design tests and code tests that cover each code, and their status (tested, gap, not built).
+- **Spec and Design** are the topics tagged for them (and a project's `Spec`, the maker's Specification from when it was hero or creator); **implementation** topics (pick one at the top) say where each part is built; **Tests** lists the design tests and code tests that cover each code, and their status (tested, gap, not built).
- The markers **D, I, T** show which levels a section has; a missing one counts as a gap.

…