R09 · VariantHub on explicit request

How to use this route

A request for variants alone does not select VariantHub. Use the requested count, distinct structural hypotheses and comparable content and states. Selecting a variant and promoting it into shared code are separate decisions. Missing infrastructure requires a separate setup mandate.

Stages: explore, refine. Work surface: VariantHub. Involvement and budget come from the run's dials (shared rules).

Map

Read from top to bottom. Labeled arrows show conditions; dashed arrows exist only in the stages they name; loops represent repairs within the budget. Instructions for each node appear below.

Loading diagram…

Mermaid source

flowchart TD
  n_p(["Explicit VariantHub request"])
  n_ready{"Is infrastructure ready?"}
  n_blocked(["Request separate setup"])
  n_b["Build code alternatives"]
  n_variants["Keep alternatives isolated"]
  n_smoke["Check opening and comparison"]
  n_human["Ask the user to select"]
  n_promote{"Is promotion authorized?"}
  n_done(["Deliver the alternatives"])
  n_production(["Hand off to verified integration"])
  n_gate{"Is comparison working and verified?"}
  n_fix["Repair the comparison"]
  n_stop(["Report unverified comparison"])
  n_p --> n_ready
  n_ready -->|"No"| n_blocked
  n_ready -->|"Yes"| n_b
  n_b --> n_variants
  n_variants --> n_smoke
  n_human --> n_promote
  n_promote -->|"No"| n_done
  n_promote -->|"Yes, authorized"| n_production
  n_smoke --> n_gate
  n_gate -->|"Yes"| n_human
  n_gate -->|"No, within budget"| n_fix
  n_fix -->|"Recheck"| n_smoke
  n_gate -->|"Budget exhausted or blocked"| n_stop

Input and outcome

Input: Explicit VariantHub request and ready infrastructure.
Outcome: Comparable alternatives and any authorized promotion.

Work limits

Route cap: at most 4 new delegations, with 2 agents in parallel; at most 1 repair batch. The effective budget is the lower of this cap and the budget dial; the stage sets the fix passes per artifact. Shared rules.