Runtime Rules and Validation

These notes explain how ADK checks configuration changes, prevents stale updates, and stops plugin work that exceeds its approved limits.

The goal is to make failure explicit. Conflicting or outdated changes are rejected, configuration is resolved through controlled rules, and work that runs beyond its budget is ended with a reason that can be inspected later.

Validating Changes Against Current State

This service checks if proposed changes are still valid. It ensures the data used to plan those changes is correct. Brain owns this validation. Plugins report what they observed. Brain decides if those observations are still true. The service validates at component or state-slice level. Unrelated changes on the same entity do not invalidate each other. Brain never allows a plugin to change core assumptions directly. This service does not decide change order or schedule execution. It only checks if changes are still acceptable before commit.

Configuration Decision Process

This service selects the best configuration from all suggestions. It follows rules to decide which settings to use. Only one version is active at a time. Plugins cannot change settings directly. No changes override others based on arrival order.

Stopping Overused Plugins

This service stops plugins that use too much time or memory. It prevents problems without changing the main system state. The Brain service handles plugin budget termination. A plugin must not mutate Warehouse state directly during calculation. The service does not allow a plugin to change committed data after cancellation. It uses safe methods to stop plugins.