# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T22:42:16Z", "synthesisSha256": "8f5ee2cdcc106ebdb1f34c8ae47f76d66edcce9e9c3c2dcbd5314beb6354a261", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-OBJ-023", "registryId": "vr.wm-obj-023", "name": "Meter / Measuring Instrument", "version": "0.1.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.OBJ.DEV" ], "tags": [ "meter", "measuring", "instrument", "phy.obj.dev" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-obj-023-meter-measuring-instrument/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-023", "model": { "registry_id": "vr.wm-obj-023", "model_id": "WM-OBJ-023", "name": "Meter / Measuring Instrument", "entry_kind": "entity", "purpose": "Describe one measuring instrument, its measurement capabilities, channel or assigned-value semantics, calibration evidence and qualified suitability for use.", "scope_statement": "One identifiable physical instrument used alone or with supplementary devices. Includes indicating instruments and material measures; a single instrument can also constitute a measuring system. A logical channel is a local interpretation context, not necessarily a digital port. Multi-instrument system masters, observations and time-series collections remain external. All operations below are proposed local record operations, not device control.", "in_scope": [ "Instrument identity, recognition evidence, local physical properties, deployment and measurement context", "Conditional channels or assigned quantities, performance envelopes, calibration and result-traceability evidence references", "Qualified legal status, metrologically relevant configuration, maintenance decisions and reading interpretation bindings" ], "out_of_scope": [ "Generic hardware inventory, party, location, asset-lifecycle, software and observation master records", "Billing, tariff calculation, clinical decisions, control loops, firmware deployment, calibration execution or physical intervention", "Universal metrology law, certification, unrestricted remote acquisition and executable uncertainty or conformity engines" ], "boundary_notes": [ { "neighbor": "WM-OBJ-008 Device / Sensor / Compute HW", "distinction": "Candidate parent is retained as an optional alignment. Instruments need not compute or have digital sensors; generic hardware identity and maintenance are referenced without requiring a hardware runtime or excluding material measures.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-MAT-008 Observation / Measurement Record", "distinction": "The instrument owns the interpretation contract and links. Observations own individual results, actual measurement conditions, time, uncertainty and provenance; no observation is mandatory for an unused instrument.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "neighbor": "WM-DAT-010 Time Series / Observation Collection", "distinction": "Streams and collected results retain external identity and lifecycle. Instrument replacement does not silently splice cumulative readings or transfer instrument identity.", "source_refs": [ "SRC-003", "SRC-004" ] }, { "neighbor": "WM-OBJ-022 Asset Lifecycle Record", "distinction": "Local metrological status refers to asset events without owning procurement, depreciation or physical disposal. The instrument may itself be an asset, not only a component mounted on one.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "neighbor": "WM-SFT-011 Software Configuration and measuring system", "distinction": "Pin metrologically relevant configuration and supplementary-device references. Software lifecycle and a multi-instrument system master are separate. Pure virtual estimators require an explicit extension beyond this physical instrument scope.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "International vocabulary of metrology - Basic and general concepts and associated terms", "organization": "Joint Committee for Guides in Metrology", "url": "https://www.bipm.org/documents/20126/2071204/JCGM_%20200_2012.pdf/f0e1ad45-d337-bbeb-53a6-15fe649d0ff1", "version_or_date": "JCGM 200:2012, third edition with minor corrections", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Sections 2.39, 2.41, 2.44, 3.1-3.6 and chapter 4 ground the instrument boundary and distinguish calibration, verification and performance concepts." }, { "id": "SRC-002", "title": "Guidelines for the determination of recalibration intervals of measuring equipment", "organization": "International Organization of Legal Metrology and International Laboratory Accreditation Cooperation", "url": "https://www.oiml.org/en/files/pdf_d/d010-e22.pdf", "version_or_date": "ILAC-G24:2022 / OIML D 10:2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Sections 4-6 support risk-based interval decisions, intermediate checks and historical calibration evidence; no universal interval is inferred." }, { "id": "SRC-003", "title": "SensorThings API Part 1: Sensing", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/18-088/18-088.html", "version_or_date": "Version 1.1, OGC 18-088", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Sections 8.2.1-8.2.8 distinguish devices, sensors, streams, observed properties, observations and features; section 8.2.7 exposes server-assigned time semantics." }, { "id": "SRC-004", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/", "version_or_date": "W3C Recommendation 19 October 2017, deliberately pinned edition", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Sections 4 and 5 support observation and deployment boundaries, conditions and capability descriptions. This is a selected edition, not a latest-version assertion." }, { "id": "SRC-005", "title": "Metrological Traceability: Frequently Asked Questions and Policy", "organization": "National Institute of Standards and Technology", "url": "https://www.nist.gov/metrology/metrological-traceability", "version_or_date": "Official living page accessed 2026-10-07; update version not independently pinned", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Sections 3 and 5.1 distinguish result traceability from equipment labels and fitness for purpose; calibration alone is insufficient." }, { "id": "SRC-006", "title": "Directive 2014/32/EU on measuring instruments", "organization": "European Parliament and Council of the European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014L0032", "version_or_date": "Original act of 26 February 2014; current consolidation and national applicability unresolved", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Articles 1-4 and Annex I provide a scoped legal-profile example including conditions, identification, result indication and protection of metrological data." }, { "id": "SRC-007", "title": "The International System of Units", "organization": "International Bureau of Weights and Measures", "url": "https://www.bipm.org/documents/20126/41483022/SI-Brochure-9-EN.pdf/2d2b50bf-f2b4-9661-f402-5f9d66e4b507", "version_or_date": "SI Brochure, ninth edition, English version 4.01 as displayed by retrieved PDF", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Chapter 5 supports quantity, numerical value, unit and uncertainty expression; no complete unit-conversion implementation is supplied." }, { "id": "SRC-008", "title": "General requirements for software controlled measuring instruments", "organization": "International Organization of Legal Metrology", "url": "https://www.oiml.org/en/files/pdf_d/d031-e23.pdf", "version_or_date": "OIML D 31:2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T22:40:08Z", "relevance": "Section 6 supports software identity, protected parameters and interface integrity for applicable software-controlled instruments; it is not universal legislation." } ], "structure": { "bundles": [ { "id": "bundle-instrument", "name": "Instrument and context", "description": "Establish the physical subject and its bounded deployment.", "rationale": "A separate concern because establish the physical subject and its bounded deployment. This grouping is a local design proposal.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-identity", "name": "Instrument identity and recognition", "description": "Distinguish an individual instrument from its type, an indication-only terminal and a metering point. Recognition evidence may be incomplete; no serial number or electronic interface is universal.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-identity", "name": "Instrument identity and recognition", "description": "Distinguish an individual instrument from its type, an indication-only terminal and a metering point. Recognition evidence may be incomplete; no serial number or electronic interface is universal. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "finding-identity-q1", "text": "Which master identifier and scoped aliases identify this physical instrument?", "kind": "identity", "answer_data": [ "data-identity-binding" ] }, { "id": "finding-identity-q2", "text": "Is the item an indicating instrument, a material measure or only a component of a measuring system?", "kind": "classification", "answer_data": [ "data-instrument-class" ] }, { "id": "finding-identity-q3", "text": "Which markings, inspection observations and dimensions distinguish the item from a similar device?", "kind": "evidence", "answer_data": [ "data-recognition-evidence" ] }, { "id": "finding-identity-q4", "text": "Who is the accountable steward, custodian and operator for this instrument?", "kind": "ownership", "answer_data": [ "data-responsibility-bindings" ] } ], "data_elements": [ { "id": "data-identity-binding", "name": "Identity binding", "description": "Authoritative master identifier, namespace, aliases and duplicate-resolution evidence; required for an admitted instance.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-instrument-class", "name": "Instrument class", "description": "Classification assertion, basis, system or component reference and applicability of electronic features.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-recognition-evidence", "name": "Recognition evidence", "description": "Evidence references and optional size, mass, enclosure or scale observations with units, method, uncertainty and observation time; unknown differs from absent.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-responsibility-bindings", "name": "Responsibility bindings", "description": "Role references, authority source and effective periods; ownership, custody and operation are distinct.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Instrument identification record", "description": "Versioned local evidence view for instrument identity and recognition. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-deployment", "name": "Deployment and measurement subject", "description": "Relate the instrument to an installation or temporary use context without equating physical location, platform, measurement point and feature of interest.", "source_refs": [ "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-deployment", "name": "Deployment and measurement subject", "description": "Relate the instrument to an installation or temporary use context without equating physical location, platform, measurement point and feature of interest. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "finding-deployment-q1", "text": "Where is the instrument deployed during the stated effective interval?", "kind": "spatial", "answer_data": [ "data-deployment-binding" ] }, { "id": "finding-deployment-q2", "text": "Which object, flow, sample or other feature is the intended subject of measurement?", "kind": "relationship", "answer_data": [ "data-subject-binding" ] }, { "id": "finding-deployment-q3", "text": "Which supplementary devices or material measures are required by this measurement arrangement?", "kind": "composition", "answer_data": [ "data-system-binding" ] }, { "id": "finding-deployment-q4", "text": "How are installation, removal and temporary relocation evidenced without overwriting earlier bindings?", "kind": "temporal", "answer_data": [ "data-deployment-history" ] } ], "data_elements": [ { "id": "data-deployment-binding", "name": "Deployment binding", "description": "Location or platform reference, installation orientation if material, effective start and end, and evidence.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-subject-binding", "name": "Subject binding", "description": "Feature or measurement-point master reference and role; observation-specific targets stay in observation records.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-system-binding", "name": "System binding", "description": "System master, component identifiers and revisions, connection roles and applicability constraints; references do not transfer ownership.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-deployment-history", "name": "Deployment history", "description": "Dated event references, effective and recording times, supersession and uncertainty of dates.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-deployment", "name": "Deployment binding history", "description": "Versioned local evidence view for deployment and measurement subject. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-semantics", "name": "Indication semantics", "description": "Preserve the meaning and exceptions of instrument indications.", "rationale": "A separate concern because preserve the meaning and exceptions of instrument indications. This grouping is a local design proposal.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-007", "SRC-008" ], "layers": [ { "id": "layer-channel", "name": "Quantity and indication contract", "description": "A versioned channel or assigned-value description binds quantity, unit and interpretation. Analog scales and material measures can be represented without inventing network channels.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "findings": [ { "id": "finding-channel", "name": "Quantity and indication contract", "description": "A versioned channel or assigned-value description binds quantity, unit and interpretation. Analog scales and material measures can be represented without inventing network channels. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ], "questions": [ { "id": "finding-channel-q1", "text": "What quantity kind and measurand definition does this channel or assigned value represent?", "kind": "definition", "answer_data": [ "data-quantity-definition" ] }, { "id": "finding-channel-q2", "text": "Which unit, scale factor, offset and sign convention interpret the original indication?", "kind": "measurement", "answer_data": [ "data-indication-transform" ] }, { "id": "finding-channel-q3", "text": "Is the indication instantaneous, cumulative, interval-based, averaged or an assigned material value?", "kind": "classification", "answer_data": [ "data-indication-kind" ] }, { "id": "finding-channel-q4", "text": "What prevents a changed quantity, unit or multiplier from silently reinterpreting earlier records?", "kind": "constraint", "answer_data": [ "data-semantic-validity" ] } ], "data_elements": [ { "id": "data-quantity-definition", "name": "Quantity definition", "description": "Quantity vocabulary reference, measurand specification, context qualifiers and semantic revision.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] }, { "id": "data-indication-transform", "name": "Indication transform", "description": "Original unit or scale, target unit if transformed, formula revision, coefficient units and sign or direction meaning; no inferred conversion from symbols alone.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] }, { "id": "data-indication-kind", "name": "Indication kind", "description": "Explicit local profile code, interval boundary or averaging definition where relevant, and not-applicable reasons.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] }, { "id": "data-semantic-validity", "name": "Semantic validity", "description": "Effective interval, immutable prior revision, authority and compatibility rule; original readings remain external and preserved.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-channel", "name": "Channel or assigned-value specification", "description": "Versioned local evidence view for quantity and indication contract. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-reading", "name": "Reading boundary and exceptional indications", "description": "Specify how external observation records refer to the instrument and semantic revision. Cumulative differences require explicit reset and rollover evidence; zero, missing and invalid values differ. These are proposed profile safeguards.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-reading", "name": "Reading boundary and exceptional indications", "description": "Specify how external observation records refer to the instrument and semantic revision. Cumulative differences require explicit reset and rollover evidence; zero, missing and invalid values differ. These are proposed profile safeguards. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "finding-reading-q1", "text": "Which instrument and channel revision must each linked observation identify?", "kind": "relationship", "answer_data": [ "data-observation-binding" ] }, { "id": "finding-reading-q2", "text": "How are phenomenon time, result time and receipt time distinguished when the device clock is absent or unreliable?", "kind": "temporal", "answer_data": [ "data-time-contract" ] }, { "id": "finding-reading-q3", "text": "How are observed, estimated, substituted, missing and invalid indications distinguished?", "kind": "quality", "answer_data": [ "data-quality-contract" ] }, { "id": "finding-reading-q4", "text": "What evidence is required to interpret register rollover, reset, reverse flow or replacement?", "kind": "exception", "answer_data": [ "data-register-exceptions" ] } ], "data_elements": [ { "id": "data-observation-binding", "name": "Observation binding", "description": "Observation master reference, instrument identity, channel revision, procedure and feature reference; no value ownership transfer.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-time-contract", "name": "Time contract", "description": "Timestamp origins, clock quality, uncertainty and explicit server-assigned flag; never represent receipt time as measured event time without qualification.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-quality-contract", "name": "Quality contract", "description": "Profile vocabulary, null versus zero rules, fault flags, responsible source and correction lineage.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-register-exceptions", "name": "Register exceptions", "description": "Counter modulus if known, event references, direction semantics and continuity decision; an unexplained negative delta remains unresolved, not automatic consumption.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-reading", "name": "Reading interpretation contract", "description": "Versioned local evidence view for reading boundary and exceptional indications. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-performance", "name": "Capability and calibration", "description": "Separate specified behavior from measured calibration evidence.", "rationale": "A separate concern because separate specified behavior from measured calibration evidence. This grouping is a local design proposal.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-capability", "name": "Performance envelope and behavior", "description": "Capabilities describe what the instrument is specified to do under stated conditions. Resolution, error limits, uncertainty and response behavior are distinct. Nominal specifications do not certify current performance.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-capability", "name": "Performance envelope and behavior", "description": "Capabilities describe what the instrument is specified to do under stated conditions. Resolution, error limits, uncertainty and response behavior are distinct. Nominal specifications do not certify current performance. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "finding-capability-q1", "text": "What measurement interval, resolution, error limits and uncertainty specification apply to each mode?", "kind": "measurement", "answer_data": [ "data-performance-envelope" ] }, { "id": "finding-capability-q2", "text": "Which operating, reference and survival conditions constrain the claimed capability?", "kind": "constraint", "answer_data": [ "data-condition-envelope" ] }, { "id": "finding-capability-q3", "text": "What response time, sampling or indication behavior is specified for the selected mode?", "kind": "process", "answer_data": [ "data-behavior-contract" ] }, { "id": "finding-capability-q4", "text": "Which hazards and failure modes require restricted use or qualified intervention?", "kind": "security", "answer_data": [ "data-hazard-policy" ] } ], "data_elements": [ { "id": "data-performance-envelope", "name": "Performance envelope", "description": "Quantity-valued bounds, resolution, maximum permissible error basis, accuracy-class reference and separately stated uncertainty with conditions and evidence.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-condition-envelope", "name": "Condition envelope", "description": "Environmental and supply limits, influence quantities, stabilization requirements and applicable profile; survival is not proof of accurate operation.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-behavior-contract", "name": "Behavior contract", "description": "Response, settling or averaging characteristics, trigger and mode dependence; unimplemented or unknown features remain explicit.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-hazard-policy", "name": "Hazard policy", "description": "Policy references for electrical, pressure, contamination or other hazards; escalation and permitted handling roles without intervention instructions.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-capability", "name": "Capability and condition sheet", "description": "Versioned local evidence view for performance envelope and behavior. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-calibration", "name": "Calibration evidence and adjustment separation", "description": "Link calibration records to the actual instrument, modes, conditions and revision. Calibration is not adjustment or verification; evidence before and after an intervention must remain distinguishable.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "finding-calibration", "name": "Calibration evidence and adjustment separation", "description": "Link calibration records to the actual instrument, modes, conditions and revision. Calibration is not adjustment or verification; evidence before and after an intervention must remain distinguishable. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "finding-calibration-q1", "text": "Which calibration evidence identifies this instrument, provider, method and covered modes?", "kind": "provenance", "answer_data": [ "data-calibration-binding" ] }, { "id": "finding-calibration-q2", "text": "Which calibration values, corrections and associated uncertainties are supported under the recorded conditions?", "kind": "measurement", "answer_data": [ "data-calibration-content" ] }, { "id": "finding-calibration-q3", "text": "Was an adjustment or repair performed between the as-found and as-left evidence?", "kind": "event", "answer_data": [ "data-intervention-binding" ] }, { "id": "finding-calibration-q4", "text": "Does the certificate apply to the present instrument configuration and intended mode?", "kind": "validation", "answer_data": [ "data-calibration-applicability" ] } ], "data_elements": [ { "id": "data-calibration-binding", "name": "Calibration binding", "description": "Certificate or report master reference and revision, issuing role, instrument identity, date, method and channel coverage.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-calibration-content", "name": "Calibration content", "description": "External result references, covered points or interval, conditions, uncertainty representation and correction validity; no extrapolation is assumed.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-intervention-binding", "name": "Intervention binding", "description": "Intervention and authorization references, configuration revisions, temporal ordering and distinct pre/post evidence; absence of data is unknown.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "data-calibration-applicability", "name": "Calibration applicability", "description": "Reviewed identity, revision and scope match with accepted, rejected or unknown conclusion and assessor evidence.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-calibration", "name": "Calibration evidence index", "description": "Versioned local evidence view for calibration evidence and adjustment separation. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Traceability and use assurance", "description": "Bind result evidence to a qualified use decision.", "rationale": "A separate concern because bind result evidence to a qualified use decision. This grouping is a local design proposal.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-traceability", "name": "Result traceability and measurement need", "description": "Traceability belongs to results. The instrument record holds evidence bindings and limitations; a calibration label or provider name cannot establish fitness for a downstream use.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "finding-traceability", "name": "Result traceability and measurement need", "description": "Traceability belongs to results. The instrument record holds evidence bindings and limitations; a calibration label or provider name cannot establish fitness for a downstream use. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "finding-traceability-q1", "text": "Which documented calibration chain and specified reference support the linked result claim?", "kind": "evidence", "answer_data": [ "data-traceability-chain" ] }, { "id": "finding-traceability-q2", "text": "What measurement need and acceptable uncertainty govern the intended use?", "kind": "requirement", "answer_data": [ "data-measurement-need" ] }, { "id": "finding-traceability-q3", "text": "Who assessed whether the available evidence is adequate for that use and with what limitations?", "kind": "decision", "answer_data": [ "data-fitness-assessment" ] }, { "id": "finding-traceability-q4", "text": "Which missing chain links, uncovered ranges or changed conditions prevent an unqualified traceability claim?", "kind": "exception", "answer_data": [ "data-traceability-gaps" ] } ], "data_elements": [ { "id": "data-traceability-chain", "name": "Traceability chain", "description": "Result and calibration references, reference standards and uncertainty contributions; chain gaps are explicit.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "data-measurement-need", "name": "Measurement need", "description": "Use-case reference, uncertainty requirement, measurand and decision criteria owned by the adopter.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "data-fitness-assessment", "name": "Fitness assessment", "description": "Responsible reviewer, assessment reference, evidence revision, outcome and limits; traceability alone is insufficient.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "data-traceability-gaps", "name": "Traceability gaps", "description": "Explicit unresolved gaps, affected results or periods, escalation role and review state.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-traceability", "name": "Traceability and suitability assessment", "description": "Versioned local evidence view for result traceability and measurement need. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-assurance", "name": "Recalibration and suspect-result management", "description": "Maintain evidence for a use-specific assurance decision. Recalibration intervals and intermediate checks depend on risk and history; a due date is not a universal validity guarantee.", "source_refs": [ "SRC-002", "SRC-005" ], "findings": [ { "id": "finding-assurance", "name": "Recalibration and suspect-result management", "description": "Maintain evidence for a use-specific assurance decision. Recalibration intervals and intermediate checks depend on risk and history; a due date is not a universal validity guarantee. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "finding-assurance-q1", "text": "What interval or trigger policy governs recalibration for this use?", "kind": "requirement", "answer_data": [ "data-recalibration-policy" ] }, { "id": "finding-assurance-q2", "text": "Which intermediate checks or drift evidence show that the instrument remains suitable?", "kind": "quality", "answer_data": [ "data-intermediate-checks" ] }, { "id": "finding-assurance-q3", "text": "What metrological use status applies now and what evidence supports release or restriction?", "kind": "state", "answer_data": [ "data-use-status" ] }, { "id": "finding-assurance-q4", "text": "Which earlier observations and decisions need review after an out-of-limit check?", "kind": "exception", "answer_data": [ "data-impact-review" ] } ], "data_elements": [ { "id": "data-recalibration-policy", "name": "Recalibration policy", "description": "Approved policy revision, risk rationale, usage or elapsed-time trigger, last event and proposed next review; no default annual interval.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-intermediate-checks", "name": "Intermediate checks", "description": "Check records, limits, method, results and reviewer; missing checks cannot be treated as passes.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-use-status", "name": "Use status", "description": "Proposed vocabulary: unassessed, usable-with-scope, restricted, suspect, out-of-service, retired; effective period and authorized assessment required.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-impact-review", "name": "Impact review", "description": "Potential affected time window, external observation or decision references, uncertainty about onset, review owner and disposition; historical values are not silently rewritten.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-assurance", "name": "Metrological assurance review", "description": "Versioned local evidence view for recalibration and suspect-result management. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-control", "name": "Legal and configuration control", "description": "Qualify legal applicability and protected configuration.", "rationale": "A separate concern because qualify legal applicability and protected configuration. This grouping is a local design proposal.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "layers": [ { "id": "layer-legal", "name": "Applicable verification and legal status", "description": "Separate calibration from verification against requirements and legal approval. The cited EU act is a bounded example; applicability, current law and national in-service control require review.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "finding-legal", "name": "Applicable verification and legal status", "description": "Separate calibration from verification against requirements and legal approval. The cited EU act is a bounded example; applicability, current law and national in-service control require review. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "finding-legal-q1", "text": "Which jurisdiction, instrument category and intended use establish the applicable legal metrology profile?", "kind": "authority", "answer_data": [ "data-legal-profile" ] }, { "id": "finding-legal-q2", "text": "Which type, conformity or verification documents apply to this individual instrument?", "kind": "evidence", "answer_data": [ "data-legal-evidence" ] }, { "id": "finding-legal-q3", "text": "Which requirements, decision rule and evidence support the recorded verification outcome?", "kind": "validation", "answer_data": [ "data-verification-assessment" ] }, { "id": "finding-legal-q4", "text": "What restrictions follow from an expired approval, damaged seal or unverified applicability?", "kind": "constraint", "answer_data": [ "data-legal-restrictions" ] } ], "data_elements": [ { "id": "data-legal-profile", "name": "Legal profile", "description": "Profile identifier, territorial and use scope, effective version, reviewing authority and unknown or not-applicable rationale.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-legal-evidence", "name": "Legal evidence", "description": "Certificate or declaration references, issuing authority, instrument or type scope, status and validity conditions; a photograph of a mark is not authentication.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-verification-assessment", "name": "Verification assessment", "description": "Separate verification event and result reference, criteria revision, uncertainty treatment where applicable, assessor and outcome.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "data-legal-restrictions", "name": "Legal restrictions", "description": "Profile-specific limitations, competent reviewer and unresolved state; no automatic legal verdict or permission to break a seal.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-legal", "name": "Legal applicability and verification index", "description": "Versioned local evidence view for applicable verification and legal status. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-configuration", "name": "Software, parameters and protected interfaces", "description": "For applicable software-controlled instruments, preserve the identity of metrologically relevant software and parameter states. A readable interface does not authorize a command, software change or seal intervention.", "source_refs": [ "SRC-006", "SRC-008" ], "findings": [ { "id": "finding-configuration", "name": "Software, parameters and protected interfaces", "description": "For applicable software-controlled instruments, preserve the identity of metrologically relevant software and parameter states. A readable interface does not authorize a command, software change or seal intervention. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-006", "SRC-008" ], "questions": [ { "id": "finding-configuration-q1", "text": "Which software and parameter revisions were effective for the measurement configuration?", "kind": "identity", "answer_data": [ "data-metrological-configuration" ] }, { "id": "finding-configuration-q2", "text": "Who may inspect or change protected parameters and under what explicit authority?", "kind": "access", "answer_data": [ "data-parameter-authority" ] }, { "id": "finding-configuration-q3", "text": "What evidence records intervention, failed integrity checks or relevant interface faults?", "kind": "security", "answer_data": [ "data-integrity-evidence" ] }, { "id": "finding-configuration-q4", "text": "What re-evaluation is required after a software or metrologically relevant parameter change?", "kind": "lifecycle", "answer_data": [ "data-configuration-impact" ] } ], "data_elements": [ { "id": "data-metrological-configuration", "name": "Metrological configuration", "description": "Configuration master reference, legally relevant identifiers if applicable, parameter-set revision and validity interval; not applicable for a purely material measure.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "data-parameter-authority", "name": "Parameter authority", "description": "Role and policy reference, authorized action scope, expiry and separation of inspection from mutation; secrets remain outside the record.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "data-integrity-evidence", "name": "Integrity evidence", "description": "External audit or event references, inspection provenance and status; checksum or seal presence alone is not proof of authenticity.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "data-configuration-impact", "name": "Configuration impact", "description": "Changed revision, affected channels and calibration/verification review references, restrictions and authorized release evidence; no automatic grandfathering.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-configuration", "name": "Metrological configuration binding", "description": "Versioned local evidence view for software, parameters and protected interfaces. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Continuity and exchange", "description": "Keep history and external projections coherent.", "rationale": "A separate concern because keep history and external projections coherent. This grouping is a local design proposal.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-008" ], "layers": [ { "id": "layer-continuity", "name": "Lifecycle and replacement continuity", "description": "Record local metrological consequences of asset events. Retirement, reassignment and replacement preserve distinct identities and the interpretation of earlier results.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-continuity", "name": "Lifecycle and replacement continuity", "description": "Record local metrological consequences of asset events. Retirement, reassignment and replacement preserve distinct identities and the interpretation of earlier results. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "questions": [ { "id": "finding-continuity-q1", "text": "Which commissioning, service, transfer or retirement event changed the metrological context?", "kind": "lifecycle", "answer_data": [ "data-lifecycle-events" ] }, { "id": "finding-continuity-q2", "text": "Which successor instrument replaces this one while the measurement point remains the same?", "kind": "identity", "answer_data": [ "data-replacement-binding" ] }, { "id": "finding-continuity-q3", "text": "Which retention, dispute hold and disposal policy applies to local calibration and interpretation evidence?", "kind": "retention", "answer_data": [ "data-evidence-disposition" ] }, { "id": "finding-continuity-q4", "text": "Who may release an instrument from a local restriction and which evidence is required?", "kind": "decision", "answer_data": [ "data-release-decision" ] } ], "data_elements": [ { "id": "data-lifecycle-events", "name": "Lifecycle events", "description": "Asset-event references, effective time, record time, event authority and local impact.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "data-replacement-binding", "name": "Replacement binding", "description": "Separate predecessor and successor master identities, deployment boundary and supporting event; never reuse an instrument identity for a replacement.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "data-evidence-disposition", "name": "Evidence disposition", "description": "Adopter policy, purpose, expiry, holds, payload erasure and minimal tombstone rules; no blanket indefinite retention.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "data-release-decision", "name": "Release decision", "description": "Authorized assessment reference, scope, configuration, required checks and refusal reason; record release is not physical actuation.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-continuity", "name": "Instrument continuity record", "description": "Versioned local evidence view for lifecycle and replacement continuity. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-exchange", "name": "Interoperability and controlled observation access", "description": "Map to external sensor and observation models with explicit losses. Governance choices are local design policy. No live adapter, unrestricted collection right or source-standard conformance is supplied.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "finding-exchange", "name": "Interoperability and controlled observation access", "description": "Map to external sensor and observation models with explicit losses. Governance choices are local design policy. No live adapter, unrestricted collection right or source-standard conformance is supplied. Proposed research grouping; sources ground the concepts, not this local schema.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "finding-exchange-q1", "text": "How does this profile map instrument, channel and observation references to the selected external schema version?", "kind": "interoperability", "answer_data": [ "data-exchange-mapping" ] }, { "id": "finding-exchange-q2", "text": "Which examples expose loss of units, quality flags, assigned timestamps or configuration history in exchange?", "kind": "validation", "answer_data": [ "data-exchange-tests" ] }, { "id": "finding-exchange-q3", "text": "What purpose and authority permit access to observations that could reveal household or personal activity?", "kind": "privacy", "answer_data": [ "data-observation-access" ] }, { "id": "finding-exchange-q4", "text": "Which artifact or field restrictions must accompany an exported instrument view?", "kind": "access", "answer_data": [ "data-export-view" ] } ], "data_elements": [ { "id": "data-exchange-mapping", "name": "Exchange mapping", "description": "Versioned SensorThings or SSN mapping, target identifiers, field semantics, unmapped concepts and test evidence; an OGC Sensor can describe a procedure and is not an automatic physical-identity match.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-exchange-tests", "name": "Exchange tests", "description": "Fixture references, expected behavior and unresolved losses; planned tests are not completed conformance claims.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-observation-access", "name": "Observation access", "description": "Policy and lawful authority reference, recipient, purpose, minimization and expiry; consent is not asserted as the only possible basis.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "data-export-view", "name": "Export view", "description": "Recipient policy, redaction rules for sensitive locations and evidence, authorization decision and export record; reading access never grants control permission.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "artifact-exchange", "name": "Interoperability and access profile", "description": "Versioned local evidence view for interoperability and controlled observation access. Source documents retain independent identity and access controls.", "media_or_form": [ "structured record", "human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Keep artifact identity separate from instrument identity, revision, event time and content digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-bind-context", "name": "Bind measurement context", "description": "Attach an evidenced deployment and supplementary-device binding. Proposed, unimplemented local operation.", "inputs": [ "Instrument master identity", "Context references and effective interval" ], "outputs": [ "Validated local binding revision or unresolved-reference refusal" ], "preconditions": [ "Local actor, purpose and expected record revision are authorized.", "All identities resolved; steward may edit context; interval conflicts reviewed" ], "effects": [ "Append context revision; leave location, system and asset masters unchanged", "Record actor, source evidence, prior and new revision; reject stale concurrent updates." ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "function-revise-semantics", "name": "Revise indication semantics", "description": "Propose a new channel or assigned-value contract without rewriting prior readings. Proposed, unimplemented local operation.", "inputs": [ "Prior revision", "Quantity, unit and transformation evidence", "Effective time" ], "outputs": [ "Candidate semantic revision and compatibility report or refusal" ], "preconditions": [ "Local actor, purpose and expected record revision are authorized.", "Authorized semantic steward; current revision matches; dimensional and temporal checks passed" ], "effects": [ "Append new contract with previous revision link; no instrument parameters or observations changed", "Record actor, source evidence, prior and new revision; reject stale concurrent updates." ], "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] }, { "id": "function-link-calibration", "name": "Link calibration evidence", "description": "Record scope and provenance of an external calibration report. Proposed, unimplemented local operation.", "inputs": [ "Certificate reference", "Instrument and configuration identifiers", "Covered modes and conditions" ], "outputs": [ "Evidence binding with applicability accepted, rejected or unknown" ], "preconditions": [ "Local actor, purpose and expected record revision are authorized.", "Reviewer authorized to record evidence; artifact accessible; identity and revision match checked" ], "effects": [ "Append evidence assessment; never infer verification, adjustment or blanket result traceability", "Record actor, source evidence, prior and new revision; reject stale concurrent updates." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "function-assess-use", "name": "Record metrological use assessment", "description": "Record an authorized reviewer decision with unresolved evidence explicit. Proposed, unimplemented local operation.", "inputs": [ "Measurement need", "Calibration, check and drift evidence", "Interval policy and current configuration" ], "outputs": [ "Scoped usable, restricted or unknown assessment with reasons" ], "preconditions": [ "Local actor, purpose and expected record revision are authorized.", "Qualified reviewer role and policy; evidence revisions pinned; no unresolved identity conflict" ], "effects": [ "Append local status assessment; no device release, billing or legal outcome is executed", "Record actor, source evidence, prior and new revision; reject stale concurrent updates." ], "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "function-flag-impact", "name": "Flag suspect measurement context", "description": "Record a potential affected period after changed configuration or failed checks. Proposed, unimplemented local operation.", "inputs": [ "Fault or intervention evidence", "Potential onset interval", "External observation index" ], "outputs": [ "Local impact-review record and unresolved scope" ], "preconditions": [ "Local actor, purpose and expected record revision are authorized.", "Authorized assurance role; preserve uncertainty about onset and historical evidence" ], "effects": [ "Add review flags and external references; do not alter observations or notify external parties", "Record actor, source evidence, prior and new revision; reject stale concurrent updates." ], "source_refs": [ "SRC-002", "SRC-008" ] }, { "id": "function-export-view", "name": "Prepare controlled instrument view", "description": "Construct a proposed local projection with documented semantic losses. Proposed, unimplemented local operation.", "inputs": [ "Target schema revision", "Recipient and purpose", "Access policy", "Instrument revision" ], "outputs": [ "Redacted view and mapping-loss report or access refusal" ], "preconditions": [ "Local actor, purpose and expected record revision are authorized.", "Recipient authorization and field-level policy checked; no unapproved sensitive payload" ], "effects": [ "Create local export artifact and provenance entry; no external delivery or device command", "Record actor, source evidence, prior and new revision; reject stale concurrent updates." ], "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "composition": [ { "target": "WM-OBJ-008", "relation": "ALIGN", "purpose": "Candidate registry parent; specialize measurement semantics without requiring computation or duplicating generic hardware master functions.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-MAT-008", "relation": "REFERENCE", "purpose": "Observation master owns results and actual measurement provenance; pin instrument and channel revision references.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-DAT-010", "relation": "REFERENCE", "purpose": "Time-series master owns collections and stream retention; only interpretation and binding metadata are local.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-OBJ-022", "relation": "REFERENCE", "purpose": "Asset lifecycle owns physical lifecycle events; retain only their metrological impact and evidence bindings.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "target": "WM-SFT-011", "relation": "REFERENCE", "purpose": "Conditional software configuration reference for relevant instruments; no configuration deployment or general software lifecycle here.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "OGC SensorThings API 1.1 / W3C SSN 2017", "relation": "ALIGN", "purpose": "Conceptual alignments only; physical instrument identity is not interchangeable with procedure, platform or stream identity.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Adopting Dimension declares an accountable instrument steward and authoritative master namespace.", "Pin scope, use and jurisdiction profiles, observation and asset bindings, role authority and review status.", "Publish local specification, storage, interface and process bindings with explicit unknowns; no product or company is a model owner." ], "namespace_guidance": "Stable model and local IDs contain no dates. Separate instance identity from physical labels, metering points, channel identities, revision and content digest.", "registry_links": [ "vr.wm-obj-023", "WM-OBJ-008 candidate parent; runtime binding unpinned", "WM-MAT-008 and WM-DAT-010 external data ownership" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve original quantity representation and semantic revision; normalize only through evidenced, versioned mappings.", "Keep uncertainty, error limits, resolution, calibration, adjustment and verification distinct; unknown is not pass or zero." ], "patch_rules": [ "Require authorized actor, expected prior revision and evidence; append supersession links with effective and recording time.", "A new multiplier, unit, firmware or deployment binding never retroactively rewrites historical results." ], "compatibility_rules": [ "Changed quantity kind, counter interpretation or identity boundary requires explicit migration review and versioning.", "Standard alignments do not establish conformance; losses in time origin, uncertainty or flags block an unqualified export." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z for instants. Separate event or effective time, phenomenon time, result time and observation/ingestion time. Preserve time origin, clock uncertainty and server-assigned flags. Keep a date-only certificate date as a date; do not fabricate precision.", "serial_naming_rule": "Stable artifact identifier plus separate revision and optional sequence; filenames and timestamps are not identities.", "integrity_rule": "Retain source digest, issuer reference, scope and revision. Digests detect change but do not establish authenticity, measurement truth or legal validity; restricted originals follow retention policy." }, "policies": [ "These governance and CRUD rules are proposed local design choices, not quoted requirements of every cited standard.", "Qualified authorization and explicit scope are required for operational adoption. The model never authorizes hazardous intervention, bypassing seals, adjustment, firmware changes or remote actuation.", "Purpose-limited access protects household patterns, personal data and sensitive locations. Applicable authority must be reviewed; consent is not assumed to be the sole lawful basis.", "Safety, legal applicability and conformity remain profile-specific; no automated billing or clinical use is certified." ], "crud": { "read": [ "Resolve pinned revision and access policy; display evidence limits and stale or unknown status." ], "create": [ "Require master identity, subject classification, accountable steward and provenance; allow other facts to remain unknown with a completion obligation." ], "update": [ "Reject stale concurrent versions; append evidence-backed revisions and preserve the observation interpretation at its effective time." ], "delete": [ "Retire the local record through an authorized retention and disposal policy. Respect dispute holds and lawful payload deletion; preserve only permitted minimal tombstones.", "Deleting a local binding does not delete observations, certificates, software masters or the physical instrument. Do not retain sensitive payload indefinitely merely to preserve history." ] }, "roles": [ { "name": "Instrument steward", "responsibilities": [ "Resolve identity, custody and scope; maintain context bindings." ] }, { "name": "Metrology reviewer", "responsibilities": [ "Assess calibration applicability, uncertainty need and assurance evidence within delegated competence." ] }, { "name": "Operator", "responsibilities": [ "Report actual conditions and faults; act only under the applicable operating policy." ] }, { "name": "Legal profile reviewer", "responsibilities": [ "Review jurisdiction and use-specific legal applicability and verification evidence." ] }, { "name": "Data custodian", "responsibilities": [ "Enforce access, retention and controlled external mappings." ] }, { "name": "Model maintainer", "responsibilities": [ "Version the proposed schema and keep holds and source limitations visible." ] } ], "access": { "default_rule": "Deny by default; authorize by role, purpose, instrument scope and evidence sensitivity. Observation access and device control are separate permissions.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Explicitly authorized redacted public views may expose non-sensitive type or capability data.", "A governed emergency or statutory access exception requires named authority, limited scope, expiry and review; never assume an exception." ], "audit_requirements": [ "Record actor, purpose, authority, resource revision, action and outcome for reads of sensitive evidence and for mutations or exports.", "Do not record credentials or unrestricted personal payloads in audit metadata; audit service master remains external." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md", "spec.yaml", "Adopting Dimension authority, access and retention policy", "Pinned instrument profile, bindings and evidence before any operation" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one physical measuring instrument, including material measures, conditional channel semantics, calibration and result-traceability evidence, qualified use status and controlled continuity. Separate frozen local no-tools self-audit completed. Reviewable draft only; independent review, source verification, applicable profiles and executable conformance remain holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Physical instrument, type, point and artifact identity are distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Metrological impacts reference external asset events." }, { "dimension": "relationships", "status": "covered", "notes": "Observation, stream, platform, system and configuration links preserve ownership." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, phenomenon, result and receipt times preserve provenance and precision." }, { "dimension": "provenance", "status": "covered", "notes": "Calibration, configuration and interpretation revisions link to source evidence." }, { "dimension": "ownership", "status": "covered", "notes": "Steward, custodian, operator and reviewer authority are separate roles." }, { "dimension": "validation", "status": "covered", "notes": "Unknown applicability and failed evidence remain explicit; no operational certification." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose and field-level export limits apply." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Scoped disposal, holds and minimal tombstones replace blanket indefinite retention." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual mappings only; executable adapters and fixtures remain deferred." }, { "dimension": "physical properties and recognition", "status": "covered", "notes": "Evidence for form, scale and optional dimensions complements quantity-valued capability." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Measurement capabilities are separate from proposed local record operations and physical control." }, { "dimension": "regional applicability", "status": "gap", "notes": "Selected international concepts and original EU act do not resolve all jurisdictions." }, { "dimension": "source verification", "status": "gap", "notes": "Browser parsed-content access is separate from pending direct HTTP and independent source/version review." } ], "known_omissions": [ "Independent external review is absent; this is a Codex-only reviewable draft under the owner waiver.", "Direct HTTP checks were not attempted because the owner reports sandbox blocking. Eight URLs were accessible as parsed browser documents, but raw responses, final redirects, hashes and independent version verification remain pending.", "Jurisdiction-specific current law, national in-service control and specialized medical, radiation, chemical and trade profiles require qualified review.", "Executable nested schemas, conformance fixtures, unit conversion and uncertainty propagation, protocol adapters and pinned neighbor bindings are not implemented.", "Detailed cumulative register profiles, batch/continuous sampling and multi-channel correlation require additional sector evidence; current exception questions are proposed local safeguards." ], "conflicts": [], "regional_assumptions": [ "VIM and SI provide vocabulary; local instrument classifications and legal obligations can differ.", "The original EU directive is an illustrative jurisdiction profile, not verified current national law.", "The SSN 2017 recommendation is intentionally pinned; newer editions and mapping compatibility are deferred." ], "adversarial_checks": [ "A material measure without electronics remains representable; not-applicable software and digital channels are explicit.", "A fresh calibration does not prove every result traceable, legally verified or fit for purpose.", "A replacement at the same point has a new identity and cannot silently continue a cumulative counter.", "Server-assigned phenomenon time remains marked as such; receipt time is not unqualified measurement time.", "An unexplained negative delta, stale calibration or unrecognized parameter revision produces unresolved assessment rather than invented corrected readings." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root is one physical instrument with stable identity across deployment and evidence revisions. Material measures and indicating instruments fit the declared scope. A single instrument can also be a measuring system; multi-instrument system masters remain external. The registry standalone-mm value is not a research subject-kind enum." }, "decisions": [ { "concept": "Physical subject boundary", "disposition": "accepted", "rationale": "Identity and classification questions preserve one persistent physical subject and distinguish type, metering point and indication-only components. Pure virtual estimators remain outside the declared scope." }, { "concept": "Candidate device parent", "disposition": "qualified alignment", "rationale": "The frozen ledger has no relation rows and no legacy alias. The candidate hardware parent is represented without requiring computation, digital sensors or a parent runtime that would exclude material measures." }, { "concept": "Observation and asset ownership", "disposition": "separated", "rationale": "Instrument context binds to separately mastered observations, collections and asset events. None of the local operations rewrites measurement values, owns billing or performs physical lifecycle actions." }, { "concept": "Channels and material measures", "disposition": "accepted with applicability", "rationale": "The logical interpretation contract permits assigned values and analog indications. Firmware, network ports and observations are conditional, avoiding the supplement's narrower display and reporting assumptions." }, { "concept": "Performance concepts", "disposition": "separated", "rationale": "Capability questions distinguish measurement range, resolution, maximum permissible error, uncertainty and behavior under specified conditions. Nominal specification and survival conditions cannot establish present measurement fitness." }, { "concept": "Calibration and verification", "disposition": "separated", "rationale": "Calibration evidence, physical adjustment and verification outcomes have separate bindings and purposes. A new certificate cannot silently establish legal approval or cover an unrelated configuration or channel." }, { "concept": "Result traceability", "disposition": "accepted with evidence scope", "rationale": "The model attaches claims to linked results and their documented reference chain. Equipment labels, issuer names and calibration alone do not establish traceability or satisfy a use-specific uncertainty requirement." }, { "concept": "Recalibration and suspect results", "disposition": "accepted as qualified assessment", "rationale": "Intervals are tied to policy, risk and history; intermediate checks and onset uncertainty remain explicit. A failed check creates an impact review and never silently corrects historical observations." }, { "concept": "Counter and time exceptions", "disposition": "accepted as proposed safeguards", "rationale": "Unknown resets, rollover, replacement and reverse direction require profile evidence. Server-assigned time remains flagged. The pack defers detailed sector rules and makes no executable counter or clock-recovery claim." }, { "concept": "Legal applicability and protected configuration", "disposition": "profile dependent", "rationale": "The original EU act and conditional software guidance support questions, not universal current-law conclusions. Changes, seal evidence and verification require applicable authority; no proposed function intervenes on a device." }, { "concept": "Local operations and access", "disposition": "accepted as unimplemented", "rationale": "All six operations are explicitly local proposals with authority, revision, evidence and refusal conditions. Reading and export permissions do not grant device control. Export creates a local artifact without external delivery." }, { "concept": "Retention and privacy", "disposition": "accepted as local policy design", "rationale": "The service rules require purpose and applicable authority, preserve lawful disposal and do not impose consent as the only basis or indefinite personal-data retention. Source citations are not presented as universal governance mandates." }, { "concept": "Source evidence and selected versions", "disposition": "limited", "rationale": "Eight admitted documents were accessible as parsed browser content with selected sections reviewed. Direct requests were not attempted under the owner-stated sandbox limit; zero measured responses is not eight observed failures. Independent versions and current legal applicability remain unresolved." }, { "concept": "Candidate schema and interoperability", "disposition": "deferred implementation", "rationale": "The 48 answer groups support research questions but do not supply executable nested schemas. Conceptual SensorThings and pinned SSN mappings, optional neighbors and planned fixtures require implementation and conformance evidence." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with no admitted result. The separate frozen phase is a local Codex self-audit and cannot support a claim of provider agreement or independent external review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped; the separate local Codex no-tools self-audit is not an independent second-provider review.", "Direct source verification remains pending: no direct HTTP requests were attempted under the owner-stated sandbox restriction, so zero HTTP 200 responses were measured. Eight admitted URLs supplied parsed browser content, with selected-section review documented in source-review.md. The coordinator must run check_sources.py; raw response hashes, redirects, independent version confirmation and current legal consolidation remain unverified.", "Jurisdiction, intended use, instrument class, licensing, national in-service controls, legal verification and specialized safety or medical profiles require qualified review before operational use. The original EU directive and selected standards do not establish universal compliance.", "Executable nested instance schemas, pinned neighbor bindings, detailed cumulative-register profiles, unit conversion and uncertainty handling, protocol adapters and adversarial conformance fixtures remain incomplete. All six local operations are proposed and unimplemented.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Complete coordinator HTTP checks and independent source/version/applicability review, including current legal consolidation and intentionally selected ontology versions.", "Implement profile-specific schemas and mappings with fixtures for material measures, analog instruments, multi-channel scope, replacement, reset, changed configuration, suspect periods and server-assigned time.", "Restore independent external review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }