One-line description
The MMH Ecosystem Working Architecture & Methodology document is a “for collaborators” resume describing how the entire multi-project MMH ecosystem is held together — the two-layer KB/Notion architecture, the protocol layer, the Claude collaboration model — rather than a developmental narrative of what any single project has built. It is itself an instance of the method it describes.
Purpose / role in the ecosystem
MMH Core is the philosophical root of everything in the ecosystem — not a product, brand, or course, but the underlying operating system (consciousness framework, documentation standards, knowledge architecture) from which all other offerings derive, never marketed directly but always present. This document exists to demonstrate, to a potential collaborator capable of recognizing systems-level thinking, that philosophical depth and operational rigor are not in tension. Its intended reader self-selects: “the right collaborator will recognize the method… no further application is required.”
Current state (as of source resume, April 2026 — see staleness note)
As of the source document:
- Two-Layer KB Architecture established: Layer 1 (Claude Project KBs — strategic, stable reference, where Claude reasons from) and Layer 2 (Notion Hub — operational, always-current, what Brian acts on day to day), connected via a Hub Reference Document per project.
- KB Naming Protocol (differentiator-first titling) applied across all active projects.
- Map-Before-Build Principle established as a standing rule, following a named violation (an AWG methodology overview generated before the full ecosystem map existed).
- Cross-Project Connections discipline: every new ecosystem element answers Upstream/Downstream/Parallel questions before registration; Hub Reference Documents and the Active Threads database formalize this.
- Claude Collaboration Model: explicit division of labor governed by the Authorship & Prose Deference Protocol — Claude extracts and proposes, does not rewrite; Brian accepts, declines, or redirects. Confabulation named as a live, actively managed risk (specific past instances of Claude fabricating nonexistent artifacts are logged as protocol refinements).
- Infrastructure built: 50+ KB documents across active projects; 10+ active protocols; two-layer Notion Hub partially implemented; Hub Reference Documents live for MMH, Present Moment/continuum, and ccapi.
Staleness note (added 2026-06-26): Dated April 2026, explicitly self-described as predating subsequent developments. This session has independently confirmed several since: Quartz adopted as the public-facing knowledge graph platform; the Pre-Quartz/Quartz/Post-Quartz kumu pipeline architecture decided; the wwz Kumu Ecosystem Map built and populated; this Pre-Quartz Notion resume database itself created and now being populated.
Key relationships
MMH Core sits upstream of every other project in the ecosystem (toi, whmi, sgbh, edl, ddd, pp-awg, wwz, continuum, pmm) as their philosophical and architectural root. The document explicitly cites the TOI Continuum Master Document as proof of the cross-project-synthesis dynamic it describes. The Notion Hub / two-layer model this document describes is the direct architectural ancestor of the Pre-Quartz database this very resume now lives in.
Status note
This document is referenced on the kumu ecosystem map as “MMH Architecture & Methodology Doc” (element ID elem-IFsb1wiK), explicitly tagged as a methodology demonstration rather than a developmental narrative, and flagged as predating WWZ/Quartz/Kumu/NTN-00 — “treat as strong foundation, not current snapshot.” Migrated into the Pre-Quartz database 2026-06-26 from the original file (For_Collabs_MMH-Working-Architecture-Methodology-Resume.docx, dated April 2026). Per Brian: “maybe stale but functional.”
Migrated from Notion Pre-Quartz database (38c2a648-07c2-81f1-8aa1-cb2042fe4ac4).