{ "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.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" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T11:00:00Z", "ingestedAt": "2026-10-06T08:00:41+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:31+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "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." ], "agent_conduct": { "may": [ "Send SMS messages on a user's instruction to recipients who have agreed to receive them.", "Report delivery status and errors for messages it sent." ], "must_not": [ "Send bulk or marketing SMS without the recipients' consent.", "Send messages that impersonate banks, authorities or other senders.", "Read or forward someone else's SMS without their consent or a lawful order.", "Rely on SMS one-time codes as strong protection where it is known to be weak." ], "requires_human": [ "Sending messages to many recipients at once.", "Sending messages on someone's behalf that commit them to anything." ] }, "ethics": { "considerations": [ "SMS is a main vector for fraud and phishing.", "Messages hold private content and reveal who talks to whom." ], "affected_parties": [ "Mobile users", "Elderly people targeted by scams", "Recipients of bulk messages" ] }, "owners": { "steward": "The sender for the message; the mobile operator for the network service.", "master_systems": [ "Mobile network subscriber records" ] }, "visual_identification": [ "A short text message in a phone's messaging app with a phone number or short sender name." ], "failure_modes_and_hazards": [ "Phishing and fraud messages.", "Interception of one-time codes through number takeover.", "Lost or delayed messages." ], "standards_and_regulation": [ "3GPP TS 23.040, Technical realization of the Short Message Service, 3rd Generation Partnership Project." ], "what_it_is_for": [ "SMS is used for short person-to-person messages and automated communications addressed to telephone numbers.", "Common uses include service notifications, appointment reminders, and verification messages.", "Its store-and-forward operation allows delivery to be attempted when a recipient becomes reachable, although timely delivery is not guaranteed." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q43024: SMS", "url": "https://www.wikidata.org/wiki/Q43024", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: SMS", "url": "https://en.wikipedia.org/wiki/SMS", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "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 } }