Operating loop
From a sentence to verified change.
Gaia keeps the conversation simple while preserving the work, authority, evidence, and context needed to operate real software.
1. Conversation captures the outcome.
The owner talks to Gaia in plain language. Gaia answers directly when the work is conversational and turns substantive delivery into durable work with scope, evidence, and status.
2. The tracker holds intent.
Work items record the objective, priority, ownership, dependencies, and delivery state. Projects group work; they are not giant catch-all tickets.
3. Conductor protects continuity.
Long-running implementation keeps leases, checkpoints, recovery state, and a bounded workspace. A failed process should not erase the work or silently start a competing executor.
4. Work stays bounded.
Changes are isolated and validated in proportion to risk. Production, publication, spending, and destructive operations retain explicit authority boundaries.
5. Review returns evidence.
Gaia verifies outcomes before claiming completion while keeping the conversation readable and focused on what materially changed.
6. Documentation catches up.
Architecture and operating documents are living system state. Material changes are reflected in the wiki and, for public facts, on this site.
Access boundary