Problem: runbooks are agent-executable procedures but lived at the repo root, separate from the other agent instruction now under .agents/. Change: - Move runbooks/<name>.md -> .agents/skills/<name>/SKILL.md (folder per skill, matching the wiki-hq skills layout). Frontmatter (name, risk_class, inputs, verification, docs_update_checklist, transition) preserved. - Rewrite links (inbound from plans; between-skill siblings) via the move map. - Update prose references in AGENTS.md, HERMES.md, .agents/OIKOS.md, and the operations schema; fix a pre-existing stale link to operations/commands.md. No code consumed runbooks/ by path, so nothing else changes. Verification: all SKILL.md frontmatter parses with valid risk_class; every lifecycle transition resolves to an oikos/ontology.yaml state; broken-link count 127 -> 126 (fixed one, introduced none). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
name, risk_class, inputs, verification, docs_update_checklist, transition
| name | risk_class | inputs | verification | docs_update_checklist | transition | ||||
|---|---|---|---|---|---|---|---|---|---|
| lifecycle-provision-node | config_mutation |
|
grep 'state: provisioning' hosts/<name>.yaml |
|
planned -> provisioning |
Lifecycle: provision a node
Per oikos/ontology.yaml lifecycle.transitions.
Policy note: provisioning nodes get a lifecycle override —
config_mutation actions downgrade to reversible_low because nothing
depends on the node yet (see oikos/policy.yaml lifecycle_overrides).
Requires (from ontology): inventory entry, IP reserved, storage pool chosen, doc page stub.
- Create the LXC/VM on its target Proxmox host (
pct create/qm create), choosing the storage pool deliberately — record it as thestorage:field once populated (Week 1 schema; not yet backfilled for existing nodes). - Add the inventory entry:
homelab client add <name>for anything that will run thehomelabCLI, or a directhosts.<name>:block withstate: provisioning,kind,host,pve_id,lan_ipfor infra-only LXCs that won't self-enroll. - Stub the doc page (
containers/<pve_id>-<name>.mdorvms/<pve_id>-<name>.md) — even a one-line "provisioning, see plan X" is enough to satisfy the transition requirement. - Reserve the IP in DNS/DHCP notes if it's a fixed LAN address.
Next: lifecycle-activate-node.md.