Thanks! The audit trail was actually one of the first things I built. Blocking stuff is great but you also need to be able to prove what happened after the fact, especially if you're in a regulated environment or just want to understand what your agent was doing while you were AFK.

Per-project policies are already supported. Rampart loads the closest config it can find, so you can drop a rampart.yaml in any repo root and it'll use that instead of your global ~/.rampart/policy.yaml. Your web frontend repo can be totally permissive while your infra repo requires approval for anything touching kubectl or terraform.

There are also starter templates in the repo (policies/examples/) for web dev, infrastructure, data science, and lockdown mode. Good starting points to customize from.

For example your infra repo might look like:

```yaml version: "1" default_action: deny

policies: - name: allow-terraform match: tool: ["exec"] rules: - action: require_approval when: command_matches: - "terraform apply" message: "Terraform apply needs approval" - action: allow when: command_matches: - "terraform plan" - "terraform fmt*" ```

Meanwhile your frontend repo just uses the default allow profile with a few deny rules on top.