novox/hq
9
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request 'Design 47 G: the lead's answers A-284 to A-286' (#580) from design/47-G-lead-answers-12 into main

Browse Source
This commit was merged in pull request #580.
This commit is contained in:
mesh-tools
2026-11-12 14:17:58 +00:00
parent e1a9a0f2d2 41dd30fe43
commit e81a8d62a5
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md
+18
View File
@@ -396,3 +396,21 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-283** (A-277, ADR 0595; principle 7) The holder of the seat `mesh-broker` makes a template `state` bucket with
the `max-mib` its requirement declares, the default cap where none is declared, as the grants part does for a
state section; one cap rule for every state bucket.
- **A-284** (ADR 0573 §2, ADR 0500 §5; principles 5 and 7) In a group's check, a TypeScript member is built
against the group's own heads, as a Go member is: the check packs every `@novox/mesh-*` package a member's
merge changes (the SDK's `lib` artifact given its path, and a member's new packages such as another member's
contracts) by the form ADR 0500 §5 gives the SDK, and serves them to every member that imports them; the
latest published version is used only for a package the group does not change.
- **A-285** (A-284; principles 7 and 8) The fetch of a build step carries the group's packages as one list,
`group-packages` (beside `packages`, which stays the Go mesh packages' versions), each a package of a member at
its commit with `path`, its directory in that member (empty for the member's root); the single `package` field
and its tagged form go. The build module packs each and places it by
its `package.json` name in every member that names it, in place of the registry's. The SDK's `lib` artifact names
its paths (`package.json`, `package-lock.json`, `tsconfig.json`, `src`) in mesh-sdk's manifest, so the indexer
holds them and a change to them is a changed package.
- **A-286** (issue 1921; principle 3) The checker previews and judges every member whose fetch merged, whatever its
later steps ended with; only a member whose head does not merge, or whose fetch did not answer, stays
unpreviewed, and the check says which of the two. A check step that errors after its fetch merged (a level that
does not compile or generate) ends failed with its answer all the same: its fetch and the levels so far, beside
its error, so the checker previews from it. A failed test or a failed level never hides the manifest validator or
the composition.