6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9379e9a96a	Keep one list of credential forms in the catalogue, so no reader of a plan refuses a form another writes (issue 774) ... Second meeting of the credential-form list kind: the provisioner client's own copy lacked "none" and refused every plan naming it, as the controller's had before. Thorough: one list in mesh-sdk, catalogue.CredentialForms and IsCredentialForm; provisions' forms are now the catalogue's constants.	2026-10-30 16:03:14 +01:00
jschoubben	58a83249c8	Give a provision the vault itself provides no credential beside it, since its offer is the value (issue 1954, ADR 0570 clause 6)	2026-10-29 22:53:15 +01:00
jschoubben	6b8c694381	Make every offer say its credential's form, pair or none where it names no own secret or issuer, and read no default, so the vault never mints a login for a provider that takes none (issue 1954, ADR 0570)	2026-10-29 22:47:32 +01:00
jschoubben	f701db0516	Key a provision's credential as the vault's own provision secret-<provision> and say what a provision depends on, so a provider waits for its credential and its own requirements (issue 1954, ADR 0570 clauses 3, 6)	2026-10-29 22:43:56 +01:00
jschoubben	66ff33dbd3	Name a provision's credential as the vault's own names it, read each node's provisions by its engine, and give mesh-config's held values their layout in the sdk, so the vault, the engine and the composition checks read one form (issue 1954, issue 1953 D7)	2026-10-29 22:39:29 +01:00
jschoubben	4a967933b3	Lay out a provision as a key of mesh-provisioner holding a reference and never a value, and a plan as a key of its own, so the holder, the vault, the clients and the providers read one record (issue 1954 L6-P2, ADR 0570 clauses 1, 2)	2026-10-29 22:32:15 +01:00