{ "model": { "rank": 3237, "code": "thing-q43024", "model_id": "vr.tr.sms", "name": "SMS", "purpose": "Enable an AI agent to recognise an SMS communication, assess its delivery and handling state, and determine which messaging actions are appropriate.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q43024/", "tier": 2, "score": 89, "payload": { "layer": "wikidata", "aliases": [ "Emergency Alerts", "cell broadcast", "premium SMS", "location-based SMS", "GPS2SMS", "Emergency Cell Broadcast System" ], "aliasCount": 6, "merged": 6, "knownIn": 89, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q43024", "url": "https://www.wikidata.org/wiki/Q43024", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:13:16Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 30.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07c36-2c09-7ea2-8f36-140681261e7a\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: SMS\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 546 things:\n# Batch 003: 1001 registered t", "usd": 0, "recall": true }, "codex": { "seconds": 76.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07c36-2c0f-7151-892f-047a2f8c7160\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: SMS\nRegistry id: vr.tr.sms\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for this" } } }, "metaModel": { "id": "THING-Q43024", "registryId": "vr.tr.sms", "name": "SMS", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q43024/", "model": { "registry_id": "vr.tr.sms", "name": "SMS", "purpose": "Enable an AI agent to recognise an SMS communication, assess its delivery and handling state, and determine which messaging actions are appropriate.", "definition": "SMS (Short Message Service) is a standardized telecommunications service for exchanging short text and other limited payloads between mobile subscribers and service applications, using network infrastructure that supports store-and-forward delivery.", "scope_statement": "This draft interprets SMS as Short Message Service and models the activity of sending, transporting, receiving and handling SMS messages; the registry's intended expansion remains unconfirmed.", "in_scope": [ "Identification of a communication as SMS and its relationship to a wider conversation", "Sender identity, recipient addressing and reply routing", "Message content, encoding, segmentation and reassembly", "Submission, delivery evidence, failure, expiry and retry decisions", "Purpose, recipient permission, sensitive content and abuse handling" ], "out_of_scope": [ "MMS, RCS, email and internet messaging services beyond their boundaries with SMS", "Mobile network infrastructure and telecommunications protocol implementation", "Handset hardware and messaging application design", "Marketing campaign strategy beyond the handling of individual SMS communications", "Authentication systems beyond the role and handling of an SMS message", "Other expansions of the acronym SMS" ], "distinguishing_features": [ "Identify SMS through transport or provider evidence; a short text or chat-style interface alone does not establish that the communication is SMS.", "Distinguish the user-visible message from its transmitted segments and determine whether several segments represent one logical message.", "Separate submission acceptance, delivery evidence and evidence of human reading; one state must not be substituted for another.", "Distinguish an originating address or displayed sender label from a verified person or organisation.", "Identify when a messaging application changes transport between SMS and another service, even within the same conversation." ], "characteristics": [ { "name": "Transport classification", "kind": "category", "unit_or_values": "SMS confirmed | SMS reported | mixed transport | other transport | unknown", "why_it_matters": "Determines whether this model applies and whether a fallback crossed into a neighbouring service." }, { "name": "Communication purpose", "kind": "category", "unit_or_values": "personal conversation | service notification | authentication | promotion | other | unknown", "why_it_matters": "Purpose affects urgency, permitted handling and the consequences of disclosure or duplication." }, { "name": "Address and identity relationship", "kind": "relation", "unit_or_values": "Observed originating and destination addresses linked to claimed or verified parties, with evidence and time", "why_it_matters": "An address does not by itself establish the identity of its current user." }, { "name": "Reply capability", "kind": "state", "unit_or_values": "reply route verified | reply route reported | replies unsupported | unknown", "why_it_matters": "Prevents an agent from offering a reply or opt-out route that has not been established." }, { "name": "Encoding", "kind": "category", "unit_or_values": "Detected or provider-reported SMS encoding | unknown", "why_it_matters": "Encoding can affect segmentation, fidelity and the cost of sending the intended text." }, { "name": "Segment count", "kind": "measurement", "unit_or_values": "Number of estimated, submitted and received segments, recorded separately", "why_it_matters": "Supports cost assessment and detection of incomplete or duplicated logical messages." }, { "name": "Message lifecycle", "kind": "state", "unit_or_values": "draft | queued | submitted | accepted | delivery reported | failed | expired | indeterminate", "why_it_matters": "Supports action decisions without treating provider acceptance as receipt by a person." }, { "name": "Evidence age", "kind": "measurement", "unit_or_values": "Elapsed seconds since the latest relevant status observation", "why_it_matters": "An old status may be insufficient for deciding whether to retry an urgent message." }, { "name": "Recipient permission", "kind": "state", "unit_or_values": "documented for this purpose | withdrawn | disputed | unknown | applicability unresolved", "why_it_matters": "Makes permission a question about this recipient and purpose rather than a blanket property of an address." }, { "name": "Content sensitivity", "kind": "category", "unit_or_values": "ordinary | personal | confidential | authentication secret | unassessed", "why_it_matters": "Determines appropriate display, retention, forwarding and escalation decisions." } ], "affordances": [ "Classify a communication as SMS using available transport evidence.", "Prepare a message and assess encoding, segmentation and recipient routing before submission.", "Send an authorised message through an established SMS route and preserve submission evidence.", "Reconcile segment and delivery reports while retaining uncertainty about human receipt.", "Decide whether to retry, escalate or use another authorised channel when delivery remains unresolved.", "Reply, suppress further messages or flag suspected abuse when the route, evidence and authority support that action." ] }, "sources": [], "structure": { "bundles": [ { "id": "sms-service-boundary", "name": "SMS service boundary", "description": "Establishes the intended meaning of SMS and the transport identity of each communication.", "rationale": "Neither the acronym nor the appearance of a text message is sufficient to establish that this model applies.", "layers": [ { "id": "sms-sense-and-instance", "name": "SMS sense and instance", "description": "Separates the registered concept from particular messages and messaging activities.", "findings": [ { "id": "sms-interpretation", "name": "Interpretation of SMS", "description": "Record the evidence supporting Short Message Service as the intended registry sense and identify the unit being assessed.", "questions": [ { "text": "Does the registry intend Short Message Service, and what source establishes that expansion?", "kind": "definition", "id": "sms-interpretation-q01" }, { "text": "Is the instance a logical SMS message, a transmitted segment, a sending event or a conversation containing SMS?", "kind": "boundary", "id": "sms-interpretation-q02" } ] } ] }, { "id": "transport-and-fallback", "name": "Transport and fallback", "description": "Identifies SMS use when interfaces or providers expose several messaging services.", "findings": [ { "id": "transport-evidence", "name": "Transport evidence", "description": "Record how the transport was identified and whether fallback changed the service used.", "questions": [ { "text": "Which message metadata, provider record or device observation identifies this transmission as SMS?", "kind": "provenance", "id": "transport-evidence-q01" }, { "text": "Did this message switch between SMS and another service, and which model owns each transmission?", "kind": "boundary", "id": "transport-evidence-q02" } ] } ] } ] }, { "id": "sms-parties-and-routing", "name": "SMS parties and routing", "description": "Connects observed SMS addresses to intended parties and usable communication routes.", "rationale": "Correct addressing, sender recognition and reply capability require separate evidence.", "layers": [ { "id": "origin-and-destination", "name": "Origin and destination", "description": "Distinguishes addressing information from party identity.", "findings": [ { "id": "address-party-binding", "name": "Address-to-party binding", "description": "Record the sender and recipient address forms, their claimed owners and the freshness of verification.", "questions": [ { "text": "What originating and destination addresses are observed, and which people or organisations are they claimed to represent?", "kind": "definition", "id": "address-party-binding-q01" }, { "text": "What evidence links the destination to the intended recipient now, and could reassignment or shared access undermine that link?", "kind": "provenance", "id": "address-party-binding-q02" } ] } ] }, { "id": "reply-and-conversation", "name": "Reply and conversation", "description": "Determines whether an SMS can support a response and how it relates to prior messages.", "findings": [ { "id": "reply-route-validity", "name": "Reply route validity", "description": "Record whether replies are supported and whether the apparent conversation corresponds to a verified route.", "questions": [ { "text": "Can this originating address receive a reply, and what evidence establishes where that reply will go?", "kind": "provenance", "id": "reply-route-validity-q01" }, { "text": "Should the agent reply by SMS, use a separately verified contact route or leave the message unanswered?", "kind": "action", "id": "reply-route-validity-q02" } ] } ] } ] }, { "id": "sms-payload-and-segments", "name": "SMS payload and segments", "description": "Tracks how intended message content becomes transmitted and received SMS segments.", "rationale": "Content length, encoding and segment handling affect whether the recipient receives a complete and faithful message.", "layers": [ { "id": "text-representation", "name": "Text representation", "description": "Assesses the relationship between composed content and its encoded representation.", "findings": [ { "id": "encoding-and-content-fidelity", "name": "Encoding and content fidelity", "description": "Record the selected encoding and any transformation affecting the intended text.", "questions": [ { "text": "Which encoding will the route use, and how does the actual text affect its estimated segment count?", "kind": "measurement", "id": "encoding-and-content-fidelity-q01" }, { "text": "Will any character substitution, truncation or provider transformation change a name, URL, code or instruction?", "kind": "boundary", "id": "encoding-and-content-fidelity-q02" } ] } ] }, { "id": "multipart-integrity", "name": "Multipart integrity", "description": "Relates a logical message to its component segments and received assembly.", "findings": [ { "id": "segment-completeness", "name": "Segment completeness", "description": "Record expected and observed segments, their ordering and evidence that the logical message is complete.", "questions": [ { "text": "How many segments were expected, submitted and observed as received, and which are missing or duplicated?", "kind": "measurement", "id": "segment-completeness-q01" }, { "text": "If only part of the message is available, can its instruction be interpreted safely or must the agent seek the complete message?", "kind": "action", "id": "segment-completeness-q02" } ] } ] } ] }, { "id": "sms-delivery-and-recovery", "name": "SMS delivery and recovery", "description": "Interprets SMS status evidence and governs responses to delay, failure and uncertainty.", "rationale": "Submission, delivery reporting and human receipt support different conclusions, especially when retrying could cause duplicate actions.", "layers": [ { "id": "delivery-evidence", "name": "Delivery evidence", "description": "Preserves the meaning, source and timing of each reported lifecycle event.", "findings": [ { "id": "status-semantics", "name": "Status semantics", "description": "Record provider status labels alongside their documented meanings and the conclusions they support.", "questions": [ { "text": "What does each observed status mean for this provider, and which system generated it?", "kind": "provenance", "id": "status-semantics-q01" }, { "text": "Does the evidence establish acceptance, endpoint delivery or human acknowledgement, and what remains unobserved?", "kind": "boundary", "id": "status-semantics-q02" } ] } ] }, { "id": "expiry-retry-and-fallback", "name": "Expiry, retry and fallback", "description": "Connects delivery uncertainty to message usefulness and duplicate risk.", "findings": [ { "id": "recovery-decision", "name": "Recovery decision", "description": "Record the useful lifetime of the content, retry history and authorised alternatives.", "questions": [ { "text": "When does this message become stale, and could a delayed delivery still prompt an incorrect action?", "kind": "measurement", "id": "recovery-decision-q01" }, { "text": "Given prior submissions and uncertain delivery, should the agent wait, retry, stop or use another authorised channel?", "kind": "action", "id": "recovery-decision-q02" } ] } ] } ] }, { "id": "sms-permission-and-trust", "name": "SMS permission and trust", "description": "Assesses whether an SMS may be sent or acted upon and how its content should be handled.", "rationale": "SMS actions depend on purpose-specific permission, credible identity evidence and the sensitivity of message contents.", "layers": [ { "id": "purpose-and-recipient-permission", "name": "Purpose and recipient permission", "description": "Connects sending authority and recipient preferences to the particular communication.", "findings": [ { "id": "send-and-suppression-basis", "name": "Send and suppression basis", "description": "Record the purpose, applicable permission evidence and any request to stop relevant messages.", "questions": [ { "text": "What authorises this SMS to this recipient for this purpose, and where is that evidence recorded?", "kind": "provenance", "id": "send-and-suppression-basis-q01" }, { "text": "Does a withdrawal, suppression instruction or unresolved permission question require the agent to stop this send?", "kind": "action", "id": "send-and-suppression-basis-q02" } ] } ] }, { "id": "sensitive-content-and-deception", "name": "Sensitive content and deception", "description": "Evaluates message handling and requested actions without assuming the displayed sender establishes trust.", "findings": [ { "id": "content-handling-and-verification", "name": "Content handling and verification", "description": "Record sensitive payloads, suspicious requests and independent evidence needed before acting.", "questions": [ { "text": "Does the SMS contain an authentication code, private information, a link or a request for money or credentials that changes how it should be handled?", "kind": "boundary", "id": "content-handling-and-verification-q01" }, { "text": "Before following its instructions or disclosing its contents, what independent verification or explicit authority does the agent need?", "kind": "action", "id": "content-handling-and-verification-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 registry supplies no sense; this description assumes SMS means Short Message Service, rather than safety management system or another expansion.", "The listed kinds overlap: traffic direction, payload format and display behavior are separate classification dimensions.", "Standards are named from recall; applicable releases, local messaging rules and operator-specific limits require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of SMS 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": [ "Person-to-person SMS", "Application-to-person SMS", "Person-to-application SMS", "Concatenated SMS", "Binary SMS", "Class 0 SMS, commonly called flash SMS" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of SMS 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": "ITU-T E.164", "value_or_pattern": "International telephone number containing at most 15 digits", "note": "Commonly identifies a subscriber destination; SMS also supports addressing forms such as short codes and alphanumeric originators." }, { "scheme": "SMS short codes", "value_or_pattern": "Short numeric service addresses allocated under national or operator arrangements", "note": "Lengths, allocation rules and reachability vary by market." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of SMS 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": [ "3GPP TS 23.040 specifies the technical realization of Short Message Service.", "3GPP TS 23.038 specifies alphabets and language-specific information used by SMS.", "3GPP TS 24.011 specifies point-to-point SMS support on the mobile radio interface.", "3GPP TS 27.005 specifies the interface between terminal equipment and mobile equipment for SMS.", "ITU-T Recommendation E.164 specifies the international public telecommunication numbering plan." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of SMS 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 text communication", "One-time verification codes", "Appointment, transaction and delivery notifications", "Marketing messages and customer responses", "Device alerts and remote commands" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of SMS this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Maximum user-data payload per SMS segment", "typical_range": "Up to 140", "unit": "octets" }, { "quantity": "Text capacity using the GSM 7-bit default alphabet without a user-data header", "typical_range": "Up to 160; extension-table characters consume two septets", "unit": "septets" }, { "quantity": "Text capacity using UCS-2 without a user-data header", "typical_range": "Up to 70", "unit": "16-bit code units" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of SMS 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": [ "Delivery can be delayed or fail because of network conditions, routing problems, filtering or message expiry.", "Concatenated messages can arrive with missing segments or fail to reassemble correctly.", "Encoding changes can reduce segment capacity and increase message counts and charges.", "Spoofed or misleading sender identities can facilitate phishing and fraud.", "SMS lacks inherent end-to-end encryption; account takeover, SIM swapping and interception can compromise messages and verification codes." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of SMS 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": [ "Short-code allocation, alphanumeric sender support and sender registration requirements vary by country and operator.", "Consent requirements and restrictions on promotional messaging vary by jurisdiction.", "Supported national-language tables and handset behavior can affect encoding and segment capacity." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of SMS 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": "MMS", "difference": "MMS supports multimedia messages through a distinct service architecture; SMS carries small text or binary payloads." }, { "name": "RCS", "difference": "RCS provides richer messaging over IP, with capabilities such as media sharing and conversational status features." }, { "name": "USSD", "difference": "USSD supports session-oriented exchanges with network services rather than SMS store-and-forward messaging." }, { "name": "Cell Broadcast", "difference": "Cell Broadcast distributes messages to devices in selected cells rather than addressing individual subscriber destinations." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of SMS this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.sms mean Short Message Service, an individual SMS message or another expansion, and how should its ACT placement constrain ownership?", "Does an existing Vercy world model already cover SMS or mobile messaging, requiring this entry to link to that model?", "Which authoritative specifications and provider documents should establish encoding, segment limits, supported payload types and delivery-status semantics?", "Should binary or application-directed SMS be included in this model, or does the intended registry scope cover only human-readable messaging?", "Which jurisdictional, provider and organisational requirements apply to permission, sender identification, retention and suppression for the intended uses?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 29 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 SMS, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an SMS communication, assess its delivery and handling state, and determine which messaging actions are appropriate.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Emergency Alerts, cell broadcast, premium SMS, location-based SMS, GPS2SMS, Emergency Cell Broadcast System.", "6 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 89 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 SMS, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "physicalCharacter": [ "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": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "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": [ "Emergency Alerts", "cell broadcast", "premium SMS", "location-based SMS", "GPS2SMS", "Emergency Cell Broadcast System" ] } ], "standing": "Described in 89 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 SMS from another, and a SMS 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 SMS, 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 SMS, 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 SMS 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 SMS, 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 SMS, 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 SMS 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 SMS 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 SMS, 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 SMS, 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 SMS 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 SMS from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a SMS, 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 SMS, 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 SMS 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 SMS 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 SMS between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a SMS, 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 SMS, 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 SMS 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 SMS, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a SMS 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 SMS, 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 SMS, 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 SMS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a SMS proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a SMS, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a SMS and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a SMS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a SMS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a SMS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a SMS consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a SMS takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a SMS, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a SMS, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a SMS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What SMS is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of SMS are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is SMS operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of SMS and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of SMS?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as SMS?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a SMS 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 SMS and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a SMS, 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 SMS, 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 SMS 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 SMS is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a SMS, 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 SMS, 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 SMS is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }