AkurAI-Build

public

Latest change 30e6b8c347048d64c2c048dfd05a8ded219d37f6 - Host authenticated Git repositories over Smart HTTP with repo host/sync CLI by Ólafur Búi Ólafsson

# Flow metrics and review cadence

Run:

```sh
node .kanban/bin/kanban.mjs metrics
```

The report includes the four minimum Kanban flow measures:

- **WIP:** cards in each state; committed WIP starts at In Progress.
- **Throughput:** Done items in the last 7 and 30 days.
- **Work-item age:** elapsed days for active committed items.
- **Cycle time:** elapsed days from first In Progress entry to Done.

## Service Level Expectation

Initial SLE: 85% of work completes within 10 calendar days after entering In
Progress. It is explicitly provisional. After 30 completed items, review the
observed p85 cycle time and update `board.json` to a realistic, evidence-based
expectation.

## Review cadence

- Daily/agent start: validate, inspect blocked and oldest active work.
- Weekly: review WIP breaches, blocked age, throughput, and p85 cycle time.
- Monthly or every 30 completions: review SLE, WIP limits, forced transitions,
  failure demand, and column policies.
- After a material incident: use the retrospective template and create
  improvement tasks; do not hide exceptions by rewriting event history.

Metrics are signals, not performance targets for individual agents. Optimize
flow and outcomes, not card counts. Never split work artificially to inflate
throughput or move incomplete work to reduce apparent WIP.