Training an AI circuit-design agent requires more than a collection of finished designs. It needs records of what was proposed, what the simulator measured, why a change was tried and how the design recovered when it failed. This paper describes how that evidence is collected for analog circuit optimisation.
The collection spans complete optimisation episodes on SKY130 circuits, preserving measurements, target-level scores and the model's hypotheses alongside each action. A two-round process distinguishes original design ambitions from targets that a given circuit has actually demonstrated it can reach. The result is an account of how training data can remain auditable: readers can follow a design trajectory and inspect the basis for its reported progress rather than relying on a final score alone.
Research context
The corpus and measured outcomes concern simulator runs on the documented SKY130 circuit collection. Finalised targets can differ from the original datasheet targets; convergence against those targets is not proof that every original specification was met or that a design has been validated in silicon.