Two-disk (system/state) btrfs-backed QEMU VM, nftables-isolated by default, adapted from a design provided as loose files. Adds a hermesHome option to the host module and migrate-docker-hermes.sh so an existing flat HERMES_HOME (e.g. from a prior Docker deployment) can be carried over intact. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
# Agent Instructions
|
|
|
|
**MANDATORY FIRST ACTION:** Read [`GUIDELINES.md`](GUIDELINES.md) in full before
|
|
doing anything in this repository. It is the single source of truth for agent
|
|
behavior here.
|
|
|
|
Key non-negotiable rules from that file:
|
|
|
|
- **Always present a plan first** and wait for user approval before making any
|
|
changes — no matter how small the task.
|
|
- **Never run builds or disk-writing steps** (`nix build`, `./setup.sh`'s disk
|
|
creation/image-write steps, `dd` to any disk image, `nixos-rebuild switch`
|
|
on any consuming host) — zero exceptions, even if asked.
|
|
- Never run `hermes-vm rollback` or `hermes-ctl reseed` without explicit,
|
|
freshly-given confirmation — both destroy live guest state.
|
|
- Never edit `guest/hardware.nix`'s disk labels without the operator having
|
|
confirmed `lsblk -f` output first.
|
|
- Never commit live secrets (`.env` values, API keys, tokens) to
|
|
`guest/hermes/home` — it's a template seed, not where real credentials go.
|
|
- When migrating existing data from elsewhere, copy — never move or delete —
|
|
the source, until the operator confirms the migration is verified.
|
|
- Never commit or push changes unless explicitly asked.
|