Tremor Ops And Recovery
This page is the operator route map for deployment, runtime services, and recovery. It does not restate the canonical runtime or product model; it points to the pages that do. Use it when you need to decide which operational surface you are actually dealing with before you debug.Start Here By Problem
| If you need to… | Start here |
|---|---|
| Understand the overall deployment layout | Deployment Operations |
| Set up or verify local development | Local Development |
| Inspect the optional service overlay | Runtime Services |
| Check runtime identity, auth mode, or host/port assumptions | Environment Matrix |
| Work on agent wakeups or bounded execution windows | Agent Runtime Guide |
| Recover from a broken local dev loop | Paperclip Recovery Playbook |
| Reason about backup, restore, or version transition behavior | Recovery & Migration |
| Validate the live operating state before action | Health & Status |
What Each Layer Covers
Deployment
The deploy docs explain how the system is assembled and started:Runtime Services
The runtime-services page describes the additive monitor stack and its supporting services:Recovery
Recovery is split between the short local reset playbook and the longer migration discipline:Operating Rule
- Verify the runtime and database identity before treating any result as meaningful.
- Use the recovery playbook for broken local-dev mechanics.
- Use the wiki recovery page for backup, restore, schema, and version-transition questions.
- Keep hosted ingress debugging separate from local-origin debugging.