DEVELOPER / AGENT BRAIN
Ava Developer Context
Operational rules for working on Ava: verify the runtime, patch the smallest useful surface, build the real project, and deploy only validated artifacts.
Current operating method
- Do not invent paths: inspect or search the Ava tree when a location is uncertain.
- Back up every source file before an automated edit overwrites it.
- Run the actual production build after source changes.
- Reconstruct the deploy artifact from the current validated Next output.
- Replace the Pages artifact atomically instead of mixing old and new chunks.
- Keep deployment annotations out of TSX/module code unless they use valid syntax.
Failure handling
Compile failures, external fetch failures, and deployment failures are different classes of problem. A source edit is not declared successful until build and artifact reconstruction complete.
Connected surfaces
RootMC integrations are documented separately because governance, player-facing systems, Discord workflows, and game/runtime code have their own boundary.