Trace Ledger
Trace posture will attach when the live frame resolves.
Live execution authority
CO2Router
Compute does not run until it is authorized.CO2 Router issues the binding decision.
CO2 Router is a deterministic environmental execution control plane. It evaluates carbon, water, latency, cost, and policy before workloads run, then attaches proof, trace, replay, and provenance to the same decision frame.
Authorization requestpre-execution
Current execution frame
baselinebaseline carbon statewater authority state
decision engine
binding outcome
Shell Ready
routing region on framecarbon delta on frameconfidence on framelatency on frame
Execution
pre-execution control
Governance
SAIQ + policy state
Proof
trace + replay + provenance
Live Control Plane
Open the HaloGrid execution console, inspect the current routing frame, and verify proof posture.
stable shell
Execution authority
The shell resolves immediately so visitors understand the control plane before live data attaches.
stable shell
Proof chain
Trace, replay, and provenance attach to the same decision frame instead of replacing the page with a loading state.
stable shell
Governance
SAIQ and policy state remain visible as product structure while the current live frame attaches.
What it does
You do not optimize infrastructure anymore.You control it.
A workload asks to run. CO2 Router co-evaluates carbon, water, latency, and cost. SAIQ governance and policy constraints return one of five binding actions before execution. The executor follows the decision. Proof, trace, replay, and provenance stay attached to the same frame.
Run Nowshell ready
This action remains visible immediately. The live decision mix attaches without replacing the page.
Rerouteshell ready
This action remains visible immediately. The live decision mix attaches without replacing the page.
Delayshell ready
This action remains visible immediately. The live decision mix attaches without replacing the page.
Throttleshell ready
This action remains visible immediately. The live decision mix attaches without replacing the page.
Denyshell ready
This action remains visible immediately. The live decision mix attaches without replacing the page.
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.
Live decision example
Binding decision with proof attached
The proof card stays visible even before the current live frame resolves. Execution authority, proof references, and governance context remain part of the public surface instead of hiding behind a loading shell.
decision cardShell Ready
baseline
baseline region
live carbon pending
water estimate pending
selected
selected region
selected carbon pending
selected water pending
carbon delta
pending
water delta
pending
confidence
pending
latency
-- ms
why
Live decision rationale will attach here when the current proof frame resolves.
Live Frame Pending
proof reference
Unavailable
frame Unavailable
governance context
SAIQ policy trace attaches with the live decision frame.
replay live proof sample
provenance posture
verified datasets will attach with live provenance
Why CO2 Router is Different
Every system below tries to optimize infrastructure.CO2 Router controls it.
Most systems suggest where workloads could run, rely on forecasts or static policies, operate after the fact, and cannot prove what actually happened. CO2 Router decides before execution, enforces one of five actions, co-optimizes carbon, water, cost, and latency, and produces replayable tamper-evident proof.
Most approaches
Suggest where workloads could run
Rely on forecasts or static policies
Operate after the fact
Cannot prove what actually happened
CO2 Router
Decides before execution
Enforces one of five binding actions
Co-optimizes carbon, water, cost, and latency
Produces replayable tamper-evident proof
This is not scheduling. This is infrastructure control.
Category dominance
Investor comparison block
| System Type | Decision Authority | Proof | Multi-Objective | Real-Time Enforcement |
|---|---|---|---|---|
| Academic schedulers | Advisory | No | Partial | No |
| Carbon APIs | Informational | No | Carbon-only | No |
| Cloud policies | Static rules | No | Limited | Partial |
| CO2 Router | Deterministic | Yes | Carbon + water + latency + cost | Yes |
Proof infrastructure
Every decision carries inspectable evidence.
Baseline vs selected region, signal lineage, governance state, and replay posture stay inside the same execution frame. That is what turns a recommendation system into authority infrastructure.
Baseline vs selected region and impact are preserved.
Signal provenance and dataset versions are attached to the proof record.
Replay can verify whether the engine still reaches the same deterministic outcome.
Proof chain
live proof sample
block 1
Input
block 2
Signals
block 3
Policy
block 4
Decision
block 5
Proof
proof record
job_id: unavailable
selected_region: unavailable
proof_hash: unavailable
confidence: 0.00
policy trace
replay available on frame
Signals, governance, and fallback discipline
Signals degrade. Execution authority does not.
Carbon and water decisions stay defensible even when providers degrade. Live providers, mirrored fallbacks, and SAIQ governance keep the control plane deterministic and auditable instead of failing open.
Live provider posture attaches here without replacing the rest of the page. The control doctrine remains visible first; the current signal window hydrates second.
WattTime
Ember
Water bundle
SAIQ + Policy
Binding decision
Proof refs
Replay posture
Start with control
Package the control plane like infrastructure.
The homepage now mirrors the live commercial surface: pricing is tied to decisioning, enforcement scope, proof, and governance depth instead of low-friction seat plans.
Operator
From $2,500/mo
One live control point for a single team.
For buyers who need one production decision loop with canonical decision storage, proof visibility, and a real enforcement wedge.
Best for teams running up to 250k decisions per month.
Decision API v1 and control-surface access
CI/CD or HTTP control-point rollout
Canonical decision storage and replay references
Governance
From $8,000/mo
Multi-team governance with production enforcement depth.
For organizations standardizing policy, proof, and runtime control across multiple workloads, regions, and entry points.
Built for high-volume decisioning, additional adapters, and regulated operating environments.
Multi-team policy governance and approval controls
Enhanced proof export and replay visibility
Kubernetes, queue, and webhook adapter coverage
Assurance
Custom
Assurance-driven deployment for enterprise control programs.
For enterprises that need governed evidence workflows, signed export chains, and controlled operational trust boundaries.
Scoped to assurance requirements, governance depth, and controlled rollout design.
Controlled assurance and proof export workflows
Signed chain delivery and replay routing design
Dedicated architecture review for internal control teams
Infrastructure is no longer passive
Control it.
Open the live Control Surface, inspect the proof posture, and watch the system decide where compute runs before the workload ever starts.
Live System
Real execution authority. Real trace. Real replay.
This section is bound to live engine outputs. It exposes recent decisions, trace and replay posture, SAIQ governance state, verified water datasets, and the current p95 latency window.
Recent Decisions
Live decision frames are hydrating.
Governance
SAIQ state will attach when live governance resolves.
Providers
Verified provider posture is hydrating.
Latency
Live latency data is hydrating.