Skip to content

ADR 0003: Rider Modality Matrix — Base Case OVRB, VOR/VRS Retired as Aliases

  • Status: Accepted
  • Date: 2026-09-17
  • Deciders: Huashan Wang
  • Related: ADR 0001 (Phase 4 BU catalog), docs/reference/terminology.md, models/vrs.md

Context

The repo carried two labels for the rider model — vrs.md (file name) and "VOR" (display name) — with unstated scope. The owner clarified the original intent: rider scenarios differ along two dimensions, {vehicle without battery, battery} × {purchase, rent}, forming a 2×2 modality matrix. The intended base case was "Own Vehicle, Rent Battery" (displayed as VOR), with other modalities possible and relevant to warranty modeling.

Decision

  1. Two named dimensions for rider market segmentation:
  2. Vehicle tenure — own / rent (motorcycle without battery)
  3. Battery tenure — own / rent (rent = swap or subscription, i.e. BaaS)
  4. Four modality codenames:
  5. OVRB — Own Vehicle, Rent Battery — the base case
  6. OVOB — Own Vehicle, Own Battery
  7. RVRB — Rent Vehicle, Rent Battery
  8. RVOB — Rent Vehicle, Own Battery
  9. OVRB replaces VOR and VRS. Both legacy labels become registered aliases retained in the terminology page for traceability. File/doc renames happen in Phase 4 with link hygiene; nothing is deleted.
  10. Scope discipline: near-term modeling focuses on the OVRB base case. Other modalities are registered but not modeled until needed.
  11. Warranty linkage: battery tenure determines who carries SOH/degradation risk — rented: operator (batch-SOH engine required); owned: rider (residual value / second-use economics apply, eMe-relevant).

Consequences

  • Positive: one unambiguous base-case symbol aligned with the industry-standard "vehicle purchase + battery subscription" arrangement; clean mapping to adopted sources and to Maxwell's v12 rider line; modality matrix generalizes cleanly if non-base cases are modeled later.
  • Neutral: models/vrs.py / models/vrs.md keep their file names until Phase 4 renames them (moves, not deletions).
  • Risk: none material; legacy labels documented as aliases prevents confusion in the interim.