Audit onboarding.
A browser pass through the flow, a critique of what it finds, and the fix made where the element lives.
What you give it.
A sentence, and what the Brain already holds. Boomship asks for a repository or a file only when the Mission needs one.
Walk through onboarding on northstar.example, find what breaks, and fix it.
Northstar Supply, a fictional company · Illustration
What it does with it.
Each step names what it makes. Every step that ran is on the receipt; one that could not run is written as not run.
- 01Walk the flow in a browserdesktop and mobile captures, console errors kept
- 02Critique what it sawa score against the Design Constitution, before
- 03Find the element’s sourceelement → component → file, through the Brain
- 04Fix it on a brancha boomship/ branch, tests and typecheck
- 05Compare before and aftervisual regression, critique after
What comes back.
Your first order in nine minutes.
Northstar v4 sets up your catalogue from last month’s invoices.
Start with an invoice- A verified change on a boomship/ branch
- Before and after: the captures, the critique scores, the diff
- A receipt that says which browser flows ran
What it needs connected.
Each one says how it connects and what Boomship may do with it. A connection on its own puts nothing into a Mission; only what you add to a project’s Files does.
Where you come in.
A steer is received at the next turn. A failed check holds a chain. The merge is a button Boomship does not press.
- Steerwhile it works
“Mobile first” or “leave the copy alone” changes the route at the next turn.
- Reviewwith the before and after
The critique is a score, not a verdict. You say whether the fix is right.
- Mergeat the end
The branch is yours to merge.