{ "model": { "rank": 4686, "code": "thing-q58199", "model_id": "vr.tr.instant-messaging", "name": "instant messaging", "purpose": "Enable an AI agent to recognise instant messaging, assess whether a conversation can proceed, and choose permitted messaging actions without confusing message submission with delivery or reading.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q58199/", "tier": 2, "score": 73, "payload": { "layer": "wikidata", "aliases": [ "private message", "Live support software", "videochat", "distributed multimedia communications platform", "Yamigo", "voice message" ], "aliasCount": 6, "merged": 6, "knownIn": 73, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q58199", "url": "https://www.wikidata.org/wiki/Q58199", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T20:47:34Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087ec-1051-7b63-ba6e-eb55caa8eb2d\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: instant messaging\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 10", "usd": 0, "recall": true }, "codex": { "seconds": 64.9, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087ec-1046-7d10-9290-5d2746a0eb2c\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: instant messaging\nRegistry id: vr.tr.instant-messaging\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entr" } } }, "metaModel": { "id": "THING-Q58199", "registryId": "vr.tr.instant-messaging", "name": "instant messaging", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q58199/", "model": { "registry_id": "vr.tr.instant-messaging", "name": "instant messaging", "purpose": "Enable an AI agent to recognise instant messaging, assess whether a conversation can proceed, and choose permitted messaging actions without confusing message submission with delivery or reading.", "definition": "Instant messaging is a networked communication service that exchanges discrete messages between identified participants with delivery intended to support near-real-time conversation, often alongside presence information and offline message storage.", "scope_statement": "This model owns instant messaging as a networked communication capability for exchanging discrete messages in conversational threads with an expectation of prompt interaction, including its participation rules, message states and operational constraints; it does not represent a particular application, device or message.", "in_scope": [ "Direct and group conversations organised around discrete messages", "Participant addressing, membership and reachability", "Message submission, delivery, ordering and acknowledgement", "Conversation continuity across offline periods and connected devices", "Messaging permissions, confidentiality and abuse controls", "Capabilities such as attachments, replies, editing and deletion when supported" ], "out_of_scope": [ "The hardware and operating systems of participant devices", "General network infrastructure and connectivity provisioning", "Email, public publishing feeds and live voice or video sessions as separate communication modes", "The substantive meaning and domain-specific correctness of message content", "A provider's entire application, business model or organisation", "Individual messages as independently catalogued information objects" ], "distinguishing_features": [ "The primary interaction exchanges discrete messages within a continuing conversation, rather than transmitting a continuous voice or video stream.", "The interface and delivery behaviour support prompt conversational exchange, although participants need not be online simultaneously.", "Messages are directed to an identified recipient or conversation membership, rather than primarily published for discovery by an unrestricted audience.", "Presence indicators, typing indicators and read receipts may support the interaction, but their absence does not by itself exclude instant messaging.", "A messaging capability is distinguished from the application hosting it: a multipurpose application can contain instant messaging alongside unrelated communication modes." ], "characteristics": [ { "name": "Conversation topology", "kind": "category", "unit_or_values": "one-to-one; group; other explicitly described topology", "why_it_matters": "Determines who can participate and how an agent must establish the intended audience." }, { "name": "Participant addressing", "kind": "category", "unit_or_values": "account identifier; telephone number; service-scoped handle; other documented address", "why_it_matters": "Determines how recipients are resolved and where identity ambiguity can arise." }, { "name": "Participant reachability", "kind": "state", "unit_or_values": "reachable now; offline delivery available; unreachable; unknown", "why_it_matters": "Helps an agent decide whether to send, defer or report that prompt contact is uncertain." }, { "name": "Message lifecycle state", "kind": "state", "unit_or_values": "locally pending; service accepted; recipient endpoint delivered; read indicated; failed; unknown, mapped to documented service semantics", "why_it_matters": "Prevents an acknowledgement at one stage from being reported as success at a later stage." }, { "name": "Observed delivery latency", "kind": "measurement", "unit_or_values": "milliseconds or seconds, with start event, end event, observation period and conditions", "why_it_matters": "Tests whether an observed exchange meets the interaction's timing needs without imposing an unsupported universal threshold." }, { "name": "Conversation membership", "kind": "relation", "unit_or_values": "conversation to current participants, roles and membership-change events", "why_it_matters": "Defines the audience and whether an agent may send messages or change participation." }, { "name": "Confidentiality mode", "kind": "category", "unit_or_values": "transport encryption only; end-to-end encryption; other documented protection; unprotected; unknown", "why_it_matters": "Supports decisions about suitable content and identifies whose access must be considered." }, { "name": "Message retention behaviour", "kind": "category", "unit_or_values": "persistent; expiration configured; session-limited; other documented behaviour; unknown", "why_it_matters": "Determines expected history availability and the limits of deletion or expiration claims." }, { "name": "Supported message operations", "kind": "category", "unit_or_values": "documented subset of send, reply, react, attach, edit, retract, forward and search", "why_it_matters": "Prevents an agent from assuming that every conversation supports the same actions." } ], "affordances": [ "Resolve an intended recipient and open or select an authorised conversation.", "Compose and send a supported message after checking audience and permissions.", "Inspect available message acknowledgements and report the strongest state actually evidenced.", "Reply, react, edit or retract within the conversation's supported operations and limits.", "Manage invitations, membership, notifications or blocking where the agent has authority.", "Recover from uncertain submission or delivery without blindly duplicating messages." ] }, "sources": [], "structure": { "bundles": [ { "id": "conversation-and-addressing", "name": "Conversation and addressing", "description": "Establishes what counts as a messaging conversation and how its audience is resolved.", "rationale": "An instant message can reach the wrong audience even when transport succeeds; conversation boundaries and addressing must be explicit.", "layers": [ { "id": "interaction-boundary", "name": "Interaction boundary", "description": "Separates the instant messaging capability from adjacent communication modes and its hosting application.", "findings": [ { "id": "messaging-mode-recognition", "name": "Messaging mode recognition", "description": "Record the evidence that an interaction consists of discrete conversational messages intended to support prompt exchange.", "questions": [ { "text": "What observable behaviour establishes that this capability supports instant messaging?", "kind": "definition", "id": "messaging-mode-recognition-q01" }, { "text": "Where does this conversation switch into a neighbouring mode such as public publishing, email or a live call?", "kind": "boundary", "id": "messaging-mode-recognition-q02" } ] } ] }, { "id": "recipient-resolution", "name": "Recipient resolution", "description": "Connects addresses and conversation identifiers to the intended participants.", "findings": [ { "id": "audience-resolution", "name": "Audience resolution", "description": "Record address namespaces, resolved identities and current conversation membership before treating a destination as established.", "questions": [ { "text": "Which identifier and service namespace resolve the intended person or group, and what confirms the match?", "kind": "provenance", "id": "audience-resolution-q01" }, { "text": "Who will receive a message sent to this conversation now, including bots or bridged participants?", "kind": "boundary", "id": "audience-resolution-q02" } ] } ] } ] }, { "id": "delivery-and-observability", "name": "Delivery and observability", "description": "Models the path from local submission to the available evidence of receipt.", "rationale": "Conversational decisions depend on whether a message was merely queued, delivered to an endpoint or indicated as read.", "layers": [ { "id": "message-lifecycle", "name": "Message lifecycle", "description": "Interprets message status signals according to their actual scope.", "findings": [ { "id": "acknowledgement-semantics", "name": "Acknowledgement semantics", "description": "Record what each acknowledgement establishes, which component issued it and which recipients it covers.", "questions": [ { "text": "What event does each pending, sent, delivered or read indicator actually represent?", "kind": "definition", "id": "acknowledgement-semantics-q01" }, { "text": "For a group or participant with multiple devices, which recipients or endpoints does the indicator cover?", "kind": "boundary", "id": "acknowledgement-semantics-q02" }, { "text": "What delivery claim can the agent make when receipts are disabled or unavailable?", "kind": "action", "id": "acknowledgement-semantics-q03" } ] } ] }, { "id": "timing-and-recovery", "name": "Timing and recovery", "description": "Captures delays, uncertain outcomes and safe continuation after connectivity failures.", "findings": [ { "id": "delayed-and-uncertain-delivery", "name": "Delayed and uncertain delivery", "description": "Record observed latency, offline queue behaviour and evidence available before retrying an uncertain send.", "questions": [ { "text": "What latency is observed between specified submission and delivery events under the relevant connectivity conditions?", "kind": "measurement", "id": "delayed-and-uncertain-delivery-q01" }, { "text": "When a send times out, how can the agent determine whether it was accepted before retrying?", "kind": "action", "id": "delayed-and-uncertain-delivery-q02" }, { "text": "How long can an undelivered message remain queued, and what evidence marks expiration or failure?", "kind": "definition", "id": "delayed-and-uncertain-delivery-q03" } ] } ] } ] }, { "id": "presence-and-continuity", "name": "Presence and continuity", "description": "Represents availability signals and how conversations continue across absences and devices.", "rationale": "Instant messaging supports conversational continuity despite incomplete availability information and changing endpoints.", "layers": [ { "id": "availability-signals", "name": "Availability signals", "description": "Interprets presence and typing indicators without treating them as commitments to respond.", "findings": [ { "id": "presence-evidence", "name": "Presence evidence", "description": "Record the meaning, freshness and visibility limits of online, last-active and typing signals.", "questions": [ { "text": "What activity produces each presence or typing signal, and when does it become stale?", "kind": "definition", "id": "presence-evidence-q01" }, { "text": "How should the agent proceed when availability is hidden, stale or inconsistent across devices?", "kind": "action", "id": "presence-evidence-q02" } ] } ] }, { "id": "history-synchronisation", "name": "History synchronisation", "description": "Tracks whether endpoints expose a sufficiently consistent conversation history.", "findings": [ { "id": "cross-device-conversation-state", "name": "Cross-device conversation state", "description": "Record history availability and the reconciliation of message order, edits and deletions after reconnection.", "questions": [ { "text": "Which history becomes available on a newly linked or reconnected device, and under what conditions?", "kind": "boundary", "id": "cross-device-conversation-state-q01" }, { "text": "How are missing messages, conflicting order and delayed edits or deletions identified and reconciled?", "kind": "definition", "id": "cross-device-conversation-state-q02" } ] } ] } ] }, { "id": "message-actions-and-group-control", "name": "Message actions and group control", "description": "Defines supported message operations and the authority required to act within a conversation.", "rationale": "An agent needs conversation-specific action limits to avoid unsupported changes or unintended audience expansion.", "layers": [ { "id": "message-operations", "name": "Message operations", "description": "Describes content capabilities and the effects of modifying an existing message.", "findings": [ { "id": "supported-content-and-mutation", "name": "Supported content and mutation", "description": "Record supported payloads, size limits, reply references and the scope of edits or retractions.", "questions": [ { "text": "Which text, attachment and structured-message forms are accepted, with what size limits and units?", "kind": "measurement", "id": "supported-content-and-mutation-q01" }, { "text": "What time limits and recipient-visible effects apply to editing or retracting a message?", "kind": "action", "id": "supported-content-and-mutation-q02" }, { "text": "Does a reply preserve a stable reference to its original message if that message changes or disappears?", "kind": "definition", "id": "supported-content-and-mutation-q03" } ] } ] }, { "id": "participation-authority", "name": "Participation authority", "description": "Establishes permission to post, invite, remove participants and operate automated accounts.", "findings": [ { "id": "membership-and-role-effects", "name": "Membership and role effects", "description": "Record role-dependent actions and how membership changes affect message access.", "questions": [ { "text": "Which participant roles may post, invite, remove members or change conversation settings?", "kind": "action", "id": "membership-and-role-effects-q01" }, { "text": "What prior history and future messages become accessible when a participant or bot joins, leaves or is removed?", "kind": "boundary", "id": "membership-and-role-effects-q02" } ] } ] } ] }, { "id": "confidentiality-retention-and-abuse", "name": "Confidentiality, retention and abuse", "description": "Captures who can access messaging data, how long it persists and how unwanted contact is controlled.", "rationale": "Messaging actions expose content to recipients and service components, while deletion and blocking can have narrower effects than their labels suggest.", "layers": [ { "id": "access-and-persistence", "name": "Access and persistence", "description": "Establishes protection boundaries and the fate of retained conversation data.", "findings": [ { "id": "content-access-and-retention", "name": "Content access and retention", "description": "Record documented access to content and metadata, including the effects of backups, linked devices and expiration settings.", "questions": [ { "text": "What documentation or inspection establishes the protection mode and which parties can access content or metadata?", "kind": "provenance", "id": "content-access-and-retention-q01" }, { "text": "Which copies are affected by deletion or expiration, and which may remain in backups, exports or recipient-held records?", "kind": "boundary", "id": "content-access-and-retention-q02" } ] } ] }, { "id": "unwanted-contact-controls", "name": "Unwanted contact controls", "description": "Describes controls for unsolicited messages, disruptive participants and abusive content.", "findings": [ { "id": "blocking-and-reporting-effects", "name": "Blocking and reporting effects", "description": "Record the distinct effects of muting, blocking and reporting, including any content disclosed by a report.", "questions": [ { "text": "How do muting, blocking and message-request filtering change delivery, notifications and visibility in direct and shared group conversations?", "kind": "definition", "id": "blocking-and-reporting-effects-q01" }, { "text": "What content and metadata would a report disclose, to whom, and what authority does the agent have to submit it?", "kind": "action", "id": "blocking-and-reporting-effects-q02" } ] } ] } ] }, { "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.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The supplied PHY.OBJ classification is questionable: this description covers a communication service, not a physical device.", "Recalled standards and identifier details have not been checked against source documents; the listed RFCs concern particular implementations, not every messaging service.", "There is no universal numerical threshold for 'instant'; latency, message size limits, retention and group capacity depend on the implementation." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "One-to-one messaging", "Group messaging", "Enterprise messaging", "Federated messaging", "Peer-to-peer messaging", "Mobile messaging" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "XMPP address (Jabber ID, JID)", "value_or_pattern": "localpart@domainpart/resourcepart", "note": "Identifies an XMPP entity; the localpart and resourcepart are optional in some address forms. This is protocol-specific, not a universal instant-messaging identifier." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "IETF RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core.", "IETF RFC 6121: XMPP: Instant Messaging and Presence.", "IETF RFC 3428: Session Initiation Protocol (SIP) Extension for Instant Messaging." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Personal conversations and group coordination.", "Workplace collaboration and operational communication.", "Customer support conversations.", "Community discussion and moderation.", "Automated notifications and interactions with software agents." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Network or service outages can delay or prevent message delivery.", "Retries and synchronization failures can produce duplicate messages or inconsistent conversation histories.", "Presence indicators and delivery or read receipts can be stale or misleading.", "Account compromise, impersonation and malicious attachments can enable fraud or malware delivery.", "Inadequate access controls, insecure backups or compromised endpoints can expose private conversations." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Preferred services and interoperability practices vary between countries and user communities.", "Service availability can differ because of network blocking and government restrictions.", "Applicable privacy, retention and workplace-monitoring requirements vary by jurisdiction." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Email", "difference": "Email is primarily organized around asynchronously exchanged mail messages; instant messaging is organized around conversational exchanges with near-real-time delivery expectations." }, { "name": "SMS", "difference": "SMS is a specific cellular messaging service; instant messaging is a broader service category commonly implemented through internet applications." }, { "name": "Chat room", "difference": "A chat room organizes conversation around a shared space or channel; instant messaging can address individuals or groups, and the categories overlap." }, { "name": "Real-time text", "difference": "Real-time text transmits text progressively as it is entered; instant messaging usually transmits completed messages after a send action." }, { "name": "Messaging application", "difference": "An application is software that implements or accesses messaging; instant messaging names the communication service or activity." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of instant messaging this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend instant messaging to denote a communication capability, a service class or a software tool, and how should that interpretation be reconciled with its recorded PHY / PHY.OBJ placement?", "Does an existing Vercy world model already own instant messaging or an equivalent concept that this registry entry should reference?", "Which researched boundary should distinguish instant messaging from SMS, asynchronous chat, persistent chat rooms and broadcast channels without imposing a universal latency threshold?", "Which primary specifications and service documentation should ground the eventual findings about acknowledgements, offline delivery, synchronisation and interoperability?", "Which security, retention and automated-participation behaviours belong in the common model, and which require explicit service-specific extensions?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 31 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a instant messaging, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise instant messaging, assess whether a conversation can proceed, and choose permitted messaging actions without confusing message submission with delivery or reading.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: private message, Live support software, videochat, distributed multimedia communications platform, Yamigo, voice message.", "6 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 73 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is." ], "openQuestionsForResearch": [ "Which of the bundles below does a real task actually need, and which are ceremony?", "What does this thing have that the facets do not capture at all?", "Which neighbouring kind is most often confused with a instant messaging, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "private message", "Live support software", "videochat", "distributed multimedia communications platform", "Yamigo", "voice message" ] } ], "standing": "Described in 73 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 6 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one instant messaging from another, and a instant messaging from things that resemble it.", "rationale": "Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.", "layers": [ { "id": "naming-and-identifiers", "name": "Names and identifiers", "description": "The names this thing goes by and the identifiers that survive translation and time.", "findings": [ { "id": "preferred-name-and-aliases", "name": "Preferred name, aliases and local names", "description": "Which name to use, which names mean the same thing, and which merely sound similar.", "questions": [ { "id": "preferred-name-and-aliases-q01", "text": "What identifies and describes the name of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "preferred-name-and-aliases-q02", "text": "Who or what asserted this about the name of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "preferred-name-and-aliases-q03", "text": "What may an agent decide or do once the name of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "stable-identifiers", "name": "Stable identifiers and external keys", "description": "Identifiers that keep pointing at this kind of thing across systems and languages.", "questions": [ { "id": "stable-identifiers-q01", "text": "What identifies and describes an identifier for a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stable-identifiers-q02", "text": "Who or what asserted this about an identifier for a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stable-identifiers-q03", "text": "What may an agent decide or do once an identifier for a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "classification-and-granularity", "name": "Classification and granularity", "description": "Where a instant messaging sits among kinds, and how finely a task needs to cut it.", "findings": [ { "id": "kind-and-parents", "name": "Kind, parents and neighbouring kinds", "description": "The classes this thing belongs to and the ones it is next to.", "questions": [ { "id": "kind-and-parents-q01", "text": "What identifies and describes the kind of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "kind-and-parents-q02", "text": "Who or what asserted this about the kind of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "kind-and-parents-q03", "text": "What may an agent decide or do once the kind of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] }, { "id": "distinguishing-features", "name": "Distinguishing features", "description": "What separates a instant messaging from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "distinguishing-features-q02", "text": "Who or what asserted this about what distinguishes a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "distinguishing-features-q03", "text": "What may an agent decide or do once what distinguishes a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a instant messaging is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a instant messaging is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a instant messaging is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a instant messaging is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a instant messaging is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a instant messaging is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "state-and-lifecycle", "name": "State and lifecycle", "description": "The states a instant messaging passes through and the events that move it between them.", "rationale": "Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.", "layers": [ { "id": "lifecycle-stages", "name": "Lifecycle stages", "description": "From coming into existence to ceasing to be one of these.", "findings": [ { "id": "stages-and-transitions", "name": "Stages and transitions", "description": "The stages worth naming and what moves a instant messaging between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "stages-and-transitions-q02", "text": "Who or what asserted this about the lifecycle of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "stages-and-transitions-q03", "text": "What may an agent decide or do once the lifecycle of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "observations-and-status", "name": "Observations and current status", "description": "What is observed about a instant messaging, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a instant messaging is recorded so that it can be superseded rather than overwritten.", "questions": [ { "id": "observation-record-q01", "text": "What identifies and describes an observation of a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "observation-record-q02", "text": "Who or what asserted this about an observation of a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "observation-record-q03", "text": "What may an agent decide or do once an observation of a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What instant messaging is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does instant messaging perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise instant messaging, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How instant messaging is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does instant messaging have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does instant messaging need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about instant messaging is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about instant messaging hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern instant messaging, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a instant messaging came from and when it held.", "rationale": "A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.", "layers": [ { "id": "source-and-authority", "name": "Source and authority", "description": "Who said it, on what evidence, and how strongly.", "findings": [ { "id": "claim-provenance", "name": "Claim provenance and confidence", "description": "The authority behind each claim about a instant messaging and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "claim-provenance-q02", "text": "Who or what asserted this about a claim about a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "claim-provenance-q03", "text": "What may an agent decide or do once a claim about a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "time-and-versions", "name": "Time, versions and supersession", "description": "When a claim was true, when it was learnt, and what replaced it.", "findings": [ { "id": "validity-and-supersession", "name": "Validity period and supersession", "description": "How an old claim about a instant messaging is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a instant messaging, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "validity-and-supersession-q02", "text": "Who or what asserted this about the validity of a claim about a instant messaging, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "validity-and-supersession-q03", "text": "What may an agent decide or do once the validity of a claim about a instant messaging is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }