Internet of Things
Enable an AI agent to recognise an Internet of Things system, assess its physical and digital operating state, and determine which observations or interventions are supported and authorised.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an AI agent to recognise an Internet of Things system, assess its physical and digital operating state, and determine which observations or interventions are supported and authorised.
The Internet of Things (IoT) is the interconnection of physical objects equipped with sensing or actuation, processing, and network communication capabilities so that they can exchange data and interact with digital services, directly or through gateways.
It can be Identify participating physical things and trace their dependencies on gateways and services.; Interpret observations using their units, sampling times, calibration context, and quality indicators.; Assess whether connectivity, energy, and service health support the intended operation.; Request an authorised physical action within recorded limits and verify its outcome.; Provision, reconfigure, update, or isolate participating endpoints within the agent's authority.; Retire endpoints by revoking access and resolving retained data and service dependencies..
Distinguishing features
The system connects digital information exchange to physical sensing or actuation; a network of software services alone does not satisfy this boundary.
Physical things participate through distinguishable identities or addressable endpoints, directly or through intermediaries; an inventory of unconnected objects is insufficient.
Observations or commands pass between physical endpoints and other components; a standalone electronic controller without such exchange falls outside the proposed scope.
The subject is the integration of connected things and services, rather than one sensor, a communications protocol, or a cloud platform considered independently.
Connectivity may be intermittent or gateway-mediated; the model must distinguish these arrangements from any claim that every thing is directly Internet-addressable.
Scope
+ Boundaries and membership of systems connecting physical things to digital services
+ Physical sensing, actuation, and the meaning of exchanged observations and commands
+ Device identities, connectivity paths, gateways, and interoperability
+ Coordination across devices, edge components, and remote services
+ Operational health, provisioning, updates, and retirement
+ Authority, cybersecurity, privacy, and physical consequences of remote actions
- Internal mechanical or electronic design of individual sensors, actuators, and machines
- General Internet infrastructure and networking independent of connected physical things
- Standalone software services with no sensing or actuation relationship to the physical world
- Domain-specific control objectives belonging to models of buildings, factories, vehicles, or healthcare systems
- Detailed organisational governance and contractual terms belonging to operator and service-provider models
- Digital twins and analytical models beyond their interfaces with connected things
Characteristics
- Physical participation
- sensing; actuation; both; unresolved Identifies how the system observes or changes the physical world.
- System membership
- physical thing ↔ device endpoint ↔ gateway ↔ service Separates the thing represented from the components that identify, connect, or operate it.
- Connectivity arrangement
- direct; gateway-mediated; intermittently synchronised; mixed Determines reachability and which intermediaries are necessary for operation.
- Observation age
- seconds since physical sampling, with clock uncertainty recorded Prevents a recently received but old observation from being treated as current physical state.
- End-to-end action latency
- milliseconds or seconds from command issue to confirmed physical response Supports judgement about whether remote action meets the use case's timing needs.
- Operational connectivity
- connected; intermittent; partitioned; offline; unknown Constrains the observations and interventions currently available.
- Control authority
- principal ↔ permitted endpoint operations ↔ conditions Distinguishes the technical ability to send a command from permission to cause its physical effect.
- Disconnected behaviour
- local continuation; buffered reporting; restricted operation; controlled stop; unspecified Makes the consequences of losing gateways or remote services explicit.
- Energy availability
- externally powered; battery sufficient; battery low; energy-limited; unknown Explains limits on sampling, communication, updates, and actuation.
- Support and update condition
- supported; update pending; update failed; unsupported; unknown Helps determine whether continued connected operation is maintainable.
Also called
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 7 bundles · 13 layers · 20 findings · 32 questions.
Physical-digital boundary Establishes what makes the subject an IoT system and which physical things and digital components participate.
Internet of Things names a system concept rather than a single device type, so membership and representation must be explicit.
System extent
Defines the connected physical activity and the boundary around its supporting components.
Physical participation
Record the physical phenomena sensed or affected and the endpoints through which they enter the system.
- Which physical things or phenomena does this system observe or change? definition
- Which devices, gateways, and services belong to this system, and which are external dependencies? boundary
Identity and representation
Connects physical things to device identities and digital representations without assuming a one-to-one mapping.
Thing-to-endpoint mapping
Record how identifiers refer to physical things, replaceable devices, and service-side representations over time.
- Does each identifier denote a physical thing, a replaceable device, or a digital representation? definition
- What evidence establishes the mapping, and how is it revised when a device is replaced or reassigned? provenance
Physical observations and actions Captures the meaning and evidential limits of sensing and actuation.
Successful message exchange alone cannot establish an accurate observation or a completed physical action.
Observation meaning
Makes sensor outputs interpretable as evidence about a physical condition.
Observation validity
Record measured quantity, units, sampling context, timestamps, and relevant quality or calibration information.
- What quantity does each observation represent, in which units and at which physical location? measurement
- What sampling time, uncertainty, calibration history, or quality flag limits its use as evidence of current state? provenance
Actuation outcomes
Relates digital commands to permitted physical transitions and observable results.
Command effect verification
Distinguish requested, accepted, executed, and physically verified actions, including failed or uncertain outcomes.
- Which physical transitions can an endpoint perform, and what preconditions and limits apply? action
- What feedback proves the intended physical effect occurred rather than only confirming message receipt? measurement
Connectivity and interoperability Describes how things exchange information and preserve its meaning across component boundaries.
An endpoint can be reachable while its data or commands remain incompatible with the receiving system.
Communication paths
Traces direct and mediated connections, including intermittent and constrained links.
Endpoint reachability
Record the path between a physical endpoint and its consumers or controllers, with dependencies and delivery constraints.
- Through which local networks, gateways, and remote services do observations and commands travel? boundary
- What measured latency, loss, disconnection periods, and payload limits constrain those paths? measurement
Shared interface meaning
Establishes how components agree on capabilities and message interpretation.
Interface compatibility
Record interface versions, capability descriptions, data meanings, and any translations performed by intermediaries.
- How do components describe and discover supported observations, commands, units, and interface versions? definition
- Which interface specifications or compatibility tests support interoperability claims across vendors and gateways? provenance
Distributed operation Captures the placement of processing and control, and behaviour when distributed components disagree or disconnect.
IoT decisions can span physical devices and remote services whose availability and state differ.
Processing and control placement
Assigns operational responsibilities to device, gateway, edge, and remote components.
Decision dependencies
Record where observations are processed and control decisions are made, including dependencies on remote computation.
- Which sensing, filtering, inference, and control functions run on devices, gateways, or remote services? definition
- Which functions remain available when the gateway or remote service cannot be reached? boundary
Disconnection and reconciliation
Defines handling of stale state, buffered observations, and commands across interruptions.
Reconnection behaviour
Record how components reconcile reported and desired state without replaying obsolete or unsafe actions.
- How are stale observations, duplicate messages, expired commands, and conflicting state detected? definition
- When connectivity returns, which buffered messages may be applied, discarded, or reviewed before execution? action
Trust and physical consequences Connects identity, authority, data handling, and safeguards to the system's physical reach.
Connected sensing can disclose physical activity, while connected control can produce physical consequences.
Access and data authority
Determines who may connect, observe, control, and receive data.
Authorised participation
Record authentication, operation-level permissions, and data destinations for devices, services, people, and agents.
- How are device and service identities authenticated, and which principals may read, configure, or actuate each endpoint? action
- Which observations can reveal people or sensitive physical activity, and what authority governs their collection and onward use? boundary
Physical action safeguards
Captures controls that bound the effects of remote commands and compromised components.
Local enforcement and isolation
Record local interlocks, command limits, manual overrides, and isolation behaviour relevant to physical operation.
- Which physical limits and interlocks are enforced locally even when an authorised remote service issues a command? boundary
- How can an endpoint be isolated or control transferred locally, and what physical state results? action
Fleet lifecycle and maintainability Tracks connected endpoints from enrolment through maintenance, ownership changes, and retirement.
IoT operation depends on maintaining distributed physical equipment alongside identities, firmware, and services.
Enrolment and maintenance
Establishes how endpoints enter service and remain observable and maintainable.
Deployment readiness
Record provisioning evidence, installed firmware, configuration, energy constraints, and update recovery capabilities.
- What checks bind a newly enrolled endpoint to the intended physical thing, owner, and configuration? provenance
- How do available energy, connectivity windows, and recovery mechanisms constrain maintenance and firmware updates? action
Transfer and retirement
Resolves physical and digital dependencies when endpoints change hands or leave service.
End-of-service resolution
Record credential revocation, ownership transfer, retained data, and the effects of discontinued support or services.
- What must be revoked, erased, retained, or reassigned when a device is retired or ownership changes? action
- Which physical functions cease or become restricted if vendor support, certificates, or required remote services end? boundary
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- This describes IoT as a technological system category, not a single physical device; the PHY.OBJ classification should be reviewed.
- Standards and identifier schemes are recalled, not checked against source documents; their current editions, scope, and applicability require verification.
- There are no useful category-wide typical ranges for dimensions, power, latency, throughput, or operating life; these require a specified device class and deployment.
- Which of these check these first hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Kinds and varieties
Recalled without web access and unsourced; every item is a lead to verify.
- Consumer and smart-home IoT
- Industrial IoT
- Healthcare IoT
- Agricultural IoT
- Smart-city IoT
- Connected transport and logistics IoT
- Which of these kinds and varieties hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- IPv6 address - 128-bit address conventionally represented as colon-separated hexadecimal groups - Identifies an IP network interface; not every IoT device uses IP directly, and an address is not necessarily a persistent device identity.
- IEEE EUI-48 and EUI-64 - 48-bit or 64-bit identifier - Used for interface or equipment identification in relevant technologies; not a universal IoT identification scheme.
- GS1 Electronic Product Code (EPC) - Structured identifiers with encodings defined by the GS1 EPC Tag Data Standard - Used to identify physical objects in applications such as RFID-based tracking; identifies the object rather than necessarily its network endpoint.
- Which of these identifiers and schemes hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Standards and regulation
Recalled without web access and unsourced; every item is a lead to verify.
- ISO/IEC 30141 - Internet of Things reference architecture, issued by ISO and IEC.
- ISO/IEC 20924 - Internet of Things vocabulary, issued by ISO and IEC.
- ETSI EN 303 645 - cybersecurity baseline for consumer Internet of Things, issued by ETSI.
- MQTT Version 5.0 - publish/subscribe messaging protocol standardized by OASIS.
- RFC 7252 - Constrained Application Protocol (CoAP), published by the IETF.
- Which of these standards and regulation hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Monitoring industrial equipment condition and supporting predictive maintenance.
- Controlling building lighting, heating, ventilation, and energy consumption.
- Tracking goods, vehicles, and cold-chain conditions.
- Monitoring soil and weather conditions to inform irrigation.
- Collecting measurements from connected medical and home-monitoring devices.
- Which of these real-world use hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Compromised credentials, insecure interfaces, or unpatched firmware can permit unauthorized access and control.
- Network or service outages can interrupt monitoring and remote control.
- Sensor drift, poor calibration, or corrupted data can produce incorrect decisions or unsafe actuation.
- Battery depletion, power loss, and environmental damage can disable unattended devices.
- Excessive data collection or weak access controls can expose personal information and enable surveillance.
- Which of these failure modes and hazards hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- Permitted radio bands, transmit-power limits, and equipment approval requirements differ by jurisdiction.
- Privacy, cybersecurity, and data-transfer obligations differ by jurisdiction and application sector.
- Available network coverage and infrastructure influence connectivity choices and deployment feasibility.
- Which of these regional variation hold for the sense of Internet of Things this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Internet - The Internet is the general network infrastructure; IoT concerns connected physical objects and their associated services.
- Embedded system - An embedded system performs dedicated computing functions within equipment and need not communicate over a network.
- Cyber-physical system - A cyber-physical system integrates computation with physical processes; Internet connectivity is not required, and feedback control is often central.
- Machine-to-machine communication - Machine-to-machine communication describes automated exchanges between machines; IoT additionally encompasses connected objects, platforms, applications, and services.
- Wireless sensor network - A wireless sensor network connects sensing nodes and may remain local; IoT also includes actuators, wired connections, and integration with wider services.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Internet of Things this model covers, and on what evidence? provenance
What the second pass must settle
- Does an existing Vercy world model already own this concept, requiring the registry entry to link to it rather than establish a separate publication?
- Which authoritative definition should govern whether closed local networks, passive identification tags, and systems without Internet connectivity qualify as Internet of Things?
- How should the PHY / PHY.OBJ placement represent this system-level concept while relating it to its information, activity, and organisational aspects?
- Which standards and issuing bodies should anchor terminology, interoperability, security, and lifecycle expectations, and which requirements depend on deployment sector or jurisdiction?
- What deployment evidence is needed to set acceptable observation age, action latency, disconnected behaviour, and update recovery criteria without inventing universal thresholds?