The infrastructure layer that keeps
Agents running reliably
Experiments, design observation, model routing, data supply, and tool generation—five infrastructure components give IC design Agents replayable experiments, explainable state, routable models, and evolvable tools.
# create experiment with immutable context $ agent-runtime start --branch exp-042 [runtime] reserve budget {cpu:4h, mem:16G} [idb ] snapshot design state @ commit 7a3f [context] bind candidate → $lineage/branch-042 → experiment ready, agents can CAS commit
Five infrastructure components
Core capabilities Agents need—from experiments to tool evolution.
Agent Runtime
Experiment engine: transactions, branches, budgets, and decision records. Each Experiment has immutable context; each Candidate has its own branch lineage. Supports multi-dimensional reserve/debit/refund budgets and CAS commit to iDB.
Learn more OBSERVER · D1 · Wave 1Design Observer
An explainable lens on design state. Summarize, diff, explain, and root-cause analysis. Agents use Observer to understand current design shape and what the last change affected.
Learn more ROUTER · D1 · Wave 1Model Router
Model registration, calibration, OOD detection, and routing (F0–F4). Manages applicability, calibration curves, and error correlation. Falls back to deterministic engines on OOD.
Learn more ORACLE · D0/DRAFT · Wave 0Data Oracle
Paired data, active learning, lineage. Provides {design state → gold result} pairs with full provenance.
Learn more FACTORY · D0/DRAFT · Wave 4Honey Tool Factory
Controlled tool generation and promotion gates via coverage/gate/regression.
Learn moreAbove infrastructure: cross-cutting services
Agent infrastructure supports cross-tool services—planning, verification, knowledge, memory, and bridging.