{ "model": { "rank": 5412, "code": "thing-q13499", "model_id": "vr.tr.debit-card", "name": "debit card", "purpose": "Enable an agent to recognise a debit card, assess its usability and restrictions, and determine which account-linked payment actions are available and authorised.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q13499/", "tier": 2, "score": 67, "payload": { "layer": "wikidata", "aliases": [ "prepaid debit card", "Interac", "Cashless Debit Card" ], "aliasCount": 3, "merged": 3, "knownIn": 67, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q13499", "url": "https://www.wikidata.org/wiki/Q13499", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:19:02Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.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: 01a0883f-d9fa-7b01-9758-53c27b7eba60\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: debit card\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 61.4, "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: 01a0883f-da0b-79e1-adae-42cc1d542c69\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: debit card\nRegistry id: vr.tr.debit-card\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q13499", "registryId": "vr.tr.debit-card", "name": "debit card", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q13499/", "model": { "registry_id": "vr.tr.debit-card", "name": "debit card", "purpose": "Enable an agent to recognise a debit card, assess its usability and restrictions, and determine which account-linked payment actions are available and authorised.", "definition": "A debit card is a payment instrument whose credentials authorize purchases or cash withdrawals charged to a linked deposit or payment account, ordinarily using available funds rather than a separate credit line.", "scope_statement": "This model owns the debit card as an issued payment instrument and credential linked to a funding account, including its physical or virtual embodiments, transaction capabilities, controls and lifecycle; it does not treat the card as a creative work or equate it with the account itself.", "in_scope": [ "Identification of the issued debit instrument, its issuer, cardholder and linked funding account", "Physical cards, virtual credentials and associated wallet tokens", "Supported purchase, withdrawal and verification methods", "Card status, expiry, replacement and credential lifecycle", "Card-specific spending controls, acceptance restrictions and transaction permissions", "Card-level evidence needed to investigate failed, disputed or unauthorised use" ], "out_of_scope": [ "The funding account's ledger, ownership structure and general banking services", "Credit cards and their revolving credit agreements", "Prepaid instruments funded through a separate stored-value arrangement", "Merchant acquiring systems and payment-network operations as independent systems", "The complete lifecycle and accounting of individual payments", "General identity records and banking customer relationships" ], "distinguishing_features": [ "Its funding arrangement directs transactions to a linked deposit or payment account rather than primarily creating debt on a card credit account; attached overdraft arrangements must be recorded separately.", "Classification depends on the issuer's funding arrangement, not the network logo, card appearance or a terminal's debit-versus-credit routing label.", "It supports purchases as a payment card; a credential restricted to cash-machine access needs separate classification or an explicit boundary decision.", "A physical card, virtual credential and wallet token may represent access to the same debit instrument without being interchangeable identifiers.", "Authorisation and account posting can occur at different times, so immediate ledger deduction is not a required recognition test." ], "characteristics": [ { "name": "Funding relationship", "kind": "relation", "unit_or_values": "Reference to linked funding account or accounts, with selection rules", "why_it_matters": "Establishes what funds the instrument can access and distinguishes it from credit and prepaid arrangements." }, { "name": "Issuer and authorised holder", "kind": "relation", "unit_or_values": "Issuer reference, holder reference and holder's authority over card use", "why_it_matters": "Separates possession of a credential from authority to spend account funds." }, { "name": "Credential embodiment", "kind": "category", "unit_or_values": "Physical card, virtual card credential, associated wallet token or combination", "why_it_matters": "Determines which presentation methods exist and which credential a control or incident concerns." }, { "name": "Instrument and credential status", "kind": "state", "unit_or_values": "Issuer-reported status such as pending activation, active, frozen, blocked, expired or cancelled, recorded separately for each credential", "why_it_matters": "A usable underlying card does not establish that every associated credential is usable." }, { "name": "Validity period", "kind": "measurement", "unit_or_values": "Issuer-provided start date where applicable and expiry month/year", "why_it_matters": "Supports expiry checks and replacement planning without assuming that expiry closes the funding account." }, { "name": "Transaction capabilities", "kind": "category", "unit_or_values": "Issuer-confirmed support for purchases, cash withdrawals, recurring payments, online use and other specified transaction types", "why_it_matters": "Prevents the agent from inferring capabilities solely from the card's debit classification." }, { "name": "Presentation and verification methods", "kind": "category", "unit_or_values": "Supported combinations of chip, contactless, magnetic stripe, remote credential use, PIN and other issuer-supported verification", "why_it_matters": "Determines whether a proposed transaction can meet the applicable presentation and verification requirements." }, { "name": "Card-specific limits", "kind": "measurement", "unit_or_values": "Amount and currency or transaction count, with transaction type, time window and reset rule", "why_it_matters": "Available account funds alone do not establish permission to make a particular payment or withdrawal." }, { "name": "Usage restrictions", "kind": "state", "unit_or_values": "Allowed or blocked channels, regions, merchant categories and transaction types, with effective times", "why_it_matters": "Explains whether otherwise supported use is currently permitted." }, { "name": "Overdraft interaction", "kind": "relation", "unit_or_values": "Reference to applicable account overdraft arrangement, or none or unknown", "why_it_matters": "Avoids assuming that debit-card use can never take an account below zero." } ], "affordances": [ "Assess whether a proposed purchase or withdrawal matches the card's supported channels, current status and recorded limits.", "Guide or perform activation, freezing and unfreezing through an authorised issuer interface when permitted.", "Identify which physical credential or wallet token should be suspended or replaced after loss or compromise.", "Explain a declined transaction using available issuer evidence while separating confirmed causes from hypotheses.", "Route a disputed transaction to the relevant issuer process with card and transaction references.", "Track expiry and replacement dependencies affecting wallet provisioning and recurring payments." ] }, "sources": [], "structure": { "bundles": [ { "id": "debit-identity-and-funding", "name": "Debit identity and funding", "description": "Establishes which debit instrument is being modelled, whose authority it carries and which account relationship funds its use.", "rationale": "The defining property of a debit card is its account-linked payment arrangement, not its physical form or branding.", "layers": [ { "id": "instrument-classification", "name": "Instrument classification", "description": "Tests the debit-card classification against neighbouring payment instruments.", "findings": [ { "id": "funding-basis", "name": "Funding basis", "description": "Record issuer evidence for the funding arrangement and distinguish it from credit-card borrowing, prepaid value and cash-access-only credentials.", "questions": [ { "text": "What issuer record establishes that this instrument is a debit card linked to a deposit or payment account?", "kind": "definition", "id": "funding-basis-q01" }, { "text": "Does this product combine debit with credit, prepaid or cash-access-only functions that require separate modelling?", "kind": "boundary", "id": "funding-basis-q02" } ] } ] }, { "id": "holder-and-account-links", "name": "Holder and account links", "description": "Connects the card to its issuer, authorised holder and funding accounts without absorbing their models.", "findings": [ { "id": "spending-authority", "name": "Spending authority", "description": "Record the holder's card-use authority, account-selection rules and any linked overdraft arrangement as distinct relationships.", "questions": [ { "text": "Which account funds each supported transaction type, and can the holder select between accounts?", "kind": "definition", "id": "spending-authority-q01" }, { "text": "What evidence establishes the holder's authority to use the card and the agent's authority to act on the holder's behalf?", "kind": "provenance", "id": "spending-authority-q02" }, { "text": "Which overdraft terms must be consulted when assessing a payment that may exceed available funds?", "kind": "boundary", "id": "spending-authority-q03" } ] } ] } ] }, { "id": "card-credentials-and-presentation", "name": "Card credentials and presentation", "description": "Describes how the debit instrument is represented and presented across physical, remote and wallet channels.", "rationale": "A card can have several related credentials whose identifiers, acceptance and suspension behaviour differ.", "layers": [ { "id": "credential-topology", "name": "Credential topology", "description": "Maps physical cards, virtual credentials and wallet tokens to their underlying instrument.", "findings": [ { "id": "credential-linkage", "name": "Credential linkage", "description": "Maintain safe references linking credentials to the debit instrument, including device association and replacement lineage where known.", "questions": [ { "text": "Which physical cards, virtual credentials and wallet tokens represent this debit instrument?", "kind": "definition", "id": "credential-linkage-q01" }, { "text": "Which issuer or wallet evidence confirms these links without requiring storage of PINs, security codes or full card numbers?", "kind": "provenance", "id": "credential-linkage-q02" } ] } ] }, { "id": "presentation-and-verification", "name": "Presentation and verification", "description": "Records supported transaction interfaces and their verification requirements.", "findings": [ { "id": "channel-verification-fit", "name": "Channel and verification fit", "description": "Assess capability for the actual credential, terminal or remote channel rather than inferring acceptance from a network logo.", "questions": [ { "text": "Which chip, contactless, magnetic-stripe, online and wallet presentation methods are supported by this credential?", "kind": "definition", "id": "channel-verification-fit-q01" }, { "text": "What verification or step-up authentication does the issuer require for the proposed use, and can the authorised holder complete it?", "kind": "action", "id": "channel-verification-fit-q02" } ] } ] } ] }, { "id": "debit-use-and-authorisation", "name": "Debit use and authorisation", "description": "Assesses purchase and withdrawal eligibility using card controls, funding evidence and transaction context.", "rationale": "A debit card's usable spending capacity depends on more than the account balance, and eligibility checks cannot guarantee approval.", "layers": [ { "id": "capabilities-and-controls", "name": "Capabilities and controls", "description": "Captures transaction permissions, limits and restrictions that apply specifically to card use.", "findings": [ { "id": "transaction-eligibility", "name": "Transaction eligibility", "description": "Evaluate the proposed transaction against supported uses and effective controls, keeping issuer-enforced limits distinct from user-selected restrictions.", "questions": [ { "text": "Are purchases, cash withdrawals, recurring payments and cross-border or online use enabled for this card?", "kind": "definition", "id": "transaction-eligibility-q01" }, { "text": "What amount or count limits apply, in which currency and time window, and how much capacity remains according to current evidence?", "kind": "measurement", "id": "transaction-eligibility-q02" }, { "text": "Who may change the relevant restriction, and through which authorised issuer action?", "kind": "action", "id": "transaction-eligibility-q03" } ] } ] }, { "id": "authorisation-and-posting", "name": "Authorisation and posting", "description": "Relates card authorisation to account availability and later payment processing without owning the payment ledger.", "findings": [ { "id": "funding-and-decision-evidence", "name": "Funding and decision evidence", "description": "Separate available-funds observations, authorisation holds, issuer decisions and final posting; retain the source and time of each observation.", "questions": [ { "text": "What current account evidence is available about spendable funds and holds relevant to the proposed card transaction?", "kind": "measurement", "id": "funding-and-decision-evidence-q01" }, { "text": "For a decline or unexpected debit, which issuer response and payment records establish what happened?", "kind": "provenance", "id": "funding-and-decision-evidence-q02" }, { "text": "Which questions about capture, reversal, settlement or final charges belong to the payment or account model?", "kind": "boundary", "id": "funding-and-decision-evidence-q03" } ] } ] } ] }, { "id": "card-lifecycle-and-recovery", "name": "Card lifecycle and recovery", "description": "Tracks activation, suspension, expiry and replacement alongside responses to loss, compromise and disputed use.", "rationale": "Card interventions can affect physical credentials, wallet tokens and continuing payment arrangements differently.", "layers": [ { "id": "status-and-replacement", "name": "Status and replacement", "description": "Maintains instrument and credential states and their issuer-defined transitions.", "findings": [ { "id": "lifecycle-transition-effects", "name": "Lifecycle transition effects", "description": "Record effective status and validity separately for the instrument and each credential, including the consequences of replacement.", "questions": [ { "text": "What are the issuer-reported status and expiry of the card and each associated credential?", "kind": "measurement", "id": "lifecycle-transition-effects-q01" }, { "text": "Which authorised activation, freeze, unblock, cancellation or replacement actions are available from the current state?", "kind": "action", "id": "lifecycle-transition-effects-q02" }, { "text": "What issuer evidence establishes how replacement affects wallet tokens and recurring payment credentials?", "kind": "provenance", "id": "lifecycle-transition-effects-q03" } ] } ] }, { "id": "loss-compromise-and-disputes", "name": "Loss, compromise and disputes", "description": "Supports targeted containment and evidence-based routing of reported card misuse.", "findings": [ { "id": "incident-response-scope", "name": "Incident response scope", "description": "Identify affected credentials and transactions, record protective actions and consult applicable issuer procedures without assuming universal reimbursement rights.", "questions": [ { "text": "Does the report concern physical loss, exposed card details, a compromised wallet token or a disputed transaction?", "kind": "definition", "id": "incident-response-scope-q01" }, { "text": "Which issuer-supported action addresses the affected credential, and what does that action leave usable?", "kind": "action", "id": "incident-response-scope-q02" }, { "text": "Which applicable issuer terms and jurisdiction-specific rules establish the reporting procedure, deadlines and dispute treatment?", "kind": "provenance", "id": "incident-response-scope-q03" } ] } ] } ] }, { "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 describes the financial payment-instrument sense; the supplied domain code should not imply that the card is a creative work.", "Standards are named from recall; their applicable editions and implementation requirements need verification.", "Deferred debit classification and the boundary between debit and prepaid products vary by market; overdraft access means debit does not always guarantee spending only existing funds." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of debit 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": [ "Consumer debit card", "Business debit card", "Virtual debit card", "Deferred debit card" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of debit 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": "Primary account number (PAN), ISO/IEC 7812", "value_or_pattern": "A numeric identifier of up to 19 digits containing an issuer identification number, an individual account identifier and a check digit", "note": "Identifies the card account within the numbering scheme; it is not necessarily the linked bank account number and should be protected." }, { "scheme": "Issuer identification number (IIN), ISO/IEC 7812", "value_or_pattern": "Leading 8 digits of the PAN; legacy 6-digit assignments also exist", "note": "Also commonly called a bank identification number (BIN); identifies an issuer allocation rather than an individual cardholder." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of debit 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": [ "ISO/IEC 7810, issued by ISO and IEC, specifies identification-card physical characteristics, including the ID-1 format.", "ISO/IEC 7812, issued by ISO and IEC, specifies identification-card issuer numbering and registration.", "ISO/IEC 7816, issued by ISO and IEC, specifies integrated-circuit cards with contacts and associated interfaces.", "EMV specifications, maintained by EMVCo, define interoperable chip-based payment technologies.", "Payment Card Industry Data Security Standard (PCI DSS), maintained by the PCI Security Standards Council, specifies security requirements for environments handling payment account data." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of debit 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": [ "Paying merchants at physical points of sale.", "Making online and recurring payments where supported.", "Withdrawing cash from automated teller machines.", "Obtaining cash back with a purchase where merchants and payment arrangements support it.", "Funding mobile-wallet payments through provisioned card credentials or payment tokens." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of debit 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": "Nominal physical dimensions of an ID-1 card", "typical_range": "85.60 × 53.98", "unit": "mm" }, { "quantity": "Nominal thickness of an ID-1 card", "typical_range": "0.76", "unit": "mm" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of debit 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": [ "Stolen cards or compromised credentials can enable unauthorized payments or withdrawals.", "Skimming, phishing and PIN compromise can expose cardholder credentials.", "Insufficient available funds, account restrictions or transaction limits can cause declines.", "Authorization holds can temporarily reduce spendable funds before a transaction settles or is reversed.", "Damaged cards, terminal faults or network outages can prevent transactions." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of debit 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": [ "Domestic debit networks and international card networks differ in acceptance, routing and authentication practices.", "Some markets distinguish immediate debit from deferred debit, in which accumulated transactions are charged to the linked account later.", "Consumer liability, dispute rights, overdraft treatment and fees depend on jurisdiction and account terms." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of debit 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": "Credit card", "difference": "Ordinary purchases draw on a credit facility rather than directly charging a linked deposit or payment account." }, { "name": "Prepaid card", "difference": "Spending draws on value loaded in advance into a prepaid arrangement rather than an ordinary linked deposit account." }, { "name": "ATM card", "difference": "An ATM-only card supports cash-machine account access without general merchant-payment functionality." }, { "name": "Bank account", "difference": "The account holds funds and records balances; the debit card is an instrument for accessing it." }, { "name": "Payment token", "difference": "A token substitutes for underlying payment credentials in a defined context; it is not itself the linked account or physical card." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of debit card this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the existing Vercy catalogue already contain a payment-card or debit-card model that should supply the shared structure or serve as the single source of truth?", "How should the registry boundary treat hybrid debit/credit products, prepaid cards marketed as debit and cards restricted to cash-machine access?", "For the intended issuers, which status changes propagate between the underlying card, physical credentials, virtual credentials and wallet tokens?", "Which issuer and jurisdiction sources establish applicable limits, authentication requirements, overdraft interactions and dispute procedures?", "Which authorised integrations expose sufficiently current status, limit and funding evidence, and what freshness threshold should an agent require before acting?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 17, "questions": 30 } }, "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 debit card, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a debit card, assess its usability and restrictions, and determine which account-linked payment actions are available and authorised.", "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: prepaid debit card, Interac, Cashless Debit Card.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 67 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 debit 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": [ "prepaid debit card", "Interac", "Cashless Debit Card" ] } ], "standing": "Described in 67 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 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 debit card from another, and a debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit card from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a debit 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 debit 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 debit 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 debit 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 debit card between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a debit 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 debit 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 debit 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 debit card, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a debit 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 debit 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 debit 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 debit 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 debit 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 debit card contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a debit 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 debit 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 debit 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 debit card and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit 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 debit card and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a debit 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 debit 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 debit 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 debit card is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a debit 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 debit 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 debit 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 } } } }