{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-obj-008","code":"wm-obj-008-device-sensor-compute-hw","url":"https://ver.cy/models/wm-obj-008-device-sensor-compute-hw/","name":"Device / Sensor / Compute HW","alternateNames":["M8"],"kind":"world-model","status":"published","version":"0.1.0-reviewable-draft","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"entity","plane":"","domain":["PHY.OBJ.DEV"],"industry":["Cross-industry"],"navPath":"NAV.PHY.OBJ.DEV","tags":["device","sensor","compute","hw","phy.obj.dev"],"facets":{}},"whatItIs":"A physical unit with sensing, computing or connected-device functions, including unit-side component, firmware, configuration and interface assertions. Sensors, networking, mutable firmware and actuation are individually optional. All structure is proposed research, not an executable controller.","purpose":"Describe one physical device, sensing unit or computing hardware unit through governed identity, capabilities, state assertions and evidence links.","scope":{"in":["Physical hardware identity specialization and recognition evidence","Installed resource and component topology, conditional power and environmental properties","Physical sensing capability and calibration evidence applicability","Component firmware and configuration bindings, interface and stream references","Scoped assurance, support and lifecycle evidence for the unit"],"out":["Product-type catalogue, fleet aggregate, virtual machine or purely virtual/human sensor root","Observation payloads, stream ingestion, software release lifecycle and runtime scheduling","External authority decisions, ownership transfers, maintenance execution, calibration execution and legal metrology certification","Device commands, firmware installation, actuation, credential provisioning, sanitization and disposal execution","Host vehicle or equipment lifecycle, incident response execution and global audit-trail semantics"],"boundaries":[{"neighbor":"WM-OBJ-001","distinction":"Proposed successor binding for legacy M2. Reuse the physical-item master identity, ownership, custody and location references; only hardware-specific assertions are local. Pin an adopted revision before runtime use."},{"neighbor":"WM-OBJ-006","distinction":"Legacy M6 host equipment candidate. Store host reference and mount role; do not duplicate machinery condition, maintenance execution or lifecycle."},{"neighbor":"WM-OBJ-007","distinction":"Legacy M7 vehicle host candidate; store installation reference without vehicle operations or custody lifecycle."},{"neighbor":"WM-MAT-008","distinction":"Observation and calibration result records remain externally mastered; the device carries evidence references and applicability only."},{"neighbor":"WM-DAT-010","distinction":"Observation collection payload, ingestion and retention remain external; keep only channel-to-collection bindings."},{"neighbor":"WM-SFT-007","distinction":"Installed firmware points to versioned software packages; release creation and distribution remain external."},{"neighbor":"WM-SFT-011","distinction":"Desired configuration profile is external; keep component binding and observed application evidence."},{"neighbor":"WM-SFT-010","distinction":"Runtime environments and virtual machines reference the physical host; do not treat them as this physical entity."},{"neighbor":"WM-XCT-010","distinction":"Use governed location and frame references; device-side placement does not own an address registry."},{"neighbor":"W3C SSN/SOSA 2017","distinction":"Conceptual alignment for physical sensors and deployment only; broader virtual and human sensor semantics are not imported."},{"neighbor":"W3C WoT Thing Description 1.1","distinction":"Conceptual interface metadata mapping, without executing actions or claiming conformance."},{"neighbor":"RFC 8348","distinction":"Map qualified component identity and state assertions; do not equate a management server identifier with the physical master."},{"neighbor":"OGC SensorThings 1.0","distinction":"Historical pin for channel-to-stream concepts; endpoint implementation and conformance are deferred."},{"neighbor":"DMTF ComputerSystem v1.24.0","distinction":"Map physical-unit resources only after checking SystemType and scope; virtual and composed views are not identical roots."},{"neighbor":"Legacy M8 and unreviewed card supplement","distinction":"Legacy standalone-mm is a record-plane label; entity is the subject kind. Reject uniqueness of mutable software and mandatory data-stream output. Replace exactly-one-current-firmware with component and slot scoped assertions; legal metrology remains an applicability profile, not a disjoint device family."}]},"distinguishingFeatures":["Unlike WM-OBJ-001: Proposed successor binding for legacy M2. Reuse the physical-item master identity, ownership, custody and location references; only hardware-specific assertions are local. Pin an adopted revision before runtime use.","Unlike WM-OBJ-006: Legacy M6 host equipment candidate. Store host reference and mount role; do not duplicate machinery condition, maintenance execution or lifecycle.","Unlike WM-OBJ-007: Legacy M7 vehicle host candidate; store installation reference without vehicle operations or custody lifecycle.","Unlike WM-MAT-008: Observation and calibration result records remain externally mastered; the device carries evidence references and applicability only.","Unlike WM-DAT-010: Observation collection payload, ingestion and retention remain external; keep only channel-to-collection bindings.","Unlike WM-SFT-007: Installed firmware points to versioned software packages; release creation and distribution remain external.","Unlike WM-SFT-011: Desired configuration profile is external; keep component binding and observed application evidence.","Unlike WM-SFT-010: Runtime environments and virtual machines reference the physical host; do not treat them as this physical entity.","Unlike WM-XCT-010: Use governed location and frame references; device-side placement does not own an address registry.","Unlike W3C SSN/SOSA 2017: Conceptual alignment for physical sensors and deployment only; broader virtual and human sensor semantics are not imported.","Unlike W3C WoT Thing Description 1.1: Conceptual interface metadata mapping, without executing actions or claiming conformance.","Unlike RFC 8348: Map qualified component identity and state assertions; do not equate a management server identifier with the physical master.","Unlike OGC SensorThings 1.0: Historical pin for channel-to-stream concepts; endpoint implementation and conformance are deferred.","Unlike DMTF ComputerSystem v1.24.0: Map physical-unit resources only after checking SystemType and scope; virtual and composed views are not identical roots.","Unlike Legacy M8 and unreviewed card supplement: Legacy standalone-mm is a record-plane label; entity is the subject kind. Reject uniqueness of mutable software and mandatory data-stream output. Replace exactly-one-current-firmware with component and slot scoped assertions; legal metrology remains an applicability profile, not a disjoint device family."],"structure":{"bundles":[{"id":"identity","name":"Identity and recognition","description":"Local device context for identity and recognition.","layers":[{"id":"unit-identity-layer","name":"Unit identity","description":"Qualify unit identity for one physical unit and the relevant time interval.","findings":[{"id":"unit-identity","name":"Unit identity","description":"One persistent physical unit has a governed master reference and qualified aliases. Network addresses and manufacturer serials alone are insufficient for automatic record merging.","questions":[{"text":"Which master record identifies this physical unit and qualifies its serial aliases?","id":"unit-identity-q1","kind":"identity"},{"text":"Which hardware class and product revision describe the unit?","id":"unit-identity-q2","kind":"classification"},{"text":"Which owner, custodian and operator references apply for this interval?","id":"unit-identity-q3","kind":"ownership"},{"text":"What evidence resolves missing labels or conflicting identifiers without merging separate units?","id":"unit-identity-q4","kind":"exception"}]}]},{"id":"recognition-layer","name":"Recognition evidence","description":"Qualify recognition evidence for one physical unit and the relevant time interval.","findings":[{"id":"recognition","name":"Recognition evidence","description":"Labels, inventory observations and attestation references support a claimed unit match. Keep reported identity, authenticated endpoint and verified hardware association distinct.","questions":[{"text":"Which label or inventory evidence supports the claimed hardware match?","id":"recognition-q1","kind":"evidence"},{"text":"Who collected recognition evidence and through which management path?","id":"recognition-q2","kind":"provenance"},{"text":"Which component and evidence freshness constraints limit the identity assertion?","id":"recognition-q3","kind":"validation"},{"text":"Which identifying evidence must be masked in public or shared views?","id":"recognition-q4","kind":"privacy"}]}]}]},{"id":"hardware","name":"Physical properties and resources","description":"Local device context for physical properties and resources.","layers":[{"id":"resources-layer","name":"Installed resources","description":"Qualify installed resources for one physical unit and the relevant time interval.","findings":[{"id":"resources","name":"Installed resources","description":"Capture installed processor, memory, storage and interface references for this unit. Capacity, allocation and measured workload are different assertions; virtual environments remain external.","questions":[{"text":"Which installed processors, memory, storage and interfaces belong to this unit?","id":"resources-q1","kind":"composition"},{"text":"What capacities and counts are reported with their units and evidence?","id":"resources-q2","kind":"measurement"},{"text":"Which installed resources are unavailable, reserved or unsupported in this configuration?","id":"resources-q3","kind":"constraint"},{"text":"How does each resource mapping distinguish physical hardware from logical or virtual views?","id":"resources-q4","kind":"interoperability"}]}]},{"id":"limits-layer","name":"Power and environmental envelope","description":"Qualify power and environmental envelope for one physical unit and the relevant time interval.","findings":[{"id":"limits","name":"Power and environmental envelope","description":"Represent declared operating and survival conditions separately from measured conditions. Local fields can include dimensions, mass, electrical supply and thermal constraints when supported by unit-specific evidence.","questions":[{"text":"Which dimensions, mass and supply quantities are evidenced for this unit?","id":"limits-q1","kind":"measurement"},{"text":"Which operating and survival envelopes apply to the installed revision?","id":"limits-q2","kind":"constraint"},{"text":"Which ratings are declared and which have been measured on the actual unit?","id":"limits-q3","kind":"quality"},{"text":"What policy limits use when required environmental or power evidence is missing?","id":"limits-q4","kind":"exception"}]}]}]},{"id":"assembly","name":"Components and placement","description":"Local device context for components and placement.","layers":[{"id":"components-layer","name":"Component continuity","description":"Qualify component continuity for one physical unit and the relevant time interval.","findings":[{"id":"components","name":"Component continuity","description":"Component membership is time-bounded. A replaceable module can retain its own identity after removal; a parent device record is not a fleet or procurement catalogue.","questions":[{"text":"Which components are embedded, replaceable or separately mastered?","id":"components-q1","kind":"composition"},{"text":"During which interval was each component installed in this unit?","id":"components-q2","kind":"temporal"},{"text":"Which replacement changed component identity while preserving the parent unit?","id":"components-q3","kind":"lifecycle"},{"text":"How are containment cycles, duplicate active slots and ambiguous parents rejected?","id":"components-q4","kind":"validation"}]}]},{"id":"placement-layer","name":"Host and spatial binding","description":"Qualify host and spatial binding for one physical unit and the relevant time interval.","findings":[{"id":"placement","name":"Host and spatial binding","description":"Record the unit-side relationship to a host, mounting frame or location reference over time. Physical mounting is distinct from network topology and from ownership of the host.","questions":[{"text":"Which host asset or platform is related to this installation?","id":"placement-q1","kind":"relationship"},{"text":"Which coordinate frame, pose or named mount locates the unit on its host?","id":"placement-q2","kind":"spatial"},{"text":"When did the placement become valid and when was it observed?","id":"placement-q3","kind":"temporal"},{"text":"How are mobile, unmounted or disputed installations represented?","id":"placement-q4","kind":"exception"}]}]}]},{"id":"sensing","name":"Sensing and metrology","description":"Local device context for sensing and metrology.","layers":[{"id":"capability-layer","name":"Sensing capability","description":"Qualify sensing capability for one physical unit and the relevant time interval.","findings":[{"id":"capability","name":"Sensing capability","description":"A physical sensing channel links an observed property and procedure to conditional performance claims. Compute-only units can declare this layer not applicable; human and purely virtual sensors are outside the root.","questions":[{"text":"Which property and feature class can this physical channel observe?","id":"capability-q1","kind":"definition"},{"text":"What range, resolution, frequency and uncertainty statements are evidenced under stated conditions?","id":"capability-q2","kind":"measurement"},{"text":"Which procedure and sensor component support the capability claim?","id":"capability-q3","kind":"relationship"},{"text":"When is sensing absent, disabled or outside its supported envelope?","id":"capability-q4","kind":"exception"}]}]},{"id":"calibration-layer","name":"Calibration evidence and suitability","description":"Qualify calibration evidence and suitability for one physical unit and the relevant time interval.","findings":[{"id":"calibration","name":"Calibration evidence and suitability","description":"Link calibration evidence for a specified channel, range and configuration. Traceability pertains to measurement results and does not itself guarantee suitability or legal verification.","questions":[{"text":"Which calibration record identifies the channel, configuration and reference chain?","id":"calibration-q1","kind":"evidence"},{"text":"What uncertainty and conditions constrain use of the calibration evidence?","id":"calibration-q2","kind":"quality"},{"text":"Which policy determines the next review and invalidation triggers for this channel?","id":"calibration-q3","kind":"temporal"},{"text":"Who assessed fitness for the intended measurement purpose and with what criterion?","id":"calibration-q4","kind":"decision"}]}]}]},{"id":"software-state","name":"Installed software and configuration","description":"Local device context for installed software and configuration.","layers":[{"id":"firmware-layer","name":"Component firmware state","description":"Qualify component firmware state for one physical unit and the relevant time interval.","findings":[{"id":"firmware","name":"Component firmware state","description":"Each relevant component may expose active, staged, recovery or unknown firmware assertions. Installed versions reference external releases; this record does not execute updates or recovery.","questions":[{"text":"Which firmware assertion is active, staged, recovery or unknown for each component?","id":"firmware-q1","kind":"state"},{"text":"Which observation or deployment result supports the installed-version assertion?","id":"firmware-q2","kind":"provenance"},{"text":"Which compatibility and rollback policies qualify a proposed firmware transition?","id":"firmware-q3","kind":"constraint"},{"text":"How are interrupted updates and conflicting version reports retained?","id":"firmware-q4","kind":"event"}]}]},{"id":"configuration-layer","name":"Configuration binding","description":"Qualify configuration binding for one physical unit and the relevant time interval.","findings":[{"id":"configuration","name":"Configuration binding","description":"Pin intended configuration and separately record observed application evidence. A successful request or configuration digest alone does not establish actual device state.","questions":[{"text":"Which desired profile revision and observed configuration evidence apply?","id":"configuration-q1","kind":"state"},{"text":"Which operator grant authorizes assessment of the configuration binding?","id":"configuration-q2","kind":"authority"},{"text":"Which settings require protected references rather than stored plaintext values?","id":"configuration-q3","kind":"security"},{"text":"How is drift recorded and referred to an external change process?","id":"configuration-q4","kind":"process"}]}]}]},{"id":"interfaces","name":"Interfaces and observation links","description":"Local device context for interfaces and observation links.","layers":[{"id":"connectivity-layer","name":"Interface and reachability assertions","description":"Qualify interface and reachability assertions for one physical unit and the relevant time interval.","findings":[{"id":"connectivity","name":"Interface and reachability assertions","description":"Describe interaction affordances and endpoint bindings with time and scope. Reachability, power state, administrative state and operational health remain separate observations.","questions":[{"text":"Which interface description and protocol binding identify the available interactions?","id":"connectivity-q1","kind":"interoperability"},{"text":"What endpoint, power and health states were observed and from which vantage point?","id":"connectivity-q2","kind":"state"},{"text":"Which policy governs reading properties or invoking the described action?","id":"connectivity-q3","kind":"access"},{"text":"What behavior is expected when the unit sleeps, disconnects or has stale reachability evidence?","id":"connectivity-q4","kind":"exception"}]}]},{"id":"stream-binding-layer","name":"Observation stream binding","description":"Qualify observation stream binding for one physical unit and the relevant time interval.","findings":[{"id":"stream-binding","name":"Observation stream binding","description":"Bind a physical channel to external observation and collection masters. The binding can change over time without rewriting historical measurement provenance or owning the stream payload.","questions":[{"text":"Which observation collection carries output from this channel during this interval?","id":"stream-binding-q1","kind":"relationship"},{"text":"Which unit, property and result-shape mapping qualifies that output?","id":"stream-binding-q2","kind":"measurement"},{"text":"How are phenomenon, result and ingestion times distinguished by the binding?","id":"stream-binding-q3","kind":"temporal"},{"text":"Which permitted purposes and recipient policies constrain the stream reference?","id":"stream-binding-q4","kind":"privacy"}]}]}]},{"id":"assurance","name":"Assurance and lifecycle","description":"Local device context for assurance and lifecycle.","layers":[{"id":"security-assessment-layer","name":"Security evidence and review","description":"Qualify security evidence and review for one physical unit and the relevant time interval.","findings":[{"id":"security-assessment","name":"Security evidence and review","description":"Retain scoped references to attestations, vulnerability applicability assessments and incident records. Evidence, verifier result and permission to operate are separate; a trusted boot claim does not establish sensor accuracy.","questions":[{"text":"Which target and time interval does an attestation appraisal actually cover?","id":"security-assessment-q1","kind":"evidence"},{"text":"What external assessment qualifies vulnerability applicability to this configuration?","id":"security-assessment-q2","kind":"validation"},{"text":"Which relying-party policy decides whether the reported assurance is sufficient?","id":"security-assessment-q3","kind":"authority"},{"text":"What restrictions govern incident evidence and compromised-unit status disclosures?","id":"security-assessment-q4","kind":"security"}]}]},{"id":"lifecycle-evidence-layer","name":"Support, service and retirement","description":"Qualify support, service and retirement for one physical unit and the relevant time interval.","findings":[{"id":"lifecycle-evidence","name":"Support, service and retirement","description":"Unit records track commissioned, service-restricted and retired assertions using external evidence. Support expiry, decommissioning, sanitization and physical disposal are distinct facts; local deletion cannot perform them.","questions":[{"text":"Which commissioning, maintenance or retirement evidence supports the recorded lifecycle state?","id":"lifecycle-evidence-q1","kind":"lifecycle"},{"text":"Which support horizon and unresolved failure modes restrict continued use?","id":"lifecycle-evidence-q2","kind":"constraint"},{"text":"Which policy governs retention or deletion of the unit record after retirement?","id":"lifecycle-evidence-q3","kind":"retention"},{"text":"Which separate records attest sanitization, transfer and disposal without inferring completion?","id":"lifecycle-evidence-q4","kind":"evidence"}]}]}]}]},"agentConduct":{"may":["Register a unit assertion: Proposed, unimplemented local record operation. Create the local hardware extension only after resolving the physical-item master.","Record a component inventory: Proposed, unimplemented local record operation. Append a time-qualified resource and containment snapshot without altering hardware.","Link calibration evidence: Proposed, unimplemented local record operation. Record an assessor-scoped applicability claim for an existing calibration result.","Record software state evidence: Proposed, unimplemented local record operation. Keep component-specific observed state separate from desired release or profile.","Bind interface and output references: Proposed, unimplemented local record operation. Record qualified links from the unit to interface descriptions and external observation collections.","Record assurance review references: Proposed, unimplemented local record operation. Link evidence, external appraisal and relying-party decision without performing verification.","Record retirement evidence: Proposed, unimplemented local record operation. Record a unit lifecycle assertion and close local bindings when supported by authorized evidence."],"mustNot":["Apply least privilege and purpose limitation to serials, precise locations, network paths, firmware state and telemetry references; never store credentials or private keys.","Use revision checks and evidence-backed patches; local changes cannot silently mutate hardware, external releases or telemetry payloads.","Deny access unless role, purpose, unit and time scope are authorized; derived views cannot widen source-artifact access."],"requiresHuman":[]},"ethics":{"considerations":["Device, electrical, safety, privacy, radio, legal metrology and disposal rules require an adopted sector and jurisdiction profile; no legal compliance assertion follows from schema validity."],"affectedParties":[]},"owners":{"steward":"Resolve the accountable owner role, custodian and technical operator separately; no company or brand is a model owner.","roles":[{"name":"Accountable owner","responsibilities":["Approve intended purposes, access policy and retention for the device record."]},{"name":"Identity steward","responsibilities":["Resolve physical master references, duplicate identities and component continuity."]},{"name":"Technical operator","responsibilities":["Supply inventory and observed state evidence within a valid grant."]},{"name":"Metrology reviewer","responsibilities":["Assess channel-specific calibration evidence and measurement suitability."]},{"name":"Security reviewer","responsibilities":["Qualify assurance references, freshness, disclosure and applicability."]},{"name":"Records custodian","responsibilities":["Apply revision, retention, hold and lawful disposition rules."]}],"masterSystems":[]},"relations":[{"target":"WM-OBJ-001","type":"extends","note":"Proposed successor binding for legacy M2. Reuse the physical-item master identity, ownership, custody and location references; only hardware-specific assertions are local. Pin an adopted revision before runtime use."},{"target":"WM-OBJ-006","type":"references","note":"Legacy M6 host equipment candidate. Store host reference and mount role; do not duplicate machinery condition, maintenance execution or lifecycle."},{"target":"WM-OBJ-007","type":"references","note":"Legacy M7 vehicle host candidate; store installation reference without vehicle operations or custody lifecycle."},{"target":"WM-MAT-008","type":"references","note":"Observation and calibration result records remain externally mastered; the device carries evidence references and applicability only."},{"target":"WM-DAT-010","type":"references","note":"Observation collection payload, ingestion and retention remain external; keep only channel-to-collection bindings."},{"target":"WM-SFT-007","type":"references","note":"Installed firmware points to versioned software packages; release creation and distribution remain external."},{"target":"WM-SFT-011","type":"references","note":"Desired configuration profile is external; keep component binding and observed application evidence."},{"target":"WM-SFT-010","type":"references","note":"Runtime environments and virtual machines reference the physical host; do not treat them as this physical entity."},{"target":"WM-XCT-010","type":"references","note":"Use governed location and frame references; device-side placement does not own an address registry."},{"target":"W3C SSN/SOSA 2017","type":"aligned","note":"Conceptual alignment for physical sensors and deployment only; broader virtual and human sensor semantics are not imported."},{"target":"W3C WoT Thing Description 1.1","type":"aligned","note":"Conceptual interface metadata mapping, without executing actions or claiming conformance."},{"target":"RFC 8348","type":"aligned","note":"Map qualified component identity and state assertions; do not equate a management server identifier with the physical master."},{"target":"OGC SensorThings 1.0","type":"aligned","note":"Historical pin for channel-to-stream concepts; endpoint implementation and conformance are deferred."},{"target":"DMTF ComputerSystem v1.24.0","type":"aligned","note":"Map physical-unit resources only after checking SystemType and scope; virtual and composed views are not identical roots."},{"target":"WM-OBJ-001","type":"neighbor","note":"Proposed successor binding for legacy M2. Reuse the physical-item master identity, ownership, custody and location references; only hardware-specific assertions are local. Pin an adopted revision before runtime use."},{"target":"WM-OBJ-006","type":"neighbor","note":"Legacy M6 host equipment candidate. Store host reference and mount role; do not duplicate machinery condition, maintenance execution or lifecycle."},{"target":"WM-OBJ-007","type":"neighbor","note":"Legacy M7 vehicle host candidate; store installation reference without vehicle operations or custody lifecycle."},{"target":"WM-MAT-008","type":"neighbor","note":"Observation and calibration result records remain externally mastered; the device carries evidence references and applicability only."},{"target":"WM-DAT-010","type":"neighbor","note":"Observation collection payload, ingestion and retention remain external; keep only channel-to-collection bindings."},{"target":"WM-SFT-007","type":"neighbor","note":"Installed firmware points to versioned software packages; release creation and distribution remain external."},{"target":"WM-SFT-011","type":"neighbor","note":"Desired configuration profile is external; keep component binding and observed application evidence."},{"target":"WM-SFT-010","type":"neighbor","note":"Runtime environments and virtual machines reference the physical host; do not treat them as this physical entity."},{"target":"WM-XCT-010","type":"neighbor","note":"Use governed location and frame references; device-side placement does not own an address registry."},{"target":"W3C SSN/SOSA 2017","type":"neighbor","note":"Conceptual alignment for physical sensors and deployment only; broader virtual and human sensor semantics are not imported."},{"target":"W3C WoT Thing Description 1.1","type":"neighbor","note":"Conceptual interface metadata mapping, without executing actions or claiming conformance."},{"target":"RFC 8348","type":"neighbor","note":"Map qualified component identity and state assertions; do not equate a management server identifier with the physical master."},{"target":"OGC SensorThings 1.0","type":"neighbor","note":"Historical pin for channel-to-stream concepts; endpoint implementation and conformance are deferred."},{"target":"DMTF ComputerSystem v1.24.0","type":"neighbor","note":"Map physical-unit resources only after checking SystemType and scope; virtual and composed views are not identical roots."},{"target":"Legacy M8 and unreviewed card supplement","type":"neighbor","note":"Legacy standalone-mm is a record-plane label; entity is the subject kind. Reject uniqueness of mutable software and mandatory data-stream output. Replace exactly-one-current-firmware with component and slot scoped assertions; legal metrology remains an applicability profile, not a disjoint device family."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","UUID or ULID assigned by the adopting Dimension"]},"properties":{"applicability":"required","items":[]},"recognition":{"applicability":"required","items":[]},"capabilities":{"applicability":"required","items":["Register a unit assertion: Proposed, unimplemented local record operation. Create the local hardware extension only after resolving the physical-item master.","Record a component inventory: Proposed, unimplemented local record operation. Append a time-qualified resource and containment snapshot without altering hardware.","Link calibration evidence: Proposed, unimplemented local record operation. Record an assessor-scoped applicability claim for an existing calibration result.","Record software state evidence: Proposed, unimplemented local record operation. Keep component-specific observed state separate from desired release or profile.","Bind interface and output references: Proposed, unimplemented local record operation. Record qualified links from the unit to interface descriptions and external observation collections.","Record assurance review references: Proposed, unimplemented local record operation. Link evidence, external appraisal and relying-party decision without performing verification.","Record retirement evidence: Proposed, unimplemented local record operation. Record a unit lifecycle assertion and close local bindings when supported by authorized evidence."]},"hazards":{"applicability":"required","items":[]},"interfaces":{"applicability":"required","items":["OGC SensorThings API Part 1: Sensing","NIST Policy on Metrological Traceability"]},"context":{"applicability":"required","items":["NIST guidance is technical evidence, not universal legislation.","W3C, IETF, OGC and DMTF alignments use specified editions; latest-version and errata checks remain open."]}},"sources":[{"title":"A YANG Data Model for Hardware Management","url":"https://www.rfc-editor.org/rfc/rfc8348","note":"IETF"},{"title":"Semantic Sensor Network Ontology","url":"https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/","note":"W3C"},{"title":"Web of Things (WoT) Thing Description 1.1","url":"https://www.w3.org/TR/2023/REC-wot-thing-description11-20231205/","note":"W3C"},{"title":"IoT Device Cybersecurity Capability Core Baseline","url":"https://doi.org/10.6028/NIST.IR.8259A","note":"NIST"},{"title":"OGC SensorThings API Part 1: Sensing","url":"https://docs.ogc.org/is/15-078r6/15-078r6.html","note":"OGC"},{"title":"Remote ATtestation procedureS (RATS) Architecture","url":"https://www.rfc-editor.org/rfc/rfc9334.html","note":"IETF"},{"title":"Platform Firmware Resiliency Guidelines","url":"https://doi.org/10.6028/NIST.SP.800-193","note":"NIST"},{"title":"NIST Policy on Metrological Traceability","url":"https://www.nist.gov/calibrations/traceability","note":"NIST"},{"title":"Redfish ComputerSystem schema","url":"https://redfish.dmtf.org/schemas/v1/ComputerSystem.v1_24_0.json","note":"DMTF"}],"openQuestions":["Run the coordinator source checker outside the sandbox, then substantively review edition pins, errata, rights and complete claim support; HTTP success alone is insufficient.","Pin physical-item and other neighbor revisions, implement nested instance schemas and test duplicate serials, replaced modules, virtual/composed views, sleeping devices, stale attestations, failed updates and conflicting observations.","Validate sector-specific measurement suitability, safety, privacy and retirement/disposition profiles with qualified reviewers.","Restore independent external review before any canonical or publishable-draft promotion.","No independent second-provider review; Claude and Grok skipped under owner override.","Direct HTTP checks not attempted under the owner-reported sandbox block; browser content was reviewed, but status, redirect bodies and live hashes are unmeasured.","Nested instance schemas, pinned neighbor releases, protocol adapters and adversarial acceptance fixtures remain incomplete.","No electrical, functional safety, medical-device, radio, export, legal metrology or disposal certification; applicable profiles require qualified review.","No guarantee of comprehensive failure-mode or supply-chain provenance coverage."],"resources":{"spec":"/models/wm-obj-008-device-sensor-compute-hw/spec.yaml","agents":"/models/wm-obj-008-device-sensor-compute-hw/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-008"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-obj-008-device-sensor-compute-hw/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T22:10:00Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"missing","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification."},"score":0.706}}