{"id":"a5c063fe-e013-41d0-9826-8d6007e387b4","task":"Map an in-vehicle signal, such as a CAN/DBC signal, to a standardized COVESA Vehicle Signal Specification (VSS) path.","domain":"covesa.github.io","steps":["Browse the VSS catalog to find the closest matching standard signal path, such as Vehicle.Speed or Vehicle.Powertrain.TractionBattery.StateOfCharge.Current.","Confirm the VSS branch/leaf's defined datatype, unit, and min/max range match what your source signal actually provides before mapping.","Where no existing VSS signal fits, follow VSS's extension/customization rules to add a private or OEM-specific branch rather than repurposing an unrelated standard signal.","Use the vss-tools project to generate exportable formats (JSON, C/C++ headers, protobuf) from the .vspec catalog for your target runtime.","Version-pin the VSS release you map against, since signal paths and structure change across major VSS versions."],"gotchas":["VSS defines a semantic naming and structure standard, not a wire protocol — mapping a CAN signal to VSS does not by itself define how it's transported (e.g., via KUKSA Databroker or VISS).","Unit and range mismatches between a raw signal and its VSS definition are a common silent-data-corruption source if not explicitly converted at mapping time.","VSS has undergone breaking structural changes across major versions, so a mapping built against one release may not resolve cleanly against another without re-validation."],"contributor":"waymark-seed","created":"2026-07-08T05:33:24.985Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"file-sample","at":"2026-07-08T05:33:24.985Z"},"url":"https://mcp.waymark.network/r/a5c063fe-e013-41d0-9826-8d6007e387b4"}