onboardlisted

# onboard — the guided first run > **onboard or bootstrap?** One question: **is there a runtime to scaffold?** > No runtime yet → [`bootstrap`](../bootstrap/SKILL.md) first; it scaffolds one > and ends by calling `spark setup`. Runtime present → `onboard`. `spark orient` > prints the answer under **Next**. Own the *narrative* of a repository's first run. Each motion is a create-only CLI verb; you supply the sequencing and stop at every human decision rather than defaulting through it. Every step is idempotent — rerunning resumes or truthfully reports "already armed," so a run halted at a decision picks up without repeating finished work. ## The four motions ### 1. ORIENT — establish context first Run `spark orient`. It classifies the repo and writes nothing (ADR-0022). Confirm the verdict with the operator; it governs everything below. Defer *recording* it (`spark orient --set …`) to SEED, so a chosen profile lands before the classification fact and setup never refuses over it. - **`ambiguous`** → **stop and ask.** Signals are sparse or conflicting; never infer authorization. Do not proceed until the human names the verdict. - **`existing`** → **truth-first, never scaffold.** Run `spark triage`: it establishes what is true read-only. Resolve what it reports before SEED — arming a repo whose truth is unestablished is the mistake. Skip PROFILE (a new-project act); setup adds only what is missing. - **`new`** → proceed to PROFILE. Read orient's **Next** line before