Default-deny is the control

Side effects are the product in operator systems — and the risk. A write to the system of record, an export of a restricted bundle, a decline on a chargeback row: these are not chat completions. They are actions. Actions require authority.

Default-deny means a tool does not run because it was available. It runs because an approval or a named capability record allows it, under a schema, with a side-effect policy, leaving a receipt. The model does not initiate an export. The model does not get a toolbox because the demo looked busy.

When a run has to stop for a human, the trace goes with it. Fluency is not the log. V4 already receipts what was read. V5 extends that into write receipts and run receipts — in progress, not GA.

Eval is the other half of the control. Groundedness, citation coverage, tool-policy, a frozen regression set. If the action cannot be evaluated, it is not in production. We will stop before we ship a costume.

This is not a philosophy page. It is the control we will write into an engagement. Operators who already know they need that bar send an engineering brief. Everyone else starts a HIVE Bootcamp.