{ "model": { "rank": 2954, "code": "thing-q81235", "model_id": "vr.tr.automated-teller-machine", "name": "automated teller machine", "purpose": "Enable an AI agent to recognise an automated teller machine, assess its ability to provide authorised self-service financial transactions, and determine which customer or maintenance actions are currently permitted.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q81235/", "tier": 2, "score": 93, "payload": { "layer": "wikidata", "aliases": [ "ATM Leaderboard", "Cash Express", "E-net ATM", "Bitcoin ATM", "cheque deposit machine", "IBM 3624", "cash deposit machine", "white-label ATM" ], "aliasCount": 8, "merged": 8, "knownIn": 93, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q81235", "url": "https://www.wikidata.org/wiki/Q81235", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T13:56:00Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.0102731, "turns": 1, "seconds": 151.6, "error": null }, "codex": { "seconds": 77.1, "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: 01a07c22-ad30-7790-b6e5-7c78441b21f4\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: automated teller machine\nRegistry id: vr.tr.automated-teller-machine\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded " } } }, "metaModel": { "id": "THING-Q81235", "registryId": "vr.tr.automated-teller-machine", "name": "automated teller machine", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q81235/", "model": { "registry_id": "vr.tr.automated-teller-machine", "name": "automated teller machine", "purpose": "Enable an AI agent to recognise an automated teller machine, assess its ability to provide authorised self-service financial transactions, and determine which customer or maintenance actions are currently permitted.", "definition": "A customer-operated, host-authorised cash terminal that authenticates a payment-card or account holder (typically chip-and-PIN or an equivalent credential) and dispenses banknotes from secured cassettes, and that may also accept deposits or offer other self-service account operations without a human teller.", "scope_statement": "This model owns the physical ATM terminal, its installed transaction capabilities, customer interfaces, cash-handling components, local operational state, and dependencies that constrain its use.", "in_scope": [ "Terminal identity, installation, operator and servicing relationships", "Supported transactions and the conditions under which each is available", "Customer authentication, interaction and accessibility interfaces", "Cash dispensing, deposit acceptance and retained-media handling where installed", "Terminal faults, physical security indicators and maintenance restrictions" ], "out_of_scope": [ "Customer identities, account balances and banking entitlements", "Bank ledgers, payment-network settlement and interbank reconciliation", "Banknote design, issuance and legal-tender policy", "Building-wide access control and site security operations", "Operator-wide compliance programmes and cash logistics fleets" ], "distinguishing_features": [ "Provides a customer-operated banking transaction interface linked to an account or other authorised financial service, distinguishing it from a passive account-information display.", "Has a configured cash dispensing or cash deposit function associated with financial transactions, distinguishing it from an ordinary banking kiosk; the exact inclusion boundary requires confirmation.", "Operates as a dedicated self-service terminal rather than requiring a cashier to perform the transaction, distinguishing it from a teller counter or staffed cash register.", "Treats cash delivery or acceptance as a financial service rather than incidental change or cashback during a retail purchase, distinguishing it from a vending machine or point-of-sale terminal." ], "characteristics": [ { "name": "Terminal identity", "kind": "category", "unit_or_values": "Operator-assigned terminal identifier; manufacturer, model and serial number when available", "why_it_matters": "Connects observations and service records to the correct physical terminal." }, { "name": "Responsible organisations", "kind": "relation", "unit_or_values": "Owner, operator, acquiring institution, cash replenisher and maintenance provider, with roles distinguished", "why_it_matters": "Identifies who can authorise use restrictions, investigate faults or service the machine." }, { "name": "Transaction capabilities", "kind": "category", "unit_or_values": "Configured operations such as withdrawal, balance enquiry, transfer, cash deposit or cheque deposit; unsupported and unknown recorded explicitly", "why_it_matters": "Prevents an agent from assuming that every ATM provides the same services." }, { "name": "Transaction availability", "kind": "state", "unit_or_values": "Per operation: available, degraded, unavailable or unknown, with observation time and reason", "why_it_matters": "Separates installed capability from what a customer can currently use." }, { "name": "Customer initiation methods", "kind": "category", "unit_or_values": "Supported card, contactless, mobile-token or other operator-documented methods", "why_it_matters": "Determines whether a customer has a compatible way to start a transaction without recording credentials." }, { "name": "Cash configuration", "kind": "category", "unit_or_values": "Accepted and dispensed currencies and denominations; dispenser, deposit-only or recycling cash paths where documented", "why_it_matters": "Constrains which cash requests and deposits the terminal can handle." }, { "name": "Cash availability and acceptance headroom", "kind": "measurement", "unit_or_values": "Authorised counts by currency and denomination, or operator-reported availability bands; deposit capacity in documented units", "why_it_matters": "Supports transaction feasibility and replenishment decisions while allowing sensitive inventory to remain access-restricted." }, { "name": "Configured transaction limits", "kind": "measurement", "unit_or_values": "Currency amount, note count or item count per operation, with the responsible rule source", "why_it_matters": "Distinguishes terminal constraints from customer-account and issuer restrictions." }, { "name": "Customer access conditions", "kind": "state", "unit_or_values": "Accessible now, access restricted, physically obstructed or unknown; applicable opening hours and interface limitations", "why_it_matters": "A functioning ATM may still be unusable by a particular customer at a particular time." }, { "name": "Security and service state", "kind": "state", "unit_or_values": "Operator-reported normal, inspection required, suspected tampering, maintenance isolation or unknown", "why_it_matters": "Constrains customer use and service actions without treating an absence of visible damage as proof of safety." } ], "affordances": [ "Determine whether the terminal supports a requested transaction and compatible initiation method.", "Guide a customer through documented public controls without collecting a PIN, authentication token or full card details.", "Assess whether a cash request is feasible using permitted denomination, availability and limit information.", "Report failed cash delivery, retained media or suspected tampering to the responsible operator using non-sensitive references.", "Recommend an alternative terminal when the required service or accessible interface is unavailable.", "Identify the authorised replenishment, inspection or repair action associated with a reported terminal condition." ] }, "sources": [ { "id": "wikipedia-atm", "title": "Automated teller machine - Wikipedia, Wikimedia Foundation", "url": "https://en.wikipedia.org/wiki/Automated_teller_machine", "what_it_supports": "Common name, history, typical functions, and everyday varieties (lobby, through-the-wall, drive-up).", "url_status": "live" }, { "id": "iso-8583", "title": "ISO 8583, Financial transaction card originated messages - Interchange message specifications - International Organization for Standardization", "url": "", "what_it_supports": "The card-originated authorisation and financial-message format used by ATM hosts and payment networks." }, { "id": "iso-9564", "title": "ISO 9564, Financial services - Personal Identification Number (PIN) management and security - International Organization for Standardization", "url": "", "what_it_supports": "PIN entry, protection and verification requirements that ATM PIN pads implement." }, { "id": "emvco-icc", "title": "EMV Integrated Circuit Card Specifications for Payment Systems - EMVCo", "url": "", "what_it_supports": "Chip-card authentication used by modern ATMs for cardholder verification and transaction cryptograms." }, { "id": "pci-pts-poi", "title": "PIN Transaction Security (PTS) Point of Interaction (POI) Modular Security Requirements - PCI Security Standards Council", "url": "", "what_it_supports": "Security evaluation and approval of ATM PIN-entry and encrypting PIN-pad modules." }, { "id": "ul-291", "title": "UL 291, Standard for Automated Teller Systems - UL", "url": "", "what_it_supports": "Physical construction and attack-resistance requirements for ATM assemblies in North American practice." }, { "id": "en-1143-1", "title": "EN 1143-1, Secure storage units - Requirements, classification and methods of test for resistance to burglary - Safes, ATM safes, strongroom doors and strongrooms - CEN", "url": "", "what_it_supports": "Burglary-resistance grades applied to ATM safes in European specification and procurement." }, { "id": "ada-atm", "title": "2010 ADA Standards for Accessible Design - U.S. Department of Justice", "url": "", "what_it_supports": "Reach, privacy, input and output requirements for ATMs treated as accessible public facilities in the United States." } ], "structure": { "bundles": [ { "id": "terminal-role-and-configuration", "name": "Terminal role and configuration", "description": "Establishes which ATM is being observed and which financial services its installed configuration supports.", "rationale": "Appearance and branding alone do not establish terminal identity, responsibility or transaction capability.", "layers": [ { "id": "terminal-identity-and-responsibility", "name": "Terminal identity and responsibility", "description": "Connects the physical terminal to its installation and accountable service organisations.", "findings": [ { "id": "identified-atm-installation", "name": "Identified ATM installation", "description": "Record the terminal identifier, physical location and evidence identifying its operator and service contacts.", "questions": [ { "text": "Which identifier and installation details distinguish this ATM from another terminal at the same site?", "kind": "definition", "id": "identified-atm-installation-q01" }, { "text": "What operator record or terminal notice establishes who handles customer incidents and machine servicing?", "kind": "provenance", "id": "identified-atm-installation-q02" } ] } ] }, { "id": "installed-financial-services", "name": "Installed financial services", "description": "Separates supported operations from branding, assumptions and temporary availability.", "findings": [ { "id": "configured-transaction-set", "name": "Configured transaction set", "description": "Record the operations enabled for this terminal and any documented customer or network eligibility constraints.", "questions": [ { "text": "Which withdrawal, deposit, enquiry or transfer operations are explicitly supported by this terminal?", "kind": "definition", "id": "configured-transaction-set-q01" }, { "text": "Which restrictions originate in the terminal configuration, and which belong to the account provider or transaction network?", "kind": "boundary", "id": "configured-transaction-set-q02" } ] } ] } ] }, { "id": "customer-access-and-authorisation", "name": "Customer access and authorisation", "description": "Describes how a customer reaches, initiates and controls an ATM session.", "rationale": "A transaction capability is useful only when the customer can access its interface and satisfy the applicable authorisation process.", "layers": [ { "id": "session-initiation", "name": "Session initiation", "description": "Captures supported initiation methods and their documented prerequisites without storing authentication secrets.", "findings": [ { "id": "supported-authentication-paths", "name": "Supported authentication paths", "description": "Record accepted initiation media and the public steps required to establish an authorised session.", "questions": [ { "text": "Which card, contactless or cardless initiation paths are enabled, and what prerequisites does each have?", "kind": "definition", "id": "supported-authentication-paths-q01" }, { "text": "How can a customer cancel or end each supported session path, and what confirms that the session has ended?", "kind": "action", "id": "supported-authentication-paths-q02" } ] } ] }, { "id": "usable-customer-interface", "name": "Usable customer interface", "description": "Captures physical access and the interface features needed to complete a transaction.", "findings": [ { "id": "accessibility-and-privacy-conditions", "name": "Accessibility and privacy conditions", "description": "Record site access restrictions, reachable controls, supported languages and documented visual, tactile or audio assistance.", "questions": [ { "text": "What observed access conditions and documented interface features affect this customer's ability to use the ATM?", "kind": "measurement", "id": "accessibility-and-privacy-conditions-q01" }, { "text": "Which assistance or alternative-terminal action is appropriate when the customer cannot independently operate a required control?", "kind": "action", "id": "accessibility-and-privacy-conditions-q02" } ] } ] } ] }, { "id": "cash-and-media-handling", "name": "Cash and media handling", "description": "Describes the terminal's cash paths, transaction constraints and handling of customer media.", "rationale": "Cash availability, accepted items and retained media create ATM-specific limits and incident states.", "layers": [ { "id": "cash-transaction-feasibility", "name": "Cash transaction feasibility", "description": "Relates requested cash operations to currency, denomination, inventory and acceptance constraints.", "findings": [ { "id": "dispense-and-deposit-constraints", "name": "Dispense and deposit constraints", "description": "Record the documented conditions under which the terminal can dispense or accept the requested cash or deposit items.", "questions": [ { "text": "Which currencies, denominations, item types and per-operation limits apply to each installed cash or deposit function?", "kind": "definition", "id": "dispense-and-deposit-constraints-q01" }, { "text": "What authorised evidence indicates sufficient dispensable cash or remaining deposit capacity for the requested operation?", "kind": "measurement", "id": "dispense-and-deposit-constraints-q02" } ] } ] }, { "id": "presented-and-retained-media", "name": "Presented and retained media", "description": "Distinguishes cash and card handling events that require different customer or operator responses.", "findings": [ { "id": "media-disposition", "name": "Media disposition", "description": "Record whether cash, cards or deposit items were presented, taken, returned, retracted, retained or left in an unresolved state, where observable.", "questions": [ { "text": "What evidence distinguishes cash presented from cash collected, and a returned card from a retained card?", "kind": "measurement", "id": "media-disposition-q01" }, { "text": "Which documented customer-support or authorised recovery action applies to retained media or an unresolved deposit?", "kind": "action", "id": "media-disposition-q02" } ] } ] } ] }, { "id": "transaction-state-and-service-health", "name": "Transaction state and service health", "description": "Connects current service availability to dependencies and distinguishes terminal events from financial outcomes.", "rationale": "An ATM can be partly operational, and its displayed transaction result may not settle whether an account was debited or credited.", "layers": [ { "id": "operation-specific-readiness", "name": "Operation-specific readiness", "description": "Records which installed services can run under current component and external-service conditions.", "findings": [ { "id": "readiness-and-blocking-dependencies", "name": "Readiness and blocking dependencies", "description": "Associate each unavailable or degraded operation with a reported component fault or dependency condition and the freshness of that evidence.", "questions": [ { "text": "Which transactions are currently available, and when was that status last confirmed?", "kind": "measurement", "id": "readiness-and-blocking-dependencies-q01" }, { "text": "Which documented dependencies or component faults block each affected operation?", "kind": "provenance", "id": "readiness-and-blocking-dependencies-q02" } ] } ] }, { "id": "transaction-outcome-evidence", "name": "Transaction outcome evidence", "description": "Separates customer-visible results, physical cash events and externally confirmed account outcomes.", "findings": [ { "id": "interrupted-or-disputed-transaction", "name": "Interrupted or disputed transaction", "description": "Record non-sensitive incident references, observed transaction stage and unresolved outcome without inferring ledger state from terminal behaviour.", "questions": [ { "text": "What terminal message, receipt or permitted event record supports the reported outcome?", "kind": "provenance", "id": "interrupted-or-disputed-transaction-q01" }, { "text": "Which outcome requires confirmation from the account provider or operator before advising a retry or treating the incident as resolved?", "kind": "boundary", "id": "interrupted-or-disputed-transaction-q02" } ] } ] } ] }, { "id": "security-and-authorised-servicing", "name": "Security and authorised servicing", "description": "Defines evidence and authority needed to suspend use, inspect the ATM or restore service.", "rationale": "ATMs combine customer authentication interfaces and protected cash compartments, making service authority and suspected tampering central to permissible action.", "layers": [ { "id": "customer-facing-security-condition", "name": "Customer-facing security condition", "description": "Captures reported anomalies without claiming that visual inspection can certify the terminal as secure.", "findings": [ { "id": "suspected-interface-tampering", "name": "Suspected interface tampering", "description": "Record observed alterations or operator alerts affecting the card reader, keypad, cash outlet or other customer-facing components.", "questions": [ { "text": "What observation or operator alert supports the suspected tampering condition, and when was it recorded?", "kind": "provenance", "id": "suspected-interface-tampering-q01" }, { "text": "What operator-documented action should follow before further customer use?", "kind": "action", "id": "suspected-interface-tampering-q02" } ] } ] }, { "id": "service-authority-and-return-to-use", "name": "Service authority and return to use", "description": "Connects maintenance and cash-handling actions to authorised roles and restoration evidence.", "findings": [ { "id": "controlled-service-transition", "name": "Controlled service transition", "description": "Record the applicable service restriction, responsible authorised role and checks required before affected transactions resume.", "questions": [ { "text": "Which role is authorised to perform the required replenishment, retained-media recovery, inspection or repair?", "kind": "action", "id": "controlled-service-transition-q01" }, { "text": "What documented checks and operator confirmation establish that the affected services may return to customer use?", "kind": "provenance", "id": "controlled-service-transition-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Cash-dispenser ATM (withdrawals and typically balance enquiry only)", "Full-function ATM (withdrawals plus deposits, transfers and related account services)", "Cash-recycling ATM (validates deposited notes and redispenses them)", "Lobby or indoor walk-up ATM", "Through-the-wall or outdoor ATM", "Drive-up ATM", "Bank-owned branded (on-us) ATM", "Independent or white-label ATM deployed by a non-bank ATM deployer" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q81281", "note": "Item for automated teller machine as a class of device." }, { "scheme": "EU Common Procurement Vocabulary (CPV 2008)", "value_or_pattern": "30144200-2", "note": "Automated teller machines, used in public procurement notices." }, { "scheme": "Acquirer terminal identifier (TID)", "value_or_pattern": "typically an 8-digit numeric terminal ID assigned per device by the acquirer or network", "note": "Identifies the ATM as a card-accepting terminal on the payment network; not a global product code." }, { "scheme": "PCI PTS approval number", "value_or_pattern": "vendor- and model-specific approval ID for the encrypting PIN pad or POI module", "note": "Names the evaluated security module, not the whole ATM as a commercial SKU." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ISO 8583 (ISO) - card-originated financial interchange messages used for ATM authorisation and completion.", "ISO 9564 (ISO) - PIN management and security for PIN pads on ATMs.", "EMV Integrated Circuit Card Specifications (EMVCo) - chip-card processing at ATMs.", "PCI PTS POI Modular Security Requirements (PCI Security Standards Council) - evaluation of ATM PIN-entry devices; PCI PIN security and PCI DSS also apply to the acquiring environment.", "UL 291 (UL) - automated teller systems, physical and construction requirements.", "EN 1143-1 (CEN) - burglary resistance of ATM safes.", "CEN/XFS, eXtensions for Financial Services (CEN) - vendor-independent software interface to ATM devices (dispenser, card reader, PIN pad, sensors).", "2010 ADA Standards for Accessible Design (U.S. Department of Justice) - accessibility of ATMs in the United States.", "Directive (EU) 2015/2366, Payment Services Directive II (European Union) - payment-account access and cash-withdrawal services that ATM operators and card issuers sit under in the EEA.", "LINK Scheme rules (Pay.UK / LINK) - UK interbank ATM interconnection, access and (historically) interchange." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Walk-up cash withdrawal at bank branches, shopping centres, petrol stations, airports, railway stations and convenience stores.", "Drive-through cash access at bank sites.", "Self-service cash and cheque deposit at branch and at some off-premise recyclers.", "Balance enquiry, intra-bank transfer, PIN change, mini-statement and prepaid top-up on many networks.", "Independent ATM deployers place white-label machines in retail for surcharge or interchange income.", "Primary remaining channel for distributing central-bank cash to the public as branch-teller volumes decline." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Notes per cash cassette", "typical_range": "2000-3500", "unit": "banknotes" }, { "quantity": "Cassettes per dispenser", "typical_range": "2-4 (some recyclers more)", "unit": "cassettes" }, { "quantity": "Single-transaction withdrawal cap", "typical_range": "highly local; often on the order of 200-3000 in the local currency's major unit, set by issuer, ATM owner and cash-in-cassette", "unit": "local currency units" }, { "quantity": "Typical withdrawal session duration", "typical_range": "20-90", "unit": "seconds" }, { "quantity": "ATM safe burglary resistance (Europe)", "typical_range": "CEN Grade L to IV depending on location risk", "unit": "EN 1143-1 grade" }, { "quantity": "Scheduled availability target", "typical_range": "95-99", "unit": "percent of planned hours" }, { "quantity": "Mains supply", "typical_range": "100-240", "unit": "V AC" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Card skimming, shimming and PIN-pad overlays capturing credentials.", "Cash-trapping devices and 'Lebanese loop' retainers that steal notes or the card.", "Jackpotting malware or black-box attacks forcing unauthorised dispense.", "Physical attacks on the safe: ram-raid, cutting, gas or solid explosives.", "Cassette jams, double-picks, misfeeds and note miscounts.", "Host, network, or key-management failure taking the machine out of service.", "Card capture after PIN retries or suspected fraud, stranding the customer's card.", "Shoulder-surfing and covert cameras observing PIN entry.", "Out-of-cash or cassette-imbalance conditions causing failed withdrawals.", "Privacy and accessibility failures (readable screens, blocked approach) that exclude users or expose account data." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "United Kingdom and Ireland: commonly 'cash machine' or 'hole-in-the-wall'; interconnection via LINK; distinction between free-to-use and surcharge machines.", "Canada: commonly 'ABM' (automated banking machine); Interac is the dominant domestic network.", "France: DAB (distributeur automatique de billets) for cash-out versus GAB (guichet automatique de banque) for fuller function.", "Italy and parts of continental Europe: 'Bancomat' used generically (originally a consortium brand).", "German-speaking countries: 'Geldautomat'.", "United States: off-us surcharge is common; deposit-taking at off-premise machines is less universal than in much of Europe or Japan.", "Japan: dense convenience-store ATM networks; cash recycling long established; some bank ATMs historically had restricted hours.", "India: full ATMs on the National Financial Switch coexist with handheld 'micro-ATMs' authenticated via Aadhaar, which are a distinct device class." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Point-of-sale (POS) terminal", "difference": "A POS terminal captures a merchant payment and does not dispense notes from ATM cassettes; any 'cashback' comes from the till." }, { "name": "Teller cash recycler (TCR)", "difference": "Staff-operated behind the counter to support a human teller, not a public self-service customer terminal." }, { "name": "Cash deposit machine (CDM)", "difference": "Deposit-only kiosk with no cash dispenser; treated as a separate class in several Asian networks." }, { "name": "Bitcoin or crypto ATM", "difference": "Exchanges crypto-assets and cash; it is not an issuer/acquirer ATM on card networks performing host-authorised account withdrawals." }, { "name": "Night safe or deposit box", "difference": "Unattended drop of cash or cheques without real-time cardholder authentication and account credit at the device." }, { "name": "Self-service banking kiosk", "difference": "Account or print services without a cash dispenser (and usually without an ATM-grade safe and cassettes)." }, { "name": "Vending machine", "difference": "Dispenses goods against payment, not banknotes drawn from a customer deposit account under card-network authorisation." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of automated teller machine this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry's intended ATM boundary include deposit-only terminals, teller-assisted machines and cryptocurrency cash kiosks, or are those neighbouring kinds?", "Which existing Vercy models already own terminal software, payment-network participation, accessibility requirements or cash-handling components?", "Which operator and manufacturer sources can establish configuration, event meanings and recovery procedures for a particular ATM?", "What inventory, diagnostic and incident information may each agent role access, and what freshness is sufficient for transaction or service decisions?", "Which jurisdictional and operator requirements govern accessibility, fee disclosure, retained media and disputed cash transactions for the installation being modelled?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a automated teller machine, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise an automated teller machine, assess its ability to provide authorised self-service financial transactions, and determine which customer or maintenance actions are currently permitted.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: ATM Leaderboard, Cash Express, E-net ATM, Bitcoin ATM, cheque deposit machine, IBM 3624, cash deposit machine, white-label ATM.", "8 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 93 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 automated teller machine, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "ATM Leaderboard", "Cash Express", "E-net ATM", "Bitcoin ATM", "cheque deposit machine", "IBM 3624", "cash deposit machine", "white-label ATM" ] } ], "standing": "Described in 93 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 8 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 automated teller machine from another, and a automated teller machine 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 automated teller machine, 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 automated teller machine, 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 automated teller machine 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 automated teller machine, 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 automated teller machine, 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 automated teller machine 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 automated teller machine 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 automated teller machine, 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 automated teller machine, 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 automated teller machine 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 automated teller machine from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a automated teller machine, 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 automated teller machine, 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 automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a automated teller machine is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a automated teller machine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a automated teller machine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a automated teller machine is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a automated teller machine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a automated teller machine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a automated teller machine is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a automated teller machine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a automated teller machine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a automated teller machine is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a automated teller machine is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a automated teller machine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a automated teller machine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a automated teller machine is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a automated teller machine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a automated teller machine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a automated teller machine 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 automated teller machine 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 automated teller machine between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a automated teller machine, 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 automated teller machine, 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 automated teller machine 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 automated teller machine, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a automated teller machine 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 automated teller machine, 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 automated teller machine, 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 automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What automated teller machine is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does automated teller machine perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise automated teller machine, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How automated teller machine is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does automated teller machine have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does automated teller machine need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about automated teller machine is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about automated teller machine hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern automated teller machine, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a automated teller machine 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 automated teller machine and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a automated teller machine, 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 automated teller machine, 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 automated teller machine 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 automated teller machine is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a automated teller machine, 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 automated teller machine, 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 automated teller machine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }