Explainability And Operations

Generated systems are acceptable only when developers can understand why they exist and what they are doing.

Trace every artifact

Atlox must map each table, index, materialization, replica, process, protocol, and effect back to the semantic definitions and objectives that require it.

An explanation should answer:

• which source values and functions created this artifact;
• which reads, writes, clients, or objectives depend on it;
• what correctness and freshness guarantees it provides;
• whether it is authoritative or replaceable;
• what must happen before it can be removed.

Reconciliation

Deployment is a durable reconciliation process from the current physical world to one satisfying the target semantic revision.

The journal records planning, verification, backfill, shadow execution, compatibility, authority transfer, activation, rollback retention, and reclamation. Progress is durable evidence, not a timer or a shell script that must be restarted from memory.

Observe logical and physical behavior

Logs and metrics connect runtime activity to application functions, commits, workflows, effects, and generated plans. Developers can inspect both the logical operation and the physical realization chosen for it.