6.7 KiB
Routing Boundaries
Read only when the entrypoint leaves a routing choice unresolved.
| Boundary | Decision |
|---|---|
| Many easy tasks | Partition independent bounded Luna batches across available capacity; size batches to keep coordination and acceptance useful. Volume alone does not justify Astra. |
| Ordinary cross-file bug | GPT-6.1 Sol; file count alone does not justify Astra. |
| Small patch with settled semantics and deterministic acceptance | GPT-6 Luna medium/high if failure is contained; parent checks the diff and behavior. |
| Small patch changes authentication or a shared schema contract | Parent settles shared decisions; bounded investigation may use Sol. Small size is not evidence of low ambiguity. |
| Cheap Luna attempts require repeated parent rewrites | Choose Sol directly next time for this shape; count total accepted-task cost. |
| Difficult accounting discrepancy | Sol reasoning; parent owns the semantic decision. |
| Coupled architecture across runtimes and tools | Consider Astra directly; keep shared decisions serial. |
| Difficult choice would constrain many downstream slices | Consider an early bounded Astra analysis; gate dependent work on the parent's accepted contract. |
| High-impact stable change needs independent counterexamples | Consider Astra review when depth adds value; give original requirements and a fixed artifact, not a preferred verdict. |
| Expert makes testable progress over several rounds | Continue the scoped topic with incremental evidence; do not impose a one-call quota or repeat unchanged questions. |
| Missing credential or inaccessible source | Resolve the evidence/environment gap; model escalation cannot supply access. |
| Astra advertised only for task creation | Child support remains unproven; do not create another user task as a workaround. |
| Named role fixes model/effort | Accept its supported binding or choose an overridable role; never attach prohibited fork overrides. |
| Repository requires Sol parent | A Sol child cannot replace that owner; preserve the gate until an authorized supported change. |
| Accepted output, unknown child model | Accept only after normal parent checks; do not attribute the result to the requested model. |
Legacy and mixed hosts
Check each route independently. The API catalog does not update an existing session's tool schema.
| Unavailable preferred route | Supported compatibility choice |
|---|---|
| GPT-6 Luna | GPT-5.6 Luna low/medium for fixed collection/checks, high for settled transformations or patches; otherwise Sol or local work. |
| GPT-6.1 Sol for implementation/investigation/complex analysis | GPT-6 Sol medium/high, or GPT-5.6 Sol medium/high when that is the adequate exposed route; otherwise local work. |
| GPT-6 Astra | An adequate supported Sol route or local work; disclose a capability gap if neither suffices. |
These are work-shape fallbacks, not capability equivalence claims or a mandatory sequence of model attempts. Terra is retired from recommended routes and automatic fallbacks; do not select it merely because a legacy host exposes it. Preserve an explicit user-pinned model or existing configuration until an authorized change. If a required model/version is unavailable, report the exact gap before dependent dispatch; a GPT-6 Sol pin must not silently become GPT-6.1 Sol. Never invent gpt-6-terra. A mixed host may use GPT-6.1 Sol and GPT-5.6 Luna, or GPT-6 Sol when 6.1 is absent, without reverting every route. Record the exact requested ID and fallback reason. Unknown observed identity stays unknown.
Production Artifact Collection
- GPT-6 Luna: use known hosts/endpoints/paths and fixed selectors to read or download actual reports, JSON, logs or job outputs; verify size/hash, parseability, required fields and specified counts. GPT-6.1 Sol: locate the current output through bounded read-only investigation, diagnose retrieval failures, or correlate logs and artifacts by run/version. Do not launch both by default; use Sol only when discovery or diagnosis is needed. Apply the compatibility table when these routes are unavailable.
- Contract: name the production source, expected run/date/version, allowed read operations, bounded time/range/volume, local destination and acceptance checks. Reuse approved access and applicable server tools. Keep secrets out of prompts/receipts. Remote access stays read-only; explicitly allow local artifact writes even for a collector role.
- Evidence: preserve the actual downloaded artifact and record source, retrieval time/timezone, producer run/version and generation time when exposed, local path, bytes/hash and check results. Unknown provenance stays unknown. Verify the expected run/freshness; mtime or successful download alone does not prove current output. Use immutable run identifiers where possible; detect/retry boundedly if files change during collection.
- No fixture, cache or old snapshot may stand in for requested live output. If the current artifact is missing, stale, inconsistent or inaccessible, report that gap. Do not trigger jobs, regenerate artifacts, restart services, change permissions/configuration or deploy as part of collection; return such remediation to the parent under existing authorization.
- P only for independent reads and disjoint local outputs; shared mutable SSH sessions or a changing multi-file output set require coordination/serialization. Parent reviews provenance, relevant artifact content and check results before semantic/final acceptance. Fetching is evidence collection, not production acceptance.
Cost Calibration
Minimize total task usage: parent input/reasoning/output + all child input/reasoning/output + retries and reintegration. A smaller model can reduce price without reducing token count; additional agents can increase both. Do not assume pricing ratios or invent token measurements.
Use actual usage counters when exposed. Otherwise report observable proxies (characters loaded, number of children, full-history forks, repeated reads/checks) with their limitations. Record only available data needed for a routing decision; do not add telemetry work to every small task. Compare similar accepted tasks before changing defaults.
If context dominates, narrow inputs and avoid full-history forks. If output dominates, bound logs and returns. If reasoning/retries dominate, clarify acceptance and choose adequate capability/effort directly. Preserve required tests and material findings.
Official model positioning checked 2026-10-06: GPT-6.1 Sol, Codex models. See model economics for the dated API price basis. The route table is an engineering starting strategy, not a measured task-cost ranking. Runtime tool schemas remain the source for actual child availability.