Servus.
Wikipedia built one encyclopedia. Global Wiki Tree proposes many community-owned branches sharing one confidence-scored trunk — a living knowledge commons, not another silo.
Global Wiki Tree — vision-stage · "Forming the Movement"
Your notes, your team's wiki, your community's docs — barely talking.
Two forces are converging. Knowledge management stays fragmented across incompatible tools. And the rise of AI has made trustworthy, curated data more valuable than ever — models trained on messy, unverified scrapes produce messy, unverified outputs.
Directional framing — this section describes the thesis, not a shipped product.
The proposed loop — not yet built.
Any kind of data enters, community editors shape and verify it, and clean interoperable files come out for whatever tool you prefer. This is the spec; nothing here runs today.
Import
Structured, semi-structured, or raw data — APIs, uploads, scrapers.
Curate
Domain-expert communities shape, verify, and connect knowledge.
Export
Clean files for Tana, Logseq, Obsidian, or any tool — also via API.
Every claim would carry provenance and a confidence level — strong shown by default publicly, adjustable for organizations that need to see tentative connections too.
Free commons. Paid tooling for professional use.
For communities
Free public knowledge hosting, community curation tools, open export in all formats, strong-confidence defaults.
- Free or near-free platform access
- The tree grows by having more public data from more communities
For organizations
Adjustable confidence thresholds, private branches and access control, priority API access, custom export pipelines.
- Standard open-core / freemium engine
- Self-contained — doesn't depend on another holon's revenue to survive
Like Wikipedia in 2000 — the seed is planted, it waits for its six roots.
The technology is the easy part. The hard part is building the culture of collaborative knowledge curation at scale. Six roles would form the initial root system — currently none are filled.
The Architect
Knowledge graphs, ontologies, interoperability at scale.
The Community Builder
Rallies early-adopter communities and the culture of open curation.
The Data Steward
Data quality, provenance tracking, confidence scoring.
The Tool Maker
Import/export pipelines, API design, integrations.
The Advocate
Articulates why knowledge commons matter; attracts institutional partners.
The Sustainer
Designs the model that keeps the commons funded without compromising it.
Idea and draft. No prototype yet.
Already real
- Live holon page — vision, business model, and the six-role movement framing fully articulated.
- A named interop link to SilkNotes — the local-first note-operating system it could export to and import from.
Honestly missing
- No code repo found anywhere on this machine — no importer, no exporter, no confidence-scoring logic.
- Zero of the six roles filled, by the page's own admission.
- No pilot community — the narrow import→curate→export loop hasn't been walked through even manually, for one data type.
Help prove the loop — one data type, one pilot.
The most valuable next increment isn't "build the platform" — it's proving the loop manually for one narrow data type. If you're an Architect, a Tool Maker, or a community that wants to be the first pilot, this is the moment to start the conversation.
Jakob Possert-Bienzle · EvoBioSys · Vienna