Policy bundles
Versioned geo, network, and service policy packages for controlled rollout.
Policy desk
Policy routing controls for high-availability teams.
RouteGrid maintains a public policy-status surface for organizations that need controlled rollout, failover planning, and audit-ready route governance.
Policy changes are tracked like production releases.
Each public status movement has an owner, a review point, and a visible release note.
| Change | Component | State | Owner |
|---|---|---|---|
| CR-0620 | Policy Compiler | Reviewed | Ops desk |
| CR-0629 | Audit Ledger | Reviewed | Ops desk |
| CR-0638 | Failover Planner | Reviewed | Ops desk |
| CR-0647 | Notice Renderer | Reviewed | Ops desk |
Failover planning
Promotion and rollback notes before service routes change.
Audit evidence
Public change summaries for status and routing-policy decisions.
Policy memo
Public change files with owner-visible history.
RouteGrid publishes changes as policy records, not as generic marketing updates.
| File | Date | Public note |
|---|---|---|
| POL-080 | 2026-05-22 | Country policy export format updated for review workflows. |
| POL-093 | 2026-04-15 | Policy signing pipeline completed certificate renewal. |
| POL-106 | 2026-02-28 | Status renderer capacity increased for verification traffic. |
Public control records without private route disclosure.
Status summaries and documentation are published for review.
Implementation routes, credentials, and partner instructions stay outside the public surface.
Policy control review is handled through [email protected] and [email protected].
Control file
Route policy is documented before it moves.
RouteGrid presents a public change-control board for teams that need policy ownership, rollout notes, and rollback evidence.
Published policy notes are versioned before operational route changes are promoted.
Standby-route decisions keep a documented owner, review note, and change window.
Public records summarize decisions without exposing private routing targets.
- 01Compile
Policy bundles are prepared from approved operational inputs.
- 02Review
Operations verifies impact, fallback state, and public wording.
- 03Publish
Public status and documentation are refreshed after approval.