diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index bb91c106..02994006 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -670,3 +670,12 @@ Where two preparers disagreed, the chosen one is named. At this clean state the hand act stands in once: the builder's first view asked again (15:00). A build step asked before the builder's view took in that revision's event, and a passed pipeline whose mover released nothing, are findings for H2 (§756, §754). P3 (failure must be loud), P7. +- **H-A-142 (an event said with a further part is declared with it, 15:12)** Met in the fix of the vault's stale view + of the licence bindings: the licence manager says each change as `binding.changed.` (G A-134), but its + `emits` names `binding.changed` alone and the vault's and claude-code's `consumes` did too, so the bus handed neither a + single change, in silence, since the clean state (the vault's consumer last delivered 08:42). A manifest declares an + event as it is said: a `consumes` of `claude-licence-manager.binding.changed.*` (as `git.merge-called.*` is written), + and an `emits` of `binding.changed.*` on the manager, so the grants part grants the publish of the subject with its + further part as it does for a seat's events. Whether the manifest validator accepts `*` in `emits` is read, not + assumed: refused, that is a finding for H2 and the manager's `emits` stays until it is built. A seat event gets its + further part from its seat definition; a module event only from its manifest. P9, P3.