Quanamo — read-docs

quanamo-read-docs loads Quanamo's documentation — functional specs, infra credentials, AI provider keys — to ground subsequent work.


Documentation locations

LocationPurpose
~/Herd/docs/quanamo/README.mdIndex — read first
~/Herd/docs/quanamo/Functional specs, architecture, feature pages
~/Herd/.credentials/quanamo/servers.jsonOdin server IP, hostname, SSH key, stack
~/Herd/.credentials/quanamo/api-keys.jsonOpenAI + Gemini keys and model mapping
Per repo (CLAUDE.md, CHANGELOG.md)Project-level context and history

Scopes

InvocationBehaviour
/do quanamo-read-docsFull read — README → servers.json → api-keys.json → CLAUDE.md per repo
/do quanamo-read-docs serversservers.json + Horizon config
/do quanamo-read-docs deployservers.json + deploy.sh files + kanban.quanamo.test/deploy/README.md + this library's quanamo-deploy.md + quanamo-warmup.md
/do quanamo-read-docs <feature>Matching feature folder

App layout (always present)

AppDB engineDB nameQueue driverHorizon?Redis DBStep dispatcher
admin.quanamo.comPostgreSQL (master)quanamoredisyes5 (queue), 6 (cache)yes — driven by schedule:run from cron
feedz.quanamo.comPostgreSQL (shared with admin)quanamodatabasenono
kanban.quanamo.comMySQL (own)kanban_quanamoredisyes7 (queue), 8 (cache)yes — driven by kanban-scheduler supervisor program, gated by storage/step-dispatcher/active.flag

When the scope touches kanban, the command also reads ~/Herd/kanban.quanamo.test/deploy/README.md — it documents the kanban-only MySQL backup gate, Redis prefix, and active.flag operational rules.


Hard rule

README first, no exceptions. Reading feature docs without the index = ungrounded claims.