{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T11:14:36Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 27.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09552-86bc-76b0-b809-42df451a462e\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: memory\nSense to describe: an electronic memory device\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 044: 1", "usd": 0.0, "recall": true }, "codex": { "seconds": 67.8, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a09552-86b5-7080-a1ae-1f19a5dc8588\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: memory\nRegistry id: vr.tr.memory-artifact\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: an electronic memory device\nNames folded into this entry" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:43:42+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T12:16:27+00:00", "evidence": [ "completeness 1.00", "sense: WordNet gloss", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-MEMORY-ARTIFACT", "registryId": "vr.tr.memory-artifact", "name": "memory", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/memory-artifact/", "model": { "registry_id": "vr.tr.memory-artifact", "name": "memory", "purpose": "Enable an AI agent to recognise an electronic memory device, assess its compatibility and data-retention state, and determine which access, testing, replacement or disposal actions are appropriate.", "definition": "An electronic memory device is a physical electronic component that stores encoded information in distinguishable internal states and permits that information to be retrieved, with writing, erasing and retention characteristics determined by its technology.", "scope_statement": "This model owns the registered kind vr.tr.memory-artifact in PHY / PHY.OBJ: a physical electronic memory device whose defining function is to retain encoded data for subsequent retrieval, including the device-level properties needed to judge particular implementations and units.", "in_scope": [ "Memory technology, physical implementation and boundary between component, module and integrated memory region", "Addressable capacity, organisation and supported read, write and erase operations", "Electrical interface, power requirements and access timing", "Volatility, retention, endurance and observable data-integrity condition", "Memory-specific protection, diagnostics, handling and end-of-service actions" ], "out_of_scope": [ "Human memory, organisational memory and abstract information retention", "The meaning, ownership and application-level structure of stored content", "Software address spaces, allocation policies and virtual-memory management", "Host processors, motherboards and complete computing systems", "Complete storage appliances and their file-system or service-level behaviour" ], "distinguishing_features": [ "The referent is physical electronic hardware with states used to retain encoded data, rather than a software memory allocation or a remembered experience.", "The device provides a defined means of retrieving stored data; merely propagating a signal does not establish a memory function.", "A read-only implementation can qualify: rewriting during normal use is not a required identifying feature.", "Loss of contents when power is removed distinguishes a retention behaviour, rather than determining whether the device qualifies as memory.", "For a controller-equipped storage product, identify whether the referent is its memory component or the complete managed storage device before applying this model." ], "characteristics": [ { "name": "Memory technology", "kind": "category", "unit_or_values": "Documented technology, such as SRAM, DRAM, ROM, EEPROM or flash; unknown", "why_it_matters": "Determines which retention, access and maintenance behaviours must be investigated." }, { "name": "Physical implementation", "kind": "category", "unit_or_values": "Discrete device; memory module; embedded memory region; other documented implementation", "why_it_matters": "Establishes the boundary for identification, testing and replacement." }, { "name": "Capacity and organisation", "kind": "measurement", "unit_or_values": "bits or bytes, with explicit prefixes; addressable locations × bits per location; exposed and reserved capacity distinguished", "why_it_matters": "Prevents nominal capacity from being confused with usable capacity or address width." }, { "name": "Power-loss retention", "kind": "category", "unit_or_values": "Volatile; nonvolatile; dependent on backup supply; unknown, with operating conditions", "why_it_matters": "Determines whether a power transition can destroy required contents." }, { "name": "Access interface", "kind": "relation", "unit_or_values": "Named electrical interface or protocol, revision, pinout and compatible host relationship", "why_it_matters": "Supports compatibility assessment beyond matching physical connectors." }, { "name": "Access and modification granularity", "kind": "measurement", "unit_or_values": "bits or bytes per read, write, program and erase unit, where applicable", "why_it_matters": "Reveals when modifying one value can affect a larger region." }, { "name": "Access performance", "kind": "measurement", "unit_or_values": "Read latency in ns or µs; write or program duration in ns, µs or ms; transfer rate in bit/s or byte/s, with workload and configuration", "why_it_matters": "Allows the agent to distinguish latency, sustained throughput and operation-completion time." }, { "name": "Supply requirements", "kind": "measurement", "unit_or_values": "V and A for each required rail and operating state; sequencing constraints recorded separately", "why_it_matters": "Determines whether powering or accessing the device is compatible with its documented limits." }, { "name": "Retention and endurance limits", "kind": "measurement", "unit_or_values": "Retention duration in hours or years under stated conditions; write or program/erase cycles where specified", "why_it_matters": "Separates expected data persistence from tolerance for repeated modification." }, { "name": "Observed integrity condition", "kind": "state", "unit_or_values": "Untested; no errors detected by stated test; corrected errors observed; uncorrectable errors observed; inaccessible", "why_it_matters": "Makes condition judgments dependent on evidence rather than successful enumeration alone." }, { "name": "Access protection state", "kind": "state", "unit_or_values": "Documented read, write or erase restrictions by region; lock reversibility; unknown", "why_it_matters": "Constrains permissible operations and identifies irreversible configuration changes." } ], "affordances": [ "Identify the device technology and physical boundary from markings, documentation and supported identification reads.", "Check host, pinout, supply and timing compatibility before connection or configuration.", "Read or test selected regions using procedures that account for content preservation and test coverage.", "Write, program or erase supported regions after checking protection, granularity and endurance implications.", "Assess retention and integrity evidence to decide whether continued use, data recovery or replacement is appropriate.", "Select a documented clearing, sanitisation or disposal procedure appropriate to the memory technology and accessible regions." ], "agent_conduct": { "may": [ "Read, test and report the capacity, health and type of memory devices it is authorized to manage.", "Securely erase memory devices at the owner's request before reuse or disposal." ], "must_not": [ "Read or copy data from a memory device that belongs to someone else without consent or lawful authority.", "Discard or resell a memory device without securely erasing personal data.", "Overwrite or erase data that has not been confirmed as backed up or unwanted.", "Install memory in a powered system or without antistatic precautions." ], "requires_human": [ "Erasing or destroying a device that may hold evidence or the only copy of data.", "Recovering data from a device for someone other than its owner." ] }, "ethics": { "considerations": [ "Memory devices hold private and sensitive information; access to them is access to people's data.", "Electronic waste harms the environment if not recycled." ], "affected_parties": [ "Owners of stored data", "People whose data is stored", "Recycling workers" ] }, "owners": { "steward": "The person or organization that owns the device; the data controller answers for personal data on it.", "master_systems": [] }, "visual_identification": [ "Chips on a circuit board, such as a memory module with a row of gold contacts, or a soldered chip with a part marking." ], "failure_modes_and_hazards": [ "Static discharge and heat can damage memory and corrupt data.", "Wear and charge loss can silently lose stored data.", "Incompletely erased devices can leak personal data." ], "standards_and_regulation": [ "JESD79, DDR SDRAM Standard, JEDEC Solid State Technology Association." ], "what_it_is_for": [ "Electronic memory devices occur in computers, controllers, instruments and other equipment that stores digital information.", "They hold working data, program instructions or retained settings according to their storage technology.", "Equipment design and maintenance assess memory capacity, electrical compatibility and retention requirements when selecting or replacing these components." ] }, "sources": [ { "id": "oewn", "title": "Open English WordNet 2024, synset oewn-03749767-n", "url": "https://en-word.net/id/oewn-03749767-n", "what_it_supports": "sense and gloss of the concept", "url_status": "live", "checked_by": "http 200" }, { "id": "wiktionary-en", "title": "Wiktionary: memory", "url": "https://en.wiktionary.org/wiki/memory", "what_it_supports": "word senses and usage", "url_status": "live", "checked_by": "http 200" } ], "structure": { "bundles": [ { "id": "memory-identity-and-boundary", "name": "Memory identity and boundary", "description": "Establishes what physical memory the entry represents and which functions belong to that memory.", "rationale": "Memory can denote a chip, module or embedded region; an agent needs a stable boundary before attributing capacity or behaviour.", "layers": [ { "id": "physical-memory-referent", "name": "Physical memory referent", "description": "Identifies the hardware boundary without promoting a product model or individual unit into a separate kind.", "findings": [ { "id": "component-module-or-region", "name": "Component, module or region", "description": "Record whether the referent is a discrete memory device, an assembly of devices or memory embedded within another component.", "questions": [ { "text": "What physical boundary does the registered memory kind include, and where does the containing host begin?", "kind": "boundary", "id": "component-module-or-region-q01" }, { "text": "Which markings, identification records or manufacturer documents establish the implementation of a particular device?", "kind": "provenance", "id": "component-module-or-region-q02" } ] } ] }, { "id": "storage-mechanism", "name": "Storage mechanism", "description": "Separates the physical storage technology from the role assigned by a host.", "findings": [ { "id": "technology-and-system-role", "name": "Technology and system role", "description": "Record the documented memory technology independently of uses such as working memory, firmware storage or buffering.", "questions": [ { "text": "What technology retains the encoded state, and what evidence identifies it?", "kind": "definition", "id": "technology-and-system-role-q01" }, { "text": "Which observed behaviours belong to the memory itself, and which are supplied by a controller or host?", "kind": "boundary", "id": "technology-and-system-role-q02" } ] } ] } ] }, { "id": "capacity-and-memory-operations", "name": "Capacity and memory operations", "description": "Describes how stored locations are organised, addressed and modified.", "rationale": "A capacity figure alone cannot establish whether a requested read or update is possible or what other data it may affect.", "layers": [ { "id": "addressable-organisation", "name": "Addressable organisation", "description": "Connects nominal storage capacity to the locations and regions exposed through the interface.", "findings": [ { "id": "capacity-map-and-reservations", "name": "Capacity map and reservations", "description": "Record address units, word width, banks and reserved regions where these affect usable capacity or access.", "questions": [ { "text": "How many locations are exposed, how many bits does each contain, and what capacity convention is used?", "kind": "measurement", "id": "capacity-map-and-reservations-q01" }, { "text": "Which regions are reserved, inaccessible or used for integrity metadata rather than caller data?", "kind": "boundary", "id": "capacity-map-and-reservations-q02" } ] } ] }, { "id": "read-write-and-erase", "name": "Read, write and erase", "description": "Records supported operations and their smallest affected regions.", "findings": [ { "id": "modification-rules", "name": "Modification rules", "description": "Determine whether updates are supported, require prior erasure or can irreversibly change stored state.", "questions": [ { "text": "What are the minimum read, write, program and erase units for each applicable region?", "kind": "measurement", "id": "modification-rules-q01" }, { "text": "What sequence can perform the requested update, and which neighbouring contents must first be preserved?", "kind": "action", "id": "modification-rules-q02" } ] } ] } ] }, { "id": "electrical-access-and-power", "name": "Electrical access and power", "description": "Captures the conditions under which the memory can be connected, accessed and placed into power states.", "rationale": "Connector fit and advertised capacity do not establish electrical compatibility or preservation of contents.", "layers": [ { "id": "interface-and-timing", "name": "Interface and timing", "description": "Relates physical connections and signalling to valid memory transactions.", "findings": [ { "id": "host-access-compatibility", "name": "Host access compatibility", "description": "Record pinout, signalling levels, protocol revision and timing requirements for the actual configuration.", "questions": [ { "text": "Which interface specification and manufacturer documentation define compatible signalling and pin assignments?", "kind": "provenance", "id": "host-access-compatibility-q01" }, { "text": "What latency, transfer-rate and operation-completion limits apply under the intended configuration?", "kind": "measurement", "id": "host-access-compatibility-q02" } ] } ] }, { "id": "power-and-retention-states", "name": "Power and retention states", "description": "Connects supply states, refresh or backup dependencies and transitions to data preservation.", "findings": [ { "id": "content-preserving-power-transitions", "name": "Content-preserving power transitions", "description": "Record which power states preserve data and what supporting activity or supply each requires.", "questions": [ { "text": "Which supply rails, refresh activity or backup source are required to retain contents in each supported state?", "kind": "definition", "id": "content-preserving-power-transitions-q01" }, { "text": "What must complete before entering standby, resetting the interface or removing power?", "kind": "action", "id": "content-preserving-power-transitions-q02" } ] } ] } ] }, { "id": "retention-endurance-and-integrity", "name": "Retention, endurance and integrity", "description": "Organises evidence about whether stored values remain retrievable and how use affects reliability.", "rationale": "Memory can remain accessible while returning incorrect data, and retention duration is distinct from modification endurance.", "layers": [ { "id": "retention-and-wear-envelope", "name": "Retention and wear envelope", "description": "Records documented persistence and modification limits together with their qualifying conditions.", "findings": [ { "id": "conditional-retention-and-endurance", "name": "Conditional retention and endurance", "description": "Associate retention and endurance claims with technology, temperature, usage history and the region to which they apply.", "questions": [ { "text": "What retention duration and endurance limits are documented, and under which temperature and usage conditions?", "kind": "measurement", "id": "conditional-retention-and-endurance-q01" }, { "text": "What evidence about this unit's modification history or exposure supports a remaining-use judgment?", "kind": "provenance", "id": "conditional-retention-and-endurance-q02" } ] } ] }, { "id": "error-observation-and-response", "name": "Error observation and response", "description": "Distinguishes raw storage behaviour from errors detected, corrected or hidden by supporting mechanisms.", "findings": [ { "id": "integrity-evidence-and-test-coverage", "name": "Integrity evidence and test coverage", "description": "Record diagnostic coverage, observed errors and the location of any correction mechanism before judging health.", "questions": [ { "text": "Which errors can the device or host detect and correct, and which error observations are exposed to the agent?", "kind": "boundary", "id": "integrity-evidence-and-test-coverage-q01" }, { "text": "Which test can investigate the suspected fault, and will it overwrite contents or consume modification endurance?", "kind": "action", "id": "integrity-evidence-and-test-coverage-q02" } ] } ] } ] }, { "id": "protection-and-service-actions", "name": "Protection and service actions", "description": "Defines memory-specific restrictions and procedures for modification, removal and end of service.", "rationale": "A technically supported operation may be blocked, irreversible or insufficient to clear all retained data.", "layers": [ { "id": "protected-and-irreversible-states", "name": "Protected and irreversible states", "description": "Identifies region-level restrictions and configuration changes that may permanently constrain use.", "findings": [ { "id": "access-locks-and-one-time-changes", "name": "Access locks and one-time changes", "description": "Record read, write and erase protection, including whether locks or programming operations can be reversed.", "questions": [ { "text": "Which regions or operations are protected, and how is the current protection state established?", "kind": "measurement", "id": "access-locks-and-one-time-changes-q01" }, { "text": "Would the proposed command set a permanent lock, consume one-time programmability or prevent later recovery?", "kind": "action", "id": "access-locks-and-one-time-changes-q02" } ] } ] }, { "id": "removal-and-data-clearance", "name": "Removal and data clearance", "description": "Relates physical service procedures to preservation or deliberate elimination of retained contents.", "findings": [ { "id": "service-and-sanitisation-evidence", "name": "Service and sanitisation evidence", "description": "Record handling requirements, replacement constraints and evidence that a clearing procedure reaches the intended storage regions.", "questions": [ { "text": "What power isolation, electrostatic handling and data-preservation steps does the documented removal or replacement procedure require?", "kind": "action", "id": "service-and-sanitisation-evidence-q01" }, { "text": "Which documented clearing or sanitisation method applies, and what evidence establishes its coverage of inaccessible or remapped regions?", "kind": "provenance", "id": "service-and-sanitisation-evidence-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is a recall-based description; no sources were consulted.", "Capacity, latency, endurance and retention must be checked against a specific device datasheet and operating conditions.", "The kinds listed are representative rather than exhaustive; verify applicable standard editions and regulatory scope for a particular product." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Static random-access memory (SRAM)", "Dynamic random-access memory (DRAM)", "Mask-programmed read-only memory (mask ROM)", "Electrically erasable programmable read-only memory (EEPROM)", "Flash memory, including NAND and NOR", "Magnetoresistive random-access memory (MRAM)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Manufacturer part number", "value_or_pattern": "Manufacturer-specific alphanumeric code", "note": "Identifies a device variant; suffixes commonly distinguish capacity, organization, package, speed and temperature grade." }, { "scheme": "JEDEC JEP106 manufacturer identification code", "value_or_pattern": "Bank and manufacturer code", "note": "Identifies the manufacturer where supported by the device identification interface; it does not uniquely identify a model or individual unit." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "JEDEC JESD79 series: electrical and operational specifications for generations of DDR SDRAM.", "JEDEC JESD22 series: semiconductor device test methods, applicable to memory qualification and reliability testing.", "European Union RoHS Directive: restrictions on certain hazardous substances in electrical and electronic equipment, subject to scope and exemptions." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Working memory for processors and embedded controllers.", "Processor caches and high-speed data buffers.", "Retention of firmware, boot code and configuration settings.", "Nonvolatile data storage within solid-state drives, memory cards and embedded systems.", "Temporary storage of image, audio and network data." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Access latency", "typical_range": "Approximately 1-20 for many SRAM devices; interface and device architecture affect the value", "unit": "ns" }, { "quantity": "Capacity per discrete DRAM chip", "typical_range": "Illustrative common capacities: 4, 8, 16 and 32; not an exhaustive or current market range", "unit": "Gibit" }, { "quantity": "Serial EEPROM rated write endurance", "typical_range": "Often 100000-1000000; the applicable byte or page granularity and test conditions depend on the device", "unit": "write cycles" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Volatile SRAM and DRAM lose stored information when power is removed; DRAM also requires refresh.", "Flash and EEPROM cells wear through repeated programming and erasing, and retained data can degrade with time and temperature.", "Radiation, electrical noise or disturbances from repeated accesses can cause bit errors; susceptibility depends on technology and implementation.", "Electrostatic discharge, excessive voltage and overheating can permanently damage a device.", "Interrupted writes or operation outside specified voltage and timing limits can corrupt data." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Environmental substance restrictions and electronic-waste obligations vary by jurisdiction; the basic memory technologies are used internationally." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Information", "difference": "Information is the encoded content; the memory device is the physical component that retains its representation." }, { "name": "Memory module", "difference": "A module assembles memory chips and supporting components on a board; a memory device may be an individual chip." }, { "name": "Solid-state drive", "difference": "An SSD combines nonvolatile memory with a controller and storage interface to provide a managed block-storage device." }, { "name": "Processor", "difference": "A processor primarily executes operations on information, whereas a memory device primarily retains and supplies it; either may contain the other as an integrated subsystem." }, { "name": "Biological memory", "difference": "Biological memory involves retention through changes in living systems rather than an electronic storage component." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of memory this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the existing catalogue already contain a world model covering this electronic-memory concept, requiring a registry link instead of a separate publication?", "Where does the registry draw the boundary between electronic memory devices, embedded memory regions and complete controller-managed storage devices?", "Which primary technology and manufacturer sources should establish representative retention, endurance, timing and capacity ranges without implying universal limits?", "Which interface, qualification, handling and sanitisation standards apply to each included implementation, and which issuing bodies and revisions govern them?", "Which integrity and wear indicators are actually observable across the included technologies, and where must unit condition remain unknown?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 29 } }