Skip to content
Back to Paths

Capture. The Intake Surface

30-second intake that routes itself when you pick the right type

FoundationFoundation~6 min|5 checkpoints
Sign in to track progress

By the end of this module

Used Cmd+Shift+K to capture without leaving the page you were on
Assigned a specific type (not Quick Note) to a capture
Linked a capture to a project at intake time
Captured a Decision and routed it to /decisions instead of Vault
Captured a Framework or Insight knowing it will likely become a vault asset

The Job of Capture

Capture exists because: get the thought out of your head before you lose it, with just enough metadata for future-you to route it correctly.

That's it. It is not the place to flesh out the idea, evaluate it, or decide what to do with it. Those are downstream jobs (triage, decisions, projects). Capture's only job is friction reduction.

The 30-second budget breaks down: ~5 seconds to type a title, ~5 seconds to pick a type, ~20 seconds to add context if it's a fresh insight, ~0 seconds if it's just a half-formed thought. If you're spending more than a minute on capture, you've started doing triage early, stop and save.

Tip:Cmd+Shift+K is the only shortcut you have to learn. It opens capture from anywhere in the app, including detail pages mid-edit. Build the muscle memory.

Why Type Matters

Every capture carries a type. The type is not bureaucratic taxonomy, it changes how the idea is routed and scored.

A Decision capture doesn't sit in the Vault waiting to be triaged. It's a flag that says "I owe future-me a structured decision log on this." Most users miss this distinction and let decision-shaped thoughts rot as RAW ideas for weeks.

A Framework or Insight capture is pre-flagged as a likely vault asset. When you triage it, the COMPOUNDING_ASSET outcome is the natural fit, and the CONVERT_TO_ASSET recommendation will fire after 14 days if you forget.

A Quick Note is the escape hatch. Use it when you genuinely don't know what category the thought belongs to. Don't use it as a default, it bypasses the routing logic entirely.

What Happens After Capture

All captures (except Decisions) enter as status: RAW and live in the Vault. From there:

  • Day 0-7: Idle in the Vault. Nothing prompts you.

  • Day 7: Appears in the Stale Captures panel on Today.

  • Day 30: If 3+ RAW ideas hit this age, STALE_CAPTURES fires as a Medium-priority recommendation.

  • Day 30+ with 10+ stale: STALE_CAPTURES escalates to High priority. The system is telling you the capture/triage ratio is broken.


The exit paths are: triage to a score (most common), bulk-park (for "interesting but not now"), or bulk-archive (for "I was wrong about this being interesting").

Common Mistakes

Writing the full idea at capture. You don't need to. The body field accepts paragraphs but is optional. A title alone is often the right capture. Detail belongs in triage notes or a project journal, not at intake.

Defaulting everything to Quick Note. This is the most common adoption failure. It bypasses Foundry's routing logic and turns the Vault into an unstructured pile. Spend the extra two seconds to pick the right type.

Capturing decided things as ideas. If you have already decided something, it is not an idea, it is a Decision. Use the Decision capture type and the entry routes to /decisions where it belongs.

Skipping project linkage. If a capture is obviously about an active project, link it now. Triage will find it 10 times faster, and the project journal stays coherent.

Capture Type Matrix

TypeUse whenRoutes toTriage signal
QUICK_NOTEGenuinely uncategorized, the escape hatch when no type fits.Vault → RAWNo bias in scoring
PRODUCT_IDEAA new product, app, or service concept.Vault → RAWStrategic Fit + Market weight
FEATURE_IDEAA specific feature for an existing product.Vault → RAWSynergy + Time to MVP
OPPORTUNITYA market gap or trend worth evaluating.Vault → RAWUrgency + Defensibility
INSIGHTA learning or 'aha' you want to preserve.Vault → RAW (CONVERT_TO_ASSET eligible)Likely COMPOUNDING_ASSET
PROMPT_ASSETAn AI prompt you'll re-run.Vault → RAW (asset-eligible)Likely COMPOUNDING_ASSET
FRAMEWORKA mental model or decision framework.Vault → RAW (asset-eligible)Likely COMPOUNDING_ASSET
DECISIONSomething you've decided or need to decide soon./decisions (skips Vault)Not triaged, logged directly
COMPETITOR_NOTEIntelligence about a competitor.Vault → RAWOften EXPLORE_LATER
LAUNCH_ANGLEA go-to-market or positioning idea.Vault → RAW (asset-eligible)Synergy + Marketing Ease
MONETIZATION_IDEAA pricing or revenue-model idea.Vault → RAW (asset-eligible)Revenue + Defensibility weight
NAMING_IDEAA brand, product, or domain name.Vault → RAWOften archived or kept as asset

Practice Checkpoints

Used Cmd+Shift+K to capture without leaving the page you were on
Assigned a specific type (not Quick Note) to a capture
Linked a capture to a project at intake time
Captured a Decision and routed it to /decisions instead of Vault
Captured a Framework or Insight knowing it will likely become a vault asset

Sign in to track your progress and mark checkpoints complete.

Next in Foundations Path

Vault. Your Compounding Library

Ideas are ephemeral; assets compound. The vault is where the difference shows up.

Start module

foundation

Foundations Path

Read time
~6 min
Checkpoints
5 items

Sign in to track

Sections
4 sections

In this module

The Job of CaptureWhy Type MattersWhat Happens After CaptureCommon Mistakes