Tracking issue from prds/IMPLEMENTATION_PLAN.md Task 4.6 + prds/shared-preamble.md §4 (walked 2026-05-28).
Required state
Per shared-preamble §4 ("Maintainer team of two minimum — each product has at least two people with publish rights and architectural context before public launch"), each of the three npm scopes must have at least two maintainers with publish rights:
@cubenest — shared substrate (rrweb-core)@tracelane — P1 product packages@peekdev — P2 product packages
Current state (2026-05-28)
```
$ npm view @cubenest/rrweb-core maintainers
harry-harish harry652k15@gmail.com
$ npm view @tracelane/core maintainers
harry-harish harry652k15@gmail.com
$ npm view @peekdev/cli maintainers
harry-harish harry652k15@gmail.com
```
Single point of failure for all three scopes. Acceptable for the alpha tier (the per-preamble §4 framing is "before public launch"), but blocks the Phase 5 public-launch gate.
Done when
For each scope, at least one additional npm publisher is added via npm access grant. Candidate sources (in rough preference order):
- Known collaborators willing to commit to release-cycle response (best — they already have architectural context).
- Public CFP via README's "Maintainers wanted" line + a
good first issue labelled tracking issue once the repo is public.
- Open call on dev-focused subreddits / HN once one of the products has visible traction.
Each invitee should also be added as an admin on the Cubenest GitHub org (per gate #8) to keep release access and source access in lockstep.
Intentional non-action acknowledgement
If a candidate isn't found before Phase 5, this gate intentionally stays unchecked. The wind-down plan in docs/SUSTAINABILITY.md documents graceful degradation. Leaving this gate unchecked is honest; pretending it's done would be theatre.
Source
prds/IMPLEMENTATION_PLAN.md Task 4.6prds/shared-preamble.md §4 "Side-project framing and sustainability — Mitigations" — second bulletprds/IMPLEMENTATION_PLAN.md Open items §6 ("Second-maintainer recruitment per preamble §4")
Tracking issue from
prds/IMPLEMENTATION_PLAN.mdTask 4.6 +prds/shared-preamble.md§4 (walked 2026-05-28).Required state
Per shared-preamble §4 ("Maintainer team of two minimum — each product has at least two people with publish rights and architectural context before public launch"), each of the three npm scopes must have at least two maintainers with publish rights:
@cubenest— shared substrate (rrweb-core)@tracelane— P1 product packages@peekdev— P2 product packagesCurrent state (2026-05-28)
```
$ npm view @cubenest/rrweb-core maintainers
harry-harish harry652k15@gmail.com
$ npm view @tracelane/core maintainers
harry-harish harry652k15@gmail.com
$ npm view @peekdev/cli maintainers
harry-harish harry652k15@gmail.com
```
Single point of failure for all three scopes. Acceptable for the alpha tier (the per-preamble §4 framing is "before public launch"), but blocks the Phase 5 public-launch gate.
Done when
For each scope, at least one additional npm publisher is added via
npm access grant. Candidate sources (in rough preference order):good first issuelabelled tracking issue once the repo is public.Each invitee should also be added as an admin on the Cubenest GitHub org (per gate #8) to keep release access and source access in lockstep.
Intentional non-action acknowledgement
If a candidate isn't found before Phase 5, this gate intentionally stays unchecked. The wind-down plan in
docs/SUSTAINABILITY.mddocuments graceful degradation. Leaving this gate unchecked is honest; pretending it's done would be theatre.Source
prds/IMPLEMENTATION_PLAN.mdTask 4.6prds/shared-preamble.md§4 "Side-project framing and sustainability — Mitigations" — second bulletprds/IMPLEMENTATION_PLAN.mdOpen items §6 ("Second-maintainer recruitment per preamble §4")