PLAN: refresh Current block; slip MS19 + cascade MS20/MS21#110
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8770f289e1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | [ ] | 19 | Open Beta Hardening & Ops | Open beta hardening before mainnet cutover: notification coverage audit; auth/password policy hardening (419-to-login redirect, session expiry logout); LLC formation (entity, EIN, bank account, operating agreement); legal layer (ToS, Privacy Policy, disclaimers, monetization-neutral copy review, UI placement); content promises reconciliation; contributor docs refresh; 2FA (email baseline, opportunistic TOTP). | 2026-08-01 | [`docs/milestones/19_OB_HARDENING_OPS.md`](milestones/19_OB_HARDENING_OPS.md) | | ||
| | [ ] | 20 | Mainnet Cutover Preparation | Define and rehearse env flips, wallet validation, mail sanity checks, and backout steps for mainnet cutover. | 2026-08-13 | [`docs/milestones/20_MAINNET_CUTOVER_PREP.md`](milestones/20_MAINNET_CUTOVER_PREP.md) | | ||
| | [ ] | 21 | CryptoZing.app Deployment (Open Beta) | Deploy the open beta under `cryptozing.app`, replace the GitHub Pages placeholder at `/` with the live app landing page without breaking the SEO baseline established in MS15, remove temporary mail aliasing, and complete rollout verification. | 2026-08-25 | [`docs/milestones/21_OB_DEPLOYMENT.md`](milestones/21_OB_DEPLOYMENT.md) | |
There was a problem hiding this comment.
When changing these milestone targets, this commit also needs a docs/CHANGELOG.log entry; docs/DOC_ROLES.md requires CHANGELOG.log to be updated alongside canonical docs when scope or doc structure shifts. Without that entry, the schedule slip to MS19/MS20/MS21 is only visible by inspecting the dashboard/calendar diff, so future planning/history readers miss the recorded scope change.
Useful? React with 👍 / 👎.
| - **MS19 - Open Beta Hardening & Ops** — in progress; Phases 1, 2, and 4 complete. Active phase: **Phase 3 (LLC formation)** — CyberCreek LLC (parent) approved 2026-06-17; CryptoZing subsidiary filing next. Phases 5–8 (Legal Layer, Content Promises Reconciliation, Contributor Docs, 2FA) pending. | ||
| - Status: `active` | ||
| - Next action: MS19 Phase 1 — notification coverage verification (Claude). | ||
| - Next action: MS19 Phase 3 — complete LLC formation (parent publication, EINs, business bank account, CryptoZing subsidiary). Phase 5 (Legal Layer) runs as a parallel track. |
There was a problem hiding this comment.
This next-action line pulls strategy-level LLC tasks (parent publication, EINs, business bank account, CryptoZing subsidiary) into PLAN.md, but docs/DOC_ROLES.md says PLAN.md next actions must stay milestone-level and not include phase or strategy-detail steps. In this context the detailed checklist already belongs in the MS19/19.3 docs, so keeping it here creates a second checklist surface that can drift during Phase 3.
Useful? React with 👍 / 👎.
Current block pointed at MS19 Phase 1 (closed); update to Phase 3 active (LLC), Phases 1/2/4 done, 5–8 pending, and refresh the last-updated stamp. Slip MS19 end 7/18 -> 8/01 to fit full LLC formation (subsidiary publication runs into August), and cascade the tail off the old overlapping windows into clean gaps: MS20 8/03–8/13, MS21 8/15–8/25 (open beta ~2 weeks later). Sync .ics, PLAN targets + release-target line, and the 19.3 timing note. Local consistency test passes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
n8bar
force-pushed
the
claude/plan-refresh-ms19-slip
branch
from
8770f28 to
e040e25
Compare
1 participant
Two fixes from the program-altitude Harvey readout.
1. PLAN Current block (was 6 weeks stale)
Dashboard claimed Active = MS19 Phase 1 / Next action = Phase 1 — but Phases 1, 2, 4 are closed and Phase 3 (LLC) is active. Updated the Current block + the
_Last updated_stamp to reflect reality.2. Slip MS19, cascade the tail (chosen over descope)
MS19's 7/18 target couldn't fit full LLC formation (CryptoZing subsidiary publication runs into August), and the old windows overlapped (MS20 started 7/17, before MS19's 7/18 end). New schedule:
Overlaps replaced with clean gaps; open beta slips ~2 weeks. Synced across
.ics, PLAN targets + the release-target line, and the19.3timing note.MilestoneScheduleConsistencyTestpasses locally (PLAN targets == .ics DTEND).Docs-only.
🤖 Generated with Claude Code