create-meeting

# Create Meeting — Orchestrator

Creates structured meeting notes from **any source**: inline text, VTT files, inbox transcription notes, or triage proposals. Detects the input type and normalizes all paths to a common creation pipeline.

```
Input Detection
├── Path A: Inline text       → create transcription note → analyze → confirm → create meeting
├── Path B: VTT file          → convert VTT to note       → analyze → confirm → create meeting
├── Path C: Inbox .md file    → validate type              → analyze → confirm → create meeting
├── Path D: Proposal object   → skip analysis              → create meeting (triage handles confirm)
│
▼ All paths converge:
Create meeting in 04 Archives/Meetings/
Link + archive transcription to 04 Archives/Transcriptions/
Report result
```

---

## Phase 0 — Input Detection

Examine the input and determine which path to take. First match wins:

| Signal | Path | Next Step |
|--------|------|-----------|
| JSON object with `proposed_template: "meeting"` | **D** (Proposal) | Jump to Phase 4 |
| File path ending `.vtt` | **B** (VTT) | See [path-workflows.md](references/path-workflows.md) — Path B |
| File path ending `.md` or bare note name | **C** (Inbox note) | Phase 1C below |
| Everything else (free text, pasted content) | **A** (Inline text) | See [path-workflows.md](references/path-workflows.md) — Path A |
| No input at all | **Prompt** | Ask what meeting to create |

**No-input behavior:** Use `AskUserQuestion` — "What meeting should I create? Paste transcription text, provide a file path (.vtt or .md), or describe the meeting."

---

## Phase 1 — Normalize to Transcription Note

Each path produces the same output: a transcription note path in the vault that can be read and analyzed.

### Path A: Inline Text

Raw text (pasted transcription, clipboard content, natural language description).

Follow [path-workflows.md](references/path-workflows.md) — Path A to create a transcription note via the CLI, then continue to Phase 2.