4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	db86dd52c8	Take a provider's software-issued credential from the provider, sealed (hq issue 526, ADR 0305) ... A token a media server got from its vendor reached its consumers only as a value the mesh minted, which the server refused, or as a copy typed by hand. An offer may now say its software issues the credential; the new issued verb carries no value and asks the provider's tool, in the controller's own name, for the value sealed to one call, then seals it to every pair that does not hold it yet.	2026-10-12 01:07:16 +02:00
jochen	52af210e47	Derive data protection from a module's declared data (hq ADR 0233) ... A module's data section says what it keeps and how precious it is; the backup holder's lines, binding stickiness, retirement on unassign and D13's conditions follow from it, so issue 273's empty replacement is said and an unassigned module's data is remembered, not forgotten.	2026-10-06 16:47:49 +02:00
jochen	3b2adda1c8	Say a mark-only provider's retirement as mark only ... A provider that cannot disable keeps the consumer reachable until a person deletes it (hq ADR 0230); the listing and the approval say so instead of claiming access was disabled.	2026-10-06 14:41:15 +02:00
jochen	68009b16fe	Hear what providers retire, and let a person approve, reject and delete (hq ADR 0230) ... A provider now waits for a person before retiring more than three consumers or half of what it holds, and deletes only when asked. The controller is that person's way in: it keeps waiting and rejected sets as conditions, answers them with retire approve|reject, lists and deletes retired consumers through the provider's own tools on its machine, records each act in the hand-act log, and probes for anything retired longer than thirty days (D11).	2026-10-06 14:41:15 +02:00