## Summary - Introduce C0/C1/C2 change classification based on the Mikado method, where documentation cards serve as persistent context for agents across sessions - Add `docs-mikado` mise task to visualize active Mikado dependency chains from `status: active` and `requires` frontmatter fields - Rename `zk-docs` task to `ai-docs` ## Changes - **New:** `docs/how-to/agent-change-process.md` — methodology card - **New:** `mise-tasks/docs-mikado` — Python uv script for dependency graph visualization - **Renamed:** `mise-tasks/zk-docs` → `mise-tasks/ai-docs` - **Updated:** `CLAUDE.md` — added Change Classification section, updated references - **Updated:** `ai-assistance-guide.md`, `exploring-the-docs.md`, `how-to.md` — updated references and index ## Verification - [x] `mise run ai-docs` works - [x] `mise run docs-mikado` runs (no active chains yet, as expected) - [x] `docs-check-links` — all valid - [x] `docs-check-index` — all indexed - [x] `docs-check-frontmatter` — all valid - [x] All pre-commit hooks pass 🤖 Generated with [Claude Code](https://claude.com/claude-code) Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/225
3.3 KiB
| title | modified | tags | ||
|---|---|---|---|---|
| Exploring the Docs | 2026-02-10 |
|
Exploring the Documentation
Audiences: All (Owner, AI, Reader, Contributor, Replicator)
This guide explains how the BlumeOps documentation is organized and how to find what you need.
Documentation Structure
The docs follow the Diataxis framework:
| Section | Purpose | When to Use |
|---|---|---|
| **[[tutorials | Tutorials]]** | Learning-oriented |
| **[[reference | Reference]]** | Information-oriented |
| **[[how-to | How-to]]** | Task-oriented |
| **[[plans | Plans]]** | Future work |
| **[[explanation | Explanation]]** | Understanding-oriented |
Quick Paths by Audience
For Erich (Owner)
You probably want quick access to operational details:
- how-to guides for common operations (deploy, troubleshoot, update ACLs)
- plans captures migration and transition plans for future execution
- reference has service URLs, commands, and config locations
- ai-assistance-guide explains how to work effectively with Claude
- Run
mise run ai-docsto prime AI context with key documentation
For Claude/AI Agents
Context for effective assistance:
- Read ai-assistance-guide for operational conventions
- plans has migration plans designed for AI-executed sessions
- reference has the technical specifics you'll need
- The repo's
CLAUDE.mdhas critical rules (especially the kubectl context requirement)
For External Readers
Understanding what this is:
- explanation covers the "why" behind design decisions
- reference shows what's actually running
- Browse service pages to see specific implementations
For Contributors
Getting started with changes:
- contributing walks through the workflow
- how-to guides for specific tasks (deploy services, add roles)
- reference tells you where things live
For Replicators
Replicators are people who want to build their own similar homelab GitOps setup, using BlumeOps as inspiration.
- replicating-blumeops provides the overview, with linked tutorials that go deep on individual components
- explanation covers architecture and design rationale
- Reference pages show specific configuration choices
Using Wiki Links
Documentation uses [[wiki-links]] for cross-references:
[[service-name]]links to a reference page[[page|Display Text]]customizes the link text
When reading on the web (docs.eblu.me), these render as clickable links. The backlinks panel shows what references each page.
Pre-commit hooks automatically validate that all wiki-links point to existing files and that link targets are unambiguous.
AI Context Priming
The ai-docs mise task concatenates key documentation files for AI context:
mise run ai-docs -- --style=header --color=never --decorations=always
This outputs the AI assistance guide, reference index, how-to index, architecture overview, and tutorials index - providing Claude with essential context for BlumeOps operations.
Related
- tutorials - Parent index of all tutorials
- update-documentation - How to publish doc changes
- review-documentation - Periodic doc review process