# Pixi Vault Namespace Instructions This is a compiled namespace source under `pixi-vault/wikis/pixi-vault/`. ## Rules - Follow the root `Wiki Compiler Maps/Namespace Wiki Compiler Map.md`. - Treat `Knowledge/` and `Projects/` as canonical authoring sources. - Treat Daily Notes as scratch chronology, not direct compiled content. - Keep this namespace scoped to: Vault architecture, Wiki Compiler Maps, AgentWikis compatibility, namespace compiler logic, source/output repo boundaries, and pixi-wiki publication model. - Do not widen scope silently; propose a namespace promotion/routing update first. - Update `wiki/index.md` and `wiki/log.md` whenever compiled pages are added. --- title: Pixi Vault created: 2026-06-16 updated: 2026-07-07 type: namespace-overview status: compiled category: knowledge-systems namespace: pixi-vault confidence: medium --- # Pixi Vault > Namespace for the private `pixi-vault` source system and its generated `pixi-wiki` public publishing surface. ## Scope ### 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 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. ## Canonical Source Roots - `Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.md` - `Wiki Compiler Maps/Namespace Wiki Compiler Map.md` ## Crosslinks - [[../agent-workflows/README|agent-workflows]] - [[../local-ai-infrastructure/README|local-ai-infrastructure]] - [[../eval-trace/README|eval-trace]] ## Public Output Contract When published to `pixi-wiki`, this namespace should expose: ```text /raw/pixi-vault/README.md /raw/pixi-vault/wiki/index.md /wiki/pixi-vault/README.md /wiki/pixi-vault/wiki/index.md ``` ## Maintenance - Edit canonical source notes first. - Use `Wiki Compiler Maps/Namespace Wiki Compiler Map.md` for routing decisions. - Do not compile Daily Notes directly unless promoted or verified. --- title: Wiki Compiler Map and Source Classes created: 2026-06-16 updated: 2026-06-16 type: concept status: compiled namespace: pixi-vault tags: [pixi-vault, wiki-compiler-map, source-of-truth, namespace-routing] sources: - Wiki Compiler Maps/Namespace Wiki Compiler Map.md - Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.md confidence: high --- # Wiki Compiler Map and Source Classes A **Wiki Compiler Map** is an internal routing artifact that maps authoring-source notes into compiled AgentWikis namespaces. It replaces the old MOC mental model when the job is source-to-namespace routing. ## Why this exists The vault has many useful authoring surfaces: `Knowledge/`, `Projects/`, scratch chronology, generated reports, and project artifacts. Future agents need a durable contract for deciding which of those are canonical enough to compile into public/agent-facing wiki pages. ## Source classes ### Canonical Canonical sources can directly feed compiled namespace pages after normal review. Examples include `Knowledge/concepts/*.md`, `Projects//Index.md`, PRDs, ADRs, source inventories, verified project reports, and committed repo artifacts with stable paths. ### Supporting Supporting sources guide routing and maintenance. Examples include Wiki Compiler Maps, taxonomy maps, verified generated reports, lint reports, and issue tracker parent/child tables. They are not usually public wiki content unless rewritten deliberately. ### Scratch Scratch sources are volatile capture. They can help agents find context, but they do not compile directly unless Jamie/Pixoid promotes or verifies the relevant material against canonical sources. ## Namespace routing rules - Use one primary namespace for each compiled page. - Use crosslinks for secondary relevance. - Duplicate only when a source is rewritten for a genuinely different namespace-specific purpose. - Promote projects or concepts to standalone namespaces only through an explicit decision. ## Promotion rule A source cluster can become a namespace when it has at least two of five signals: independent audience, multiple document types, raw source corpus, ongoing update lifecycle, or clear covers/not-covered scope. ## Source Compiled from `Wiki Compiler Maps/Namespace Wiki Compiler Map.md` and `Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.md`. --- title: Pixi Wiki created: 2026-06-16 updated: 2026-07-07 type: entity status: active namespace: pixi-vault tags: [pixi-vault, pixi-wiki, agentwikis, public-wiki, rag] sources: - wikis/pixi-vault/wiki/syntheses/pixi-vault-to-pixi-wiki-publishing-model.md - wikis/local-ai-infrastructure/wiki/concepts/rag-over-agent-wikis.md - https://github.com/pixiiidust/pixi-wiki confidence: high --- # Pixi Wiki `pixi-wiki` publishes Jamie's notes, project docs, and research as maintained knowledge bases so humans can browse a clean wiki and agents can read, search, and cite the same Markdown corpus. ## What it does Pixi Wiki turns each compiled knowledge base into: - rendered HTML pages for human browsing; - raw Markdown pages for source-backed retrieval; - `llms.txt` files for compact agent routing and onboarding; - `llms-full.txt` files for full-corpus agent context; - `index.json` registries for tools, tests, and retrieval pipelines; - a local read-only MCP server so agents can list, search, and read the same KB Markdown files; - an Agent Setup page and replication guide that explain how agents and other users connect to or copy the pattern; - client-side search, a shareable search results page, an Updates history, heading anchors/TOCs, sitemap/404, and browser-tested responsive navigation for human use. ## Why it exists The project turns messy private knowledge work into a shareable publishing surface. Humans browse the web wiki; agents consume the raw Markdown, routing files, registry, and local MCP tools. The private vault remains the source of truth. ## Potential uses - **RAG over compiled wiki pages:** use maintained pages as the retrieval corpus before adding vector/search infrastructure. - **Hallucination reduction:** route agents to scoped, cited, freshness-aware pages instead of letting them answer from memory. - **Agent onboarding:** give new sessions a compact `llms.txt` map before they read deeper pages. - **Project memory:** preserve decisions, entities, concepts, syntheses, and publication boundaries across sessions. - **Portfolio surface:** expose selected knowledge/project work as a coherent public system. - **Eval target:** test whether agents retrieve from the right namespace and cite the right source. ## Namespace classification Pixi Wiki is primarily an **entity/project artifact** inside the `pixi-vault` namespace because it is the generated public output of the vault compiler system. Its retrieval use case cross-links to `local-ai-infrastructure`, especially [[../../../local-ai-infrastructure/wiki/concepts/rag-over-agent-wikis|RAG over Agent Wikis]]. Its workflow/use-contract side cross-links to [[../../../agent-workflows/README|Agent Workflows]]. ## Current milestone As of 2026-07-07, the public mirror has moved from a useful generated surface into a hardened wiki product: - compiled namespace pages for project/domain clusters; - correct Markdown rendering for emphasis, tables, ordered lists, blockquotes, code spans, and link attributes; - collapsible grouped namespace sidebars, mobile navigation, visible theme toggle, skip links, and labeled controls; - rendered Markdown pages with metadata, raw Markdown links, report-a-mistake links, heading anchors, table of contents, and previous/next navigation; - client-side header search, `/` keyboard shortcut, shareable `search.html?q=...` results, title-weighted ranking, highlighting, namespace badges, and result pagination; - `updates.html`, `updates.json`, date-section pagination, month strip, namespace dropdowns, and recent-page redirect; - shared hash-versioned `site.css`, SEO metadata, sitemap, and 404 page; - a repository README and GitHub About description that frame Pixi Wiki as a publishing surface for human and agent KB access; - a simplified homepage IA: `WIKIS`, `AGENT SETUP`, `GITHUB`, dark toggle, and an “Agents start here” command using `curl https://pixiiidust.github.io/pixi-wiki/llms.txt`; - a reusable approach guide at `docs/REPLICATE_APPROACH.html` for adapting the pattern to other Markdown KBs; - MCP setup docs at `docs/MCP_SERVER.md`; - a local read-only MCP server with `list_kbs`, `list_documents`, `read_document`, `search_kb`, `search_all_kbs`, and `get_kb_summary`; - CI running the full pytest suite on pushes/PRs, route-contract tests over committed artifacts, and browser-level verification for live deploys. ## Public handles - Human site: https://pixiiidust.github.io/pixi-wiki/ - Repository: https://github.com/pixiiidust/pixi-wiki - Agent registry: https://pixiiidust.github.io/pixi-wiki/llms.txt - Full corpus: https://pixiiidust.github.io/pixi-wiki/llms-full.txt - Machine registry: https://pixiiidust.github.io/pixi-wiki/index.json - Agent setup: https://pixiiidust.github.io/pixi-wiki/docs/AGENT_SETUP.html - Replication guide: https://pixiiidust.github.io/pixi-wiki/docs/REPLICATE_APPROACH.html - Search page: https://pixiiidust.github.io/pixi-wiki/search.html - Updates history: https://pixiiidust.github.io/pixi-wiki/updates.html - MCP guide: https://pixiiidust.github.io/pixi-wiki/docs/MCP_SERVER.md --- title: Pixi Vault — Master Index created: 2026-06-16 updated: 2026-07-07 type: index status: compiled namespace: pixi-vault --- # Pixi Vault — Master Index > Compiled index for `pixi-vault`, the private source vault and namespace compiler system. ## Concepts - [[concepts/wiki-compiler-map-and-source-classes|Wiki Compiler Map and Source Classes]] — Routing contract, source classes, primary namespace rule, and namespace promotion rule. ## Entities - [[entities/pixi-wiki|Pixi Wiki]] — Hardened publishing surface for maintained knowledge bases: human wiki with search/Updates/navigation plus agent-readable raw Markdown, `llms.txt`, `llms-full.txt`, `index.json`, local read-only MCP, Agent Setup, and reusable approach guide. ## Summaries - Cross-namespace summary: [[../../hermes-agent/wiki/summaries/external-hermes-wikis-import-review|External Hermes Wikis Import Review]] — Hermes-specific instance of external wiki import triage and namespace-routing rules. ## Syntheses - [[syntheses/pixi-vault-to-pixi-wiki-publishing-model|Pixi Vault to Pixi Wiki Publishing Model]] — Source/output repo boundary and publish workflow from vault to human and agent KB surfaces. ## Source Roots - `Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.md` - `Wiki Compiler Maps/Namespace Wiki Compiler Map.md` --- title: Pixi Vault — Activity Log created: 2026-06-16 updated: 2026-07-07 type: log status: compiled namespace: pixi-vault --- # Pixi Vault — Activity Log > Append-only namespace log. ## 2026-06-16 create | Namespace scaffold initialized - Created README, CLAUDE instructions, raw folder, index/log, and typed wiki folders. - Source routing comes from `Wiki Compiler Maps/Namespace Wiki Compiler Map.md`. - No Daily Notes were copied or compiled. ## 2026-06-16 update | Compile pixi-vault content pack v1 - Added concept `wiki/concepts/wiki-compiler-map-and-source-classes.md`. - Added synthesis `wiki/syntheses/pixi-vault-to-pixi-wiki-publishing-model.md`. - Updated namespace README and index from scaffold to compiled status. - Sources are the PRD and Namespace Wiki Compiler Map. - Scratch chronology was not copied or compiled. ## 2026-06-16 update | Align publishing model with clean rebuild - Replaced legacy-shim language with clean rebuild policy for `pixi-wiki`. - Added cross-namespace links to Agent Workflows, Eval Trace, and Local AI Infrastructure. - No Daily Notes were copied or compiled. ## 2026-06-16 update | Record Pixi Wiki public artifact milestone - Added entity `wiki/entities/pixi-wiki.md` to classify Pixi Wiki as a public generated artifact under the `pixi-vault` namespace. - Recorded the current UX contract: collapsible namespace sidebars, rendered Markdown pages with metadata, raw/source links, report-a-mistake links, and previous/next navigation. - Linked Pixi Wiki's RAG/retrieval use case to `local-ai-infrastructure` and `RAG over Agent Wikis`. - No Daily Notes were copied or compiled. ## 2026-06-18 update | Clarify Pixi Wiki human/agent publishing surface - Reframed Pixi Wiki as a publishing surface for curated KBs: human web wiki plus agent-readable raw Markdown, `llms.txt`, `index.json`, and local read-only MCP. - Recorded the shipped local MCP server and docs as repo/public-artifact features, while preserving the boundary that the MCP server is not hosted by GitHub Pages. - No Daily Notes were copied or compiled. ## 2026-06-18 update | Ship agent-first homepage and reusable approach guide - Recorded the live homepage IA: `WIKIS`, `AGENT SETUP`, `GITHUB`, dark toggle, and `curl https://pixiiidust.github.io/pixi-wiki/llms.txt` as the explicit agent-start command. - Moved `index.json` out of the primary hero/nav and kept it as a footer/docs machine-contract link. - Added the replication guide handle so other users can copy the Markdown KB → human wiki → agent entrypoints → local MCP pattern. - Recorded the corrected dark palette contract: near-black background, muted teal links, `#8b4356` reddish-purple active accent, and pale gold highlights. - No Daily Notes were copied or compiled. ## 2026-06-18 update | Crosslink external wiki import method - Added cross-namespace pointer to the Hermes Agent external wiki import review as a concrete instance of Pixi Vault namespace-routing/import triage. - No Daily Notes were copied or compiled. ## 2026-07-07 update | Record Pixi Wiki hardening and feature delivery - Captured the shipped hardening pass: 18 issues closed through 20 merged PRs, live on GitHub Pages and browser-verified. - Recorded the user-facing features now in the public artifact: correct Markdown rendering, mobile navigation, heading anchors/TOC, client search, `search.html`, Updates history, pagination, SEO/sitemap/404, and shared hash-versioned CSS. - Recorded the agent/ops features now in the public artifact: CI running 207 tests, route-contract tests over committed artifacts, MCP search performance improvements, and browser-level deploy verification for CSS/JS/runtime issues that HTTP checks miss. - No Daily Notes were copied or compiled; this log entry summarizes verified repo/live-site milestone state. --- title: Pixi Vault to Pixi Wiki Publishing Model created: 2026-06-16 updated: 2026-07-07 type: synthesis status: compiled namespace: pixi-vault tags: [pixi-vault, pixi-wiki, publishing, agentwikis] sources: - Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.md - Wiki Compiler Maps/Namespace Wiki Compiler Map.md confidence: high --- # Pixi Vault to Pixi Wiki Publishing Model `pixi-vault` is the private source repository. `pixi-wiki` is the public generated mirror. The boundary is intentional: authoring truth and public output are separate artifacts. ## Source side ```text pixi-vault/ ├── Knowledge/ # reusable concept authoring ├── Projects/ # project/application source truth ├── Wiki Compiler Maps/ # routing contracts └── wikis// # compiled namespace source ``` The `wikis//` layer is compiled/curated source inside the vault. It is reviewable in Git and Obsidian, but agents should edit `Knowledge/`, `Projects/`, or Wiki Compiler Maps first unless intentionally patching compiled output. ## Public side ```text pixi-wiki/ ├── llms.txt ├── llms-full.txt ├── index.json ├── search.html ├── updates.html ├── updates.json ├── sitemap.xml ├── site.css ├── raw//... └── wiki//... ``` `llms.txt` is the compact agent registry. `llms-full.txt` is the full concatenated corpus. `index.json` is the machine-readable registry. `raw//` preserves Markdown, `wiki//` exposes human-readable HTML, `search.html`/`updates.html` provide human retrieval and freshness surfaces, and the local MCP server exposes read/search tools over the same KB files. Human pages render Markdown with breadcrumbs, visible frontmatter metadata, raw Markdown links, report-a-mistake links, namespace sidebars, heading anchors, table of contents, and previous/next navigation. The goal is a two-surface publication model: humans browse/search the web wiki and update history, while agents use raw Markdown, `llms.txt`, `index.json`, and local MCP tools over the same KBs. ## Publication workflow 1. Update canonical source in `Knowledge/`, `Projects/`, or Wiki Compiler Maps. 2. Compile/curate into `wikis//`. 3. Run namespace linting against `pixi-vault/wikis`. 4. Run the `pixi-wiki` generator. 5. Run public-output tests. 6. Push both repos as needed. 7. Verify live GitHub Pages URLs with HTTP 200 and expected content tokens. 8. Run browser-level verification for pages affected by CSS, layout, navigation, or JavaScript. HTTP checks alone miss computed-style and runtime failures. 9. For local MCP changes, run the MCP self-test and a real stdio client smoke test. ## Clean rebuild policy Old root flat pages in `pixi-wiki` are removed from the canonical public contract. The clean mirror should keep root-level global surfaces such as the homepage, registries, search, Updates, sitemap, shared assets, and docs, plus `/raw//...` and `/wiki//...` namespace trees. No old `concept-*.html`, `projects-*.html`, `knowledge.html`, `projects.html`, `maps-of-content.html`, `root.html`, `agent/`, or `legacy/` surface should reappear without a deliberate compatibility policy and regression coverage. ## Cross-namespace relationships - [Agent Workflows](../../../agent-workflows/README.md) documents crew workflows affected by source-truth boundaries, Knowledge Pack Routing, and markdown-first agent memory. - [Eval Trace](../../../eval-trace/README.md) evaluates whether agents overfit stale context or skip live verification. - [Local AI Infrastructure](../../../local-ai-infrastructure/README.md) will matter when RAG or local models consume compiled wiki pages. ## Source Compiled from `Projects/Hermes Mission Control/PRD - Pixi Vault Namespace Compiler.md` and `Wiki Compiler Maps/Namespace Wiki Compiler Map.md`.