AKC Documentation

What’s missing to ship?

Start here:

akc deliver preflight

preflight checks your repo + environment and returns a structured report of the exact prerequisites missing for execute-mode delivery (web / iOS / Android, plus store lanes when applicable).

The docs in this directory focus on the AKC surfaces that exist in the repository today.

Ops quickstart (suggested path)

If you're operating AKC and want a single “what do I do next?” track, follow this path:

• evaluate → Delivery architecture
• preflight → Ops runbook
• execute → Runtime execution
• observe evidence → Runtime execution (evidence + replay surfaces) and Ops runbook (incident handling)

Start here

• Getting started - install AKC, bootstrap a project, and run a safe local demo
• Configuration - repo defaults, environment variables, provider credentials, and control-plane config files
• CLI command reference - current akc command tree and what each top-level command is for
• Architecture - the current package layout and how ingest, compile, runtime, and control surfaces fit together
• Environment model - how dev / staging / prod operator profiles relate to local / staging / production delivery environments
• Validation - evidence-driven observability and mobile validation with operator-side bindings
• Runtime execution - runtime commands, routing, adapters, coordination, reconcile, and autopilot
• Viewer - how akc view reads and exports local evidence

Deeper references

• Compile-time skills
• Artifact contracts
• IR schema
• Delivery architecture
• Viewer trust boundary
• Ops runbook
• Security
• Research

Project docs

Root-of-repository policies and overview (GitHub):

• README
• Contributing
• Governance
• Security policy