Issues: The Backlog Primitive

A real backlog shape, not a flattened notification list

An Issue carries the fields you'd expect from an actual project-management tool: status (backlog, todo, in_progress, in_review, blocked, done, cancelled), priority, labels, an optional link to the workflow it concerns, an optional assignee agent, and even a schedule — a due time and a recurrence cron for work that repeats. This is also the surface the Instinct Engine's Sentinel behavior files into automatically when a production run fails, so a broken automation becomes a real, trackable, deduplicated backlog item instead of a line buried in a run log nobody's watching.

An agent-assigned issue can dispatch on its own

An Issue doesn't have to be tied to a workflow to be actionable — one assigned directly to an agent (with no linked workflow at all) can still dispatch that agent to work it, provided the runtime adapter manager is wired in. The backlog isn't just a place work gets logged; it's a place work can actually get picked up from.

Continue