Chapter 2 of 6 · Architecture

Foundry evaluations and release quality gates

Runtime assurance 4 hours in a non-production POC

Chapter 2 of 6

Architecture at a glance#

Approved and candidate versions use the same data and evaluators before release thresholds return PASS or BLOCK.

The runner sends the same synthetic cases to two immutable agent versions. Foundry keeps detailed results. The release gate reads payload-free aggregates, applies the repository policy, and returns PASS or BLOCK to the approved release platform.

Design choices and tradeoffs#

DecisionChosen approachTradeoff
Test dataVersioned synthetic golden setA changed use case or risk needs a new baseline
Gate structureSeparate final-answer, tool-process, and safety layersSeveral owners must maintain explicit floors
Protected materialBlocking in East US 2The run stops if that supported path is unavailable
Authoritative stateFoundry keeps detail; the release platform keeps gate and promotion stateThe gate reads external result records

Architecture guidance#

Session 09

Foundry evaluations and release quality gates slide deck