alpha-jwc Wired In as a Firm-Private Submodule
Alpha JWC Ventures becomes the sixth firm wired into the orchestrator under the established io/<firm>/ private-submodule pattern. This is a structural addition only — registering the submodule path in .gitmodules and pinning the initial commit. The firm-private content (brand config, customized 9-section 7Cs outline, first-deal setup) lives in the alpha-jwc-secure repo and is documented in its own changelog there, per the CLAUDE.md scope rule.
Michael StatonMusic Editoraugmented with Claude Code (Opus 4.7)new(io): add alpha-jwc as private submodule
Adds Alpha JWC Ventures as a private submodule at io/alpha-jwc,
pointing at lossless-group/alpha-jwc-secure. Matches the established
firm-private submodule pattern used by alpha-partners, hypernova,
avalanche, dark-matter, emerge, and humain.
Structural change only:
* .gitmodules — new [submodule "io/alpha-jwc"] block
* io/alpha-jwc — new submodule entry pinned at the initial firm-data sha
The firm's content (brand config, customized 9-section 7Cs outline
with Risks + Diligence front-loaded, the first deal's codified
Sources.md and memo outputs) lives in alpha-jwc-secure and is
documented in that submodule's own changelog. Per the CLAUDE.md
"Changelog scope" rule, this entry intentionally does not narrate
what's in that sha.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>Changelog — 2026-06-08_01
What this entry is
A two-line structural change at the orchestrator level: register a new
firm-private submodule, pin its initial commit. The submodule path is
io/alpha-jwc; the upstream is lossless-group/alpha-jwc-secure. It
matches the pattern every other firm-private submodule under io/
follows (alpha-partners, hypernova, avalanche, dark-matter,
emerge, humain). Alpha JWC is now the sixth firm wired in this way.
What this entry deliberately is NOT
A description of the firm's brand config, its customized outline, the
deals already set up against it, the deck-input handling, the codified
Sources.md, or any memo content. All of that lives in the
alpha-jwc-secure private repo and is documented in that submodule's
own changelog/ — not here. The CLAUDE.md scope rule introduced in
the next entry makes this explicit; this entry is the first one
written in deliberate respect of it.
What the pattern looks like
The full procedure (brand acquisition, firm-directory scaffolding,
outline selection, first deal setup, optional private-repo split) is
documented as the setup-new-firm agent-skill that landed in the
2026-06-14_01 entry. The next firm onboarded should follow that
skill rather than improvising — Alpha JWC's onboarding surfaced
enough failure modes (primary-color heuristic wrong, deck analyst
misreading DocSend watermarks as the company name, firm-geography
leaking into company-specific risk prose, citation enrichment
fabricating URLs even in codified mode) that consolidating the
procedure was overdue.
What's next
Alpha JWC's first deal (Panthalassa Series B) is in motion inside the submodule; bumps to
io/alpha-jwcadvance the pinned sha as the firm's work lands, but stay as quietbump(submodule):entries per the CLAUDE.md rule.The
setup-new-firmskill (see2026-06-14_01) is the reusable output of this onboarding.
References
.gitmodules— the new submodule registration2026-06-14_01.md§setup-new-firm — the procedure this onboarding producedapps/memopop-orchestrator/CLAUDE.md§"Changelog scope" — why this entry is intentionally short