Operate 301 — Production and reliability

Purpose: operate Fleet with clear trust boundaries, day-two procedures, and incident ladders.

Updated

Audience Production operators, SRE-adjacent owners, security reviewers
Effort ~1–3 hours to read core pages; ongoing runbook use
Prerequisites Build 201 topics you actually deploy (Caddy, templates, etc.)
Success You can answer “who may execute code on this host?”, restart Fleet safely, and walk a symptom → check → fix path

At a glance

  • You will: lock down trust boundaries, run day-two checks, and navigate incidents with explicit ladders.
  • Tone: assume production — prefer checklists and explicit rollback over tutorial pacing.
  • Pair with: CHANGELOG.md host-operator notes when cutting releases.
Topic Page
Trust boundaries + bearer hygiene Security
Day-two checks (systemctl, SQLite, rotations) Operations runbook
Dispatcher diagrams + data paths Architecture
Symptom → fix ladders Troubleshooting · start at symptom headings
Cooperative upgrade (POST /v1/admin/upgrade) + apt channel Upgrade & remote operations
Backup / DR posture Backup, restore & DR
Telemetry, SLOs, alerting Observability & SLOs
Production / enterprise go-live Enterprise deployment checklist
Disk self-healing (Space Guardian) Space Guardian
RAM parking (Memory Guardian) Memory Guardian
Host cleanup inventory / apply GET /v1/admin/cleanup-inventory, POST /v1/admin/cleanup — HTTP API
Fleet environment provisioning Environments · ADR Fleet environments
Laptop ↔ Granite admin federation Distributed nodes
Git install channel → apt Migrate installations to apt

Granite host runbooks (operator-specific)

Topic Page
Fleet upgrade without routine SSH Granite Fleet upgrade (API only)
Market Studio cutover Granite Market Studio cutover
Market Studio dev / N-env / edge Dev · Environments · Edge plane
Postgres on Granite Granite Postgres (PG-A)

Release notes (CHANGELOG.md) complement this section—particularly ### Host operator blocks paired with docs/host-operator-steps.json and scripts/fleet-host-upgrade-hints.sh when upgrading bare-metal installs.

Before: Build 201 · After: Reference for protocol detail