Safety & boundaries

Rhodd is built so you can trust what it does to your repository. These properties hold on every compile, by construction.

Local-first

Everything runs on your machine. There is no account and no cloud dependency to compile a baseline, and no live provider or cluster calls happen by default — that includes AI providers.

Deterministic & inspectable

The same input produces byte-identical output, recorded by the .rhodd.lock hashes. Every artifact is plain text on disk — no black-box state, nothing you can't read, diff or commit.

Ownership-aware

Rhodd tracks generated paths separately from the source you own:

{
  "generated":  ["services/api/Dockerfile", "compose.yaml", "k8s/", ".rhodd/"],
  "user_owned": ["services/api/src/**", "services/web/src/**"],
  "policy": "regenerate-generated-only"
}

Regeneration only rewrites generated paths. The code you write is never clobbered.

Guarded apply & rollback

Generating files is one thing; acting on them is another, and Rhodd keeps them separate. apply and rollback are explicit and opt-in — nothing is deployed or mutated automatically. A deployment export is a set of manifest files; turning those into a running system is a deliberate step you take.

What Rhodd is not

• Not an AI code generator — AI is a bounded consumer of state, never the generator.
• Not a Terraform replacement — different layer; Rhodd does not output Terraform.
• Not a one-shot scaffold — it keeps the model and recalculates against it.

Rhodd is pre-release (v0.1.0-rc.1); treat it as early access while the surfaces settle.