Console and API share one record

Many stacks grow an “admin CMS” and a “developer API” that slowly diverge. Schemas fork. Publish meaning forks. Agents make it worse by writing yet another client against whatever is convenient.

One system of record

LUNO’s API-only path reads and writes the same definitions and entries Console manages. Review and publish rules do not change because the caller is a framework instead of a browser.

Pick the path, keep the platform

Use Console when editors need a human UI. Use API-only when Next, Astro, or a custom runtime should own the presentation. Use Agents when the loop starts in a coding environment. The backend underneath should not multiply.