Open Thread

Turn a user's starting point into a durable thread on disk. You interpret the raw input, 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 a rough idea in prose, and/or an external ticket reference (a tracker URL or identifier), describing what the work is. The seed records why the work exists: persist no recipe name, no progress markers, and no lifecycle values anywhere in it.

Ticket input

When the invocation carries a ticket reference, read references/supplied-ticket.md and follow it before composing any field — it covers reading the ticket through the right tracker reference, the fallback when the tracker cannot be reached, and the check for a thread that already exists on that ticket.

Compose the seed fields

From the user's input (and, when a ticket is linked, its content), assemble the fields /allocate-thread needs: