Automation should earn authority, then prove what it did.

Knox separates a useful plan from permission to act. The control model is built around exact authority, provider-level verification, durable evidence, and safe recovery.

The five-part control contract

Trigger truthShow what started the run and the data Knox received.
Decision truthRecord the rules, context, and version that produced the decision.
Action truthConfirm the consequence through the authoritative provider, not a hopeful log line.
Control truthKeep approval scope, permissions, expiry, replay protection, and recovery visible.
Audit truthTie the evidence to the exact automation version and preserve it for review.

These are Knox product requirements. Capability earns public maturity only after the full contract is demonstrated through a real Knox session and real provider destination.