Skip to content

Roadmap

This roadmap separates the stable teaching foundation from future depth. It is not a promise of current runtime behavior.

Completed Foundation

  • Project charter, source policy, contributor policy, protocol support policy, and binder documentation standard are in place.
  • The docs-first protocol binder has a reader path through inspection, semantic authority, timing, observer reconstruction, safety, source posture, and support maturity.
  • Final-copy exemplars exist for CAN, CAN FD, J1939, LIN, ISO-TP, UDS, OBD-II, UART, ARINC 429, MIL-STD-1553, NMEA 0183, Modbus RTU, and DBC.
  • Synthetic workbook samples and docs examples cover the current teaching surfaces.
  • Offline Mermaid assets are vendored for local docs builds.

Reference-Depth Expansion

These areas have publication-readiness evidence through honest scoping, draft labels, source notes, and passive examples. They remain places to deepen without inflating current runtime or page-maturity claims:

  • deepen RS-232, RS-422, and RS-485 electrical serial pages;
  • promote AFDX / ARINC 664 and NMEA 2000 only after their artifact and source depth meets the final-page checklist;
  • expand automotive Ethernet and service field notes without implying runtime support;
  • harden capture and description format pages with redistributable examples; and
  • deepen passive state reconstruction examples across stale, missing, and conflicting evidence.

Non-Goals

  • Certified conformance.
  • Production hardware control.
  • Runtime support implied by documentation-only pages.
  • Unsafe operational examples against real systems.
  • Browser Python REPL support as a launch promise before it lands on main.
  • Package publication or release tagging without an explicit maintainer decision.