Skip to content

Routing Policy

Deterministic rules for choosing the execution runtime once a project has a Go decision.

Inputs

  • Data classification (private_sensitive / internal / low_sensitive).
  • Estimated runtime duration.
  • Custom hardware/network dependencies.
  • First-pass confidence (post-handoff feedback).
  • Cost budget (optional).

Rules (apply in order; first match wins)

  1. R-1: Privacy hard floor. If data_classification == private_sensitive, allowed runtimes are local or home-lab only. Cloud is denied.
  2. R-2: Custom hardware/network. If the work requires custom infra (LAN-only services, GPU profiles, hardware in the lab), prefer home-lab.
  3. R-3: Cloud-eligible long jobs. If data_classification != private_sensitive AND estimated runtime > 30 minutes AND no custom hardware, prefer cloud.
  4. R-4: Default short. Otherwise prefer local.
  5. R-5: Confidence override. After first pass, if confidence < threshold (default 0.6), route to local with human-assisted execution regardless of prior choice.

Allowed-runtime matrix

data_class local home-lab cloud
private_sensitive yes yes no
internal yes yes yes (with audit)
low_sensitive yes yes yes

Documentation requirements

The packet's "Execution routing rationale" section must record:

  • Selected runtime.
  • Which rule(s) matched.
  • Alternatives considered and why rejected.

Re-routing

A run may be re-routed mid-flight only if:

  • A new constraint appears (e.g., the job tries to fetch data that turned out to be private_sensitive).
  • The original runtime fails repeatedly (R-5).

Re-routing is logged and counted against rework metric.