Developers / Architecture

One deterministic chain from signals to proof.

The public architecture is intentionally direct: signals are normalized, SAIQ and policy shape the decision, the engine returns one binding action, and proof stays attached to the resulting frame.

How it works

Signals become one binding decision path.

Step 1
Signals

Carbon, water, latency, and runtime posture are normalized into a bounded decision input.

Step 2
SAIQ Governance

Weighting, constraint logic, and zone posture shape the decision frame before execution.

Step 3
Policy

Water guardrails, hard overrides, and execution rules determine what is admissible.

Step 4
Decision

The engine returns one binding action: run, reroute, delay, throttle, or deny.

Step 5
Proof

Proof hash, trace state, replay posture, and provenance remain attached to the same frame.

Deterministic inputs

Signals degrade, caches warm, and fallback discipline protects the decision path from becoming advisory.

Execution authority

The returned action is the control point. Downstream runtimes use it before the workload starts.

Replayable artifact

One decision frame, one proof chain, and one replayable envelope that can be inspected later.