Product overview
AOC combines context, memory, tasks, and runtime into one cockpit.
The public explanation should stay readable, but the underlying system is real: the workspace is organized around persistent project continuity and terminal-native operation.
module
Context
AOC keeps reactive project facts and structure available through .aoc/context.md so the workspace remains project-aware.
module
Memory
Architectural decisions and durable project knowledge live in .aoc/memory.md instead of disappearing between sessions.
module
Tasks
Taskmaster gives AOC a native work-tracking surface inside the same cockpit as coding and file navigation.
module
Runtime
PI runs as the coding runtime inside a Zellij-based workspace alongside Yazi, Pulse, and operator controls.
Workflow
The system is designed to keep the operator in one serious surface.
AOC is easiest to understand as a loop: enter the project, operate inside the cockpit, retain continuity, and keep work moving without scattering state across tools.
step 01
Enter a project and launch AOC inside the repo itself.
step 02
Navigate files in Yazi while the PI runtime stays project-aware in parallel.
step 03
Track work through Taskmaster without losing the coding surface.
step 04
Retain continuity through context and memory artifacts that live with the project.