The agent loop
MangoX runs three agents in tight coordination: a planner that reasons over the domain, a coder that writes typed APIs, and a tester that verifies every endpoint before declaring the build done.
Schema as the source of truth
Everything in MangoX flows from the data model. The planner agent emits a schema first; the coder generates APIs and admin views from it; the tester writes contract tests against it.
Why it matters
When the schema changes, the rest of the system regenerates predictably. No drift between the database and the API layer.
The tester is the safety net
We give the tester agent veto power. A build is not done until the contract tests pass — even if the planner thinks it is.