Foundgine Architecture

Core execution pipeline

Separation of concerns

Semantic model

Defines the application-facing capabilities.

Intent

Describes what the caller wants without binding it directly to a physical provider.

Authorization

Determines which parts of the requested operation are permitted and can contribute predicates or constraints to the execution plan.

Planner

Builds a provider-independent representation of the requested operation.

Rewriting and optimization

Transforms the plan while preserving semantics and authorization constraints.

Provider

Compiles and executes the plan against a concrete backend.

Multiple callers, one execution model

The goal is to avoid implementing separate execution semantics for every interface.

Why the intermediate plan matters

The plan is the architectural boundary between semantic intent and physical execution. It gives the runtime a place to:

• preserve authorization constraints
• validate dependencies
• rewrite operations
• estimate cost
• reason about provider capabilities
• optimize execution
• produce execution evidence

This is the core mechanism that allows multiple input surfaces and providers to share execution semantics.