Capture the parts that move
Pin the model route, harness version, instruction digests, skill releases, tool schemas, permission policy, workflow, checks, and runtime image, then create a new candidate whenever one of those components changes.
Product / Stack Releases
What is a coding-agent Stack Release?
Two teams can call the same model and get very different results because the harness, instructions, tools, permissions, context policy, and checks all shape the work. That difference matters. Fullbeam records the complete setup as a Stack Release before you test it on private repository work.
What the release gate checks
The evidence behind the decision
Each result stays tied to the Stack Release, workload, repository state, and coverage that produced it. If evidence is missing, the gap remains visible in the release call.
Keep unknowns visible
Closed providers do not expose every version or internal change, so Fullbeam records the provider route, timestamp, and available identity while leaving the missing parts unknown. No guesswork.
Separate the plan from the run
The release describes what your team approved. Runtime evidence records the models, tools, plugins, permissions, and subagents seen during execution, including fallbacks that changed who did the work.
Leave a trail for every default
A Platform owner can trace a promotion, restriction, pause, or replacement back to its repository states, qualification policy, exclusions, and observed outcomes.
Bring us the next stack change
Every approved default points back to the exact Stack Release, repository states, evidence set, qualification policy, and workload decision that put it there.
One current releaseOne candidatePrivate repository workA workload-level decision