mesh-catalog

Files

T

jschoubben 86342c4399 GIT12: the forge module's package registry checks a publish against the builder's reservation, asked by the package's name

The holder asks the seat mesh-builds' verb reserved with the publish's name and version in place of builder_versions, and stores
only a version reserved for an artifact of the publish's digest; the manifest invokes the verb and takes no builder package.

Builds: design 47 G §381, §478, §504

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

2026-11-11 14:04:56 +01:00

agent-teams

G-catalog-B 8: the retire removes only the teams the npm pair provisioner made

2026-11-04 18:13:44 +01:00

agent-token

CAT-G1, G2: the forge's Go bundle serves both package seats' verbs into its package registry, for both packages

2026-11-04 13:43:59 +01:00

forge

GIT1, GIT2, GIT3, GIT10: the forge module serves the seat git's verbs and says its events, retires its acting tools, follows the catalog half

2026-11-11 11:31:24 +01:00

forge-account-provider

No client names the holder of the seat mesh-provisioner: each reader keeps its own constant, held to its manifest (ADR 0625 section 4, issue 1966)