One-line description
The Worldwide Zettelkasten (WWZ) is a civilizational-scale semantic knowledge commons — Buckminster Fuller’s World Game made real — that makes the invisible connections between human knowledge traditions visible and verifiable.
Purpose / role in the ecosystem
The WWZ’s philosophical foundation frames it as addressing a perception problem rather than a filing problem — the connections between distributed pieces of knowledge that would make them collectively useful are invisible, not missing, and structurally outside the perceptual field of anyone working within a single tradition. Structurally, every card is human-authored and every connection is AI-proposed and human-verified — the platform reveals, it does not generate. The atomic unit is the concept, not the document, and relationships are semantic rather than keyword-based. Within the broader mmh ecosystem, WWZ sits at the civilizational/platform tier — the culmination of the developmental continuum running from toi through whmi, sgbh, edl, to ddd, with mmh Core as its philosophical substrate.
Current state (updated 2026-06-26, post-Session 6 + MMH cross-project synthesis)
Session 6 (WWZ-ADDENDUM-S6, June 23). Quartz is no longer just “partially built” — the empty shell is deployed to Netlify under the MMH team account as continuum-at-mmh (confirmed June 19–21). The Pre-Quartz Notion resume-aggregation system (this document’s own database) is built and populated. Its downstream architecture is now decided: Pre-Quartz DB stays plain/link-free (source-of-record); Quartz performs the hyperlinking/backlink work natively; a separate Post-Quartz DB (named, not yet built) will hold Quartz’s link-enriched output and feed kumu node descriptions. A circular “Quartz output back into Pre-Quartz” design was explicitly considered and rejected.
The kumu ecosystem node-map work (CARRY-07) and the Glossary/resume-merge architecture (CARRY-08) remain open and in-progress — now informed by a new finding: the Kumu baseline JSON’s “Element Type” field is already populated with real values in places, contradicting the earlier assumption of “no node typing.”
Major resolution since S5 (2026-06-25): the open question of where ukbtp belongs on the ecosystem map is resolved via a two-role split — Infrastructure A (development substrate: naming, glossary, cross-reference, session continuity — real, active today) vs. Infrastructure B (the scaled WWZ/World Game platform — aspirational, not an active build). This split now also applies to WWZ’s own self-conception: a personal Luhmann-style ZK for one mind + AI is real and working today; WWZ-the-civilizational-platform is the aspirational layer. Per Brian: A and B are sequential, not parallel — B is not resourced unless/until A is workable; until then B exists deliberately as a fictional plot device in the pp-awg novel.
Caveat: toi’s collective-field spec is a thin, already-built slice of Infrastructure B living inside current A-track work (gated post-MVP on session count / CCAPI Build 3.9).
Key relationships
Parented philosophically by mmh Core. toi serves as a working instrument within WWZ — its quadrant-calibrated orientations are a candidate template for commons onboarding, and TOI’s collective-field spec is a live slice of the WWZ semantic-connection mechanic. sgbh functions as small-group preparation for commons participation generally. continuum is closely linked structurally — extraction and kumu work increasingly treat WWZ/Continuum as a paired unit. upc’s chapters remain the first candidate prototype corpus for concept-card extraction. Kieran — an outside collaborator and advisor — designed Interamnia and hosts briancrescenzo.com; the World Game / WWZ vision has not been disclosed to them by name.
Status note
Philosophically mature, technically nascent but progressing — the foundation and concept documents are settled (still DRAFT-labeled but stable); Quartz has cleared its first build/deploy milestone; the Notion resume pipeline is built with its full downstream architecture decided; the semantic-layer build and kumu mapping remain early or in-progress. Two structural decisions remain open: CARRY-07 (Kumu diff / node-typing / forking, complicated by the Element Type discrepancy) and CARRY-08 (spreadsheet architecture for merging Glossary and project-resume data into Kumu).
Migrated from Notion Pre-Quartz database (3892a648-07c2-819e-8c1f-e4642292e6eb).