---
name: showup-capture
description: Capture Steven's real work, decisions, failures, screenshots, ideas, and shipped proof as content material in Notion. Use when he asks to log a moment, save something for content, inspect recent work for stories, capture an asset, or update the Content Inbox.
---

# Show Up capture

Leave a useful record of what happened without turning content into another task list.

Read [work sources and safety](../../references/sources.md) before inspecting connected apps, moving an asset, or writing to Notion.

## Workflow

1. Start with the supplied material. Inspect GitHub, Linear, Codex, Notion, or Calendar only when the request calls for it or the evidence points there.
2. Apply the proof-to-post filter. Record what happened, what shipped or broke, where the evidence lives, why somebody might care, and the reusable pattern.
3. Preserve exact links, dates, tool names, numbers, commands, decisions, and outcomes. Ask only for missing human context that changes the story: why it mattered, what surprised or frustrated Steven, what he did next, and what must stay private. Never invent feelings, intent, authority, or results.
4. Classify the item by content type and lifecycle separately. `Shipped proof` is a content type. The lifecycle is `Raw`, `Seed`, `Draft`, `Approved`, `Scheduled`, `Published`, or `Archived`.
5. For private work, save only a safe generalized pattern for public use. Keep the identifying case private.
6. When capture is requested, fetch the live Content Inbox schema and create or update the Notion entry. Map the conceptual fields in the source reference to properties that actually exist.

For shipped proof, capture the artifact, project, evidence URL or path, outcome, public or private classification, and reusable pattern. Set `Human context ready?` only when the material contains a human point and the public/private decision is explicit.

## Capture an asset

When Steven asks to capture an accessible local screenshot, video, or other asset:

1. Verify the current canonical content asset destination from live configuration or connected storage.
2. Check the source, existing links, filename, and checksum when available. Reuse the existing canonical asset instead of copying it twice.
3. Copy or upload the asset only after the destination is verified.
4. Preserve the source and capture date. Link the canonical asset from the Content Inbox and record what the asset proves.

Keep secrets, private URLs, credentials, and unsafe client material out of the asset store and public content record. Do not use an old Drive folder ID without verification.

## Boundaries

- Capture source material. Draft copy only when Steven also asks for a draft.
- Notion owns mutable content state. Do not create a local proof ledger or social database.
- Ordinary activity does not create Todoist tasks, reminders, or artificial deadlines.

## Done

The capture is complete when each saved item has traceable evidence, a reason it may matter, a safety classification, and a verified Notion record when a write was requested. A captured asset also has a verified canonical link, source, capture date, and proof note.