Core concepts

PillarMesh is being designed around a sequence of explicit artifacts. Each artifact has a narrower job than the one before it, so intent does not silently become execution authority.

Integration Contract

An Integration Contract declares a supported outcome, its boundaries, and its constraints. It is the durable statement of what a team intends to operate. It does not prescribe every engine-specific step and does not imply that every source or destination is supported.

Intermediate integration representation

The intermediate integration representation (IIR) is the canonical, technology-neutral form of an accepted Integration Contract. It gives deterministic legality and planning logic a stable input. The IIR is not an executable plan and is not an API payload available today.

Physical plan

A physical plan is a concrete, reviewable approach selected for a valid IIR and supported engine scope. PostgreSQL and ClickHouse are the planned initial managed warehouse engines. A different physical plan may implement the same durable contract as capabilities evolve.

Execution graph

An execution graph makes the dependencies, order, and bounded work of a physical plan explicit before runtime. It is not a general-purpose workflow schedule and cannot expand beyond the accepted contract at runtime.

Reconciliation

Reconciliation compares observed outcomes with the declared contract and expected plan results. It is how the planned platform will distinguish completed work from work that merely started or returned an intermediate success signal.

Evidence

Evidence is an attributable record of what was declared, planned, run, and observed. Evidence is part of the operating path, not a marketing claim or a substitute for independent assurance. Missing or invalid evidence is intended to remain visible rather than becoming silent success.