Reviews and Engines

Review surfaces collect decisions the system cannot make on a person's behalf: approving a gated action, accepting a proposal, resolving a conflict, or judging evidence. The review record should preserve who decided, what was shown, and which artifact changed.

Engines and managed routines execute connected work. Treat definition, activation, run state, and receipts as separate objects. Paused or waiting work should resume from its durable step rather than restart and duplicate earlier outputs.

If a local plugin view and connected view disagree, check synchronization and freshness before changing the underlying code or spec.