akurai-tasks

public

Latest change c5be5e616090ae3f9ae037e3702c07f72dc783f3 - chore: establish AkurAI Tasks planning baseline by Ólafur Búi Ólafsson

# AkurAI-Tasks

AkurAI-Framework-based, agent-first project-management service for every AkurAI project.
It will replace repository-local Kanban files and disconnected task databases with one
durable source of truth exposed through a machine-first CLI, REST API, MCP server, and a
small human web interface.

This repository currently contains the reviewed planning baseline and the unmodified
`akurai new` application scaffold. No production service or migration has been claimed.

## Product contract

- One central project/task store; source systems become import inputs, not competing truth.
- Kanban is enforced flow: pull, WIP limits, dependencies, evidence, leases, and audit.
- Humans and agents use the same server-side transition rules.
- MCP is the agent tool interface. ACP remains the editor-to-agent protocol and connects to
this service through MCP. A2A is optional future agent delegation, not storage.
- AkurAI Notes notebook **AkurAI-Tasks** (ID 34) holds canonical operational and architectural
documentation; tasks, dispositions, leases, handoffs, and execution events become canonical
only in AkurAI-Tasks after cutover.
- AkurAI PassVault folder **AkurAI-Tasks** (ID 5) is the only approved home for credentials.

See [PLAN.md](PLAN.md) for the architecture, migration inventory, protocol contract,
delivery increments, and verification gates.

## Repository

- GitHub: <https://github.com/olibuijr/AkurAI-Tasks>
- Workspace: `/home/olafurbui/Projects/AkurAI-Tasks` on Titan
- Framework: `/home/olafurbui/Projects/AkurAI-Framework`

## Current scaffold

```text
backend/collections.toml AkurAI-Framework declarative example; not the task schema
backend/page.json generated page context
frontend/ generated no-build Framework frontend
akurai.toml generated local server configuration
```

The implementation plan replaces the example `posts` collection with a typed Rust domain;
workflow invariants are too important for generic CRUD routes.