Files
dtoro 60effcb2fe
Some checks failed
ci / build-test (push) Has been cancelled
ci / docker-build (push) Has been cancelled
Desktop App / Build Linux (amd64) (push) Has been cancelled
Desktop App / Attach to Release (push) Has been cancelled
session reliability: reconnect, knowledge loop, retire request_execution
Phase 1 — crash recovery: SSE auto-reconnect + backoff, polling gate
during disconnect, connection banner with retry button, empty-response
retry 3x, non-terminal resume on empty response, persistent error cards.

Phase 2/4 — visibility + continuation: custom ExecutionStatus renderer,
approvals extracted on every tool_result (not just done), activity bar
with status/goal, SessionDigest live polling, Continue button.

Phase 3 — cleanup: complete_task auto-cancels orphaned approvals,
deletes assent/destructive window keys, propose_plan marks pending
steps as replaced, plan step seq-order enforcement.

Phase 5 — knowledge loop: list_lxcs state filter (active/destroyed),
SOUL.md unmissable writeback section, propose_plan validation nudge,
complete_task writeback check, upsert_knowledge about array support,
plan generation grouping in frontend, session approval count badge.

Retire request_execution — all mutations now route through run.
Updated SOUL.md, AGENTS.md, CLIENTS.md, skills, and agent system notes.

Migration 020: plan step generation column, audit_log session_id index,
nomos_plan_executions pending-approval index.
2026-07-14 11:03:23 +02:00

52 lines
1.7 KiB
Markdown

# 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 `run` → Oikos policy
gating → actuator (SSH). The `request_execution` fixed-enum tool was retired
2026-07-14.
## 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 → `run` (auto-restart)
- `config_mutation` or `destructive` → escalate to operator
- Repeated flapping → escalate with flap count
### Execution tracking
1. `run` returns the execution ID in its result text
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-14 — request_execution retired
All references to `request_execution` replaced with `run`. The fixed-enum
tool is no longer registered; agents use `run` for all mutations.
Agent renamed from Hermes to Nomos (N0 milestone).
### 2026-07-07 — initial Phase 4 skill
Baseline homelab operations skill for Nomos container.