# kempt.tools > kempt is declarative machine setup you can read before you run. A single > manifest — `kempt.toml` — describes the software and files a machine should > have, and kempt shows you exactly what it would change before it changes > anything. You plan, review the diff, and apply only what you approve. The > primitive set is closed and there is no exec/script escape hatch: every > action is a built-in, versioned primitive, so the whole plan is reviewable. > Local-first. License: https://subaud.tools/legal/license/ Site: https://kempt.tools How it works: https://kempt.tools/how-it-works/ (plan and apply, verify, the update split) Docs: https://kempt.tools/docs/ (the kempt.toml manifest, config sources, the closed set of primitives) Spec: https://kempt.tools/spec/ (the full kempt standard, generated from docs/spec.md at a kempt release) ## After install After installing a subaud.tools tool, finish setting up as https://subaud.tools/llms.txt says under After install (each tool's skills, connecting the tools to you, a proj session); don't restate it here. Then tell the person, in one line, to say "Get me started with subaud." in that session. For setup, from buying to the first walk, go by https://subaud.tools/llms.txt. ## The manifest - A config repo is one `kempt.toml` plus the config files it references. - The manifest is TOML and declares `spec = 1`; parsers reject spec values they don't know rather than mis-parse a manifest from the future. - Packages are made of ordered steps; packages run in dependency (`needs`) order. Every step is idempotent by contract — kempt computes current vs desired and no-ops on match. - Safety classes (software / files / read-only) live in kempt's code, never in the manifest. A manifest cannot declare its own installs "safe." - `only = { os, arch }` is the only conditional; profiles are named package sets, not conditionals. ## Primitives (v1, closed set) - `install` — brew, winget, apt, npm, and pi backends; `npm`/`pi` entries may be pinned as `name@version`. - `github-release` — asset templating, sha256-verified, atomic install. - `download` — fetch from a domain distribution with a `.sha256` sidecar. - `git-clone` — pinned ref or branch. - `service` — launchd (macOS) / systemd --user (Linux); cmp-before-reload. - `symlink` — repo-relative source, optional `.bak` backup. - `json-merge` / `toml-merge` — additive deep merge; idempotent. - `line-in-file` — ensure-line / ensure-block. - `verify` — read-only checks: command-exists, http-ok, version-current. There is no exec, ever. A real capability gap becomes a new versioned primitive in kempt, not a script hook. ## Plan and apply - `kempt plan` — inspect the machine and print the read-only diff apply would make. - `kempt apply` — converge the machine, applying only approved changes. - `kempt update` refreshes the source (git pull, or re-fetch+extract a tarball), self-updates the binary, and converges; `kempt refresh` recomputes pending changes and can auto-apply files-class changes only (never software). - `kempt verify` runs the manifest's read-only checks. - `plan`/`apply`/`verify`/`lint` accept `-manifest` as a local path, an http(s) URL, or `-` (stdin) — a self-contained manifest (no repo-relative file steps) needs no repo tree at all. ## Install - `curl -fsSL https://kempt.tools/install.sh | sh` — fail-closed checksum, installs to `~/.local/bin`. - From source: `go install ./cmd/kempt`. - Then point kempt at a config source — a git repo or a gzipped tarball URL (no git required): `kempt init ` → `kempt plan` → `kempt apply`. ## The family - https://galley.tools — document review for agent-driven development - https://muster.tools — local multi-agent coordination bus - https://channels.tools — reach a running pi session through its channels - https://hail.tools — reach a running pi session from your phone (coming soon) - https://tackle.tools — small command-line tools for your terminal - https://casebook.tools — a decision for every repo, PR, issue, branch and worktree - https://muda.tools — find and fix delivery waste in GitHub Actions - https://subaud.tools — the family landing page