Planned architecture
Contracts are durable. Plans are replaceable.
PillarMesh is being designed around deterministic compiler authority: identical canonical inputs and compiler versions should produce identical semantic artifacts.
The platform will reject an illegal or infeasible request with No Valid Planinstead of allowing generated candidates or runtime convenience to become execution authority.
Public system boundary
Five cooperating planes
Semantic plane
Durable Integration Contracts declare outcomes, meaning, constraints, and ownership.
Compilation plane
Deterministic compilation evaluates legality and feasibility before producing a reviewable candidate artifact.
Managed data plane
Admitted work will operate supported connections, a dedicated warehouse, transformations, and bounded state transitions.
Experience plane
Catalog, governed discovery, dashboards, and reports will expose approved consumer outcomes.
Operations plane
Approval, reconciliation, evidence, recovery, and cost boundaries will remain attributable.
Six explicit boundaries
- 01
Integration Contract
Declares the supported outcome, boundaries, and constraints.
- 02
Physical plan
Selects a concrete, reviewable approach for the declared contract.
- 03
Execution graph
Makes the ordered, bounded work explicit before runtime begins.
- 04
Runtime
Carries out approved work under supervised automation.
- 05
Reconciliation
Checks source-to-consumer outcomes rather than assuming success.
- 06
Evidence
Records attributable facts about what was planned, run, and observed.
Explicit limits
Bounded by what can be proved and governed.
The planned boundary does not include arbitrary destinations, a general-purpose scheduler, autonomous semantic approval, or universal exactly-once behavior.
Reconciliation and evidence will establish attributable source-to-consumer facts. Logs and monitoring remain useful operational signals, but they are not substitutes for that evidence.