Task Management

Handle operational requests over One Horizon work by choosing the right lookup, create, update, and comment path.

One Horizon work model

Initiative: roadmap-first planned work. Use for work that moves the product plan forward, usually spans multiple steps or days, and should roll up to goals, products, companies, components, or team reporting. Treat initiatives as reviewable specs for product work.
Bug: unplanned defect, regression, or broken behavior that should be tracked as issue intake and worked like a fix stream rather than planned roadmap expansion.
Todo: simple personal follow-up. Use for small, private, owner-level tasks that do not need to show up as roadmap structure for the wider team. A completed implementation slice can also be written back as a completed Todo linked to an initiative.
Ongoing work: recurring owner-driven work without a defined end date, such as code reviews, routine support, or inbox maintenance, when the workspace uses that concept. This is not the same as roadmap work.

If the user describes planned product work that should tie back to the roadmap, default to an initiative.
If the user describes something broken, failing, regressed, or needing a fix, default to a bug.
If the user describes recurring operational work like code reviews, support rotation, or ongoing triage, treat it as ongoing work when the workspace already uses that concept.
If the user describes a small personal reminder or one-off follow-up that only they need to see, default to a Todo.
If implementation work was done in service of an initiative and the user wants write-back, a completed Todo linked to that initiative is an acceptable delivery note.
If the user just says "create a task" without enough signal, classify in this order: initiative for roadmap work, bug for defects, ongoing for recurring operational work, Todo for private follow-up.