Reify Capture

You are tasked with capturing an idea or note using the Reify conviction-spectrum type system.

Process

1. Parse Input

Extract from $ARGUMENTS:

• Content: The main text to capture (required)
• --type: Optional explicit type override
• --tags: Optional comma-separated tags

If no content provided, ask: "What would you like to capture?"

2. Load Type System

Read .reify/types.json to understand:

• Categories: ideas, captures, references, workflow
• Conviction spectrum: question (0.1) → thought (0.3) → observation (0.7) → principle (0.9)
• Type definitions with when_to_use guidance

3. Infer Type (if not specified)

Analyze the content against conviction spectrum:

Signal	Suggested Type
"?" at end, "what/how/why", uncertainty	question
"I think", "maybe", speculation	thought
"I noticed", "saw", witnessed event	observation
"Always", "never", strong belief	principle
Concrete case, demonstration	example
Quick note, doesn't fit spectrum	note
Action item, todo	task

Present your inference: "This sounds like a [type] because [reason]. Proceed with this type?"

If user disagrees, offer alternatives from the same category.

4. Generate Metadata

Timestamp: Current time in format YYYY-MM-DD_HHMM

• Use: !date +%Y-%m-%d_%H%M`` to get current time

Slug: Generate from content

• Lowercase, hyphens for spaces
• Max 50 chars
• Remove special characters

ID: {timestamp}_{slug}

Filename: {id}.{type}.md

• Example: 2026-01-09_1430_conviction-spectrum-idea.thought.md

5. Determine Category Folder

Map type to category folder:

• ideas: question, thought, observation, principle, example
• captures: note, web_clip, voice_memo, highlight, screenshot, bookmark, chat, message, prompt_result
• references: person, work, concept, term
• workflow: task, email, intel

Path: .imaginary/{category}/{filename}

6. Create File

Write with this structure:

---
id: {id}
type: fragment
subtype: {type}
title: {first line or summary, max 80 chars}
created: {ISO8601 timestamp}
tags: [{tags}]
source:
  kind: chat
  ref: "claude-code /reify.capture"
---

## The {Type}

{content}

## Links

- belongs_to: [[loop_reify-studio]]

## Trail

- {date} {time} - captured via /reify.capture

7. Confirm Creation

Report:

Created: .imaginary/{category}/{filename}
Type: {type} (conviction: {level})

Examples

Input: /reify.capture What if we used wikilinks for all references? Output: Creates .imaginary/ideas/2026-01-09_1430_wikilinks-for-references.question.md

Input: /reify.capture I think the vault should be read-only --type principle Output: Creates .imaginary/ideas/2026-01-09_1430_vault-read-only.principle.md

Input: /reify.capture Meeting notes from standup --tags work,meetings Output: Creates .imaginary/captures/2026-01-09_1430_meeting-notes-standup.note.md

Important

• Always read .reify/types.json first for current type definitions
• Respect the conviction spectrum for idea types
• Use .imaginary/ as the base path (never write outside)
• Generate proper timestamps (not hardcoded)
• Keep captures atomic - one idea per file