{ "model": { "rank": 5868, "code": "thing-q183731", "model_id": "vr.tr.memory-card", "name": "memory card", "purpose": "Enable an AI agent to recognise a removable memory card, assess its compatibility and storage condition, and decide which handling or data operations are appropriate.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q183731/", "tier": 2, "score": 64, "payload": { "layer": "wikidata", "aliases": [ "CFexpress", "CompactFlash", "SxS", "UFS card", "CFast", "PlayStation Vita memory card", "MemCard Pro", "P2", "Europcard", "Nintendo GameCube Memory Card", "SD card", "MultiMediaCard", "Memory Stick", "PlayStation 2 memory card", "SDXC card", "MiniSD", "SDSC card", "SDHC card", "SDUC card", "RS-MMC", "Memory Stick Pro Duo" ], "aliasCount": 21, "merged": 23, "knownIn": 64, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q183731", "url": "https://www.wikidata.org/wiki/Q183731", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:47:16Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.01141584, "turns": 1, "seconds": 166.6, "error": null }, "codex": { "seconds": 82.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07b40-beb8-7aa3-90c4-34a9aa1ad24f\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: memory card\nRegistry id: vr.tr.memory-card\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA" } } }, "metaModel": { "id": "THING-Q183731", "registryId": "vr.tr.memory-card", "name": "memory card", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q183731/", "model": { "registry_id": "vr.tr.memory-card", "name": "memory card", "purpose": "Enable an AI agent to recognise a removable memory card, assess its compatibility and storage condition, and decide which handling or data operations are appropriate.", "definition": "A memory card is a user-removable solid-state storage module, almost always NAND flash with an onboard controller, whose mechanical and electrical interface is a standardized small card that seats in a host slot rather than a cable plug, and that presents a block device or file volume to cameras, phones, consoles, and embedded equipment.", "scope_statement": "This model owns a physical removable solid-state memory card as a storage medium, including its identity, host compatibility, capacity, recorded-data accessibility, integrity and readiness for use; interpreting the stored content belongs to neighbouring models.", "in_scope": [ "Card family, physical format, markings and evidence of identity", "Electrical, protocol and host compatibility, including required readers or adapters", "Advertised and verified capacity and workload-relevant performance", "Partitioning, formatting, readability and protection against unwanted modification", "Physical condition, data-integrity evidence and suitability for continued use", "Conditions and authority for insertion, removal, testing, formatting, erasure and retirement" ], "out_of_scope": [ "Host-device operation beyond its interface and requirements for the card", "Reader and adapter construction, maintenance and independent condition", "Meaning, quality and ownership of individual files or datasets", "Embedded storage, USB flash drives and solid-state drives as separate device types", "Backup-service operation and management of other storage copies", "Packaging, retail offers and supply-chain transactions except as evidence about this card" ], "distinguishing_features": [ "Determine whether the item is the storage-bearing card or merely an adapter that requires another card to supply storage.", "Check whether its form factor and interface identify it as a memory-card family rather than a USB flash drive or separately enclosed storage drive.", "Establish whether its intended role is general host-accessible data storage rather than subscriber identity, payment or authentication, as with SIM and smart cards.", "Confirm that it is a separately removable medium rather than flash storage integrated into a host board.", "Check for electronic contacts and solid-state storage evidence to distinguish it from optical discs and other non-electronic card-shaped media." ], "characteristics": [ { "name": "Card family and physical format", "kind": "category", "unit_or_values": "Identified family and size variant, with unknown permitted", "why_it_matters": "Determines the candidate slots, readers and handling constraints." }, { "name": "Identity confidence", "kind": "state", "unit_or_values": "Unverified, markings inspected, device identity read, independently corroborated, conflicting evidence", "why_it_matters": "Prevents printed branding or controller reports from being treated as conclusive identity evidence." }, { "name": "Physical dimensions", "kind": "measurement", "unit_or_values": "Length, width and thickness in millimetres", "why_it_matters": "Helps distinguish formats and detect a mismatch before insertion." }, { "name": "Advertised capacity", "kind": "measurement", "unit_or_values": "Bytes, preserving the original label value and unit convention", "why_it_matters": "Records the capacity claim separately from what the card can reliably store." }, { "name": "Verified usable capacity", "kind": "measurement", "unit_or_values": "Bytes, accompanied by verification method, coverage and date; unknown if untested", "why_it_matters": "Supports storage planning and detection of capacity misrepresentation or inaccessible regions." }, { "name": "Host compatibility", "kind": "relation", "unit_or_values": "Card-to-host-and-reader combination: documented, demonstrated, incompatible or untested", "why_it_matters": "Physical fit alone does not establish that a particular host can use the card." }, { "name": "Observed transfer performance", "kind": "measurement", "unit_or_values": "Read and write bytes per second, with workload, duration, host and reader recorded", "why_it_matters": "Determines whether the card can support a proposed recording or transfer workload." }, { "name": "Logical layout", "kind": "state", "unit_or_values": "Observed partition layout and filesystem, or unformatted, unrecognised, unreadable or unknown", "why_it_matters": "Explains whether a host can locate and interpret the stored volume." }, { "name": "Modification protection", "kind": "state", "unit_or_values": "Writable, host-enforced read-only, reader-reported write-protected, access-restricted or unknown", "why_it_matters": "Distinguishes actual permitted writes from a switch position or an untested assumption." }, { "name": "Integrity assessment", "kind": "state", "unit_or_values": "Untested, no errors within stated test coverage, intermittent errors, reproducible errors or inaccessible", "why_it_matters": "Supports decisions about ordinary use, recovery and retirement without implying complete certainty." }, { "name": "Physical condition", "kind": "state", "unit_or_values": "Observed housing, contact and contamination condition, with inspection date", "why_it_matters": "Identifies insertion hazards and possible causes of unstable access." }, { "name": "Data-preservation requirement", "kind": "relation", "unit_or_values": "Link to applicable retention, recovery, backup and operation-authorisation requirements", "why_it_matters": "Determines whether testing or modification may proceed without unacceptable data loss." } ], "affordances": [ "Inspect markings, dimensions, contacts and host-reported identity to classify the card.", "Select a compatible host, reader and adapter combination and establish access.", "Read, copy or image accessible data within the applicable authority.", "Test capacity, transfer performance and integrity using methods appropriate to data-preservation requirements.", "Write, partition, format or erase the card when authorised and compatible with its intended host.", "Remove, store, quarantine or retire the card according to its access state and condition." ] }, "sources": [ { "id": "wikipedia-memory-card", "title": "Memory card - Wikipedia, Wikimedia Foundation", "url": "https://en.wikipedia.org/wiki/Memory_card", "what_it_supports": "Form-factor families, historical formats, typical uses, and the distinction from other small storage and identity cards.", "url_status": "live" }, { "id": "sd-association", "title": "SD Memory Card specifications and capacity/speed classes - SD Association", "url": "https://www.sdcard.org/", "what_it_supports": "SD/miniSD/microSD mechanical sizes, SD/SDHC/SDXC/SDUC capacity classes, Speed Class, UHS, Video Speed Class, Application Performance Class, and SD Express.", "url_status": "live" }, { "id": "compactflash-association", "title": "CompactFlash, CFast and CFexpress specifications - CompactFlash Association", "url": "https://compactflash.org/", "what_it_supports": "CF Type I/II, CFast, and CFexpress Type A/B as the professional/high-speed card family.", "url_status": "live" }, { "id": "jedec-mmc", "title": "MultiMediaCard (MMC) / JESD84 family - JEDEC Solid State Technology Association", "url": "https://www.jedec.org/", "what_it_supports": "MMC as the JEDEC-standardized ancestor of the SD electrical family (distinct from removable SD licensing).", "url_status": "live" } ], "structure": { "bundles": [ { "id": "card-identity-and-format", "name": "Card identity and format", "description": "Establish what storage-bearing item is present and how confidently its family and identity are known.", "rationale": "Similar-looking cards and adapters can require different interfaces, and labels alone may not establish the actual device.", "layers": [ { "id": "physical-format", "name": "Physical format", "description": "Identify the card through its outline, dimensions, contacts and storage-bearing role.", "findings": [ { "id": "storage-bearing-card", "name": "Storage-bearing card", "description": "Record whether the inspected item contains the storage medium and which physical card format the evidence supports.", "questions": [ { "text": "Does this item itself provide storage, or is it an adapter containing or awaiting another card?", "kind": "boundary", "id": "storage-bearing-card-q01" }, { "text": "Which card format is supported by its dimensions, contact arrangement and markings?", "kind": "definition", "id": "storage-bearing-card-q02" } ] } ] }, { "id": "identity-evidence", "name": "Identity evidence", "description": "Connect printed and electronically reported identity to their evidence and limitations.", "findings": [ { "id": "claimed-and-observed-identity", "name": "Claimed and observed identity", "description": "Keep manufacturer, product, serial and capability claims distinguishable from corroborated observations.", "questions": [ { "text": "Which identity details come from the card label, packaging, purchase record or device interrogation?", "kind": "provenance", "id": "claimed-and-observed-identity-q01" }, { "text": "Do those details agree, and what evidence would resolve any suspected relabelling or substitution?", "kind": "provenance", "id": "claimed-and-observed-identity-q02" } ] } ] } ] }, { "id": "host-and-reader-compatibility", "name": "Host and reader compatibility", "description": "Determine whether the card can operate through a particular slot, reader and adapter chain.", "rationale": "A card can fit mechanically yet remain unsupported or work only with restricted capabilities.", "layers": [ { "id": "connection-path", "name": "Connection path", "description": "Describe the physical and interface path between the card and host.", "findings": [ { "id": "supported-insertion-path", "name": "Supported insertion path", "description": "Record the required slot or reader, any adapter and the evidence that the complete combination is suitable.", "questions": [ { "text": "Which slot, reader and adapter combination is intended for this card's identified family and format?", "kind": "boundary", "id": "supported-insertion-path-q01" }, { "text": "What fit, orientation and contact checks must pass before the card can be inserted without force?", "kind": "action", "id": "supported-insertion-path-q02" } ] } ] }, { "id": "host-support", "name": "Host support", "description": "Assess compatibility beyond physical insertion.", "findings": [ { "id": "usable-host-combination", "name": "Usable host combination", "description": "Record supported capacity ranges, interface modes and formatting requirements for the actual host configuration.", "questions": [ { "text": "What documentation or observed operation supports this host's ability to use the card's family, capacity and logical format?", "kind": "provenance", "id": "usable-host-combination-q01" }, { "text": "Does the host recognise and access the card consistently through the selected reader and adapter?", "kind": "measurement", "id": "usable-host-combination-q02" } ] } ] } ] }, { "id": "capacity-and-workload-fitness", "name": "Capacity and workload fitness", "description": "Assess how much data the card can retain and whether it can sustain the intended access pattern.", "rationale": "Reported capacity and speed markings are insufficient to establish reliable suitability for a specific recording or transfer task.", "layers": [ { "id": "capacity-evidence", "name": "Capacity evidence", "description": "Separate labelled, controller-reported, formatted and tested capacity.", "findings": [ { "id": "reliably-addressable-storage", "name": "Reliably addressable storage", "description": "Record capacity observations together with test coverage and whether writes and subsequent reads were verified.", "questions": [ { "text": "What capacities are labelled, reported by the device and available in the current filesystem, using explicit units?", "kind": "measurement", "id": "reliably-addressable-storage-q01" }, { "text": "How much addressable storage has been verified by writing and reading back data, and under what preservation constraints?", "kind": "measurement", "id": "reliably-addressable-storage-q02" } ] } ] }, { "id": "sustained-workload", "name": "Sustained workload", "description": "Relate performance evidence to a concrete host workload.", "findings": [ { "id": "performance-for-intended-use", "name": "Performance for intended use", "description": "Record speed claims and measured behaviour separately, including the conditions that limit their applicability.", "questions": [ { "text": "Which speed markings are present, and what authoritative specification defines each marking's test conditions?", "kind": "provenance", "id": "performance-for-intended-use-q01" }, { "text": "Can the card sustain the required write rate and access pattern in the intended host for the required duration?", "kind": "measurement", "id": "performance-for-intended-use-q02" } ] } ] } ] }, { "id": "recorded-data-and-access", "name": "Recorded data and access", "description": "Establish how stored data is organised, whether it is accessible and which modifications are permitted.", "rationale": "An unreadable card may have an unsupported or damaged logical layout, and apparently available storage may still contain data that must be preserved.", "layers": [ { "id": "volume-accessibility", "name": "Volume accessibility", "description": "Assess the card's logical layout and access barriers without equating mount failure with absent data.", "findings": [ { "id": "interpretable-storage-layout", "name": "Interpretable storage layout", "description": "Record detected partitions, filesystems and access restrictions, including uncertainty when inspection is incomplete.", "questions": [ { "text": "Which partitions and filesystems are detected, and can the intended host read them?", "kind": "measurement", "id": "interpretable-storage-layout-q01" }, { "text": "If access fails, what evidence distinguishes unsupported formatting, missing credentials, logical corruption and device-level failure?", "kind": "boundary", "id": "interpretable-storage-layout-q02" } ] } ] }, { "id": "write-and-erasure-authority", "name": "Write and erasure authority", "description": "Connect effective write protection and preservation requirements to proposed modifications.", "findings": [ { "id": "permitted-data-operation", "name": "Permitted data operation", "description": "Determine whether a particular write, format, test or erasure is both technically possible and authorised.", "questions": [ { "text": "What mechanism, if any, currently prevents writes, and has its effect been established for this reader and host?", "kind": "measurement", "id": "permitted-data-operation-q01" }, { "text": "Before modification, what authority and verified preservation copies are required for the data currently on the card?", "kind": "action", "id": "permitted-data-operation-q02" }, { "text": "What erasure outcome is required, and what evidence could demonstrate that the chosen method achieves it on this card?", "kind": "action", "id": "permitted-data-operation-q03" } ] } ] } ] }, { "id": "integrity-handling-and-retirement", "name": "Integrity, handling and retirement", "description": "Assess physical and storage faults and choose safe continued-use, recovery or retirement actions.", "rationale": "Small removable media can suffer contact damage, intermittent access and data errors that require different responses from routine formatting.", "layers": [ { "id": "fault-and-condition-evidence", "name": "Fault and condition evidence", "description": "Combine physical inspection with reproducible access and integrity observations.", "findings": [ { "id": "card-versus-connection-fault", "name": "Card versus connection fault", "description": "Record damage and errors while distinguishing evidence about the card from faults in its reader, adapter or host.", "questions": [ { "text": "Are the housing or contacts damaged, contaminated or deformed in a way that affects insertion or electrical contact?", "kind": "measurement", "id": "card-versus-connection-fault-q01" }, { "text": "Do access failures or data mismatches recur through a known-working compatible connection path?", "kind": "measurement", "id": "card-versus-connection-fault-q02" } ] } ] }, { "id": "handling-and-disposition", "name": "Handling and disposition", "description": "Choose actions that account for pending writes, recovery needs and the intended future use.", "findings": [ { "id": "next-safe-storage-action", "name": "Next safe storage action", "description": "Record the conditions for removal, further testing, reuse, quarantine or retirement without overstating remaining service life.", "questions": [ { "text": "What host-specific stop, flush or eject procedure must complete before this card is removed?", "kind": "action", "id": "next-safe-storage-action-q01" }, { "text": "Does the observed condition justify continued use, preservation imaging, quarantine or retirement for the proposed workload?", "kind": "action", "id": "next-safe-storage-action-q02" }, { "text": "Which documented handling and storage limits apply to this particular card, and are its intended conditions within them?", "kind": "boundary", "id": "next-safe-storage-action-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Full-size Secure Digital (SD, SDHC, SDXC, SDUC)", "microSD (and the short-lived miniSD)", "CompactFlash Type I and Type II", "CFast", "CFexpress Type A and Type B (XQD as the immediate predecessor)", "MultiMediaCard (MMC, RS-MMC, MMCplus)", "Sony Memory Stick family (Standard, PRO, Duo, Micro/M2)", "xD-Picture Card" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of memory card 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": "Q18373", "note": "Item commonly used for the removable flash memory-card class as a whole." }, { "scheme": "Wikidata", "value_or_pattern": "Q466977", "note": "Secure Digital card." }, { "scheme": "Wikidata", "value_or_pattern": "Q493106", "note": "CompactFlash." }, { "scheme": "SD Association form factor", "value_or_pattern": "SD | miniSD | microSD", "note": "Physical size class in the SD specifications." }, { "scheme": "SD Association capacity class", "value_or_pattern": "SD (≤2 GB) | SDHC (>2 GB-32 GB) | SDXC (>32 GB-2 TB) | SDUC (>2 TB-128 TB)", "note": "Marked on the card; also implies the expected file system (FAT16 / FAT32 / exFAT)." }, { "scheme": "SD CID register", "value_or_pattern": "128-bit Card IDentification (manufacturer ID, OEM ID, product name, serial, date)", "note": "On-card identifier readable by a host; analogous CID exists on MMC." }, { "scheme": "CFexpress type", "value_or_pattern": "Type A | Type B", "note": "Mechanical/electrical type; Type B shares the XQD body." }, { "scheme": "Retail GTIN", "value_or_pattern": "GTIN-13 / UPC-A on packaged SKUs", "note": "Identifies a manufacturer's capacity/speed SKU, not the inserted card instance." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of memory card 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": [ "SD Association - SD Specifications (Physical Layer, file system, Speed Class, UHS Speed Class, Video Speed Class, Application Performance Class, SD Express)", "CompactFlash Association - CompactFlash, CFast, and CFexpress specifications", "JEDEC - MultiMediaCard / JESD84 family", "PCI-SIG - PCI Express (electrical basis of CFexpress and SD Express)", "NVM Express, Inc. - NVMe (protocol used by CFexpress)", "Camera & Imaging Products Association (CIPA) - DCF (DC-009), the camera file layout commonly written onto memory cards", "European Union - RoHS Directive 2011/65/EU (hazardous-substance limits on the electronic assembly)" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of memory card 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": [ "Recording still photographs and video in interchangeable-lens cameras, compact cameras, camcorders, drones, action cameras, and dashcams", "Expanding or moving files on phones, tablets, and handheld consoles that still expose a microSD slot (for example Nintendo Switch)", "Field logging and removable media in industrial controllers, medical instruments, broadcast decks, and POS terminals that retain CF or SD slots", "Copying files to a computer through a USB or built-in card reader rather than tethering the host device", "Older game consoles used a different product sold under the same English name: a proprietary save card (PlayStation, GameCube, Xbox memory unit)" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of memory card 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": "Usable storage capacity", "typical_range": "8-1024 (retail 2020s; SD max 2, SDHC max 32, SDXC max 2048)", "unit": "GB" }, { "quantity": "Sustained sequential write", "typical_range": "10-300 (consumer SD/UHS); 300-2000 (CFexpress Type B)", "unit": "MB/s" }, { "quantity": "Full-size SD body", "typical_range": "32.0 × 24.0 × 2.1", "unit": "mm" }, { "quantity": "microSD body", "typical_range": "15.0 × 11.0 × 1.0", "unit": "mm" }, { "quantity": "Supply voltage", "typical_range": "2.7-3.6 (nominal 3.3; some UHS/Express modes also 1.8)", "unit": "V" }, { "quantity": "Mass", "typical_range": "0.25-2 (microSD/SD); about 8-12 (CompactFlash)", "unit": "g" }, { "quantity": "Consumer operating temperature", "typical_range": "0-70 (industrial grades often −25 to 85)", "unit": "°C" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of memory card 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": [ "NAND program/erase wear and spare-block exhaustion, after which writes fail or the card goes read-only", "Counterfeit cards that report a false capacity and silently overwrite earlier data", "File-system corruption from power loss or removal while mounted", "Generation mismatch: an SDXC/exFAT card in an SDHC-only host, or a UHS-II/CFexpress card run in a slower slot", "Insufficient sustained write causing dropped video frames even when the labelled burst speed looks adequate", "Dirty, worn, or bent contacts (especially CompactFlash pin arrays)", "Data-retention loss after long unpowered storage, worse with heat and with TLC/QLC NAND", "Personal data remaining on lost, sold, or 'formatted' cards", "Choking hazard from microSD and similar tiny cards" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of memory card 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": [ "In mainland China and much of East Asia, microSD is widely named and sold as a TF card (from SanDisk's T-Flash name)", "In Japan in the 2000s, Sony Memory Stick and Olympus/Fujifilm xD-Picture Card competed in cameras before SD became the default", "Professional stills and cinema worldwide use CFast or CFexpress in the high-speed slot that consumer cameras fill with SD", "Through the sixth video-game generation in Japan, North America, and Europe, 'memory card' meant a proprietary console save card, not SD-class media", "CompactFlash remains common in industrial and broadcast gear in many regions after consumer cameras dropped it" ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of memory card 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": "USB flash drive", "difference": "A USB flash drive has a USB plug and inserts into a USB receptacle; a memory card has no cable connector and needs a matching card slot or reader." }, { "name": "Smart card (ICC)", "difference": "A smart card follows ISO/IEC 7816 contacts and holds a cryptographic application; it is not a bulk NAND file volume." }, { "name": "SIM / UICC", "difference": "A SIM identifies a telecom subscriber and holds a small dedicated file system; it is not camera or media storage." }, { "name": "eMMC / UFS package", "difference": "eMMC and UFS are BGA packages soldered to a board; they are not user-removable cards." }, { "name": "SSD (M.2 or 2.5-inch)", "difference": "Those drives use SATA or M.2/U.2 hosts; a memory card uses an SD/CF/CFexpress slot - even though CFexpress is electrically an NVMe SSD in a card body." }, { "name": "Game ROM cartridge", "difference": "A cartridge presents factory software the console executes; a memory card is a user-writable general storage volume (console save cards are a grey zone under the same English name)." }, { "name": "PC Card (PCMCIA)", "difference": "A PC Card is the 85.6 × 54 mm laptop expansion card; CompactFlash is electrically related but much smaller and used as removable storage." }, { "name": "SDIO peripheral card", "difference": "An SDIO card uses the SD slot to provide I/O (Wi-Fi, GPS, and similar) rather than a mass-storage volume." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of memory card this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "With no registry definition recorded, which legacy and specialised removable card families does this entry include, and where is its boundary with card-form solid-state drives?", "Which authoritative family and host specifications should ground compatibility, capacity and speed-marking interpretations for each supported card type?", "Which card families expose useful health or endurance information, and how reliably can those observations support continued-use decisions?", "Which capacity and integrity tests provide sufficient evidence for each intended workload while respecting existing-data preservation requirements?", "Which erasure or sanitisation methods have a verifiable effect on each supported card family, including storage outside ordinary host-addressable space?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 30 } }, "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 memory card, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a removable memory card, assess its compatibility and storage condition, and decide which handling or data operations are appropriate.", "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: CFexpress, CompactFlash, SxS, UFS card, CFast, PlayStation Vita memory card, MemCard Pro, P2, Europcard, Nintendo GameCube Memory Card, SD card, MultiMediaCard.", "23 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 64 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 memory card, 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": [ "CFexpress", "CompactFlash", "SxS", "UFS card", "CFast", "PlayStation Vita memory card", "MemCard Pro", "P2", "Europcard", "Nintendo GameCube Memory Card", "SD card", "MultiMediaCard" ] } ], "standing": "Described in 64 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 23 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 memory card from another, and a memory 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 memory 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 memory 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 memory 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 memory 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 memory 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 memory 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 memory 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 memory 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 memory 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 memory 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 memory card from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a memory 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 memory 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 memory card 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 memory card 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 memory card, 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 memory card, 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 memory card 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 memory card is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a memory card, 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 memory card, 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 memory card 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 memory card is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a memory card, 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 memory card, 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 memory card 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 memory card 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 memory card is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a memory card, 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 memory card, 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 memory card 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 memory card 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 memory card, 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 memory card, 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 memory 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 memory 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 memory card between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a memory 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 memory 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 memory 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 memory card, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a memory 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 memory 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 memory 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 memory card 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 memory card 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 memory card 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 memory card, 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 memory card 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 memory card 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 memory card 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 memory card 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 memory card 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 memory card, 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 memory 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 memory card and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a memory 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 memory 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 memory 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 memory card is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a memory 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 memory 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 memory card 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 } } } }