alivecapture-context

# Capture Bring context in. The most important skill in the system. If capture is hard, people skip it. If people skip it, the system dies. Capture must feel instant. --- ## When It Fires - File pasted or dropped into conversation - Email forwarded or pulled via API - Transcript from a call or meeting - Screenshot shared - Content pasted from another app - API context pulled (Gmail, Slack, Calendar) - Research completed during a session - The human says "capture this" or "add this" - Squirrel detects external content and offers to capture - The human says "check inbox", "clear inputs", or "what's in my inbox" - Capture is invoked with no obvious in-conversation content (triggers inbox scan — see below) **Capture is one of two operations that writes mid-session** (the other is bundle drafts). Everything else waits for save. --- ## Three Stages ### Stage 0 — Detect and Classify (instant) No processing. Just identification. - **ref_type** — email, transcript, screenshot, document, message, article, research - **sensitivity** — public, private, restricted (default: private) - **source** — gmail, slack, web, manual, in-session ### Stage 1 — Store Raw + Route to Bundle (always happens, non-negotiable) Even if extraction fails or is skipped, the raw content is preserved. **Pre-capture check:** Before proposing a destination, grep the target walnut's bundle manifests and `brief.md` files for the inbox filename. If found, the file is already referenced — route into that ...