Docs component gallery
Every D01-D20 docs component, rendered once against fixture data.
This page renders every component in RFC-0050 §5.4’s closed D01-D20 set
against fixture data, so a reviewer can see all twenty without reading the
partial source. It lives outside content/docs/ and carries no
docs-tree.yaml row — check-docs-gallery.test.ts asserts the count below
against data/docs-gallery.yaml, which transcribes §5.4’s table.
D01 — Page header. This page’s own title, summary, role chip and
reviewed date, rendered once at the top by the anatomy dispatcher — the
same call every docs page gets, on this page’s own front matter.
D02 — Prose. This paragraph. The default; every other component is an exception to it.
D03 — Procedure
RFC-0050 §5.4, §2.3. A one-step procedure renders unnumbered; a multi-step one is an ordered list. Both carry a required escape hatch.
One step:
Run
mise run agent:spawn -- <id>.Result A worktree exists for the task.
If this doesn't work
If the id names no task file, create it first.
Three steps:
Open the new-channel wizard and pick a template.
Result The channel exists, empty.
Mention the agent you want by name.
Result An agent has joined.
Send it the task in one sentence.
Result The agent has replied in the channel.
If this doesn't work
If no agent replies within a minute, open the channel’s roster and add one by hand.
D04 — Callout
RFC-0050 §5.4, §5.5. Four kinds, at most two per page — this page keeps that cap the same as any real page, so two render live and the other two are named rather than instantiated a third and fourth time.
The other two kinds are warning (something the reader is about to get
wrong) and danger (a step that cannot be undone). Same markup, a
different icon and a different data-docs-callout value.
D05 — Code block
RFC-0050 §5.5. Every block carries a language tag.
mise run agent:spawn -- DX-0040-18D06 — Tabs
RFC-0050 §5.4. Alternatives, never sequential steps. Two independent groups: language, and role.
pnpm
pnpm install
npm
npm install
Member
A member sees the pending-decision card in the channel.
Admin
An admin also sees who else can act on it.
D07 — Field table
RFC-0050 §5.4. Name, type, default, description — for reference pages.
| Name | Type | Default | Description |
|---|---|---|---|
signal | enum | all | Which activity opens a system notification. |
priority | enum | normal | Sort order within one channel's feed. |
D08 — Provider block
RFC-0050 §2.2.4, §5.4. genre: surface only, immediately after D01. The
fixture below joins to the real terminal row in data/surfaces.yaml, so
this is the actual join D08 performs on every real surface page.
- Modes
- First-party only.
- First-party
- Included. Crusible provisions the machine itself — that is what lets a shell outlive your laptop and your network.
- Connect instead
- Nothing to connect — Crusible provides this one.
- Who holds the record
- Crusible. There is no provider to hand it to.
D09 — Matrix
RFC-0050 §3.6, §5.4. Index pages only, generated from data/. This is the
real surface-by-channel-kind matrix — index pages have no fixture form,
only real data.
| Surface | Worktree | Dashboard | Bridged | Direct message | Epic | Chatter |
|---|---|---|---|---|---|---|
| Terminal | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Project | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Forge | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Docs | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Diagrams | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Design preview | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Test replay | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Review | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Flow | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Dashboards | — Not available | Included | — Not available | — Not available | — Not available | — Not available |
| Issues | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
| Roadmap | Included | — Not available | — Not available | — Not available | — Not available | — Not available |
Terminal
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Project
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Forge
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Docs
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Diagrams
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Design preview
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Test replay
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Review
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Flow
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Dashboards
- Included in
- Dashboard
- Optional in
- —
- Not available in
- Worktree, Bridged, Direct message, Epic, Chatter
Issues
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
Roadmap
- Included in
- Worktree
- Optional in
- —
- Not available in
- Dashboard, Bridged, Direct message, Epic, Chatter
D10 — Card grid
RFC-0050 §5.4. Index pages only, generated from docs-tree.yaml. Three
real, published /concepts/ routes stand in — a card grid has no fixture
form either, since its whole job is linking to real pages.
- Start here Get from nothing to a running channel: install the CLI, join or set up a workspace, and create your first channel.
- Your first melt Create a Feature delivery channel, watch Forge and Probe work, answer when an agent asks you to, accept a doc suggestion, and take the change to review.
- Joining a workspace Someone set this workspace up before you arrived: what you are looking at, which parts are yours, and what to do first.
D11 — Figure
RFC-0050 §5.4, §5.5. Image, caption, required alt, source screen.
D12 — Next steps
RFC-0050 §5.4. Two to four links, on tutorial, how-to and explanation, last on the page.
D13 — Related
RFC-0050 §3.5, §5.4. Generated from related_guides, on reference and
troubleshooting pages. The fixture below is a doctype: reference page
naming two real, published routes.
D14 — Status notice
RFC-0050 §5.4, §5.7. Rendered automatically from status, never
hand-placed. Two fixtures, one per non-published state.
Planned:
Planned · Phase 2
This page is scheduled for phase 2 and has no content yet.
Gap:
Not yet documented
Blocked on a screen that does not exist yet.
D15 — Prerequisites
RFC-0050 §5.4. tutorial and how-to; the heading is always plural.
Prerequisites
- A workspace you can sign in to.
- The CLI installed.
D16 — Outcome
RFC-0050 §5.4. tutorial and how-to; time renders only on a tutorial.
What you'll have
A channel with one agent in it, doing real work. 10 minutes
D17 — Symptom block
RFC-0050 §5.4, §2.3. Four named slots, all fail empty; the fourth slot requires a time bound.
- What you're seeing
- A channel shows Lost the link.
- What it means
- The worktree's machine is unreachable.
- What to do
- Reopen the channel from the workspace sidebar.
- If you do nothing
- Crusible retries the connection for ten minutes, then posts a blocking message.
D18 — Genre fields
RFC-0050 §2.3, §5.4. Reference genres, each with its own field order — a field renders only when populated. Four fixtures, one per genre.
Surface (fields render after D08 on a real page; shown alone here):
- What it shows
- A persistent shell attached to the channel's worktree.
- Controls
- Resize, split, and reconnect after the machine idles out.
- What agents do here
- An agent can run commands here when a pending decision needs one.
Provider:
- Which surface it backs
- Issues.
- MCP or API
- API, with an MCP path planned.
- Who holds the record
- The connected tool, once connected.
- What agents may read and write
- Read every field this tool exposes; write a comment or a status change.
- What happens on disconnect
- Existing links stay readable; nothing new resolves.
- What is not supported
- Custom workflow states are not mirrored.
Bridge:
- Which platform
- Slack.
- What relays in each direction
- A channel message posts to the linked Slack channel and back.
- What does not relay
- Reactions and thread edits stay on their own side.
- Where the record stays
- Crusible's conversation is still the record.
- The origin badge
- Every relayed message carries a small Slack mark.
- What happens when the bridge is removed
- History already relayed stays; nothing new crosses.
Agent:
- What it does
- Drafts a reply and cites its sources.
- What it posts
- A message plus a details block for anything long.
- What it needs from you
- A pending-decision card, answered.
- Permissions it can hold
- Read every connected provider; write to none by default.
- Costs and limits
- One run per pending card; no background polling.
- Cordon behaviour
- A cordoned agent stops posting until a human lifts it.
D19 — Details
RFC-0050 §5.4. A long list, collapsed by default — never around a step.
What is not supported
D20 — Term
RFC-0050 §3.5, §5.4. An inline glossary link, usable anywhere. The glossary page does not exist yet (RFC-0050 §Open questions 1), so this link resolves once that page ships.
A channel’s worktree outlives the laptop that opened it.