N0: rename Hermes → Nomos (standalone commit)

Problem: "Hermes" collides with Nous Researchs unrelated product;
  unclear identity for the resident agent.

  Change: Rename the live service identity across 39 files:
  - cmd/hermes/ → cmd/nomos/ (binary, env vars NOMOS_*)
  - internal/config/ server.go (NomosAgentSlug, nomosAgentID)
  - compose/hermes/ → compose/nomos/ (Dockerfile, service name)
  - hermes/ → nomos/ (SOUL.md, config.yaml, skills/)
  - .agents/HERMES.md → NOMOS.md (persona)
  - tools/setup-hermes-soul.sh → setup-nomos-soul.sh
  - seeds/inventory.yaml (agent:hermes → agent:nomos)
  - migrations/014_rename_agent_hermes_to_nomos.up.sql
  - Caddy vhost hermes.hubris.network → nomos.hubris.network
  - All referencing docs, scripts, ADR notes

  History preserved: archive/, plans/done/, ADRs not rewritten.
  Matrix @hermes notifier account and Legacy bin/hermes on LXC 129
  intentionally untouched (out of scope).

  Risk: N0 is identity-only rename; zero behavioral changes.
  Verification: go build ./... passes; docker compose --profile full
  resolves nomos service; grep -ri hermes (excluding archive/plans)
  returns only intentional refs (LLM model name, Matrix user).
This commit is contained in:
2026-07-08 14:14:56 +02:00
parent 9d9cbb63c4
commit 2b3aa248b1
39 changed files with 230 additions and 200 deletions

View File

@@ -0,0 +1,48 @@
# Homelab Operations Skill
**Risk class:** Depends on action (see OIKOS.md policy)
**Required scope:** agent
**Verification:** `get_health_summary` after action
## Overview
Standard operating procedures for the Nomos agent managing the hubris
homelab. All mutations route through `request_execution` → Oikos policy
gating → actuator (SSH).
## Procedures
### Health check triage
1. `get_health_summary` — check fleet health
2. For degraded/down entities, `get_entity` for detail
3. `get_signal_history` on the target to check for repeats
4. `get_blast_radius` to assess downstream impact
5. `get_trend` for metric context before deciding
### Signal response
- `reversible_low` with validated pattern → `request_execution` (auto-restart)
- `config_mutation` or `destructive` → escalate to operator
- Repeated flapping → escalate with flap count
### Execution tracking
1. `request_execution` returns a correlation_id
2. Poll `get_event_timeline` filtering by correlation_id
3. Once complete, `get_health_summary` to verify recovery
4. Record outcome via internal reasoning
### Pattern learning
- After 5 identical successful executions on the same (type, action), the
learning engine promotes the pattern to `validated`
- Check `get_patterns(status=validated)` to know what's trusted
## Changelog
### 2026-07-08 — rename to Nomos
Agent renamed from Hermes to Nomos (N0 milestone).
### 2026-07-07 — initial Phase 4 skill
Baseline homelab operations skill for Nomos container.