The canvas Start node says only 'an event or a task starts the run'. Show the real triggers: intake kinds routed to it (bug -> tdd, feature -> feasibility), capture bindings and schedules that name it, and workflows that call or hand off to it. Done when each shipped workflow's Start node lists its actual triggers.
Close reason
Start node lists the workflow's real triggers: issue routes (served as x-intake-routes), event bindings, playbooks that dispatch it, and workflows that call it, hand off to it (including a handoff whose target an agent result picks from a fixed list) or run it after approval. Schedules only drive chat jobs, so they do not appear. Found that routing overrides are never applied: archie-core-ctcr.
Imported from beads archie-core-t19m.4 · GitHub #1433 · type task · priority P2 · created 2026-10-04 · closed 2026-10-04
The canvas Start node says only 'an event or a task starts the run'. Show the real triggers: intake kinds routed to it (bug -> tdd, feature -> feasibility), capture bindings and schedules that name it, and workflows that call or hand off to it. Done when each shipped workflow's Start node lists its actual triggers.
### Close reason
Start node lists the workflow's real triggers: issue routes (served as x-intake-routes), event bindings, playbooks that dispatch it, and workflows that call it, hand off to it (including a handoff whose target an agent result picks from a fixed list) or run it after approval. Schedules only drive chat jobs, so they do not appear. Found that routing overrides are never applied: archie-core-ctcr.
---
_Imported from beads `archie-core-t19m.4` · GitHub #1433 · type task · priority P2 · created 2026-10-04 · closed 2026-10-04_
sam
added the mediumtask labels 2026-10-27 13:36:17 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The canvas Start node says only 'an event or a task starts the run'. Show the real triggers: intake kinds routed to it (bug -> tdd, feature -> feasibility), capture bindings and schedules that name it, and workflows that call or hand off to it. Done when each shipped workflow's Start node lists its actual triggers.
Close reason
Start node lists the workflow's real triggers: issue routes (served as x-intake-routes), event bindings, playbooks that dispatch it, and workflows that call it, hand off to it (including a handoff whose target an agent result picks from a fixed list) or run it after approval. Schedules only drive chat jobs, so they do not appear. Found that routing overrides are never applied: archie-core-ctcr.
Imported from beads
archie-core-t19m.4· GitHub #1433 · type task · priority P2 · created 2026-10-04 · closed 2026-10-04