docs: ADRs 0003-0006 — Plan-2 portfolio decisions (MVP set, public-only, separate site, maintenance cap)

[millsmillsymills]

Context

The Plan-2 portfolio spec (Section 8 of docs/superpowers/specs/2026-05-14-millsymills-portfolio-content.md) gates moving its status from draft to accepted on four ADRs being filed:

• ADR-0003 — why these four MVP repos and not the held-back four
• ADR-0004 — public-only posture (no .github-private companion)
• ADR-0005 — millsymills.com stays separate from a GH Pages org site
• ADR-0006 — explicit maintenance budget cap (≤ 4 hours/month across all repos)

Acceptance

• Each ADR filed as a separate PR using the existing docs/adr/NNNN-slug.md shape (Status, Context, Decision, Consequences, Alternatives, References).
• All four ADRs Accepted or explicitly deferred before flipping the spec status to accepted.
• Plan-2 implementation plan (separate follow-up) references each accepted ADR.

Source

Follow-up from review of PR #37/#39 (Plan-2 portfolio spec).

[millsmillsymills]

🤖 Automated multi-agent issue review

Recommendation: keep-open · Priority: P2 · Effort: medium · Premise still valid: True

Review. Valid, well-specified docs task. The Plan-2 portfolio spec is still draft and Section 8 gates acceptance on four ADRs (0003-0006) that have not been written — docs/adr/ holds only 0001 and 0002, with no branches or PRs in progress. The work is unstarted, not stale or duplicated. It is a writing/decision task rather than a code change; effort is medium because four distinct ADRs each need the full Status/Context/Decision/Consequences/Alternatives/References shape, but the decisions themselves are already articulated in Section 8.

Suggested next step. Keep open. File four separate ADR PRs (docs/adr/0003-plan2-mvp-repo-set.md, 0004-public-only-posture.md, 0005-millsymills-com-separate.md, 0006-maintenance-budget-cap.md) following the 0001/0002 heading shape, seeding Context/Decision/Alternatives from Section 8 rationale. Once all four are merged or explicitly deferred, flip the spec status to accepted and have #48 reference each accepted ADR. Lower than P1 since it blocks only a spec status flip, not any live infrastructure.

Adversarial re-review (concurs). premise recheck: confirmed

The first review is correct on every load-bearing point: ADRs 0003-0006 do not exist on origin/main (only 0001/0002), the Plan-2 spec is still status 'draft', Section 8 gates the draft→accepted flip on those four ADRs verbatim, no branches or PRs are in flight for them, and follow-up #48 remains open. Keep-open at P2/medium effort stands; the only refinement is noting the 'ready-for-human' label makes this an owner-decision task and that ADRs may be explicitly deferred rather than written.

Open points raised:

• The review calls the issue 'actionable: true' without flagging that issue docs: ADRs 0003-0006 — Plan-2 portfolio decisions (MVP set, public-only, separate site, maintenance cap) #46 carries a 'ready-for-human' label, signaling the four decisions need owner judgment rather than fully autonomous agent execution. The decisions are pre-articulated in Section 8, so an agent can draft the ADR prose, but ratification is a human gate. Minor framing nuance, not a recommendation change.

_{Posted by a review + adversarial-review agent sweep across all open issues. No code was changed; no PRs were opened.}