Architecture
The planned architecture separates durable intent from replaceable implementation. Identical canonical inputs and compiler versions should produce identical semantic artifacts. Timestamps, trace identifiers, and other run-specific facts belong in the surrounding evidence.
Public architecture planes
Section titled “Public architecture planes”Semantic plane
Section titled “Semantic plane”The semantic plane will hold the Integration Contract and its canonical IIR. It preserves the declared outcome, meaning, and constraints without embedding engine-specific execution choices.
Compilation plane
Section titled “Compilation plane”The compilation plane will apply deterministic legality and feasibility rules to the IIR. It will produce a physical plan and execution graph, or return No Valid Plan with attributable constraints. It cannot run work or relax the contract.
Managed data plane
Section titled “Managed data plane”The managed data plane will carry out an accepted execution graph against supported managed warehouse engines. Its authority is bounded by the compiled plan; it cannot choose a different outcome or expand the supported source and destination scope.
Experience plane
Section titled “Experience plane”The experience plane will let people declare outcomes, review plans, provide required approvals, and inspect reconciliation and evidence. A user interface can present or collect an authoritative decision, but it does not create legality or execution authority on its own.
Operations plane
Section titled “Operations plane”The operations plane will observe runtime health, coordinate bounded recovery, and make failures visible. It consumes the accepted artifacts and runtime facts rather than rewriting contract or plan semantics.
How the planes relate
Section titled “How the planes relate”The semantic plane supplies canonical meaning to the compilation plane, which supplies bounded work to the managed data plane. The experience plane exposes human decisions across those boundaries, while the operations plane observes execution and recovery. Reconciliation and evidence connect observed managed-data and operations facts back to the declared contract for human inspection.
Artifact path
Section titled “Artifact path”- Integration Contract declares the supported outcome, boundaries, and constraints.
- Physical plan selects a concrete, reviewable approach for the accepted contract.
- Execution graph makes ordered, bounded work explicit before runtime.
- Runtime carries out approved work without expanding its authority.
- Reconciliation checks source-to-consumer outcomes rather than assuming success.
- Evidence records attributable facts about what was planned, run, and observed.
The IIR sits between the Integration Contract and physical planning as the canonical input to deterministic legality and planning decisions. PostgreSQL and ClickHouse are the planned initial managed warehouse engines; this is not a promise of arbitrary destination support.
No Valid Plan
Section titled “No Valid Plan”No Valid Plan is a terminal planning result for a request that cannot be made legal, safe, and feasible within its declared constraints. It is a useful result, not an invitation to bypass a boundary. The result should identify attributable constraints so a person can revise the contract or choose not to proceed.
Generated candidates, provider responses, and AI suggestions remain inputs to validation. The complete AI authority boundary applies across every plane.