# 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.
