{ "model": { "rank": 5624, "code": "thing-q230110", "model_id": "vr.tr.sim-card", "name": "SIM card", "purpose": "Enable an agent to recognise a SIM card, assess its subscription and access state, and determine which installation, authentication, transfer or retirement actions are appropriate.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q230110/", "tier": 2, "score": 66, "payload": { "layer": "wikidata", "aliases": [ "EZ-Link NFC SIM", "Apple SIM", "Universal Subscriber Identity Module", "micro SIM card", "full-size SIM", "mini SIM card", "nano SIM card", "eSIM", "iSIM" ], "aliasCount": 9, "merged": 9, "knownIn": 66, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q230110", "url": "https://www.wikidata.org/wiki/Q230110", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:47:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 27.6, "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: 01a08859-b331-7ca1-b254-102dabc637c7\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: SIM card\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 188 things:\n# Batch 006: 1001 registe", "usd": 0, "recall": true }, "codex": { "seconds": 57.7, "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: 01a08859-b339-7a72-993f-75af4ff5972a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: SIM card\nRegistry id: vr.tr.sim-card\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContex" } } }, "metaModel": { "id": "THING-Q230110", "registryId": "vr.tr.sim-card", "name": "SIM card", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q230110/", "model": { "registry_id": "vr.tr.sim-card", "name": "SIM card", "purpose": "Enable an agent to recognise a SIM card, assess its subscription and access state, and determine which installation, authentication, transfer or retirement actions are appropriate.", "definition": "A SIM card is a secure integrated-circuit card used in cellular equipment to hold subscriber identity data and authentication credentials and perform authentication functions, traditionally through a SIM application and, in modern networks, commonly through a USIM application on a UICC.", "scope_statement": "This model owns the SIM card as a subscriber-identity and authentication medium, recording its physical carrier, SIM or USIM application, subscription association and access controls while distinguishing these from the handset, mobile service contract and downloadable eSIM profile.", "in_scope": [ "Identification of the card, its carrier technology and resident SIM or USIM applications", "Physical format, interface and compatibility with a target device", "Relationships between card identifiers, subscriber identities and operator subscriptions", "Authentication capabilities, credential protection and PIN or PUK access state", "Provisioning, activation, replacement, loss and retirement states" ], "out_of_scope": [ "Handset hardware, operating system and device identity management", "Mobile network infrastructure and radio coverage", "Tariff pricing, billing and the full mobile service contract", "The subscriber's complete personal identity record", "General-purpose smart cards without a mobile subscriber-identity application", "Detailed eSIM provisioning infrastructure and profile-package management" ], "distinguishing_features": [ "Provides or hosts a mobile subscriber-identity application used in network authentication; physical resemblance to a memory card is insufficient.", "A UICC is the secure carrier, while SIM and USIM identify applications; a card may host multiple applications and should not be classified solely by its packaging.", "A card identifier such as ICCID identifies a different object from the subscriber identity, telephone number or handset IMEI.", "A removable SIM card can be moved between compatible devices, whereas a downloadable eSIM profile is installed on an eUICC and is not itself a removable card.", "Presence of an intact card does not establish an active subscription, an unlocked application or permission to use the associated service." ], "characteristics": [ { "name": "Carrier and application classification", "kind": "category", "unit_or_values": "Legacy SIM card; UICC hosting SIM, USIM or other identified applications; eUICC relationship; unknown", "why_it_matters": "Prevents conflating the secure carrier with its applications and determines which compatibility questions apply." }, { "name": "Physical format", "kind": "category", "unit_or_values": "Full-size; mini-SIM; micro-SIM; nano-SIM; embedded package; other; unknown", "why_it_matters": "Determines mechanical fit and whether the record concerns a removable card or an embedded implementation." }, { "name": "Target-device compatibility", "kind": "relation", "unit_or_values": "Target device and slot linked to confirmed, incompatible or unverified compatibility", "why_it_matters": "Mechanical fit alone does not establish application, interface or operator compatibility." }, { "name": "Card identifier", "kind": "category", "unit_or_values": "ICCID where available, with observation source and masked display", "why_it_matters": "Supports card inventory and replacement tracking without treating the identifier as proof of service ownership." }, { "name": "Subscription association", "kind": "relation", "unit_or_values": "Operator subscription linked to subscriber identities and assigned telephone numbers where applicable", "why_it_matters": "Keeps card identity separate from subscriber identity and potentially changing number assignments." }, { "name": "PIN access state", "kind": "state", "unit_or_values": "Verification not required; verification required; verified for current session; blocked; unknown", "why_it_matters": "Determines whether application use can proceed and avoids unsafe repeated PIN attempts." }, { "name": "Remaining verification attempts", "kind": "measurement", "unit_or_values": "Non-negative integer attempts, separately for each reported PIN or unblock credential; unknown if unreported", "why_it_matters": "Indicates the risk of further verification attempts without assuming a universal retry limit." }, { "name": "Operator service state", "kind": "state", "unit_or_values": "Unprovisioned; pending activation; active; suspended; deactivated; unknown, using operator-confirmed meanings", "why_it_matters": "Separates service authorisation from local card readability and PIN status." }, { "name": "Custody and use authority", "kind": "relation", "unit_or_values": "Issuer, subscription holder, current custodian and authorised operator, with evidence", "why_it_matters": "Physical possession alone does not authorise activation, replacement or access to stored data." } ], "affordances": [ "Identify and match a card to an authorised inventory or subscription record using permitted identifiers.", "Assess whether a card can be installed in a specified device and slot.", "Support authorised PIN verification or operator-directed unblocking without exposing credentials.", "Diagnose whether failure concerns card detection, application access, subscription state or network registration.", "Coordinate authorised activation, suspension or replacement through the responsible operator.", "Prepare a card for reassignment or retirement by checking service revocation and treatment of any locally stored data." ] }, "sources": [], "structure": { "bundles": [ { "id": "carrier-and-application-boundary", "name": "Carrier and application boundary", "description": "Establishes which physical medium and subscriber-identity applications the record represents.", "rationale": "SIM terminology commonly conflates a card, a UICC, a USIM application and an eSIM profile, leading to incorrect installation or transfer decisions.", "layers": [ { "id": "represented-sim-object", "name": "Represented SIM object", "description": "Identifies the object behind the registry label and its relationship to embedded implementations.", "findings": [ { "id": "carrier-application-separation", "name": "Carrier and application separation", "description": "Record the carrier and its identified applications separately; flag unresolved use of the term SIM instead of inferring application type from appearance.", "questions": [ { "text": "Does this record represent a legacy SIM card, a UICC hosting subscriber applications, or an embedded implementation?", "kind": "definition", "id": "carrier-application-separation-q01" }, { "text": "If an eSIM profile is involved, which object is the carrier and which object is the downloadable profile?", "kind": "boundary", "id": "carrier-application-separation-q02" } ] } ] }, { "id": "device-installation-fit", "name": "Device installation fit", "description": "Connects card format and application support to a concrete target device.", "findings": [ { "id": "slot-and-application-compatibility", "name": "Slot and application compatibility", "description": "Assess mechanical fit, interface support and required subscriber application independently, using evidence for the target device.", "questions": [ { "text": "What physical format does the card have, and does the target slot accept it directly or require an approved adapter?", "kind": "measurement", "id": "slot-and-application-compatibility-q01" }, { "text": "Which resident application and interface capabilities does the target device require, and what evidence confirms support?", "kind": "boundary", "id": "slot-and-application-compatibility-q02" } ] } ] } ] }, { "id": "subscriber-identity-and-issuance", "name": "Subscriber identity and issuance", "description": "Relates the card to its issuer, subscriber identities and operator service records.", "rationale": "Card identifiers, subscriber identities and telephone numbers serve different purposes and can change through different processes.", "layers": [ { "id": "identifier-associations", "name": "Identifier associations", "description": "Maintains the distinctions and evidence behind card-to-subscription mappings.", "findings": [ { "id": "card-subscriber-number-mapping", "name": "Card, subscriber and number mapping", "description": "Record permitted identifiers and their associations without assuming a telephone number is present on the card, current or unique to it.", "questions": [ { "text": "Which ICCID and subscriber identities are confirmed, and were they obtained from the card, packaging or an operator record?", "kind": "provenance", "id": "card-subscriber-number-mapping-q01" }, { "text": "Which subscription and telephone-number assignments are current, and what establishes their association with this card?", "kind": "provenance", "id": "card-subscriber-number-mapping-q02" } ] } ] }, { "id": "issuer-and-custody", "name": "Issuer and custody", "description": "Separates operator issuance, subscription authority and physical possession.", "findings": [ { "id": "authorised-card-control", "name": "Authorised card control", "description": "Identify the responsible issuer or service provider and the parties entitled to use, recover or replace the card.", "questions": [ { "text": "Who issued the card and who currently administers its associated mobile subscription?", "kind": "provenance", "id": "authorised-card-control-q01" }, { "text": "What evidence authorises the current custodian or agent to activate, unblock, suspend or replace it?", "kind": "action", "id": "authorised-card-control-q02" } ] } ] } ] }, { "id": "authentication-and-local-access", "name": "Authentication and local access", "description": "Describes authentication capability, protected credentials and local verification barriers.", "rationale": "A SIM is a security-bearing medium; authentication capability must be understood without turning the model into a store of secret credentials.", "layers": [ { "id": "network-authentication-capability", "name": "Network authentication capability", "description": "Records the supported subscriber-authentication role and its operational evidence.", "findings": [ { "id": "protected-authentication-operation", "name": "Protected authentication operation", "description": "Record supported authentication applications and observed results while excluding secret key material from the model.", "questions": [ { "text": "Which subscriber-authentication application is available, and which network or device requirements must it satisfy?", "kind": "definition", "id": "protected-authentication-operation-q01" }, { "text": "What authorised diagnostic evidence distinguishes authentication failure from failure to detect or access the card?", "kind": "measurement", "id": "protected-authentication-operation-q02" } ] } ] }, { "id": "pin-and-unblocking-state", "name": "PIN and unblocking state", "description": "Tracks local access restrictions and safe recovery options.", "findings": [ { "id": "verification-and-retry-budget", "name": "Verification and retry budget", "description": "Record which verification control applies, its reported state and remaining attempts; distinguish card PIN restrictions from handset or operator locks.", "questions": [ { "text": "Which PIN or unblock control is involved, and how many attempts remain according to the device or authorised card interface?", "kind": "measurement", "id": "verification-and-retry-budget-q01" }, { "text": "Is another verification attempt justified, or must the authorised holder obtain operator recovery assistance or a replacement?", "kind": "action", "id": "verification-and-retry-budget-q02" } ] } ] } ] }, { "id": "service-lifecycle-and-retirement", "name": "Service lifecycle and retirement", "description": "Connects provisioning and observed usability to replacement, loss handling and end of use.", "rationale": "A readable card can be inactive, a replacement can invalidate its predecessor, and physical disposal alone does not establish service revocation.", "layers": [ { "id": "activation-and-service-diagnosis", "name": "Activation and service diagnosis", "description": "Separates card condition and access from operator authorisation and network availability.", "findings": [ { "id": "independent-operational-states", "name": "Independent operational states", "description": "Record card detection, application access, operator service state and observed network registration as distinct observations with timestamps.", "questions": [ { "text": "Is the card detected and its application accessible, and what service state does the operator report?", "kind": "measurement", "id": "independent-operational-states-q01" }, { "text": "What evidence attributes the current failure to the card, device restrictions, subscription authorisation or network conditions?", "kind": "boundary", "id": "independent-operational-states-q02" } ] } ] }, { "id": "replacement-and-end-of-use", "name": "Replacement and end of use", "description": "Controls continuity of service and disposition of the previous card and its data.", "findings": [ { "id": "replacement-revocation-and-data-disposition", "name": "Replacement, revocation and data disposition", "description": "Track the operator-confirmed relationship between old and replacement cards, service revocation and any card-resident data requiring authorised treatment.", "questions": [ { "text": "When replacing or reporting this card lost, what confirms the old card's service status and the replacement card's subscription association?", "kind": "provenance", "id": "replacement-revocation-and-data-disposition-q01" }, { "text": "Before reassignment or disposal, what card-resident contacts, messages or other accessible data require preservation or removal, and what confirms service revocation?", "kind": "action", "id": "replacement-revocation-and-data-disposition-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": [ "This is recalled knowledge; no sources were consulted.", "SIM is used colloquially for several distinct objects: the legacy application, a UICC carrying USIM, and an eSIM subscription profile.", "Check applicable standards editions, ICCID length conventions and operator-specific provisioning behavior before implementation." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of SIM card 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": [ "Full-size removable card (1FF)", "Mini-SIM (2FF)", "Micro-SIM (3FF)", "Nano-SIM (4FF)", "Embedded eUICC supporting downloadable subscription profiles, commonly called eSIM" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of SIM card 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": "ICCID - ITU-T E.118", "value_or_pattern": "Decimal identifier beginning with 89 for telecommunications", "note": "Identifies the card or subscription profile; distinct from the subscriber identity and telephone number." }, { "scheme": "IMSI - ITU-T E.212", "value_or_pattern": "Up to 15 decimal digits comprising MCC, MNC and MSIN", "note": "Identifies a mobile subscription; the mobile country code has three digits and the mobile network code has two or three." }, { "scheme": "EID - GSMA eUICC identification", "value_or_pattern": "32 decimal digits", "note": "Identifies an eUICC, which can contain multiple subscription profiles." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of SIM card 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": [ "ETSI TS 102 221 specifies the UICC-terminal interface, including physical and logical characteristics.", "3GPP TS 51.011 specifies the SIM-mobile equipment interface for GSM.", "3GPP TS 31.102 specifies characteristics of the USIM application.", "ISO/IEC 7816 series, issued by ISO and IEC, standardizes integrated-circuit cards and their interfaces.", "GSMA SGP.22 specifies remote SIM provisioning for consumer devices." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of SIM card 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": [ "Authenticating mobile subscriptions for voice, messaging and data services.", "Moving a subscription between compatible devices by transferring a removable card.", "Provisioning and changing subscriptions remotely on eSIM-capable devices.", "Providing subscription credentials for cellular meters, trackers, vehicles and other connected equipment.", "Storing limited contacts and SMS messages on implementations that support these functions." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of SIM card 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": "Mini-SIM (2FF) nominal length × width × thickness", "typical_range": "25 × 15 × 0.76", "unit": "mm" }, { "quantity": "Micro-SIM (3FF) nominal length × width × thickness", "typical_range": "15 × 12 × 0.76", "unit": "mm" }, { "quantity": "Nano-SIM (4FF) nominal length × width × thickness", "typical_range": "12.3 × 8.8 × 0.67", "unit": "mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of SIM card 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": [ "Damaged, contaminated or poorly seated contacts can prevent the device from detecting a removable card.", "Repeated incorrect PIN attempts can block access and require a PUK; exhausting PUK attempts can permanently block the affected application.", "Fraudulent SIM replacement or subscription transfer can redirect calls and messages and compromise SMS-based account recovery.", "Lost or stolen cards can enable unauthorized subscription use when access controls are insufficient.", "Deleted, disabled or unsuccessfully provisioned eSIM profiles can interrupt service until a usable profile is restored or installed." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of SIM card 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": [ "Subscriber registration and identity-verification requirements vary by jurisdiction.", "Availability of eSIM activation, profile transfer and remote provisioning varies by operator and market.", "Roaming availability and charges depend on operator agreements and applicable regional rules." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of SIM card 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": "UICC", "difference": "The UICC is the secure card platform; SIM and USIM are applications that can run on it." }, { "name": "USIM", "difference": "USIM is a subscriber identity application used for UMTS and later cellular systems, rather than a physical card size." }, { "name": "eSIM", "difference": "Commonly denotes an eUICC and remotely provisioned subscription profiles; it does not simply mean a smaller removable SIM card." }, { "name": "Memory card", "difference": "A memory card primarily provides general-purpose data storage; a SIM card primarily protects subscription credentials and performs controlled authentication operations." }, { "name": "IMEI", "difference": "IMEI identifies mobile equipment, whereas SIM-associated identifiers identify a card, profile or subscription." }, { "name": "Telephone number", "difference": "A telephone number is a service addressing identifier assigned to a subscription; it is distinct from the SIM's ICCID and IMSI." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of SIM card this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the authoritative registry intend SIM card to include embedded UICCs and eSIM profiles, or should those remain linked neighbouring concepts?", "Which primary specifications should ground the distinctions among legacy SIM cards, UICC carriers, SIM applications and USIM applications?", "Which operator and device interfaces can reliably expose activation state, verification retry counts and replacement status without collecting secret credentials?", "How should multi-application cards and cards supporting multiple subscriber identities be represented without assuming one card equals one subscription?", "Which card-resident data and retirement procedures apply across the supported card generations and issuers?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 17, "questions": 25 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "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 SIM card, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a SIM card, assess its subscription and access state, and determine which installation, authentication, transfer or retirement actions are appropriate.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: EZ-Link NFC SIM, Apple SIM, Universal Subscriber Identity Module, micro SIM card, full-size SIM, mini SIM card, nano SIM card, eSIM, iSIM.", "9 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 66 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 SIM card, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "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": [ "read it and act on what it says", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "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": [ "EZ-Link NFC SIM", "Apple SIM", "Universal Subscriber Identity Module", "micro SIM card", "full-size SIM", "mini SIM card", "nano SIM card", "eSIM", "iSIM" ] } ], "standing": "Described in 66 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 9 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 SIM card from another, and a SIM card 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 SIM card, 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 SIM card, 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 SIM card 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 SIM card, 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 SIM card, 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 SIM card 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 SIM card 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 SIM card, 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 SIM card, 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 SIM card 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 SIM card from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a SIM card, 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 SIM card, 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 SIM card 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 SIM card 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 SIM card between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a SIM card, 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 SIM card, 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 SIM card 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 SIM card, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a SIM card 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 SIM card, 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 SIM card, 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 SIM card is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a SIM card says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a SIM card contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a SIM card, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a SIM card, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a SIM card is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a SIM card and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a SIM card, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a SIM card, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a SIM card is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of SIM card a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For SIM card, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of SIM card exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made SIM card and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to SIM card, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in SIM card, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a SIM card 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 SIM card and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a SIM card, 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 SIM card, 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 SIM card 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 SIM card is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a SIM card, 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 SIM card, 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 SIM card 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 } } } }