2.4 KiB
2.4 KiB
Hermes Sidecar Deployment Checklist
Updated: April 4, 2026
This checklist is for the current local-first Timmy stack, not the archived uni-wizard deployment path.
Base Assumptions
- Hermes is already installed and runnable locally.
timmy-configis the sidecar repo applied onto~/.hermes.timmy-homeis the workspace repo living under~/.timmy.- Local inference is reachable through the active provider surface Timmy is using.
Repo Setup
- Clone
timmy-hometo~/.timmy - Clone
timmy-configto~/.timmy/timmy-config - Confirm both repos are on the intended branch
Sidecar Deploy
- Run:
cd ~/.timmy/timmy-config ./deploy.sh - Confirm
~/.hermes/config.yamlmatches the expected overlay - Confirm
SOUL.mdand sidecar config are in place
Hermes Readiness
- Hermes CLI works from the expected Python environment
- Gateway is reachable
- Sessions are being recorded under
~/.hermes/sessions model_health.jsonupdates successfully
Workflow Tooling
~/.hermes/bin/ops-panel.shruns~/.hermes/bin/ops-gitea.shruns~/.hermes/bin/ops-helpers.shcan be sourced~/.hermes/bin/pipeline-freshness.shruns~/.hermes/bin/timmy-dashboardruns
Heartbeat and Briefings
~/.timmy/heartbeat/last_tick.jsonis updating- daily heartbeat logs are being appended
- morning briefings are being generated if scheduled
Archive Pipeline
~/.timmy/twitter-archive/PROJECT.mdexists- raw archive location is configured locally
- extraction works without checking raw data into git
checkpoint.jsonadvances after a batch- DPO artifacts land under
~/.timmy/twitter-archive/training/dpo/ pipeline-freshness.shdoes not show runaway lag
Gitea Workflow
- Gitea token is present in a supported token path
- review queue can be listed
- unassigned issues can be listed
- PR creation works from an agent branch
Final Verification
- local model smoke test succeeds
- one archive batch completes successfully
- one PR can be opened and reviewed
- no stale loop-era scripts or docs are being treated as active truth
Rollback
If the sidecar deploy breaks behavior:
cd ~/.timmy/timmy-config
git status
git log --oneline -5
Then:
- restore the previous known-good sidecar commit
- redeploy
- confirm Hermes health, heartbeat, and pipeline freshness again