Module approval 

§16 Approvals show the change (owner decision, Nov 2): the configuration a generation transition that asks would apply. The core builds it from the derived facts, which come from the evaluated generations (§11), never from the proposal. planarian approve, the console and the notice show it; approve --json and IPC Pending.diff carry the same data. A diff that differs when the facts are re-derived at approval changes the token’s bound_to (the binding hashes the facts), so the approval does not apply and the change asks again.

Constants

EACH_UNAVAILABLE

Said when the facts carry no sensitivity per removed unit (a record journaled before removes_each), so each shows the change’s union.

UNAVAILABLE

Said when the evaluated generations could not be read, so the options shown are the requested override settings only.

Functions

diff

The diff a generation transition would apply; empty for any other. config_diff and removed (the units it would remove or stop, from removed) come from the derived facts.

first 🔒

Shown first: what a person most needs to see before approving.

removed

The removed units with their sensitivities: removes_each[i] for removes[i] when the two are the same length, otherwise the union removes_sensitivity for each, and false (the display says so).