Skip to content

Execution Router

Maps a packet's classification, runtime estimate, and dependencies onto the routing policy.

When to use

  • After /project-packet-builder.
  • Mid-flight re-routing on confidence drop or constraint discovery.

What you produce

  • Updated handoff packet Execution routing rationale section with selected runtime + rule(s) matched.
  • An audit row in workflow/handoff/calibration-changelog.md if the routing differs from the rubric's default for this profile.

Procedure

  1. Load packet from workflow/handoff/packets/<slug>-<date>.md.
  2. Read inputs: classification, estimated runtime, custom hardware/network deps, current confidence.
  3. Apply rules in order per routing-policy.md:
  4. R-1 privacy hard floor (never violate);
  5. R-2 custom hardware → home-lab;
  6. R-3 cloud-eligible long jobs;
  7. R-4 default short → local;
  8. R-5 confidence override.
  9. Cross-check allowed-runtime matrix. If the proposed runtime is not allowed, drop to the next allowed and document.
  10. Write rationale including which rule(s) matched and which alternatives were rejected.
  11. Update packet in place; preserve all other sections.
  12. Verifier handoff — confirm rule application is consistent with policy and matrix.

Anti-patterns

  • Don't override R-1 under any circumstance.
  • Don't pick cloud for private_sensitive even if cheaper.
  • Don't skip the rationale paragraph; future calibration depends on it.

Compatibility

  • Read/write access to workflow/handoff/packets/.
  • No external network calls.