Order routing v2
Replacement for the legacy router (see deprecate-router-v1). Goal: cut p95 from ~800ms to <200ms while exposing the rules engine surface to customers like acme-logistics who want to author their own routing rules.
Goals (this quarter)
- Cut p95 latency 800ms → <200ms across the EU + US regions
- Stand up the customer-facing rules editor (see rules-engine-customer-ui)
- Migrate 3 design partners off the legacy router by end of quarter
- Audit log every rule change (compliance ask from northwind-supply)
Decisions
- use-protobuf-internal — internal RPC moves to protobuf; JSON only at the edge
- single-region-eu — one EU region for v2 launch; multi-region phase 2
- sli-budget — not yet written; expected by 2026-05-05
Stakeholders
- Eng: devon-kim (owner), 2 backend ICs, EM priya-sharma
- Design: anna-rao
- GTM: kai-mendez (Acme AE), nora-bell (CS handoff)
Open questions
How aggressive should the default retry policy be? Default = 3 retries with jitter. Acme's traffic patterns may need a customer-overridable setting — pulled into 2026-04-22-q2-planning for discussion.
Risks
- Migration window collides with billing-migration freeze in late May.
- Acme renewal is conditional on routing v2 GA — see 2026-04-18-acme-qbr.
- Self-hosted edge for northwind-supply is out of scope for v2; they've accepted v1 + read replicas as a stopgap.
KR mapping
- KR2 in 2026-okrs: ship to GA with p95 <200ms, 3 design partners migrated.
Backlinks · 18
↪customers/acme-logistics…see 2026-04-18-acme-qbr — and contingent on order-routing-v2 GA + customer-authored rules. ## Threads - [[meetings/2026…↪customers/northwind-supply…compliance lead is the project sponsor on their side) - order-routing-v2 — they want self-hosted edge, which is out of scope; accept…↪customers/stellar-freight…ut the most engaged. Renewal: September 2026. ## Threads - order-routing-v2 (third migration target) - [[projects/rules-engine-customer…↪customers/vector-foods…are not a great latency proof point. Don't lean on them for order-routing-v2 case studies.↪decisions/deprecate-router-v1…ough. ## Decision Replace, do not refactor. New service is order-routing-v2; old router enters deprecation mode at GA (target mid-June)…↪decisions/single-region-euContext order-routing-v2 needs a launch posture. Multi-region is technically possibl…↪decisions/use-protobuf-internalContext order-routing-v2 needs single-digit-ms internal serialization to hit a <200m…↪meetings/2026-04-18-acme-qbr…VP Eng on their side. ## Top-line - Renewal contingent on order-routing-v2 GA + customer-authored rules in [[projects/rules-engine-cus…↪meetings/2026-04-22-q2-planning…and what owns the freeze window collision. ## Decisions - order-routing-v2 is the headline commit; GA target moved from late May to…↪people/devon-kimStaff engineer, owner of order-routing-v2. Joined Helix from a logistics startup; deep latency/observ…↪people/maya-chen…Helix, ~14 months in. I own the rules engine surface area: order-routing-v2, rules-engine-customer-ui, and the GTM threads…↪people/priya-sharma…d Helix 8 months ago from a payments company. ## Threads - order-routing-v2 - billing-migration - [[meetings/2026-04-14-st…↪people/tom-hayashi…ve]] ## Notes - The billing freeze in late May affects our order-routing-v2 launch window. Coordinate cutover dates. - Has a complete v…↪projects/audit-log-v2…Stakeholders - Eng: devon-kim (shared with order-routing-v2 — same data plane) - GTM: nora-bell handles the…↪projects/billing-migration…t; Maya's stake is the late-May freeze window that overlaps order-routing-v2 launch. ## Goals - Cutover all customers by 2026-05-29 - N…↪projects/rules-engine-customer-uiThe customer-authored rules editor that sits on top of order-routing-v2. First time we're letting customers author their own routin…↪strategy/2026-okrs…ith rules engine as the primary use case. - **KR1.2**: Ship order-routing-v2 to GA with p95 < 200ms, 3 design partners migrated. - **KR1…↪strategy/rules-engine-narrative…if-this-then-that" toy ceiling. The unlock is performance (order-routing-v2) + a UI ops can use (rules-engine-customer-ui)…