Skip to content

19.3: §2.2 — CryptoZing LLC Articles filed #114

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
n8bar merged 1 commit into from
Jun 19, 2026
Merged

19.3: §2.2 — CryptoZing LLC Articles filed #114

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/strategies/19.3_LLC_FORMATION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,10 @@ Sequence is serial: CryptoZing's filing can't name CyberCreek as member until Cy

## 2. CryptoZing LLC (subsidiary) formation

CyberCreek (parent) is approved (Business ID 25076646), so this track can start now — it does not wait on CyberCreek's publication or affidavit.
CyberCreek (parent) is approved (Business ID 25076646). CryptoZing's Articles filed 2026-06-19, awaiting AZCC approval.

1. [x] Run AZCC name search for `CryptoZing LLC`; confirm availability. Available per AZCC Name Availability Search.
2. [ ] File Articles of Organization (azcc.gov) naming **CyberCreek LLC (Business ID 25076646) as sole member** (member-managed); statutory agent: self. Filing fee $50; expedite ~$35.
2. [x] File Articles of Organization (azcc.gov) naming **CyberCreek LLC (Business ID 25076646) as sole member** (member-managed); statutory agent: self. Filed 2026-06-19; awaiting AZCC approval.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Synchronize the active-phase rollups

Marking the CryptoZing Articles filing complete here leaves the canonical rollups stale: docs/PLAN.md:19 and docs/milestones/19_OB_HARDENING_OPS.md:25 still say the CryptoZing subsidiary filing is next. Since docs/DOC_ROLES.md makes PLAN/milestone docs the rollup sources and requires them to stay in sync, merging this status update as-is will point future work at a completed task instead of the new blocker, AZCC approval.

Useful? React with 👍 / 👎.

3. [ ] Receive Articles confirmation from AZCC. Save digital + physical copy. This is the name-lock the MS21 deploy swap depends on.
4. [ ] Publish the formation notice — 3 consecutive runs in a Mohave County AZCC-approved paper, within 60 days of filing; collect the affidavit after the final run. Reuse the parent's publication playbook (§1 item 4 — The Standard, legals@thestandardnewspaper.net, ~$48), but the published member is **CyberCreek LLC**, not an individual.
5. [ ] Apply for CryptoZing's EIN at irs.gov (free, instant) — its own EIN even though disregarded; banks expect it. Save the CP 575.
Expand Down
Loading