Pixi Vault Knowledge Base
updated: 2026-07-07
Covers
Vault architecture, Wiki Compiler Maps, AgentWikis compatibility, namespace compiler logic, source/output repo boundaries, and pixi-wiki publication model.
Not Covered
General agent workflow behavior unless it changes vault/compiler architecture; project-specific implementation details unless they affect the namespace compiler.
Current As Of
2026-07-07 — Pixi Wiki hardening and feature delivery recorded: CI, browser-verified deploys, human search, Updates, rendering correctness, mobile navigation, SEO, shared CSS, MCP performance, and route contract tests are now part of the public artifact.
Vault architecture, Wiki Compiler Maps, AgentWikis compatibility, namespace compiler logic, source/output repo boundaries, and pixi-wiki publication model.
Structure
raw/— raw Markdown provenance mirror for agents and source inspection.wiki/— synthesized knowledge pages: concepts, entities, summaries, and syntheses.- Schema and maintenance rules: see
CLAUDE.md.
Usage
- Add new sources: update canonical source notes in
pixi-vault, then compile into this namespace. - Ask questions: agents read this wiki and cite raw/source paths.
- Publish: regenerate
pixi-wiki, run tests, then live-verify raw and HTML routes.
Pixi Vault¶
Namespace for the privatepixi-vaultsource system and its generatedpixi-wikipublic publishing surface.
Canonical Source Roots¶
Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.mdWiki Compiler Maps/Namespace Wiki Compiler Map.md
Crosslinks¶
- agent-workflows
- local-ai-infrastructure
- eval-trace
Public Output Contract¶
When published to pixi-wiki, this namespace should expose:
/raw/pixi-vault/README.md
/raw/pixi-vault/wiki/index.md
/wiki/pixi-vault/README.md
/wiki/pixi-vault/wiki/index.mdMaintenance¶
- Edit canonical source notes first.
- Use
Wiki Compiler Maps/Namespace Wiki Compiler Map.mdfor routing decisions. - Do not compile Daily Notes directly unless promoted or verified.