AkurAI-Build

public

Latest change 8b7d82067948ebc7b869db9957d99ed3baa7876a - docs: migrate agent guidance to AkurAI Notes pointer by Ólafur Búi Ólafsson

# AkurAI-Build — Agent Guidance

Repo: self-hosted AkurAI Build controller and worker; source publication and deployment run through Titan.

Canonical docs: AkurAI Notes notebook **AkurAI-Build**, note **AkurAI-Build — Agent Guidance**.

- Read canonical note and `.akurai.yml` before implementation, deployment, diagnosis, or operations.
- CI trigger: commit intended paths, `mcp__akurai_build_akurai_repo_sync`, verify hosted `sha` with `mcp__akurai_build_akurai_repo_branches`, queue exact SHA with `mcp__akurai_build_akurai_run_queue`, then wait/promote.
- Gate chain: `verify` → immutable `package` with SHA-256 → approval-gated production consumes same artifact → post-deploy health/behavior acceptance; rollback on failure.
- `deploy.sh` lives at repository root (`/home/olibuijr/Projects/AkurAI-Build/deploy.sh`) and forwards non-Titan commands to Titan after `git pull --ff-only`.
- Run checks, builds, deployment, and operations on Titan; never use file-copy paths instead of Git.
- Require persisted `succeeded`; `waiting` needs explicit `akurai_run_promote`; `queued`/`running` incomplete.
- Never expose secrets or manually mutate production state; use configured `mcp__akurai_build_akurai_*` tools.