Overview
The Knowledge Vault is a Quartz-powered personal knowledge base for Aloysius Productions, deployed to GitHub Pages. It captures decisions, patterns, research, learnings, and discoveries from every project across all AP zones — operating on the principle that knowledge collection is not optional but a mandatory output of all work. Content lives in obsidian/ and is structured as a Zettelkasten: pages connect through wikilinks rather than existing in isolation. The vault enforces a minimum of 2 wikilinks per document because isolated pages are structural failures in a linked knowledge system.
Key Concepts
- Quartz infrastructure — Static site generator that compiles Obsidian-flavored markdown (including
[[wikilink]]syntax) into a browsable site. Build and deploy run via GitHub Actions on push to main. - Content taxonomy — Six top-level sections:
daily/(date-named notes),organization/(project status, tech stack),patterns/(reusable code and design patterns by language),projects/(project documentation),references/(technical references and this encyclopedia),research/(active, completed, and experiments). - Frontmatter requirements — Every file needs
title,created(YYYY-MM-DD), andtags. Imported documents addsourceandimported-prefixed tags for traceability. - Link validation —
npm run validate:linksreports broken links and orphan count. Must be run before updating.management/status.md. Known state: 0 broken links, 2 orphans (daily notes only). - Security layer — Pre-commit hooks run
scripts/security-scan.mjsvia Husky + lint-staged. TruffleHog scans git history in CI before deploy..security-config.ymlcontrols scan behavior but has known config drift. - Summarization pipeline — A 3-stage AI pipeline in
research-lab-materials/external/scripts/processes the external research corpus: JSON summaries (gemini-1.5-flash), concept abstracts (gemini-1.5-pro), and CATALOG.md assembly. - Wikilink compliance — 100% (744/744 files compliant as of 2026-03-13). Target is ≥2 wikilinks per file.
Related
- AP Ecosystem — The ecosystem this vault documents
- Ops-Core — Governance zone that defines what must be documented and how
- Gloriously Awesome System — Tooling that generates knowledge artifacts as part of its execution model
- Architecture — System design concepts referenced throughout vault patterns and research