Refiner critique and validation

Every proposed Harness mutation receives a second model critique before host validation. The critique can generalize an edit, route it elsewhere, or reject it when it copies task-specific facts, names, outlines, transient paths, or an isolated workflow.

Host validation

The host then checks the parts that must be deterministic:

• schema and content identity;
• target authority and safe paths;
• exact edit and release-base compatibility;
• activation and runtime validation; and
• atomic application or rollback.

Invalid decisions fail closed to no_action or a recorded validation failure. The system documents observable outcomes and receipts, not a model's private reasoning.

Next: Apply and rollback.