How the Main Wiki Is Selected

Question (confidence: high)

Across sibling/domain-wiki architectures documented in this vault, how is one wiki elected “main” — and how does this vault’s own main/prompt split decide it?

Implications: this reframes “which wiki is primary” from a fixed label into an architectural choice, so the answer has to compare mechanisms, not just name a winner.

Short Answer (confidence: medium)

There is no universal election or automatic promotion mechanism across the ecosystem. Selection depends on the architecture: an active-wiki marker in krakiun-llmwiki, contextual routing with no fixed primary in Wyndo’s practitioner setup, broadest integrated ownership in Mycelium’s personal-to-team model, and an explicit governance-defined scope in this vault. This vault does not elect a main wiki dynamically — main is a manifest entry like any other, distinguished only by being declared first and by convention (root-level catalog/log files vs. nested ones for prompts).

Implications: “main” is a naming and governance choice, not a computed property. A third wiki added to this vault would not need to contest “main wiki” status — it just needs its own scope entry.

Comparison of Selection Mechanisms (confidence: medium)

System	Mechanism	Is there a “main”?	Evidence
krakiun-llmwiki	~/.llmwiki/wikis.json registry + current.txt active-wiki marker	Yes, but it’s a pointer, swappable via switch_wiki — not architecturally privileged	wiki/entities/krakiun-llmwiki.md
Wyndo (practitioner)	Contextual routing layer directs queries to the domain wiki that matches (YouTube / meetings / business)	No — wikis are peers, routing picks per-query, not a standing default	wiki/concepts/wyndo.md
Mycelium (ai-brain-starter)	Personal vault is the root; team vaults are scoped children with role/tenant boundaries	Yes — the personal vault is structurally parent, not just labeled first	wiki/entities/mycelium-hq-ai-brain-starter.md
This vault	wiki-scopes.json manifest; main scope = entities/concepts/comparisons/queries, prompts scope = prompts/**	Yes, by governance declaration and file placement (root index.md/log.md vs. nested prompts-index.md/prompts-log.md), not by any runtime selection logic	wiki-scopes.json, mcp/server.py

Implications: three distinct answers to “what makes a wiki main” — a mutable pointer (krakiun), no main at all (Wyndo), and structural parenthood (Mycelium) — plus this vault’s fourth answer: a static governance label. None of the four compute “main” from evidence or usage; all four are configured.

This Vault’s Mechanism, in Detail (confidence: high)

• main and prompts are both entries in wiki-scopes.json; MCP callers select main, prompts, or all, defaulting to all for most tools.
• No runtime switching between separate vaults exists — both scopes live in one vault, filtered by path inclusion (classify_wiki_path in scripts/wiki_scopes.py).
• The asymmetry that makes main feel privileged is structural, not logical: its catalog (index.md), log (log.md), and schema (_schema.md) sit at the repo root, while prompts’s equivalents sit nested inside wiki/prompts/. This is a placement convention from when prompts was split out as a second wiki, not a routing rule.

Implications: adding a third wiki does not require deciding which of the three is “main” — the label is inherited from being first, and a new scope can be declared without contesting it.

Open Question

Does any surveyed system compute “main” dynamically from query volume, page count, or recency, rather than configuring it? No evidence of this was found in krakiun, Wyndo, or Mycelium’s documented behavior — all three configure the relationship explicitly.

Related

• krakiun-llmwiki
• wyndo
• mycelium-hq-ai-brain-starter
• ecossistema-stacks-vs-nosso-vault

Sources

• wiki/entities/krakiun-llmwiki.md
• wiki/concepts/wyndo.md
• wiki/entities/mycelium-hq-ai-brain-starter.md
• wiki-scopes.json
• mcp/server.py