dtoro
a2410cf9c2
Rewrote .agents/domains/knowledge/schema.md and .agents/shared/llm-wiki.md
which described the deleted Python substrate (bin/homelab, oikos/cards/,
oikos/ledger.py, root inventory.yaml, knowledge/sources/, get_page/
search_docs MCP tools). Now reflect ADR 0003: Postgres DB is the single
source of truth for structured data and narrative knowledge; seeds/*.yaml
are bootstrap+DR manifests (content-hashed via seed_versions); archive/
knowledge/ is the frozen legacy wiki; MCP search_knowledge/get_entity_
knowledge replace get_page/search_docs.
Swept substrate refs in .agents/shared/{writing-style,page-templates}.md
and .agents/domains/operations/schema.md: bare inventory.yaml ->
seeds/inventory.yaml; knowledge/sources/ -> archive/knowledge/sources/
(historical); get_changelog/oikos/ledger.py -> DB audit trail / structured
document changelog field; HERMES -> Nomos.
Root inventory.yaml (618-line Python-era file superseded 2026-07-07 by
seeds/inventory.yaml) replaced with a deprecation stub pointing to the seed
and DB. Kept as a stub rather than deleted because AGENTS.md §1/§2 still
point clients at /opt/homelab-context/inventory.yaml; full on-client path
reconciliation deferred to R13.
Flagged export gap: oikos export regenerates seeds/{ontology,inventory,
policy}.yaml but NOT seeds/knowledge.yaml — API-added knowledge lives only
in the DB until hand-edited into the seed.
VERSION 0.7.7 -> 0.7.8. Plan R5 marked done.
2.7 KiB
Operations domain — schema
The operations domain holds the procedural and time-stamped documentation: runbooks (repeatable procedures), investigations (incident evidence), and plans (design docs for non-trivial work). It follows writing-style; runbooks and plans use the imperative voice exception.
Where each kind lives: runbooks are skills under .agents/skills/; operator
reference (command cheatsheet, enrollment, Nomos agent) lives in
.agents/operations/; investigations are investigation entities in the DB
(historically archive/knowledge/sources/investigations/); plans stay in the repo-root plans/
folder (below).
Plans always live in plans/
Any plan or design doc for the Homelab is written into the repo plans/ folder as
plans/YYYY-MM-DD-slug.md — never a scratch path, an agent-private plan location, or a chat
message. An agent drafting a plan:
- Writes the file under
plans/using the plan template in page-templates.md. - Lists it in
plans/index.md. - On completion, moves it to
plans/done/and updates the index status.
This is the single source for homelab design intent; keeping it in-repo means the plan is
versioned, reviewable, and reachable by MCP search_knowledge like any other doc.
Runbooks
Repeatable procedures are skills — one folder per skill at .agents/skills/<name>/SKILL.md, with
YAML front-matter that the Oikos policy and lifecycle machinery reads:
---
name: <name>
risk_class: read_only | reversible_low | config_mutation | destructive
inputs: [<param>, ...]
verification: "<shell expression that proves success>"
docs_update_checklist: [<doc artifacts to update>]
transition: "<from> -> <to>" # only for lifecycle runbooks
---
risk_class values and the lifecycle transition states must match
seeds/policy.yaml and seeds/ontology.yaml.
Investigations
Incident records are investigation entities in the DB, linked to the entities they implicate via
about edges. They are evidence sources — written once at incident time, then back-linked from
the changelogs of the nodes they implicate. Sections: ## Summary, ## Timeline, ## Root cause,
## Mitigations applied, ## Open questions. The legacy file-based investigations live at
archive/knowledge/sources/investigations/ (frozen 2026-07-07); new investigations go in the DB.
The operations log
plans/log.md is the append-only record of documentation operations on plans
(## [YYYY-MM-DD] <op> | <summary>), distinct from the DB audit trail. The legacy
archive/knowledge/log.md is frozen with the rest of the archived wiki.