operational-router

name	operational-router
description	Tier 4 operational workflow router for Godot execution loops: validation, tests, project audits, file-safe refactors, and editor-tool delivery.

Operational Router

Use When

• Tier 1-3 knowledge selection is done and execution workflow must be chosen.

Outcomes

• One or more execution runbooks are chosen for deterministic implementation.
• Validation gates are explicit before task completion.
• Operational steps are reusable across projects without game-specific assumptions.

Required Rules

• Enter this router only after Tier 1-3 choices are explicit.
• Choose the smallest workflow set that covers implementation and validation.
• Always include at least one validation-oriented runbook for non-trivial changes.
• Keep workflow selection independent of specific game mechanics.

Workflow

1. Determine execution need: implementation, refactor safety, validation, or delivery.
2. Map need to one or more operational skills.
3. Sequence selected runbooks from safest to highest-cost checks.
4. Execute and record evidence from required validation steps.
5. Feed failures back to Tier 3 contract or Tier 1 architecture as needed.

Validation

• Selected runbooks include explicit verification criteria for task scope.
• Workflow order surfaces parse/type/runtime failures early.
• Similar tasks route to the same operational workflow set.

Failure Modes

• Starting execution without Tier 3 contract clarity causes invalid test loops.
• Selecting too many runbooks creates duplicate or conflicting steps.
• Validation is deferred to the end, hiding early structural defects.

Local Doc Anchors

• godot-docs/tutorials/editor/command_line_tutorial.rst
• godot-docs/tutorials/scripting/debug/overview_of_debugging_tools.rst