3. Processes and the curated index

Capture a runbook as steps, then pin everything into a navigable tree.

Before you start: Capture your first units

A repeatable task is a procedure: ordered steps (each with a body screen showing what's on screen and a body steps saying what to do), from -> to flow edges that draw the flowchart, and a verification line — how you know it worked.

Units become navigable when an index pins them: each index is a sidebar branch whose related lists the unit ids it owns. Unpinned units stay reachable through links but invisible in the nav.

§ 1Exercise: Capture a runbook

Write the task you do most often in your topic as a procedure with at least two steps and a verification, then pin it (and your earlier units) into an index.

procedure daily_task {
  title   = "…"
  purpose = "…"
  step first  { n = 1  body steps { p "Do this." } }
  step second { n = 2  body steps { p "Then this." } }
  first -> second
  verification = "How you know it worked."
}

index basics {
  name    = "Basics"
  related = [my_first_idea, daily_task]
}