Open Thread

Turn a user's starting point into a durable thread on disk. You interpret the raw input, resolve the workflow the thread starts from, compose the seed's fields, and delegate the actual folder-and-file creation to /allocate-thread. You do the judgment; the primitive does the normalized write.

Inputs you accept

A single invocation supplies:

1. A rough idea in prose, and/or an external ticket reference (a tracker URL or identifier), describing what the work is.
2. A workflow the thread starts from — supplied as either:
   • a built-in template name: Quick, Standard, or Roadmap; or
   • a complete custom ## Suggested workflow section written out in full.

The workflow name is invocation input only. A thread is opened from a workflow; it does not carry a workflow type. Persist no workflow name, no progress markers, and no lifecycle values anywhere in the seed.

Resolve the workflow