Use this guide when changing TAMOSS itself. For public deployment, use the getting-started and operations guides instead.
task setup
task dev
task checktask dev runs native API and frontend dev servers with the local Compose
dependency stack. Stop the Kind stack first because both paths use local
PostgreSQL and S3 ports.
task kind:up PROFILE=local-kind
task kind:test PROFILE=local-kindUse this when changes affect Kubernetes manifests, operator behavior, ingress, authentication, S3, or deployed UI/API integration.
task operator:build
task operator:test
task operator:manifests
task operator:templateRun the normal operator gate:
task operator:testUse the detailed Chainsaw tasks only when changing operator reconciliation or
lifecycle behaviour. Those commands are documented in
operator/test/chainsaw/README.md.
Keep changes small and provable. A commit means the current iteration is ready to build on.
Keep module docstrings sparse and meaningful. Package entry points, public adapters, and scripts may use them to explain a boundary or execution purpose; ordinary implementation modules should not gain boilerplate docstrings solely for consistency.
See also: