Your first venture

The fastest way to understand Bridge end-to-end is to walk through one project from capture to Build Plan. This guide narrates a real example — three notes about a recipe converter that turn into a complete spec set you can hand to your coding agent.

The idea

Suppose you cook a lot and you have ingredient quantities scattered across recipes in different units — cups, grams, tablespoons, milliliters. You want a small tool that lets you punch in a quantity and convert it. Nothing fancy. A weekend project at most.

Capturing the notes

Open Bridge, tap +, type your first note. Don't structure it. Just get the thought out.

Note 1 (captured Monday morning):

"Tired of converting cups to grams while cooking. Need a quick mobile-ish thing where I type '1.5 cups flour' and it tells me grams. Should work on planes."

Within thirty seconds Bridge's scan extracts: no URLs, no hashtags, no code. Classification: Expandable (it's an idea, worth elaborating). If you're on Discover or higher, the general expansion runs too — Bridge writes a one-paragraph elaboration that fleshes out what you're after.

Note 2 (captured Tuesday evening, after you almost burned dinner):

"Same thing again — wanted to convert tablespoons to ml. Why isn't there a clean converter that works offline and doesn't need an account? Just a calculator basically."

The scan extracts: nothing. Classification: Expandable. The second note about the same topic seeds a constellation candidate — but Bridge needs at least three related notes to actually form one.

Note 3 (captured Wednesday, while reading a baking blog):

"Density-aware conversion would be the killer feature — 1 cup of flour and 1 cup of sugar weigh different grams. The web tools all assume water density. That's the entire reason recipe conversions are unreliable."

This note is the third related capture. Bridge recognizes it as close in meaning to notes 1 and 2 and connects them. A constellation forms.

The constellation

Open the graph view. Three nodes sit in a small cluster, edges drawn between them. The constellation has an AI-generated name — something like "Offline recipe unit converter with ingredient density". Tap any node to focus the cluster.

This is the signal that the idea has cohered: three related captures, connected on their own, named for what they're about. There's no proposal to approve and no project to set up — once the constellation forms, it is the venture.

Starting the venture

Tap Start a venture — from the constellation popup in the graph, or from any of the three notes on the note detail screen. The venture picker opens with the three constellation notes pre-checked. You can adjust the set here — pull in a related note from another cluster, drop one that doesn't belong — then tap Build Plan to generate.

Bridge gathers context: every note you picked, their expansions, the constellation theme, your user-behavior memory. The plan generator runs. Within about a minute, a plan artifact lands in the Plan tab.

How ambiguity gets handled

There's no separate question-and-answer step before generation. The generator resolves ambiguity inside the plan instead. Your notes emphasized "works on planes" and "works offline" but never pinned down whether the prototype should be strictly local-only or just offline-tolerant — so the generator makes the most defensible call from your notes (strictly local-only, the stronger signal) and records it as an explicit constraint in 03_architecture.md and 07_scope.md.

When the generator genuinely can't resolve an ambiguity, it leaves a [NEEDS CLARIFICATION: ...] marker inline in the relevant file, so you and your coding agent can both see exactly what was assumed. You resolve it by adding a note that settles the question and regenerating — or, on the Refine tier, by asking chat to change it directly. See Handling ambiguity.

Reading the spec set

Open the artifact. You see:

00_index.md — orients an agent to the eight files in the set.
01_brief.md — "A mobile unit converter for cooking quantities, density-aware. Target: home cooks who want fast unit conversion without their hands on a flour-covered screen."
02_user_flow.md — "WHEN the user opens the app, THE System SHALL display a converter input. WHEN the user types '1.5 cups flour' and taps convert, THE System SHALL display the equivalent in grams using flour density."
03_architecture.md — the architecture file reflects the locked-in offline constraint: "Local-only SQLite, no network calls, no analytics SDK. Bundled density lookup table. Flutter for cross-platform mobile."
04_data_model.md — pre-defines the Ingredient entity (name, density, units) and a Conversion function signature.
05_tasks.md — atomic tasks ordered by dependency, each with an accept-when condition.
06_acceptance.md — the end-to-end test scenario: "Convert 1.5 cups of flour to grams; expect 188g (±5%)."
07_scope.md — the canonical positive scope, with the offline constraint baked in: "Scope: single-user, local-only, no network calls. Demo data: 30-ingredient density table bundled at install."
AGENTS.md — the overlay that points your coding agent at the right reading order.

Handing it off

Tap Download zip. Move the zip to your project directory. Unzip. The AGENTS.md overlay sits at the root; your coding agent reads it first.

Open the project in your coding agent of choice. The agent reads AGENTS.md, follows the reading order, opens 05_tasks.md, and starts working through tasks T01, T02, T03 — updating the status as it goes.

Come back the next day. Re-open 05_tasks.md. Half the tasks are marked Status: done with one-line deviation notes. The other half are Status: pending. The plan is the status.

What just happened

In about an hour of elapsed real-time — three captures spread across a week, one Start-a-venture tap, one Build Plan tap — you went from a vague itch to a portable spec set an agent can implement against. No tagging. No template. No structured input.

That's Bridge.

See Capture habits for patterns that get the most out of every capture.
See Refining a plan for what to do when the generated plan needs tightening (Refine tier).
See Sharing a plan for download / share-sheet / overlay-deployment details.