ADR 0262: a preference has a default in its manifest, and the operator's own value has none #216

Merged

mesh-admin merged 5 commits from feat/setting-defaults into main 2026-10-08 16:18:54 +00:00

Conversation 1 Commits 5 Files Changed 8

+381 -4

5 Commits

Author	SHA1	Message	Date
jochen	6a9bc3f4b3	ADR 0262: say what a left-out module loses, and how far an entry's unknown key is read ... The record claimed a left-out module kept what the machine holds for it and that an entry's unknown key was read like a top-level one; neither is true of the merged controller.	2026-10-08 17:55:38 +02:00
jochen	f09c9befdf	ADR 0262: a module with a field the controller does not know is left out and raised, never read silently ... Dropping an unknown key would run a module without something its manifest says. Also name the check by what a key is about, narrow the listing to one machine, and say how to roll back below this record.	2026-10-08 17:55:04 +02:00
jochen	de7aca4fa6	ADR 0262: one listing of every preference, and research 037 surveying the literals to convert ... The operator asked for one place that lists every module's preferences and each machine's value, and for a list of the values the catalogues hard-code that should become preferences.	2026-10-08 17:55:04 +02:00
jochen	0e5a5e2085	ADR 0262: record the lenient read of stored manifests and the marked defaults layer ... A stored manifest read strictly would fail the whole catalogue after a controller rollback, and a node called default would lose its layer. Also scope the default, retire tunable, and list the new checks.	2026-10-08 17:55:04 +02:00
jochen	417db4d837	ADR 0262: let a preference carry a default so a running module can gain a setting ... A ${setting:} nothing set failed composition, and settings refused a key no file asked for yet, so no order of changes could add a setting to a running module. A manifest may now default a preference; the operator's own value still has none.	2026-10-08 17:55:04 +02:00