Ethos onboarding — seed selection
A sequence diagram of the journey a user takes from landing on the
seed-picker screen to handing off to the Builder. The screen is
EthosSeedSelectionScreen at
route /ethos-onboarding/seeds; the call is GET /api/ethos/seeds;
the hand-off is a navigation to /builder?mode=create after the user
taps a seed. The diagram visualises what the
Ethos onboarding seeds page
prose already documents — this is a complement, not a new source of
truth.
Last reviewed against client commit
ea9d091(gnostikon-client, branchmain).
How a user goes from the seed-picker screen to a Builder pre-seeded with the selected Ethos seed, via a single catalog fetch and a local hand-off write.
The seeded Builder takes over from there. The auto-Analyze → STM →
auto-Propose chain it runs with intent="onboarding" is documented in
Auto-Generate bypass and is
intentionally not depicted in this diagram — the pilot stops at the
navigation to keep the journey legible. A future Builder diagram in a
later wave will own that surface.
Client surface
- Ethos onboarding seeds —
the per-screen reference for
/ethos-onboarding/seeds, including the four UI states, the four telemetry events, and the scope-flip dismissal behaviour.
API endpoints
GET /api/ethos/seeds(operationlist_ethos_seeds) — fetches the curated catalog rendered by this screen. See the API reference for the response shape (EthosSeedListResponseModel, items ofEthosSeedItemResponseModel).
Related guides
- Ethos onboarding — the end-to-end flow that brings a user to this screen (no-Ethos CTA, scope handshake, seed catalog, Builder hand-off).
- Auto-Generate bypass — what
happens in the Builder after the user taps a seed (the
intent="onboarding"chain and its natural-window closure).