Skip to content

MoTeC MCP 0.5.0

Choose a tag to compare

View all tags
@Herbertmt978 Herbertmt978 released this 19 Jul 14:56
v0.5.0
b06e18f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

MoTeC MCP 0.5.0

This release adds an additive 125-tool public surface for local, evidence-led
motorsport workflow planning, resource handling, whole-vehicle analysis,
logging diagnostics, and virtual display design.

Highlights

  • Adds logical-resource and manual-coverage workflows with six explicit
    coverage states, official-source metadata, permission-gated local
    acquisition and admission, installed-help indexing, and bounded read-only
    queries. Vendor manuals, private vehicle material, generated indexes, and
    application assets remain outside the repository.
  • Adds an open-world whole-vehicle catalogue covering 22 system groups, plus
    evidence-bound Vehicle System Profile v2 and Signal Path v2 owners. Catalogue
    knowledge is not target fitment, and an empty search is not evidence of
    absence.
  • Adds original simulation-only C125-primary/C1212-secondary display studies
    with shared semantic channels, request-versus-independent-actual feedback,
    menus, alarms, logging, diagnostics, deterministic previews, and bundle
    validation. They create no native project, generated DBC, device
    configuration, send route, or hardware authority.
  • Adds public resource-admission, dual-display availability, and guarded C127
    controlled-experiment contracts. Reduced and full smoke coverage remains
    synthetic and offline-only; it does not inspect ambient applications or
    prove native hardware capability.
  • Retains configured-root CSV telemetry support for summaries, channel
    discovery, selected numeric queries, and aggregate quality observations.
    Results are evidence for diagnosis, not a substitute for mechanical checks,
    calibration proof, or a native i2/Race Studio log.

Declared Ultima coverage

The portable expert workflow covers the declared PDM30, PDM15, C125, C1212,
M150, MoTeC rotary controller, MoTeC 8-button and 15-button boxes, AiM
RBI-WW-10 steering-wheel controls, AiM TPMS, Delta ABS, Holinger MXT,
paddle-shift auxiliary kit, and reverse camera. These are candidate devices
and integration requirements until the exact fitted revisions, firmware,
packages, wiring, CAN definitions, licences, configurations, and private target
files are supplied and admitted.

Compatibility and installation

The 0.5.0 public surface is additive: existing MCP tool names remain available,
and v1 profile/signal/capability surfaces remain conservative compatibility
paths. Upgrade by installing locked dependencies, building the server, and
re-registering or restarting the MCP so the 125-tool inventory is loaded.

A reduced installation supports offline workflows. Full readiness asks for the
separately authorized installed application/help inputs required by a selected
live or evidence-capture route. Logs, private configurations, manuals,
screenshots, and generated local indexes must stay in authorized local storage,
outside the clone.

Follow setup from GitHub, the
portable resource workflow, and
the Ultima dual-display builder. The exact
machine-readable release and UAT contract is
data/release-metadata.json.

Native-UAT status

The shipped virtual display work is not native display support. Current
machine-readable dispositions are:

  • c125-native-display=native-unavailable
  • c1212-native-display=native-unavailable
  • red-mini-c127-controlled-experiment=native-unavailable

C125 and C1212 remain unavailable because their product-specific native
bindings are unproven. The Red Mini controlled experiment remains unavailable
because the production facade reports
controlled-experiment-native-driver-unavailable. No native C125/C1212 manager,
file suffix, project format, generated DBC, send route, or completed hardware
UAT is claimed. A later C127 experiment requires the exact version-bound driver,
private evidence, fresh single-use authorization, receipt, diff, save/reopen
proof, and clean recovery.

Catalogue and repository-file identities

All three SHA-256 values use the machine-readable
catalogueHashBasis=canonical-utf8-lf: decode as UTF-8 and normalize CRLF to
LF before hashing. Windows and LF checkouts therefore verify the same content.

  • Product knowledge snapshot: motorsport-product-knowledge
    2026-07-17.1, checked 2026-07-17 (schema 1.0.0), repository-file
    SHA-256 8c9d2d37e727a1f9291b1529ac9405928f5c7cc3550cfd68a2d9b4dc431eca64.
  • Whole-vehicle catalogue:
    whole-vehicle-instrumentation-and-control-catalog 1.0.0 (schema
    1.0.0), repository-file SHA-256
    fd6e183e3e1b4d9969b177455f3fee1c61ec974d3aa38c1ae534de075db9bd81.
  • Logical-resource catalogue: motorsport-logical-resource-catalog (schema
    1.0.0; no separate catalogue-version field), repository-file SHA-256
    44ce407be8ad01a05508023c40dea3a434f46bf3e84b142d1c22a1a3019146da.

These are canonical repository-file identities, not target fitment,
manual-content, software-installation, configuration, or hardware evidence.

Licence and evidence boundaries

Copyright © 2026 Herbertmt978. All rights reserved. Use and modification are permitted only by Herbertmt978 and people explicitly authorized in writing. Redistribution is prohibited.

Previously published v0.3.0 and v0.4.0 copies retain their historical MIT
terms. Public visibility of later proprietary revisions does not grant use,
modification, or redistribution rights.

A green offline test, catalogue match, virtual bundle, installed application,
or local resource observation does not prove vehicle wiring, CAN traffic,
sensor health, calibration correctness, activation, connected-device state, or
safe hardware operation.

Assets 2
Loading