AkurAI-Build

public

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

---
{
  "schemaVersion": 1,
  "id": "KB-YYYYMMDDHHMMSS-XXXX",
  "title": "Outcome-focused title",
  "type": "feature",
  "priority": "P2",
  "status": "inbox",
  "blocked": false,
  "blockReason": null,
  "owner": null,
  "createdAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
  "updatedAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
  "statusEnteredAt": "YYYY-MM-DDTHH:mm:ss.sssZ",
  "startedAt": null,
  "completedAt": null,
  "dueAt": null,
  "estimate": null,
  "labels": [],
  "dependencies": [],
  "spec": null,
  "branch": null,
  "issue": null,
  "pr": null,
  "evidence": [],
  "handoff": null,
  "resolution": null
}
---
<!-- markdownlint-disable MD025 -- JSON front matter is not a heading. -->
# Outcome-focused title

## Objective

Describe the user or project outcome and why it matters.

## Context

Link the canonical issue, specification, decision, or incident. Record
constraints and non-goals.

## Acceptance criteria

- [ ] State observable, testable outcomes.

## Boundaries

State always-do, ask-first, and never-do boundaries for this task.

## Implementation notes

Keep this section current; do not turn it into a transcript.

## Verification

List exact commands, checks, URLs, screenshots, or artifacts required for
completion.

## Handoff notes

Record only information the next owner cannot reconstruct cheaply.