| name | jellycore-ops |
| description | Operate JellyCore services in Docker Compose with a safe runbook: start, stop, restart, health-check, inspect logs, and collect diagnostics. Use when asked about service status, outages, deployment verification, or runtime operations. Use when this capability is needed. |
JellyCore Operations
Use this runbook for production-safe service operations.
Safety Rules
- Verify target environment before running commands.
- Prefer read-only diagnostics before restart actions.
- Do not run destructive Docker prune/remove commands unless explicitly requested.
Standard Flow
- Check status
docker compose ps
- Check health endpoints
curl -fsS http://localhost:47778/api/health
curl -fsS http://localhost:47779/health
- Inspect focused logs
docker compose logs --tail=200 oracle
docker compose logs --tail=200 nanoclaw
docker compose logs --tail=200 chromadb
- Recover by smallest action
docker compose restart <service>
- Re-verify status and health
Delivery Format
- Incident summary (symptom, scope, likely root cause)
- Actions taken (ordered)
- Current status (healthy/degraded/down)
- Next recommendation
Load references/commands.md for detailed command variants.
Source: b9b4ymiN/JellyCore — distributed by TomeVault.
