akurai-tasks

public

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

---
title: AkurAI-Tasks agent index
project: AkurAI-Tasks
repository: olibuijr/AkurAI-Tasks
kind: agents
status: planning
notes_notebook_id: 34
passvault_folder_id: 5
updated: 2026-07-14
---

# AkurAI-Tasks

Repository work runs on Titan. Follow the global host, GitHub, UI-feedback, and
secret-handling rules. Read `PLAN.md` before implementation.

## Current state

Planning baseline only. The generated AkurAI-Framework scaffold exists, but no task service,
MCP server, migration, deployment, or production data store exists yet. Never report the
service as operational until the corresponding acceptance gates in `PLAN.md` pass.

## Architecture rules

- Build on AkurAI-Framework crates and the AkurAI Notes pattern: one Rust workspace, one
binary, one embedded BTree database, web/REST/MCP in the same process.
- Keep domain rules in one core command layer. REST, MCP, CLI, and web handlers call that
layer; they do not implement parallel transition logic.
- Current task state and its append-only audit event are committed atomically under one
database lock.
- Every mutation is idempotent, actor-attributed, revision-checked, and validated server-side.
- Preserve source records losslessly during migration. Never overwrite collisions, infer
missing history, or treat audit snapshots as live boards.
- Use structured filters. Do not build a JQL clone, workflow DSL, plugin system, queue,
semantic index, or microservice without measured need.
- ACP connects editors to agents; AkurAI-Tasks is an MCP tool server. Do not implement an ACP
task-store server.

## Project records

- Canonical implementation plan: `PLAN.md`; mirror each approved revision to the AkurAI Notes
notebook as an approval record and handoff summary.
- Operational and architectural notes: AkurAI Notes notebook `AkurAI-Tasks` (ID 34).
- Credentials and connector tokens: AkurAI PassVault folder `AkurAI-Tasks` (ID 5). Store only
PassVault entry references in configuration; never secret values.
- Repository code and executable public documentation stay in Git. Notes do not replace
build/runtime inputs.

## Required implementation gates

Use focused commands during development. Add a gate only when its real capability exists:

- Increment 1: `scripts/check.sh` plus a focused local authenticated CLI/REST/MCP smoke;
- Increment 3: `scripts/test-import.sh`;
- Increment 5/final pre-deploy: `scripts/validate.sh --local`;
- post-deploy and before enabling writes: `scripts/validate.sh --live` plus the restore and
complete source-fence probes named in `PLAN.md`.

Never add placeholder scripts that return success. Pre-deploy production gate:

```sh
./scripts/check.sh
./scripts/test-import.sh
./scripts/validate.sh --local
```

Post-deploy/pre-write-enable gate:

```sh
./scripts/validate.sh --live
```

Deployment must use the maintained AkurAI Build/AkurAI deployment path from Titan. No ad-hoc
systemd, Nginx, TLS, database copy, or secret provisioning commands.