metadata-protocol: the item door judges a package member by member, so the package's own member order decides admission #32901

Activity

1. objectstack-fleet

   added

   priority:p2Medium: important, M3Medium: important, M3

   pm:queueReady for the PM dispatch loopReady for the PM dispatch loop

   domain:serverDomain lane — seat card indexed by label:pm:seatDomain lane — seat card indexed by label:pm:seat

   on Nov 12, 2026
2. objectstack-fleet

   added a parent issue on Nov 12, 2026

   • metadata: overlaySlotBinding's other readers (bundleMembersHeldBy, getEnvironmentScopedItem) bind a pair row without reading overrides.package (ADR-0150 D4) #32408
3. objectstack-fleet commented on Nov 13, 2026

   

   objectstack-fleetBot

   on Nov 13, 2026

   ContributorAuthor

   More actions

   triage#1 · hotlong · session_01Q4EjjMnyLqJdzuktEmRPXH

   Path: none

   Triage: first-touch audit (pre-labeled card) · p2 confirmed · 2026-11-13T08:12Z

   ⛔ Not a claim; the claim (if any) is unchanged.

   • Line: installers of an App member shipping a locale beside an undeclared row · item door vs package door · rare · read
   • Why: Admission differs by member order, a rare arrangement; the sibling metadata-protocol: the registry's bare slot keeps only the row hydrated last when a pair row and a package-less row of the same member are both stored #32900 was kept at p2 with the maintainer's agreement, and I am unsure, so p2 kept.
   • Rule: the card was filed already carrying a grade and state and had no triage audit; this is that audit, under the adopted grading rules (pm-dispatch(grading) + NORTH-STAR: grade in a fixed order — impact, reach discount, one raise, release window — with decidable tests for security boundary, core task, workaround and "a real user can hit" #32997).

   ---

   Generated by Claude Code
4. objectstack-fleet

   added

   lease:E1

   pm:dispatchedDispatched to a dev agent by /pm-dispatchDispatched to a dev agent by /pm-dispatch

   and removed

   pm:queueReady for the PM dispatch loopReady for the PM dispatch loop

   on Nov 14, 2026
5. objectstack-fleet

   assigned

   os-elon-musk

   on Nov 14, 2026
6. objectstack-fleet commented on Nov 14, 2026

   

   objectstack-fleetBot

   on Nov 14, 2026

   ContributorAuthor

   More actions

   domain:server#5 · os-elon-musk · session_016WV4cy1y7UNVbT2QAdmgdn

   Measured on main e540baf (area E1, pilot #33059) · 2026-11-14T15:05Z. Held until the E1 registry-set PR (#33127 lead) lands: the fix is in the same file.

   Shape: X is a module of App A and ships welcome en-US. W (another namespace, depends on X) ships de-DE (L) and en-US.

   door	member order	answer
   item door	L, then en-US	422 BareNameConflict naming X
   item door	en-US, then L	admitted
   package door	either order	admitted

   The same four answers hold with an undeclared pair row of L, with a row declared for X, and with no row at all, so the pair row is not needed for the split.

   Where: packages/objectql/src/registry.ts, SchemaRegistry#registerItem (the bare-name item-seam gate's incoming holding reads only registered members plus the arriving one) and SchemaRegistry#bareNameHoldersOtherThan (once the first member is admitted, later members skip judgement).

   Planned fix (after the registry set lands): the item door's incoming holding also counts the installed manifest's declared members, so both doors agree whenever the manifest declares them. A package whose manifest declares no members (members registered one at a time) stays order-dependent at the item door; that residual is stated and pinned as a CONTROL.