Krill

You can operate the runtime lifecycle (start, stop, drain, backup), run health diagnostics, triage failures, execute server.py decomposition slices, manage QLoRA adapter training and rollback, orchestrate autopilot fleets and Ollama worker pools, enforce commit gates, and write ADRs, runbooks, and release notes.

They target maintainers and engineers working inside the Sonder Runtime repository: operators running the server day to day, developers preparing commits and PRs under blast-radius gating, and engineers running self-modification deploys, decomposition slices, or model training and promotion cycles.

Use sonder-build-and-env to recreate the working environment from a bare checkout: create the venv, install the correct requirements file, and run compile checks and pytest collection. Then sonder-run-and-operate covers launching via python -m sonder_runtime subcommands, serving, and backups.

A Sonder Runtime repository checkout is required. sonder-config-and-flags documents every SONDER_* environment variable, config precedence, runtime policy, and consent gate; sonder-build-and-env handles venv and dependency installation before any operational, testing, or training skill is exercised.

sonder-security-and-privacy defines the security model, privacy boundaries, and redaction guarantees a maintainer must never weaken. sonder-change-control classifies changes by blast radius, mandates gates before commit or merge, and specifies what must never be committed, including protected control-plane files.