Operations
Day-to-day running: keep storage healthy, keep the brain synced, automate the rest.
| Page | Job |
|---|---|
| Storage | The storage layer: statuses, stats, WAL, mirrors |
| Locks | The two lock types: lease and mutex, roots, failure postures |
| Sync | Git sync flows and troubleshooting |
| Automation | Scheduled and triggered workflows |
| Webhooks | Outbound and inbound webhooks |
| Cron | Scheduled jobs inside Vant |
| Events | The event system and handlers |
| QoS | Rate limiting and request budgets |
| Network | Peer networking and the headless server |
| Day-to-day CLI | The commands you type most |
| CI | The GitHub Actions pipeline and local equivalents |
| Testing | Test suites and how to run them |
| Steward Runbook | Running a group’s router install: orgs sharing one decision chain |
| Federation Playbooks | Join, vote, sync, settle, catch up: mesh participant recipes |
| Agora | Cross-node votes and ledger sync: the vant agora verbs |
| Notices | The board: post, catch up, bridge decisions |
| Settlement | Cross-node payment: claims-not-cash |
| Cache | Cache behavior and clearing |
Where to start
Something feels slow or broken: Storage first, then Cache. Brain changes not landing on the remote: Sync. Wiring Vant into scheduled work: Cron and Automation.
One command to remember
vant health # Start here when anything looks off