Repository navigation
MS19 +2wk for LLC lead time; bind PLAN Target to .ics + guard drift - #98
Merged
Merged
Conversation
LLC formation (CyberCreek parent → CryptoZing subsidiary, serial AZCC filing + publication) needs more runway than MS19's original close allowed. Push MS19 end out two weeks and slide the downstream milestones to keep the gaps intact. - MS19: ends 2026-07-04 → 2026-07-18 (start unchanged; underway) - MS20: 2026-07-03→07-16 becomes 2026-07-17→07-30 - MS21: 2026-07-15→07-28 becomes 2026-07-29→08-11 .ics is canonical; PLAN.md target column shifted +2wk to match. 19.3 watch-item updated to the new MS21 swap date (CryptoZing name-lock ≈7/20 still lands ahead of it). Carries an in-flight 19.3 AFCU edit. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
![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: f94002077f
ℹ️ 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".
| Sequence is serial: CryptoZing's filing can't name CyberCreek as member until CyberCreek exists. Rough path — CyberCreek formation + ~3-week publication (filed 2026-06-08, ≈6/29), then CryptoZing formation + ~3-week publication (≈7/20). | ||
|
|
||
| **Timing watch-item, not a blocker:** MS21 (deploy-time entity-name swap) is 2026-07-15. The swap needs the CryptoZing LLC name *locked* — i.e., AZCC Articles approved, which lands early in CryptoZing's window — not the full 3-week publication, which may finish after MS21 as a compliance step. The parallel-track design insulates MS19 regardless: Phase 5 drafts ToS/Privacy with placeholder names, and nothing in MS19 close waits on formation. If AZCC is slow approving CryptoZing's Articles, reconsider then; don't pre-slip. | ||
| **Timing watch-item, not a blocker:** MS21 (deploy-time entity-name swap) is 2026-07-29 (moved out two weeks alongside the rest of MS19 to absorb LLC formation lead time). CryptoZing formation + ~3-week publication now lands ≈7/20, comfortably ahead of the swap. The swap needs the CryptoZing LLC name *locked* — i.e., AZCC Articles approved, which lands early in CryptoZing's window — not the full 3-week publication, which may finish after MS21 as a compliance step. The parallel-track design insulates MS19 regardless: Phase 5 drafts ToS/Privacy with placeholder names, and nothing in MS19 close waits on formation. If AZCC is slow approving CryptoZing's Articles, reconsider then; don't pre-slip. |
There was a problem hiding this comment.
This updated timing still puts the LLC phase completion after the new MS19 close: the strategy says the serial CyberCreek → CryptoZing formation/publication path lands around 2026-07-20, while the canonical calendar in this commit closes MS19 on 2026-07-18 and the phase exit criteria still require CryptoZing publication to be complete. In that schedule, MS19 can reach its planned close before this required phase can finish, so either the MS19 window needs to move past ≈7/20 or publication needs to be explicitly moved out of MS19 exit criteria.
Useful? React with 👍 / 👎.
Root cause of the drift: milestone dates lived in two hand-edited places
(PLAN.md Target column and milestones.ics) with no rule binding them.
- Reconcile PLAN Targets to the .ics end dates: MS19 2026-07-18,
MS20 2026-07-30, MS21 2026-08-11 (narrative target updated too).
- Add MilestoneScheduleConsistencyTest asserting PLAN Target == .ics
DTEND per milestone. Tagged #[Group('local-only')].
- Exclude local-only from the GitHub PR Tests gate; it runs in the
local suite instead, so drift fails locally without gating every PR.
- Document the invariant + the local-only mechanism in AGENTS.md.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
n8bar
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
LLC formation (CyberCreek parent → CryptoZing subsidiary, serial AZCC filing + ~3-week publication each) needs more runway than MS19's original close allowed. This pushes MS19's end out two weeks, slides the downstream milestones, and — to stop the schedule files drifting apart again — binds the two date sources together and guards them.
Schedule shift (+2wk)
Drift fix
The drift's root cause: milestone dates lived in two hand-edited places (
milestones.icsand PLAN.md's Target column) with no rule binding them — they'd already diverged ~3 weeks before this change.milestones.icsis the single source of truth. PLAN.md's Target column now equals each milestone's.icsend date (DTEND): MS19 07-18, MS20 07-30, MS21 08-11.MilestoneScheduleConsistencyTestassertsTarget == DTENDper milestone. Tagged#[Group('local-only')].PR Testsgate (--exclude-group=local-only) — it runs in the local suite (sail artisan test) so drift fails locally, without gating every PR on a docs invariant.AGENTS.md.Files
docs/milestones.ics,docs/PLAN.md,docs/strategies/19.3_LLC_FORMATION.mdtests/Feature/Docs/MilestoneScheduleConsistencyTest.php(new).github/workflows/pr-tests.yml,AGENTS.md🤖 Generated with Claude Code