Maturity Map
This map tells reviewers what to treat as implemented, docs-first, draft, or
future work. The binder deliberately leads implementation, so runtime status and
page maturity must stay separate.
Final-Copy Teaching Surfaces
| Surface |
Runtime status |
Binder status |
Review focus |
| CAN |
Thin object and runnable docs example |
final-copy |
Frame anatomy, arbitration, cadence, source notes. |
| CAN FD |
Thin object and runnable docs example |
final-copy |
Larger payload metadata, DLC boundary, passive diagnostics context. |
| J1939 |
Identifier parser and runnable docs example |
final-copy |
Composition over CAN, PGN/PDU rules, source-address evidence. |
| LIN |
Frame/checksum example |
final-copy |
Protected identifier, checksum, schedule authority. |
| ISO-TP |
Reassembly example |
final-copy |
Transport shape versus diagnostic meaning. |
| UDS |
Synthetic observed exchange example |
final-copy |
Diagnostic semantics remain catalog/source-dependent. |
| UART |
Framing model |
final-copy |
Bit order, parity, sampling hypothesis, ambiguity. |
| ARINC 429 |
Word parser and runnable docs example |
final-copy |
Label/parity simplification, SSM, wrong-authority risk. |
| MIL-STD-1553 |
Word and transaction model |
final-copy |
Command/status/data transaction authority and timing. |
| NMEA 0183 |
Runnable docs example |
final-copy |
Talker/formatter authority, checksum, sentence cadence. |
| Modbus RTU |
Runnable docs example |
final-copy |
Observed request/response shape, CRC evidence, register-map authority. |
| DBC |
Runnable docs example |
final-copy; Enriched semantic-authority exemplar |
Semantic authority, database provenance, false precision. |
| Observer state reconstruction |
Runnable docs example |
final-copy |
Passive freshness, missingness, conflict, and confidence boundaries. |
Draft Core Lab Scope
| Surface |
Runtime status |
Binder status |
Review focus |
| RS-232 |
no current runtime example |
draft-core-lab |
Electrical interface versus byte/application meaning. |
| RS-422 |
no current runtime example |
draft-core-lab |
Differential point-to-point evidence and carried protocol boundary. |
| RS-485 |
no current runtime example |
draft-core-lab |
Multipoint electrical timing, driver-enable ambiguity, carried protocol boundary. |
| AFDX / ARINC 664 |
conceptual runnable docs example |
draft-core-lab |
Virtual-link observation only; no Ethernet/IP/UDP/PCAP parser claim. |
| NMEA 2000 |
no current runtime example |
draft-core-lab |
Marine PGN/fast-packet posture without certified semantics. |
| OBD-II |
Synthetic PID example |
draft-core-lab |
Runtime teaching profile pending claim-level formula provenance. |
Field Notes And Docs-Only Pages
| Surface group |
Runtime status |
Binder status |
Review focus |
| ASC and candump Log |
limited one-line synthetic record examples |
field-note |
Capture-record provenance, passive examples, no live interface setup. |
| MDF/MF4, BLF, PCAP/PCAPNG, ARXML, LDF, EDS/DCF |
docs-only |
draft-structure-only or field-note |
Source posture and parser-boundary honesty. |
| SOME/IP, DoIP, CAN XL, FlexRay, SENT, PSI5, MOST |
docs-only |
draft-structure-only |
Field-note status, passive diagnostics/service wording. |
| ARINC 629, ARINC 717, ARINC 825, SpaceWire, TTEthernet |
docs-only |
draft-structure-only |
Public source context without final-copy claims. |
| CANopen, EtherCAT, PROFINET, Modbus TCP |
docs-only |
draft-structure-only |
Industrial field-note posture and no runtime support claim. |
What Is Not Mature Yet
- Browser Python REPL support is not implemented or advertised.
- Draft Core Lab scope is not a claim of final-copy quality.
- Field-note and docs-only pages are not runtime parser guarantees.
- The site does not claim conformance to any protocol standard.