AkurAI-Build

public
Latest change e11509261b6a2aa4ea9ef67250b0be01bfb4f53b - Restore paths swept in from uncommitted WIP by Ólafur Búi Ólafsson
---
name: akurai-framework
description: "Cornerstone: pure-Rust application foundation all AkurAI apps build on"
---

# AkurAI-Framework — the application boundary
Pure-Rust single-binary foundation (~/Projects/AkurAI-Framework). Cargo workspace crates: http, json, sql, sqlexec, storage (BTree), template, markdown, ws, router, cli, css, assets, toml, collections, vector, blobs, i18n, llm, oidc, schema, telemetry. No external runtime deps.
- Ops contract (AKURAI_APPS.toml): every app exposes `GET /api/health` -> `{app, version, status:"ok"}`; validate with scripts/validate.sh.
- App config `akurai.toml`: name, server host 127.0.0.1, port, frontend dir; TLS terminates at the edge (nginx).
- `akurai serve` serves static frontend + /api/health + /api/_meta with SPA fallback; asset pipeline hashes/minifies CSS/JS in memory.
- `akurai new` scaffolds frontend/backend/data; IDP SSO via AKURAI_IDP_CLIENT_ID/SECRET/PUBLIC_URL (names only).
- Collections API: backend/collections.toml, data/collections.db + embeddings via AKURAI_EMBED_URL/MODEL/API_KEY.
- CI (.akurai.yml): cargo fmt check; clippy -D warnings; cargo test --all; package `cargo build --release --target x86_64-unknown-linux-musl -p akurai`; deploy akurai-ec2 release --mode publish --yes.
MIGRATION RULE (WOR-251): the approved pure-Rust application boundary IS this framework. New/migrated app units consume its crates by path or its shared binary — never a from-scratch stack, never project-authored TS/JS app processes.