Amanuel2x

dyflo

Repository-agnostic hybrid dev loop. Routes an incoming ticket (GitHub Issue, Jira, or any adapter) into one of two lanes by label: an AUTONOMOUS lane (small/mundane work → the dyflo-watcher runs it headless, one-ticket-one-PR-exit) or a HITL lane (big/risky work → a research stage computes blast radius and picks an architecture pattern, emits a draft ADR you approve, then TRIP plans/implements/releases with human gates). Use when the user says "dyflo", "assign this ticket", "research this issue before I plan it", "route this ticket", "set up the hybrid agent loop", "run the research stage", or wants the launcher that turns on assign-or-do-it-yourself. The research stage is the core: it fuses Graphify blast radius + the vendored pattern catalog and MAY conclude "no pattern needed" — downgrading a small ticket straight to the autonomous lane with zero ceremony. Non-goals: it does not merge PRs, does not schedule cron/launchd, and never escalates a small ticket into unattended execution — the research stage onl