Hi! I work at Entire. We actually have another feature that we announced called Trails which indicates Confidence, Risk, Drift of code changes to give the maintainer more confidence that the code is high quality.

Each of those signals -- confidence, risk, drift are determined by a workflow file that the maintainer can create.

And trails continuously evaluate every time a change is made.

So that's exactly what we're doing..a gate that checks and weighs and measure everything before it gets committed.

The point of us capturing the agent sessions is so we can do more things with it..like adding "gates" that verify quality!

Who would trust the classifiers, though? I would not.

A team of professionals will trust a gateway they built themselves -- by an AI, most likely, as that is boring work -- that works for their organisation and whatever weird quirks and house styles they have. In a year or two when things are a bit more stabilised that'll be dozens of subagents each testing a little thing each in isolation plus a bevvy of software that looks for antipatterns in addition to running tests and linters and what have you. It'll be tested against the ground truth specification and not the boring crap in the middle.

At no point will anybody's session matter. Results count; nothing more.