A dual-system architecture composed of a data authority engine and an execution engine. Structure is defined explicitly. Execution is disciplined. Mutation is governed.
Philosophy
Traditional systems translate requests into database queries, transform rows into objects, convert objects into JSON, and then render output.
We remove most of that journey. The structured JSON state already exists. CORE interprets it directly.
The data you store is the data you execute.
There is no hook-based extension model and no runtime injection of behavior.
Extension happens through explicit system boundaries: handlers, resolvers, templates, blocks. Behavior is declared through structure, not attached through side effects.
Extend by design, not by patch.
Execution and authoring are separate systems. Either can evolve or be replaced without redefining the canonical data state.
The runtime engine reads structured state. The authority system governs it. The data remains stable.
The engines may change. The structure endures.
Systems
AWA is the Data Authority and Structure Definition System.
It defines and governs the canonical JSON state of the system. Pages, collections, menus, configuration, import discipline, merge policy, versioning, and structural validation are handled here. It does not render output. It defines structure.
Authority over structure. Discipline over mutation.
CORE is the execution engine.
It interprets structured JSON state and produces outcome. Routing, security, orchestration, resolvers, templates, and blocks operate within strict boundaries. CORE does not create or mutate canonical data autonomously.
Orchestrated execution. Clear boundaries.
Every request passes through the kernel.
Security is centralized before dispatch. The kernel determines channel and structural identity. Handlers coordinate resolvers. Resolvers interpret domain trees. Templates and blocks render prepared state.
No hidden logic. No improvisation.
All system state exists as structured JSON in a canonical data tree.
Domain data and structural configuration are distinct but equally governed. Import operations are transactional. Snapshots protect integrity. External tools may propose structure; AWA validates and approves it.
Determinism over convenience. Integrity over automation.