Philosophy
AOC is built on a disciplined view of human-machine coding.
The goal is not to chat more. The goal is to work better with machines through continuity, structure, and operator control.
principle
Structure over prompt improvisation
AOC starts from the belief that coding with machines should be a workflow, not a string of disconnected requests. The system is designed so context, decisions, and active work survive beyond one interaction.
principle
Continuity as infrastructure
Context, memory, and tasks are not side notes. They are core operating layers that keep the machine aligned with the project as work evolves.
principle
Terminal-native seriousness
The terminal remains the strongest environment for disciplined development. AOC treats it as a control surface rather than something to be abstracted away behind a glossy GUI.
principle
Local-first compatibility
Developers need freedom to work with local models, constrained hardware, and offline-friendly workflows. AOC is shaped to respect those realities instead of assuming cloud dependence.
Core stance
This is the operating doctrine underneath AOC.
These principles shape both the product and the way Intrface uses it in practice.
signal 01
Human-machine coding should be strategic, not theatrical.signal 02
Operator control matters more than feature spectacle.signal 03
A serious workflow must survive across sessions, machines, and projects.