Terms for operating CO2 Router.

CO2 Router provides routing, proof, replay, and signal-visibility surfaces for compute control. The service is designed for pre-execution decisioning and does not guarantee specific carbon, water, latency, or cost outcomes outside the data and policy envelope in force at decision time.

Customers are responsible for configuring their workloads, deadlines, candidate regions, and policy tolerances accurately. The control plane can only make defensible decisions from the facts provided to it and the signal sources available at the time of execution.

Customers must protect credentials, use supported integration paths, and avoid bypassing enforcement behavior after a decision has been issued. Deliberate attempts to suppress proof, tamper with replay state, or misrepresent workload metadata are prohibited.

Customers remain responsible for compliance with their own legal, regulatory, and contractual obligations. CO2 Router supplies decision evidence and enforcement logic, but it does not replace legal review or governance approvals inside a customer organization.

The service may evolve as signal providers, infrastructure, or policies change. Material changes to billing, plan limits, or product behavior are communicated through normal account channels.

Operational degradations may cause the system to enter mirrored or fallback modes. When that happens, the service must continue to make the degraded state explicit in proof, replay, and control-surface posture.