Wiki Overview
This wiki is the persistent documentation and synthesis layer for TazLab knowledge work.
Purpose
The goal is to give both humans and agents a stable, organized place to accumulate knowledge over time instead of rediscovering it from raw documents on every query.
Current State
- The repository scaffold exists.
- The operational schema for agents is defined in
../AGENTS.md. - The first seed pages now define the TazLab system map, repository map, and knowledge-layer model.
- The wiki is ready for deeper ingestion and cross-project documentation passes.
- The wiki is now intentionally split into two trunks: the TazLab operational trunk and the software/technology reference trunk.
- A Hugo publication adapter now lives under
publish/, withhomepage.mdas the rendered front door andwiki/index.mdpreserved as the internal directory.
Expected Growth Pattern
As sources are added, this wiki should gradually develop:
- source summaries in
wiki/sources/ - durable pages for systems, repositories, and actors in
wiki/entities/ - conceptual pages in
wiki/concepts/ - larger synthesis pages in
wiki/topics/ - reusable investigations and comparisons in
wiki/analyses/ - practical runbooks in
wiki/operations/
TazLab Positioning
This repository is meant to complement, not replace, other TazLab knowledge layers:
AGENTS.ctx/memory/for active present-state memory and chronologymnemosynefor semantic retrievalwiki.tazlab.netfor durable, browsable, interlinked documentation and synthesis
Seed Pages
- topics/tazlab-system-map - High-level map of the main TazLab components and how they interact.
- topics/tazlab-repository-map - Repository boundaries and operational ownership map.
- concepts/tazlab-knowledge-layers - Relationship between active memory, semantic retrieval, and the wiki layer.
First Structured Coverage
The wiki now has first-pass coverage for:
- the main repository hubs under
wiki/entities/ - the
ephemeral-castlesubtracks for Hetzner Vault runtime and Tailscale - cross-cutting topics for cluster delivery, Flux DAG, secret flow, and CRISP program structure
- the software/reference trunk for Proxmox, Talos, Tailscale, Kubernetes, storage, and secrets tooling
The next useful expansion is likely one level deeper: repository-specific entrypoints, key files, common commands, and runbooks.