Skip to content

Where does the autonomous-kickoff trigger layer live? #240

Description

@kyle-sexton

The single biggest 2→3 blocker: nothing turns an external signal (new issue, PR comment, cron, channel message) into a running agent. Decide the home and shape of the trigger layer: ci-workflows reusable (GitHub-event-driven, the vendor-converged label/assignment pattern)? a new plugin? the future runner repo? routines//schedule? Claude Tag channel monitoring? Evidence: explore-plugins-inventory.md gap 2→3 #1; RESEARCH-headless-agents.md invocation-adapter + queue seams; RESEARCH-product-surface.md routines/Tag maturity.

Metadata

Metadata

Assignees

Labels

needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.wayfind: designWayfind decision item: design-space or domain-model decision; human in the loop.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions