EnderMio

Use when a formed task needs durable human-approved meaning, completion obligations, evidence claims, non-goals, or live/destructive authority boundaries.

Use when maintaining or resuming an existing v1 requirements.control.json run; new runs use forming-cybernetic-commitments.

Use when an existing v1 run must compile its reviewed control chain into runtime.control.json.

Use when optional local workflow guidance or legacy v1 workflow compatibility needs diagnosis.

Use when an existing v1 control chain requires design.control.json; v2 strategies remain agent-owned.

Use when cybernetic routing is requested but user input is pre-task intent or role-ambiguous context: confusion, dissatisfaction, risk sense, observed symptoms, failed attempts, method preference, process distrust, source material, declared current state, or unclear requested transformation.

Use when resuming an existing v1 run that already requires pre-goal control-chain compilation.

Use when an existing v1 requirements/design/goal/plan chain needs compatibility review.

Use when handling Cybernetics Desk maintenance work, including direct operator sessions, no executable Desk actions, needs_human tickets, WorkPackage-bounded code changes, required tests, local repair evidence, or Desk process gaps.

Use when a developer needs to handle Redmine issues or feedback through the Redmine UI/API, configure Redmine API access, split public comments from private engineering notes, list assigned issues, add comments or private notes, change statuses, search, attachments, calendar/gantt views, or ADX Project feedback workflow.