Summary
Mumega.com needs a new content collection for engineering/operational specifications, distinct from the existing blog/, labs/, pages/, products/, team/, tools/, topics/ collections.
The immediate driver: Lambda.16D — a 17-document control-plane specification series — needs to live on mumega.com per architectural register split (Hadi 2026-04-25).
Register split that motivates this
| Domain |
Content register |
Examples |
| fractalresonance.com |
Physics / academic |
FRC 100, 566, 821, 841 series |
| mumega.com |
Engineering / operational |
Lambda.16D series (this issue) |
| kayhermes.com |
Artistic / cultural |
Albums, book |
Lambda.16D's own master document (16D.000) explicitly disclaims physics framing and self-describes as a control-layer specification. None of the existing mumega.com collections fits its shape — it's not a blog post, not a lab/product, not a topic-page, not a static page. It's a 17-doc sequenced specification with internal cross-references.
What's needed
- A new content collection:
content/en/specs/ (or alternative name like control-plane/ or docs/ — happy to defer naming to substrate team)
- Zod schema in
src/content.config.ts for spec frontmatter — at minimum: title, series (e.g., Lambda.16D), series_order, status (canonical/draft/archived), date, description, prev/next for sequence navigation
- Route pages:
src/pages/specs/index.astro (series listing), src/pages/specs/[series]/index.astro (within a series), src/pages/specs/[series]/[slug].astro (individual spec)
- Optional: backlinks panel (similar to fractalresonance.com's paper structure)
What I'll do once this lands
Once the collection ships, I'll dispatch a subagent to migrate the 17 Lambda.16D files from /home/mumega/infra/shared-kb/frc/Lambda.16D/ into the new collection with standardized frontmatter, sequence ordering, and cross-references. That's user-side labor under River's existing storefront delegation.
Priority
Not urgent. Sprint 006 + GTM Phase 1 should close first. This is gardener-cadence work that lands cleanly when substrate has cycles.
Coordination
Filed by: river (queen, FRC gardener)
Substrate owner: kasra / loom / athena per architectural split
Hadi-directed: yes (2026-04-25)
Summary
Mumega.com needs a new content collection for engineering/operational specifications, distinct from the existing
blog/,labs/,pages/,products/,team/,tools/,topics/collections.The immediate driver: Lambda.16D — a 17-document control-plane specification series — needs to live on mumega.com per architectural register split (Hadi 2026-04-25).
Register split that motivates this
Lambda.16D's own master document (16D.000) explicitly disclaims physics framing and self-describes as a control-layer specification. None of the existing mumega.com collections fits its shape — it's not a blog post, not a lab/product, not a topic-page, not a static page. It's a 17-doc sequenced specification with internal cross-references.
What's needed
content/en/specs/(or alternative name likecontrol-plane/ordocs/— happy to defer naming to substrate team)src/content.config.tsfor spec frontmatter — at minimum:title,series(e.g.,Lambda.16D),series_order,status(canonical/draft/archived),date,description,prev/nextfor sequence navigationsrc/pages/specs/index.astro(series listing),src/pages/specs/[series]/index.astro(within a series),src/pages/specs/[series]/[slug].astro(individual spec)What I'll do once this lands
Once the collection ships, I'll dispatch a subagent to migrate the 17 Lambda.16D files from
/home/mumega/infra/shared-kb/frc/Lambda.16D/into the new collection with standardized frontmatter, sequence ordering, and cross-references. That's user-side labor under River's existing storefront delegation.Priority
Not urgent. Sprint 006 + GTM Phase 1 should close first. This is gardener-cadence work that lands cleanly when substrate has cycles.
Coordination
Filed by: river (queen, FRC gardener)
Substrate owner: kasra / loom / athena per architectural split
Hadi-directed: yes (2026-04-25)