Wiki Arcana is the ecosystem's knowledge orchestration layer. It stores knowledge as a graph plus vectors, classifies it into a hierarchy of knowledge spaces, and enforces a Jedi-Archive-style access model (public, archivist, council, hidden holocron) through Auth Arcana OIDC — no local logins. It does not replace Scrutator or Long-Term Memory: Scrutator's BGE-M3 engine mints embeddings and serves search, LTM keeps episodic memory, and Wiki Arcana binds them together behind a single API and an MCP server for agents. Phase 1 delivers the research corpus, the storage abstraction and access registry, a self-contained public landing at arcanada.wiki, and the API/MCP skeleton — knowledge content and links come next.
Capabilities
- Graph + vector storage layer with a knowledge-space classifier (a hierarchy of spaces)
- Jedi-Archive-style RBAC — public / archivist / council / hidden holocron — via Auth Arcana OIDC (deny-wins, no local auth)
- Single API + MCP server (Streamable HTTP) as the agent entry point
- Delegates embeddings and search to Scrutator (BGE-M3); episodic memory stays in LTM — it orchestrates, it does not duplicate
- Storage abstraction with engine-pure ports — the graph+vector engine is chosen by consilium, not locked in Phase 1
- Ecosystem-native — identity via Auth Arcana, retrieval via Scrutator, memory via LTM
Current autonomy level
Weakest link
Phase 1 — the research corpus, two public repos with self-hosted CI, the live arcanada.wiki landing, the relational access/space registry, and the API/MCP skeleton are in place. Knowledge content, graph/vector activation, and cross-links are deliberately deferred to later tasks, and the API is not yet publicly exposed.
Roadmap to L4
- Phase 1 → Phase 2 — activate the graph + vector engine (per consilium) behind the storage ports and benchmark it before any content build.
- Phase 2 → Phase 3 — ingest knowledge, wire Scrutator-delegated search + LTM memory, and populate knowledge-space cross-links.
- Phase 3 → Phase 4 — full RBAC enforcement across the API and MCP, per-user sharing and delegation, agent-facing retrieval at scale.
Links
Next step
Review the current build and its development plan
BUILDING means active development, not a promise of public availability. Use the current capabilities and roadmap above as the reference.
Review the path to the target level