Question
What does focusing a cluster mean in the cockpit — what is rendered, what is conversable, and how does a cluster tile relate to its member repo tiles?
Type
grilling (HITL, /grill-with-docs)
Context
Per operator ruling D2: repo-only v1, and no cockpit-local cluster grouping invented ahead of the registry.
The blocker is upstream and real. ns:cluster-<name>@<semver>#P<n> is [SCHEMA ITERATION 6] — DESIGNED in decisions/northstar/offsite/schema-evolution-log.md. There is no cluster node in decisions/northstar/schema.md, none in scripts/lib/northstar-fm.mjs, none in lint — and no grouping above a repo in the cockpit's fleet tiles (phase is a flat tag, not a hierarchy).
The topology is already ruled (operator-verbatim, offsite/confirmed/cluster-golf.md): cluster members are REPOS, uniformly — a thin membership/coordination overlay, not a ladder parent. Two-mean rollup unchanged; members report into l2-ojfbot#P1/#P2 like any L1.
Three clusters declared today: cluster-golf (formatted block landed 2026-07-30, 7 members incl. 4 seeds), cluster-gameworld (declared 2026-07-02, block never authored), cluster-f1 (card 11b pre-drafted, quick-confirm pending). The operator flagged 2026-08-01 that the pattern is increasingly load-bearing.
Also open once the schema exists: do seeds (pull-condition members with no registry entry, hence no resolvable path) render at all?
Blocked by
core's cluster-tier schema build (RFQ-004) — committed in offsite/contract-amendment-2026-07-27.md, scoped in offsite/rfi-response-nsr-001-2026-07-27.md:441. Not a wayfinder ticket; a core delivery. This ticket cannot be worked until it lands.
Resolution (filled at close)
—
Question
What does focusing a cluster mean in the cockpit — what is rendered, what is conversable, and how does a cluster tile relate to its member repo tiles?
Type
grilling (HITL, /grill-with-docs)
Context
Per operator ruling D2: repo-only v1, and no cockpit-local cluster grouping invented ahead of the registry.
The blocker is upstream and real.
ns:cluster-<name>@<semver>#P<n>is[SCHEMA ITERATION 6] — DESIGNEDindecisions/northstar/offsite/schema-evolution-log.md. There is no cluster node indecisions/northstar/schema.md, none inscripts/lib/northstar-fm.mjs, none in lint — and no grouping above a repo in the cockpit's fleet tiles (phaseis a flat tag, not a hierarchy).The topology is already ruled (operator-verbatim,
offsite/confirmed/cluster-golf.md): cluster members are REPOS, uniformly — a thin membership/coordination overlay, not a ladder parent. Two-mean rollup unchanged; members report intol2-ojfbot#P1/#P2like any L1.Three clusters declared today: cluster-golf (formatted block landed 2026-07-30, 7 members incl. 4 seeds), cluster-gameworld (declared 2026-07-02, block never authored), cluster-f1 (card 11b pre-drafted, quick-confirm pending). The operator flagged 2026-08-01 that the pattern is increasingly load-bearing.
Also open once the schema exists: do seeds (pull-condition members with no registry entry, hence no resolvable path) render at all?
Blocked by
core's cluster-tier schema build (RFQ-004) — committed in
offsite/contract-amendment-2026-07-27.md, scoped inoffsite/rfi-response-nsr-001-2026-07-27.md:441. Not a wayfinder ticket; a core delivery. This ticket cannot be worked until it lands.Resolution (filled at close)
—