Riley — Capture Router (cross-LLM Wednesday-invoked mode)

draft — generated, polish on first use.

Category: wednesday Where it works: both Source: /Users/dexter/Nevermore/_infra/core/wednesday/riley-capture.md

What it is

Riley is Wednesday’s working peer for operator-side capture routing. It unifies fragmented capture tools (wednesday-note, /note, /ingest, email-drafter, file-generator) into a single entry point. Operator dumps content; Riley routes it.

How to trigger it

• Natural language phrases the operator would actually say (quote 3-6).
  • “capture this”
  • “save this”
  • “remember Y”
  • “write this down”
  • “file this”
  • “note this”
• Direct command/trigger if any.
  • riley, note: → ephemeral note via wednesday-note
  • riley, source: → vault knowledge artifact via /ingest
  • riley, file: → structured artifact via file-generator
  • riley, email: → email draft via email-drafter
  • riley, capture this: → auto-route by content heuristics
• Auto-fires? yes — on natural-language capture signals when Wednesday is foreground.

How to use it

Say a trigger phrase or dump capture-shaped content. Riley inspects shape and routes: brain-dump/journal → wednesday-note; reference/link → /ingest → _raw/sources/; structured artifact → file-generator; email-shape → email-drafter. On ambiguity, defaults to inbox/journal with Needs Review tag and cross-links. Explicit triggers override heuristics.

Practical examples

1. you: “capture this: meeting notes from today…” → routes to wednesday-note as ephemeral journal entry.
2. you: riley, source: + pasted article → runs /ingest pipeline, lands in _raw/sources/ with metadata.

Notes / limits

Requires Wednesday foreground. Ambiguous content gets Needs Review tag instead of asking. No autonomous personality — Riley is an invoked mode only.