AkurAI-Build

public

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

# Research basis

The board deliberately implements a small set of established practices rather
than copying a vendor-specific workflow.

## Sources

1. [The Kanban Guide (December 2020)](https://kanbanguides.org/the-kanban-guide/2020.12/)
defines Kanban as a visual, pull-based system for optimizing flow. Its
Definition of Workflow requires work-item definitions, start/finish points,
states, WIP controls, explicit policies, and a Service Level Expectation. It
also requires measuring WIP, throughput, work-item age, and cycle time.
2. [GitHub Projects built-in automations](https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/using-the-built-in-automations)
documents automatic status updates on issue closure and PR merge, auto-add,
and automatic archival.
3. [GitHub Actions project automation](https://docs.github.com/en/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)
documents event-driven project updates and recommends GitHub App credentials
for organization projects. Repository `GITHUB_TOKEN` alone cannot manage
Projects; no credential-dependent workflow is enabled here.
4. [GitHub issue templates and forms](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)
supports structured intake, default labels/assignees/projects, and ordered
template selection.
5. [Atlassian WIP-limit guidance](https://www.atlassian.com/agile/kanban/wip-limits)
emphasizes using WIP limits to expose bottlenecks, reduce context switching,
and pull only when capacity exists.
6. [How to write a good spec for AI agents](https://addyosmani.com/blog/good-spec/)
recommends goal-oriented specs, explicit commands/testing/structure/
boundaries, small independently verifiable tasks, durable source-of-truth
artifacts, and clear handoffs.

## Decisions derived from the research

- **Nine flow states, no Blocked column.** Blocked work stays in its actual state
so WIP and age do not disappear. `blocked` and `blockReason` are task fields.
- **Explicit commitment and finish.** Cycle time starts at `In Progress` and ends
at `Done`; upstream intake queues do not inflate delivery cycle time.
- **Pull and WIP enforcement.** The CLI prevents entry into a full bounded
column. Exceptions require a forced transition plus a reason.
- **Provisional SLE.** Until 30 completed items provide project data, the board
uses a provisional expectation: 85% of committed work completes within 10
calendar days. Review it from observed p85 cycle time.
- **Evidence-bearing transitions.** Review and later states require evidence;
Done additionally requires a resolution.
- **Durable handoffs.** A receiver gets objective, state, changed artifacts,
evidence, remaining work, risks, exact next action, and stop conditions.
- **Local automation first.** The standard-library CLI is authoritative and
works without GitHub, network access, a package manager, or secrets. Optional
external integrations are documented but not enabled speculatively.