Concepts
The ideas behind the commands. Read these and AOForge’s behaviour stops being surprising.
Context rot
The problem AOForge exists to solve, and why the answer is structural rather than a prompting trick.
The loop
Six phases, each writing files the next one reads. What each phase produces and when to skip it.
The .aoforge directory
Every file AOForge creates, who writes it, and who reads it back.
The intent model
kind × work → TDD posture, planning depth, model profile and verification rigor. A spike is not tested like a payments API.
Waves and checkpoints
How independent jobs run in parallel, and the four ways execution can legitimately stop.
State and memory
What survives a /clear, a reboot and a week away — and how to get it back.
Context discipline
Measured guidance on keeping an agent's window small. The lever is behaviour, not configuration.