bridge-onboard

Bridge Onboard — Setup Wizard

Set up a new Bridge user or reconfigure an existing one. Read the referenced file ONLY when triggered.

Philosophy — Discover, don't Interrogate

A new user came here to configure an assistant, not to inventory their life. Asking abstract questions like "do you file taxes for multiple legal entities?" or "do you have a household mandant?" makes the user defensive — they don't know yet what those features do, so they say "skip" to everything and miss the point.

Instead, the wizard:

1. Looks at what's already on the system (with permission)
2. Proposes specific features that match the evidence
3. Shows the rest as a read-only catalogue with "when you need it"
4. Surfaces features proactively later (feature-discovery standing-order) when patterns suggest they'd help

All of this is consent-first: before step 1, the user picks discovery.mode — confined (default) or broader. Confined means the Bridge never scans the machine (other repos, installed apps, devices, files, and mail stay untouched) — you still get every feature, just enabled modularly when you want it via the Phase E catalog, --add <feature>, or the feature's enabled: flag in bridge-config.yaml. Only broader unlocks the permission-gated scan in step 1.

The entry point is the four-lane front door in rules/session-start.md § NEW USER front door — it reflects what Phase 0 detected (origin state, git name), notes the guard is already armed, and opens four discoverable lanes under a free-text invite: [1] show me around (demo) · [2] describe what I'll use it for (→ this wizard, purpose pre-filled) · [3] make it private first (protection) · [4] bind a workspace / org overlay. This file and references/ are where lanes [2]/[3]/[4] land; the heavy lifting lives in references/.

Defaults — what the wizard assumes

• Purpose pins a north-star (ordering, never gating). It is captured at the front door — the user describes what they're here to do (session-start lane [2] or a free-text answer) and that sentence becomes purpose.statement verbatim; Phase A does not re-ask. purpose.focus and user_profile are derived silently from the statement — never posed as a visible six-domain questionnaire. Purpose ORDERS the Phase C suggestions, the Phase E catalogue, and (under broader) the feature-discovery standing-order; it never hides, gates, or removes a feature. Empty purpose = today's flat, general-purpose behaviour. Change anytime via --purpose.
• GitHub is optional. Onboarding completes end-to-end without a GitHub org, without gh CLI, and without GitHub-projects integration.
• Upstreams stay empty (upstreams: []) by default. Upstream variant choice is a separate, optional step via --upstream.
• Work-system on by default. Phase D recommends enabling — it's what makes Claude resume context across sessions. The wizard explains the trade-off but suggests [y].
• Discovery scan is opt-in per source. Default-on sources are non-invasive (git config, dir listings, app list). Sensitive sources (mail accounts, finance-app accounts, calendar names) are default-off and only opt-in.
• Nothing scanned beyond names. Mail content, document content, message bodies, keychain, passwords — NEVER touched. Explicit in the permission prompt so trust is established.