{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.tr.bluetooth","code":"thing-q39531","url":"https://ver.cy/models/thing/q39531/","name":"Bluetooth","alternateNames":["Bluetooth 5"],"kind":"thing","status":"published","version":"0.1.0-research.1","language":"en","classifiers":{"family":"Thing Registry","category":"Physical world and living systems","entryKind":"thing","plane":"PHY","domain":["PHY.OBJ"],"industry":[],"navPath":"","tags":[],"facets":{}},"whatItIs":"Bluetooth is a short-range wireless communications technology and open protocol stack, specified by the Bluetooth Special Interest Group, that enables devices to discover, pair, and exchange data over unlicensed 2.4 GHz ISM-band radio using frequency-hopping spread spectrum.","purpose":"Enable an AI agent to recognise a Bluetooth implementation, assess its supported interactions and current state, and decide which discovery, connection, data exchange or configuration actions are appropriate.","scope":{"in":["Evidence that an implementation uses Bluetooth and which transports, roles and features it supports","Bluetooth discovery, advertising, scanning, pairing, bonding and connection states","Profiles, services and characteristics through which Bluetooth peers can interact","Radio configuration, observed link quality and coexistence conditions","Bluetooth-specific permissions, trust relationships and permitted actions"],"out":["The complete physical device, its ownership and its non-Bluetooth functions","Wi-Fi, NFC, Zigbee and other neighbouring communication technologies","Application meaning and governance of data carried over Bluetooth","Battery chemistry, charging systems and general device power management","The full operating system, firmware lifecycle and general vulnerability management","Bluetooth SIG governance and commercial qualification administration"],"boundaries":[]},"distinguishingFeatures":["Require Bluetooth protocol, controller or service evidence; operation in the 2.4 GHz band alone does not distinguish Bluetooth from Wi-Fi or other radios.","Distinguish Bluetooth BR/EDR from Bluetooth Low Energy using supported transport and procedure evidence; a generic Bluetooth label does not establish support for both.","Identify Bluetooth interaction contracts through advertised or discovered profiles and services; a device name or product category does not establish interoperability.","Distinguish a Bluetooth peer relationship from proximity alone by recording the actual advertising, discovery, connection or bonding evidence.","Distinguish a Bluetooth address from enduring device identity by checking its address type and any supported identity-resolution evidence."],"structure":{"bundles":[{"id":"bluetooth-identity-and-capability","name":"Bluetooth identity and capability","description":"Establishes what Bluetooth subject is being described and which capabilities have evidence.","layers":[{"id":"subject-and-protocol-evidence","name":"Subject and protocol evidence","description":"Separates the registered technology concept from its interfaces and endpoints.","findings":[{"id":"identify-bluetooth-subject","name":"Identify the Bluetooth subject","description":"Record the subject boundary and the evidence that identifies its communication interface as Bluetooth.","questions":[{"text":"Does this record describe Bluetooth as a technology, a particular controller or interface, a peer endpoint or a deployment?","id":"identify-bluetooth-subject-q01","kind":"boundary"},{"text":"Which inspected controller information, protocol observation or implementation documentation establishes Bluetooth support?","id":"identify-bluetooth-subject-q02","kind":"provenance"}]}]},{"id":"transport-and-feature-support","name":"Transport and feature support","description":"Records supported transports, roles and optional features without inferring them from a version number.","findings":[{"id":"establish-usable-capabilities","name":"Establish usable capabilities","description":"Distinguish advertised, documented and directly verified capability support.","questions":[{"text":"Which BR/EDR or LE transports and roles are supported, and which are exposed to the agent?","id":"establish-usable-capabilities-q01","kind":"definition"},{"text":"What evidence supports each required feature beyond the reported Bluetooth version?","id":"establish-usable-capabilities-q02","kind":"provenance"}]}]}]},{"id":"radio-and-link-behaviour","name":"Radio and link behaviour","description":"Describes Bluetooth radio availability and the observed conditions of particular links.","layers":[{"id":"radio-availability-and-observation","name":"Radio availability and observation","description":"Distinguishes an unavailable controller from an enabled radio that has not observed a peer.","findings":[{"id":"assess-radio-conditions","name":"Assess radio conditions","description":"Record controller availability and contextualised observations without translating signal strength directly into distance.","questions":[{"text":"Is the Bluetooth controller enabled and available to the agent, or blocked by hardware, platform policy or permissions?","id":"assess-radio-conditions-q01","kind":"measurement"},{"text":"What timestamped reception, loss or coexistence observations explain the peer's current visibility, and what remains unobserved?","id":"assess-radio-conditions-q02","kind":"measurement"}]}]},{"id":"negotiated-link-performance","name":"Negotiated link performance","description":"Relates active transport parameters to the requirements of the intended service.","findings":[{"id":"assess-link-fitness","name":"Assess link fitness","description":"Evaluate actual link behaviour rather than treating nominal radio capability as delivered performance.","questions":[{"text":"Which transport, PHY and link parameters are active, and what latency, throughput or failure behaviour has been measured?","id":"assess-link-fitness-q01","kind":"measurement"},{"text":"Which exposed parameter changes could meet the service requirement, and what responsiveness or energy tradeoffs must be accepted?","id":"assess-link-fitness-q02","kind":"action"}]}]}]},{"id":"peer-discovery-and-session-lifecycle","name":"Peer discovery and session lifecycle","description":"Tracks how Bluetooth peers become observable, identifiable and connected.","layers":[{"id":"discovery-and-peer-recognition","name":"Discovery and peer recognition","description":"Records visibility procedures and the strength of evidence linking observations to a peer.","findings":[{"id":"recognise-observed-peer","name":"Recognise an observed peer","description":"Preserve address type, observation context and identity uncertainty when recognising Bluetooth endpoints.","questions":[{"text":"Was the peer observed through LE advertising or scanning, BR/EDR discovery or another supported Bluetooth procedure?","id":"recognise-observed-peer-q01","kind":"provenance"},{"text":"What evidence links this observation to the intended peer despite address changes, duplicate names or stale discovery results?","id":"recognise-observed-peer-q02","kind":"provenance"}]}]},{"id":"connection-transitions","name":"Connection transitions","description":"Separates supported connection procedures from current peer-specific session state.","findings":[{"id":"choose-session-transition","name":"Choose a session transition","description":"Record active connections, role constraints and failure reasons before choosing the next lifecycle action.","questions":[{"text":"For the intended peer, is connection establishment pending, active, failed or ended, and what event or reason supports that state?","id":"choose-session-transition-q01","kind":"measurement"},{"text":"Can the agent initiate, accept, retry or terminate this connection given the active roles, peer availability and concurrent-connection limits?","id":"choose-session-transition-q02","kind":"action"}]}]}]},{"id":"profiles-services-and-data-access","name":"Profiles, services and data access","description":"Establishes what useful Bluetooth interactions compatible peers can perform.","layers":[{"id":"interaction-contract","name":"Interaction contract","description":"Identifies profiles and services required for an intended function.","findings":[{"id":"verify-service-compatibility","name":"Verify service compatibility","description":"Record the profile or service, complementary roles and required features behind the requested interaction.","questions":[{"text":"Which Bluetooth profile or service implements the requested function, and which roles must each peer provide?","id":"verify-service-compatibility-q01","kind":"definition"},{"text":"Which advertised, discovered or tested evidence confirms the required service and features on both peers?","id":"verify-service-compatibility-q02","kind":"provenance"}]}]},{"id":"permitted-data-operations","name":"Permitted data operations","description":"Describes the operations exposed by a discovered service and their prerequisites.","findings":[{"id":"select-service-operation","name":"Select a service operation","description":"Connect service-specific operations to supported properties, access requirements and freshness of discovery evidence.","questions":[{"text":"For the chosen service, which operations are available, including GATT reads, writes, notifications or indications where applicable?","id":"select-service-operation-q01","kind":"definition"},{"text":"What security, authorization, subscription or service-rediscovery prerequisites must be satisfied before the requested operation?","id":"select-service-operation-q02","kind":"action"}]}]}]},{"id":"pairing-trust-and-authority","name":"Pairing, trust and authority","description":"Records Bluetooth security relationships and the authority to create, use or revoke them.","layers":[{"id":"pairing-and-link-protection","name":"Pairing and link protection","description":"Separates pairing method, stored bonding material and protection of the current connection.","findings":[{"id":"assess-peer-security","name":"Assess peer security","description":"Record independently evidenced security properties and any required human participation.","questions":[{"text":"What pairing method and resulting authentication properties are evidenced, and is a bond stored for this peer?","id":"assess-peer-security-q01","kind":"measurement"},{"text":"Is the current link encrypted with protection sufficient for the requested service, and does pairing require user confirmation or an out-of-band step?","id":"assess-peer-security-q02","kind":"action"}]}]},{"id":"permission-and-trust-revocation","name":"Permission and trust revocation","description":"Connects Bluetooth operations to platform permissions, user intent and peer-specific authorization.","findings":[{"id":"bound-agent-authority","name":"Bound agent authority","description":"Record who permits discovery, access and trust changes, including the operational consequences of revocation.","questions":[{"text":"Which user instruction, platform permission and service authorization permit the agent's proposed Bluetooth action?","id":"bound-agent-authority-q01","kind":"provenance"},{"text":"When may the agent disconnect, remove a bond or disable Bluetooth, and which dependent interactions would that interrupt?","id":"bound-agent-authority-q02","kind":"action"}]}]}]},{"id":"evidence-and-external-alignment","name":"Evidence and external alignment","description":"What the world already says about this thing, gathered so the model can be checked against it.","layers":[{"id":"reported-evidence","name":"Reported evidence","description":"Findings from the breadth pass, kept separate from the structural claims.","findings":[{"id":"evidence-kinds","name":"Kinds and varieties","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these kinds and varieties hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-kinds-q01","kind":"provenance"}]},{"id":"evidence-identifiers","name":"Identifiers and schemes","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these identifiers and schemes hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-identifiers-q01","kind":"provenance"}]},{"id":"evidence-standards-and-regulation","name":"Standards and regulation","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these standards and regulation hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-standards-and-regulation-q01","kind":"provenance"}]},{"id":"evidence-real-world-use","name":"Real-world use","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these real-world use hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-real-world-use-q01","kind":"provenance"}]},{"id":"evidence-measurements","name":"Typical measurements","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these typical measurements hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-measurements-q01","kind":"provenance"}]},{"id":"evidence-failure-modes-and-hazards","name":"Failure modes and hazards","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these failure modes and hazards hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-failure-modes-and-hazards-q01","kind":"provenance"}]},{"id":"evidence-regional-variation","name":"Regional variation","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these regional variation hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-regional-variation-q01","kind":"provenance"}]},{"id":"evidence-neighbours","name":"Neighbouring kinds and how to tell them apart","description":"Reported by the breadth pass; each item needs checking against its source before it becomes normative.","questions":[{"text":"Which of these neighbouring kinds and how to tell them apart hold for the sense of Bluetooth this model covers, and on what evidence?","id":"evidence-neighbours-q01","kind":"provenance"}]}]}]}]},"agentConduct":{"may":["Pair and connect devices with their owner's consent.","Report connection status, battery and signal for devices it manages.","Turn short-range radio off when the owner asks or the device is not in use."],"mustNot":["Scan for and log nearby people's devices to track their movements without consent.","Pair with or connect to a device that its owner has not approved.","Leave a device discoverable in a way that exposes it to attack.","Use the link to read data from devices the agent does not control."],"requiresHuman":["Pairing medical devices such as hearing aids or insulin pumps.","Unlocking vehicles or doors over short-range radio."]},"ethics":{"considerations":["Device identifiers can be used to track people through shops, streets and homes.","Short-range links now control locks, cars and medical devices, so security matters for safety."],"affectedParties":["Device owners","People nearby being scanned","Users of medical devices"]},"owners":{"steward":"The owner of each device; the technology's specification is maintained by an industry group.","roles":[],"masterSystems":[]},"relations":[{"target":"Q11375","type":"parent","note":"registry parent class"}],"interaction":{"identity":{"applicability":"required","items":["Vercy registry: vr.tr.bluetooth","Wikidata: Q39531 (https://www.wikidata.org/wiki/Q39531)"]},"properties":{"applicability":"required","items":["Modelled Bluetooth subject: technology definition | controller or interface | peer endpoint | deployment | unresolved","Supported transports: BR/EDR | LE | both | unknown","Reported specification and feature support: reported version, explicitly supported features and supporting evidence","Bluetooth roles: transport-specific supported and active roles, including LE central, peripheral, broadcaster or observer where applicable","Address and identity basis: observed address, address type, observation time and identity-resolution basis where available","Procedure and connection state: supported, active or unavailable advertising, scanning, discovery and connection procedures, recorded separately","Service compatibility: peer-specific profile, service, characteristic, role and feature compatibility evidence","Observed received signal strength: dBm, with peer, observation time and measurement context","Negotiated link parameters: transport-specific values, such as LE connection interval in ms, PHY and negotiated data limits","Peer security state: separate pairing, bonding, encryption, authentication and application-authorization states, with unknown allowed"]},"recognition":{"applicability":"not-applicable","items":[]},"capabilities":{"applicability":"required","items":["Discover or observe Bluetooth peers using supported procedures and granted permissions.","Evaluate whether a peer supports the transport, roles and services needed for a requested interaction.","Initiate or accept an authorised connection, pairing or bonding procedure.","Read, write, subscribe to or exchange data through compatible services within their access requirements.","Adjust exposed Bluetooth settings or link preferences within implementation limits and operational constraints.","Diagnose failed interactions and, when authorised, disconnect peers, remove bonds or disable the interface."]},"hazards":{"applicability":"required","items":["Tracking of people through device identifiers.","Unauthorized pairing and data access.","Interference or dropped links in crowded radio environments."]},"interfaces":{"applicability":"required","items":["IEEE 802.15.1, Wireless personal area networks, Institute of Electrical and Electronics Engineers.","Directive 2014/53/EU on radio equipment, European Union."]},"context":{"applicability":"required","items":["This protocol is used for nearby wireless connections between computing devices, peripherals, audio equipment and sensors.","It supports activities such as audio transmission, input control and small data exchanges where compatible devices need a local radio link.","Supported interactions depend on the implemented protocol versions, profiles and device configuration."]}},"sources":[{"title":"Wikidata item Q39531: Bluetooth","url":"https://www.wikidata.org/wiki/Q39531","note":"identity and sense of the item"},{"title":"Wikipedia: Bluetooth","url":"https://en.wikipedia.org/wiki/Bluetooth","note":"general description of the item"}],"openQuestions":["Does the registry intend Bluetooth to denote the communication technology, a physical interface or a deployed system, and how should that interpretation align with its PHY.OBJ placement?","Does an existing Vercy world model already own Bluetooth or the relevant wireless-interface concept, requiring this entry to link to it?","Should Bluetooth Mesh, LE Audio, broadcast services and specialised positioning capabilities be extensions of this entry or references to neighbouring models?","Which authoritative specification sections and implementation documents should support the final capability, security and lifecycle findings?","Which controller and platform observations will actually be available to agents, especially for address resolution, pairing authentication and negotiated link parameters?"],"resources":{"spec":"/models/things/publications/thing-q39531/spec.json"},"provenance":{"origin":"thing registry research (pass 2)","builtFrom":["models/things/publications/thing-q39531/spec.json"],"providers":["Codex","Grok"],"researchStatus":"unreviewed","generatedAt":"2026-09-07T10:11:53Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"filled","interaction.recognition":"not-applicable","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_gate":"Published through the thing publication gate 1.0 on 2026-10-07T10:10:30+00:00: completeness 1.00; sense: Wikidata description; 2 live sources; review by codex: pass","interaction.recognition":"The protocol cannot be perceived directly, and device markings or interface indicators cannot by themselves establish an active or compatible implementation."},"score":1.0}}