Hiro development journal

Measured Codex task router activated

2026.07.23 at 15:21:41 America/Los_Angeles Published Machine-readable JSON

Executive summary

Implemented a separate Hiro development-task router that selects among local Qwen, Luna Low, Terra Medium, Sol Medium, and explicitly approved Sol High without changing Hiro's conversational router.

The policy permits at most one automatic escalation, and only an objective process or operator-supplied validation failure can trigger it. High-consequence work has a Sol capability floor, while Sol High requires explicit approval.

Installed and verified the official standalone Codex CLI because Windows denied child-process execution of the desktop application's packaged binary. A real read-only Luna Low probe completed successfully and returned the exact expected response.

Work completed

Deterministic routing policy

Completed

Added five explicit route profiles with model and reasoning settings, risk floors, task-kind handling, operator overrides, and a one-escalation ceiling.
Restricted local handling to bounded, low-risk, non-mutating transformations. Normal implementation defaults to Terra Medium; ambiguous, cross-system, security-related, or high-consequence work routes to Sol Medium.
Sol High cannot be selected automatically without an explicit allow flag.

Audited Codex dispatch

Completed

Added a noninteractive Codex dispatcher using JSONL events, saved ChatGPT authentication, explicit model and reasoning overrides, least-required sandbox selection, and resumable thread IDs.
Task text is passed through stdin rather than interpolated into a shell command. The child process uses an argument array with shell execution disabled.
Added an append-only local summary ledger and per-task artifacts containing route, duration, validation status, thread identity, and reported input, cached-input, output, and reasoning tokens.

Windows launcher and CLI readiness

Completed

Added a PowerShell launcher that normalizes the known Path/PATH collision from machine and user path values before starting Hiro's pinned Python runtime.
Installed Codex CLI 0.145.0 through the official OpenAI standalone installer and configured Hiro to use that executable.
Kept the router opt-in through the dedicated launcher so existing assistant chat behavior is unchanged.

Decisions and reasoning

Do not merge development-task dispatch into core/router.py; conversational inference and repository-changing Codex work have different safety and evidence requirements.
Optimize total task usage rather than the apparent cost of the first attempt. A cheap failure followed by repeated repository discovery is not a saving.
Resume a prior Codex thread on objective failure instead of starting a context-free replacement attempt.
Do not use target percentages for route distribution until real task outcomes provide evidence.

Validation and evidence

Check	Status	Result
Focused router and operational regression suite	passed	27 tests passed in 3.05 seconds, including route floors, Sol High authorization, prompt/command separation, Path normalization, one-escalation resume behavior, output-budget behavior, payload handling, and operational boundaries.
Python compilation	passed	All five new Python router modules compiled successfully.
Launcher child-process startup	passed	The normalized PowerShell launcher started Hiro's pinned Python runtime, returned the five-route self-check, and produced a Luna Low dry-run decision.
Real Codex routed probe	passed	A read-only Luna Low task completed in 3.719 seconds with exit code 0 and returned ROUTER_OK. Codex reported 13,498 input tokens, 9,984 cached input tokens, 27 output tokens, and 17 reasoning-output tokens.

Current state

Hiro now has an operational, opt-in development-task routing command documented in docs/HIRO_CODEX_ROUTER.md.
The official standalone Codex CLI is installed and the router's executable setting points to it.
No scheduled evaluation, production connector, assistant service, live calendar, email, task data, or user-facing chat route was changed.

Next steps

Route a representative sample of real bounded Hiro development tasks and compare first-pass success, total tokens, cached tokens, duration, validation, and correction rates by route.
Keep route thresholds fixed during the initial sample so the evidence is comparable.
After sufficient varied tasks, adjust route floors only where measured total task cost and validated success justify the change.
Consider a private dashboard view of aggregate router metrics without exposing prompts, full model output, credentials, or sensitive task artifacts.