# About Hakama

Hakama is the governance layer for teams adopting AI coding tools in serious software delivery: it checks scope, approvals, evidence, and commit control around the work.

Canonical: https://hakama.ai/about/




## Why We Exist

AI-assisted delivery needs an acceptance layer. Coding assistants produce useful work quickly. Teams still need a reliable way to decide which changes are allowed into the repo.

### Govern The Output

Hakama checks the change that reaches the repo: files, dependencies, routes, schema, approvals, and evidence.

### Keep Engineers Moving

Engineers keep using Claude, Codex, Gemini, Copilot, and the tools already in their workflow.

### Leave Proof Behind

Governed runs leave receipts that reviewers and auditors can inspect after the work ships.

## Where Hakama Came From

Hakama started as an attempt to make working with AI coding tools less stressful. Better prompts and structured workflows improved what the model produced, but the behavior stayed advisory: the model could still drift past the scope, drop a constraint, or wander off the task.

The lesson was that reliable control lives in the system around a change: in the scope, the checks, and the evidence at the commit. So Hakama moves the control point to where a change becomes real, around the repo, before it lands.