AkurAI Build
Menu

akurai-tasks

public

Latest change 2bdfaf2c92055afb48e100fe2ae38cb3c3caa0e8 - plan: require AkurAI Build deployment for AkurAI-Tasks by Ólafur Búi Ólafsson

# Task: Converge AkurAI Tasks on canonical Framework capabilities

- **Epic:** [framework-convergence](../.plan/epics/framework-convergence.md)
- **Status:** backlog
- **Updated:** 2026-09-02

## What
Migrate this project toward AkurAI-Framework as canonical core. Generic capabilities live in Framework; project-specific domain logic remains here.

## Notes
- No big-bang rewrite. Land smallest vertical migration with rollback.
- Do not duplicate missing generic capability locally; create Framework prerequisite first.
- Never expose secret values.

## Steps
- [ ] Inventory HTTP, storage, auth, UI, telemetry, health, and migration code.
- [ ] Consume pinned Framework APIs and delete replaced local generic code.
- [ ] Preserve task workflow, leases, dependencies, audit events, and existing data.
- [ ] Make /api/health satisfy canonical Framework metadata contract.
- [ ] Pass scripts/check.sh, AkurAI Build, deployment, health, and MCP workflow verification.

## AkurAI Build deployment contract
All production delivery must pass through AkurAI Build:

- [ ] Canonical source is AkurAI Build hosted Git; local and hosted branch SHAs match.
- [ ] `.akurai.yml` has ordered `verify`, immutable `package`, and production deployment jobs.
- [ ] Production consumes package output from same exact commit; no rebuild or ad hoc file copy.
- [ ] Production job declares `environment: production` and required approval policy.
- [ ] Deployment goes through root-owned host agent with checksum verification, bounded restart, public health gate, and automatic binary rollback.
- [ ] Database change is reversible/additive and has verified backup/recovery path before activation.
- [ ] Secrets enter through protected Build/environment contracts and never logs, source, artifacts, or arguments.
- [ ] Persisted AkurAI Build run reaches `succeeded`; queued, running, waiting, verify-only, and package-only states are incomplete.
- [ ] Post-deploy public health and app-specific behavior are verified against exact deployed commit.