+ {tal.tolkning} +
++ Starkaste evidenstyp per ärende. Ett mätvärde räknas som E4 endast med spårbart mätdon. +
++ Var arbetet ligger, i ALVA-termer. Övervikt i Localization betyder att fel hittas men inte fastställs. +
++ Kontroller som oftast hoppas över, med dokumenterat undantag. Ett steg högt upp i listan är antingen + felskrivet eller kräver utrustning verkstaden inte har. Bägge går att åtgärda — men bara om man vet + vilket steg det gäller. +
+ {data.undantag.length === 0 ? ( ++ ALVA connects to the systems the workshop already runs. The interface is profile-driven: a profile + describes what a category of system expects, and is marked validated only after it has been run against + the vendor’s actual interface. +
+ ++ A profile at draft has an interface but has not been run against the vendor. Listing + it as ready would be the fastest route to a failed rollout, because the workshop plans around it. +
++ An integration subscribes to what it needs. Deliveries are signed with HMAC over timestamp and body; + the timestamp is inside the signature so a captured delivery cannot be replayed. +
++ Readings become evidence, not an attachment. Provenance travels with every entry, so + a value that arrived from outside never looks like something the technician measured. Where the + instrument identity is supplied it is retained — without it the value is graded E1 rather than E4. +
+
+{`POST /api/arenden/{arendeId}/protokoll
+Authorization: Bearer
+
+{
+ "kalla": "Diagnostic tool, bay 3",
+ "profil": {
+ "felkoder": { "vag": "dtcs", "kod": "code", "text": "description" },
+ "matvarden": { "vag": "liveData", "beskrivning": "name",
+ "varde": "value", "enhet": "unit",
+ "instrumentId": "toolSerial" }
+ },
+ "protokoll": { "...": "vendor payload, unchanged" }
+}`}
+
+