---
name: lifecycle-provision-node
risk_class: config_mutation
inputs: [node_name, kind, storage_pool]
verification: "grep 'state: provisioning' inventory.yaml"
docs_update_checklist: [doc_page_stub]
transition: "planned -> provisioning"
---

# Lifecycle: provision a node

Per [seeds/ontology.yaml](../../../seeds/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 `seeds/policy.yaml` `lifecycle_overrides`).

Requires (from ontology): inventory entry, IP reserved, storage pool
chosen, doc page stub.

1. Create the LXC/VM on its target Proxmox host (`pct create` /
   `qm create`), choosing the storage pool deliberately — record it as
   the `storage:` field once populated (Week 1 schema; not yet backfilled
   for existing nodes).
2. Add the inventory entry: a `hosts.<name>:` block in
   `seeds/inventory.yaml` with `state: provisioning`, `kind`, `host`,
   `pve_id`, `lan_ip`, then `oikos seed` to ingest it. For anything that
   will self-enroll as a client afterward (see
   [CLIENTS.md](../../../CLIENTS.md#enrollment)), the entity must exist in
   `planned`/`provisioning` state before `bootstrap.sh` runs there.
3. Stub a document entity via MCP `upsert_knowledge` with
    `kind: document` and about set to the new entity slug — even a
    one-line "provisioning, see plan X" is enough to satisfy the
    transition requirement.
4. Reserve the IP in DNS/DHCP notes if it's a fixed LAN address.

Next: [lifecycle-activate-node.md](../lifecycle-activate-node/SKILL.md).