repository

Work Vault

README.md

Rendered from markdown source. Open raw source on GitHub.

Work Vault

A git-backed personal work vault, artifact wiki, and AI-managed continuity system.

This repository is prepared to hold a body of work in a form that can be inventoried, versioned, linked, classified, reconciled into stable standard-named source files, semantically processed, and navigated over time.

The repository now contains active intake content, archived snapshots, lineage-aware project pages, and instructions for separating inbound originals from standard-named source files. The structure, instructions, scripts, and review pages exist to keep that content legible over time.

The initial operating principle:

Witness before mutation.

No file should be renamed, moved, deleted, merged, or overwritten until it has first been inventoried.

Directory Map

artifacts/   actual work files, intake archive, standard-named source files, auxiliary material
wiki/        human-readable semantic navigation layer
manifest/    machine-readable inventory, logs, and reconciliation state
scripts/     executable maintenance tools
agents/      instructions for AI management agents
docs/        repository operating instructions
.vault/      configuration and rules

Current Phase

The wiki should stay evidence-led. Small durable branches get their own pages. Durable pages should increasingly contain semantic compression and deliberate cross-links, not only labels and source pointers. At this stage, expanding the semantic content of existing wiki pages is more important than ingesting more material when the foundational project is already present. Markdown should be the preferred working and wiki-facing form when a document can be converted cleanly, while inbound originals remain preserved as archival evidence. HTML-published items keep HTML primary and may archive DOCX or MD companions when they are not needed for coherence. Keep auxiliary bundles separate from core source unless otherwise noted. The public site now also exposes graph exports and a maintenance hub for queue pressure. External published feeds are handled separately under wiki/external/ and tracked through manifest/external_sources.json, manifest/external_published_index.jsonl, and manifest/external_ingest_log.jsonl. They are metadata-first wiki integrations, not intake-archive or standard-named source material.

The repository is also adopting a standard-named source layer:

artifacts/intake-archive/  original inbound files preserved as received
artifacts/standard-named/   flat directory of standard-named source files

Inbound files are evidence. Standard-named files are named source copies under the Work Vault naming standard. The wiki should prefer standard-named source links once available, while preserving provenance back to inbound originals where useful.

For projects already represented in the wiki, prioritize semantic extraction, synthesis, and cross-linking on the existing pages before adding more intake or more structural branches.

For document migration, prefer a markdown-first working layer for active material, but do not delete or rewrite inbound originals. Convert high-value clusters first, validate the markdown output, then update wiki links and manifests before broad replacement.

Abracadabracadoo is the protocol-family name and public site. Abracadoo is the renamed PWA app lineage and should stay separate from the protocol page and naming.

First Content Intake

  1. Add received source files to a dated batch under artifacts/intake-archive/.
  2. Run python3 scripts/inventory.py.
  3. Run python3 scripts/detect_duplicates.py when needed.
  4. Assign or propose standard filenames for meaningful artifacts.
  5. Copy source files into the flat artifacts/standard-named/ directory.
  6. Run python3 scripts/build_wiki_index.py.
  7. Review the generated state before any move, rename, merge, canon decision, or irreversible consolidation.

Source Of Truth

Inbound Archive       = what was received.
Standard-Named Files  = source files named under the Work Vault naming standard.
Manifest              = identity, provenance, roles, and relationships.
Git                   = witnessed state transitions.
Wiki                  = semantic navigation and interpretation.
Agents                = coherence, reconciliation, standard naming, and salience processing.

Operating Instructions

See:

Public Site

The wiki web layer is a static HTML build generated from the markdown wiki sources.

  • Build command: npm run build
  • Validate command: npm run validate
  • Landing page output: dist/index.html
  • Search index output: dist/search.json
  • Graph index output: dist/graph/index.html
  • Maintenance hub output: dist/wiki/maintenance/index.html
  • Sitemap output: dist/sitemap.xml
  • Robots output: dist/robots.txt
  • Raw vault browser: dist/vault/index.html
  • Public source repository: https://github.com/bobrs/_work-vault-wiki