{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:00:56Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 26.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094d8-1094-7c11-a5d9-a292b32b48bd\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: data loss\nSense to describe: (none recorded)\nDomain code: XCT.STA\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001 regis", "usd": 0.0, "recall": true }, "codex": { "seconds": 73.5, "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: 01a094d8-10a0-73f2-9b76-7c2bb0149bfa\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: data loss\nRegistry id: vr.tr.data-loss\nPlane / domain: XCT / XCT.STA\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCont" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:45:42+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:33+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q891179", "registryId": "vr.tr.data-loss", "name": "data loss", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.STA" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q891179/", "model": { "registry_id": "vr.tr.data-loss", "name": "data loss", "purpose": "Enable an agent to recognise suspected data loss, establish what information is missing or unusable, judge recoverability and consequences, and choose authorised preservation and recovery actions.", "definition": "Data loss is the unintended destruction, disappearance, or corruption of recorded data such that the required information cannot be retrieved in usable form from the affected system, whether or not it remains recoverable elsewhere.", "scope_statement": "This model owns data loss as an event or resulting condition in which expected information is absent, destroyed, or unusable relative to a stated preservation obligation, system boundary, and time; it records uncertainty about whether the loss is temporary, recoverable, or permanent.", "in_scope": [ "The information expected to survive and the evidence establishing that expectation", "Missing, destroyed, overwritten, or corrupted information and the affected copies or versions", "The loss interval, causal mechanism, and propagation across replicas or backups", "Recovery options, dependencies, achievable recovery points, and validation", "Consequences of missing information and decisions about residual loss" ], "out_of_scope": [ "Unauthorised disclosure or exfiltration without loss of the original information", "Service outages in which preserved data remains intact and usable after access returns", "General backup architecture and routine storage administration", "Routine authorised disposal that satisfies the applicable preservation obligations", "Complete cybersecurity incident management beyond its data loss aspects", "General data quality defects that do not remove or make expected information unrecoverable" ], "distinguishing_features": [ "An instance requires identifiable expected information and a preservation baseline; an empty dataset alone does not establish loss.", "Failure to retrieve data establishes suspected loss, but intact data behind a failed service or permission barrier may indicate an access outage instead.", "Disclosure alone changes who can access information; data loss changes whether the expected information remains available in a usable form within the stated boundary.", "Deletion of one replica establishes copy-level loss, while intact recoverable replicas may prevent information-level loss.", "Corruption counts as loss to the extent that expected information cannot be correctly interpreted or reconstructed; changed bytes alone do not establish that extent." ], "characteristics": [ { "name": "Preservation baseline", "kind": "relation", "unit_or_values": "Expected dataset, version, retention obligation, acknowledged write, or other evidenced preservation commitment", "why_it_matters": "Establishes what should exist before declaring anything lost." }, { "name": "Assessment boundary", "kind": "category", "unit_or_values": "Individual copy, storage system, organisation-held copies, or all known recoverable copies", "why_it_matters": "Separates local destruction from loss of the information across the assessed boundary." }, { "name": "Loss manifestation", "kind": "category", "unit_or_values": "Missing records, deleted objects, overwritten versions, truncation, corruption, lost decryption capability, or undetermined", "why_it_matters": "Directs evidence collection and recovery methods." }, { "name": "Affected extent", "kind": "measurement", "unit_or_values": "Records, objects, files, bytes, transactions, or percentage of an explicitly defined baseline", "why_it_matters": "Makes the amount of missing information assessable without equating storage size with business importance." }, { "name": "Loss interval", "kind": "measurement", "unit_or_values": "Earliest and latest possible loss timestamps, with timezone and uncertainty", "why_it_matters": "Helps locate usable recovery points and identify changes at risk." }, { "name": "Recoverability", "kind": "state", "unit_or_values": "Unknown, recovery candidate identified, recovery demonstrated, partially recoverable, or no recovery demonstrated within stated search limits", "why_it_matters": "Prevents the absence of a known recovery method from being presented as proof of permanent loss." }, { "name": "Recovery gap", "kind": "measurement", "unit_or_values": "Duration and identified changes between the latest validated recoverable state and the required state", "why_it_matters": "Distinguishes a recovery target from the actual information that restoration would omit." }, { "name": "Evidence confidence", "kind": "state", "unit_or_values": "Suspected, corroborated, confirmed for specified information, or disproved", "why_it_matters": "Allows an agent to act cautiously while separating observations from conclusions." }, { "name": "Lost information dependencies", "kind": "relation", "unit_or_values": "Affected decisions, transactions, services, obligations, and downstream datasets", "why_it_matters": "Connects loss to concrete consequences and recovery priorities." } ], "affordances": [ "Compare observed data against an evidenced preservation baseline to identify suspected gaps.", "Trace affected versions and copies to distinguish local loss from wider information loss.", "Recommend authorised containment that limits overwriting and propagation while preserving recovery evidence.", "Assess recovery candidates for completeness, integrity, dependencies, and achievable recovery point.", "Validate restored information against the baseline and record residual gaps.", "Escalate unresolved or consequential loss with explicit evidence, uncertainty, and decision ownership." ], "agent_conduct": { "may": [ "Detect and report data loss on systems it is authorized to monitor.", "Restore data from backups when the owner asks and the restore is tested.", "Keep backups and verify they can be restored." ], "must_not": [ "Delete, overwrite or corrupt data it is not authorized to change.", "Hide or downplay a data loss from the data owner.", "Claim data is recovered without verifying it.", "Run bulk changes on important data without a backup." ], "requires_human": [ "Notifying people or authorities when personal data is lost.", "Choosing to restore over current data, which may erase newer changes." ] }, "ethics": { "considerations": [ "Loss of records can harm people's health, money and rights.", "Hiding losses breaks trust and the law where personal data is involved." ], "affected_parties": [ "Data owners", "People whose data is lost", "Organizations relying on the data" ] }, "owners": { "steward": "The data owner or controller; the system operator answers for safeguards.", "master_systems": [] }, "failure_modes_and_hazards": [ "Untested backups can fail when needed.", "Silent corruption can spread into backups before it is noticed." ], "standards_and_regulation": [ "Regulation (EU) 2016/679, the General Data Protection Regulation, European Union.", "ISO/IEC 27001 Information security management systems, International Organization for Standardization and International Electrotechnical Commission." ], "what_it_is_for": [ "Data loss is encountered when stored, transmitted or processed information becomes missing or unusable.", "The concept is used in incident response, backup planning and reliability assessment to distinguish damaged information from temporary access failures.", "Recovery work evaluates the affected information, remaining copies and consequences for dependent services or records." ], "facets_not_applicable": { "recognition": "Data loss is an information-system condition without an intrinsic visual appearance, and visible errors alone cannot establish it." } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q891179: data loss", "url": "https://www.wikidata.org/wiki/Q891179", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Data loss", "url": "https://en.wikipedia.org/wiki/Data_loss", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "loss-definition-and-baseline", "name": "Loss definition and baseline", "description": "Establishes what information was expected to persist and the boundary within which its loss is assessed.", "rationale": "Data loss cannot be recognised reliably without separating preservation expectations from mere absence or failed access.", "layers": [ { "id": "expected-information", "name": "Expected information", "description": "Identifies the information and version that should still exist.", "findings": [ { "id": "preservation-expectation", "name": "Preservation expectation", "description": "Record the evidence that particular information existed or was committed for preservation, and who defines that obligation.", "questions": [ { "text": "Which records, objects, versions, or acknowledged transactions were expected to survive?", "kind": "definition", "id": "preservation-expectation-q01" }, { "text": "What receipt, inventory, transaction log, agreement, or other evidence establishes that expectation?", "kind": "provenance", "id": "preservation-expectation-q02" } ] } ] }, { "id": "assessment-boundaries", "name": "Assessment boundaries", "description": "Separates loss of a copy, loss of access, and loss of information.", "findings": [ { "id": "loss-versus-inaccessibility", "name": "Loss versus inaccessibility", "description": "State whose loss definition applies and whether the assessment concerns one copy, operational availability, or all known recoverable information.", "questions": [ { "text": "Does the applicable definition treat recoverable deletion or temporary inability to decrypt as data loss, and who uses that definition?", "kind": "definition", "id": "loss-versus-inaccessibility-q01" }, { "text": "What evidence distinguishes missing information from an intact copy hidden by permissions, indexing, connectivity, or service failure?", "kind": "boundary", "id": "loss-versus-inaccessibility-q02" } ] } ] } ] }, { "id": "missing-information-and-extent", "name": "Missing information and extent", "description": "Describes exactly what is absent or unusable and how much of the expected information is affected.", "rationale": "A count of damaged files or bytes may conceal partial records, lost relationships, or a small but decisive missing transaction.", "layers": [ { "id": "loss-manifestation", "name": "Loss manifestation", "description": "Distinguishes deletion, overwriting, corruption, and loss of interpretability.", "findings": [ { "id": "unusable-content", "name": "Unusable content", "description": "Identify whether content is physically absent, replaced by another version, or present but unusable because required information is missing.", "questions": [ { "text": "Is the expected content deleted, overwritten, truncated, corrupted, or inaccessible because a required key or interpretive dependency is missing?", "kind": "definition", "id": "unusable-content-q01" }, { "text": "Which comparison, integrity check, decoding attempt, or application-level check demonstrates the affected information?", "kind": "measurement", "id": "unusable-content-q02" } ] } ] }, { "id": "extent-and-uncertainty", "name": "Extent and uncertainty", "description": "Measures affected information against an explicit denominator.", "findings": [ { "id": "bounded-loss-inventory", "name": "Bounded loss inventory", "description": "Record confirmed missing units, potentially affected units, and intact units separately, including gaps in the baseline itself.", "questions": [ { "text": "How many records, objects, versions, or transactions are confirmed lost, and relative to which expected total?", "kind": "measurement", "id": "bounded-loss-inventory-q01" }, { "text": "Which portions cannot yet be assessed because inventories, logs, or comparison copies are incomplete?", "kind": "boundary", "id": "bounded-loss-inventory-q02" } ] } ] } ] }, { "id": "loss-timeline-and-propagation", "name": "Loss timeline and propagation", "description": "Reconstructs when information ceased to be preserved and how the loss reached other copies.", "rationale": "Recovery depends on locating an intact state before deletion, corruption, or overwriting propagated beyond it.", "layers": [ { "id": "event-reconstruction", "name": "Event reconstruction", "description": "Separates the last known good state, the suspected loss event, and discovery.", "findings": [ { "id": "loss-event-evidence", "name": "Loss event evidence", "description": "Record the time bounds and supported causal explanations without treating discovery time as loss time.", "questions": [ { "text": "When was the affected information last verified intact, and when was its absence or damage first verified?", "kind": "measurement", "id": "loss-event-evidence-q01" }, { "text": "Which evidence supports deletion, failed persistence, media failure, destructive modification, or another cause?", "kind": "provenance", "id": "loss-event-evidence-q02" } ] } ] }, { "id": "copy-propagation", "name": "Copy propagation", "description": "Tracks whether destructive changes reached replicas, synchronised folders, snapshots, and backups.", "findings": [ { "id": "surviving-copy-boundary", "name": "Surviving copy boundary", "description": "Map known copies to their version and integrity status, including whether they share the suspected failure mechanism.", "questions": [ { "text": "Which replicas, snapshots, archives, exports, or recipient-held copies predate the suspected loss and remain independently usable?", "kind": "provenance", "id": "surviving-copy-boundary-q01" }, { "text": "Which authorised pause, isolation, or retention action would prevent further propagation or expiry of a potentially intact copy?", "kind": "action", "id": "surviving-copy-boundary-q02" } ] } ] } ] }, { "id": "recovery-and-validation", "name": "Recovery and validation", "description": "Assesses restoration or reconstruction and determines whether recovered information meets the required state.", "rationale": "A backup's existence or a successful restore operation does not establish that the expected information has been recovered.", "layers": [ { "id": "recovery-candidates", "name": "Recovery candidates", "description": "Evaluates candidate copies, logs, and reconstruction inputs.", "findings": [ { "id": "achievable-recovered-state", "name": "Achievable recovered state", "description": "Record the latest demonstrably recoverable state, its prerequisites, and the information each recovery option would leave missing.", "questions": [ { "text": "Which candidate can restore the required information, and are its keys, logs, formats, and dependent datasets available?", "kind": "action", "id": "achievable-recovered-state-q01" }, { "text": "What time interval and specific changes would remain missing after using that candidate?", "kind": "measurement", "id": "achievable-recovered-state-q02" } ] } ] }, { "id": "recovered-information-verification", "name": "Recovered information verification", "description": "Checks completeness, correctness, and consistency after restoration.", "findings": [ { "id": "verified-recovery-outcome", "name": "Verified recovery outcome", "description": "Assess recovery against the preservation baseline, including transaction consistency and relationships that file-level checks may miss.", "questions": [ { "text": "Which baseline comparisons and application-level checks demonstrate that recovered content is complete and usable?", "kind": "measurement", "id": "verified-recovery-outcome-q01" }, { "text": "Which records, versions, relationships, or transactions remain missing or uncertain after validation?", "kind": "boundary", "id": "verified-recovery-outcome-q02" } ] } ] } ] }, { "id": "consequences-and-loss-disposition", "name": "Consequences and loss disposition", "description": "Connects missing information to dependent activities and records decisions about further recovery or accepted residual loss.", "rationale": "Recovery priorities and closure depend on what the missing information enables and who can accept the remaining gap.", "layers": [ { "id": "information-dependent-consequences", "name": "Information-dependent consequences", "description": "Identifies decisions, operations, and evidence that require the missing information.", "findings": [ { "id": "affected-use-and-priority", "name": "Affected use and priority", "description": "Link missing information to specific blocked or unreliable uses, distinguishing observed consequences from possible ones.", "questions": [ { "text": "Which transactions, decisions, services, or obligations cannot be completed or trusted because this information is missing?", "kind": "boundary", "id": "affected-use-and-priority-q01" }, { "text": "Which information should be recovered first based on its dependent uses, deadlines, and available substitutes?", "kind": "action", "id": "affected-use-and-priority-q02" } ] } ] }, { "id": "residual-loss-decision", "name": "Residual loss decision", "description": "Records the remaining uncertainty and authority for ending recovery efforts.", "findings": [ { "id": "documented-loss-disposition", "name": "Documented loss disposition", "description": "State what remains lost, what recovery avenues were assessed, and the basis for continuing, suspending, or closing recovery.", "questions": [ { "text": "What evidence and search limits support the conclusion that no further recovery is presently achievable?", "kind": "provenance", "id": "documented-loss-disposition-q01" }, { "text": "Who may accept the residual information gap, and what new evidence would trigger renewed recovery work?", "kind": "action", "id": "documented-loss-disposition-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "No sense is recorded; this description assumes digital information systems.", "Usage varies between loss from a particular system and permanent loss across all recoverable copies; any operational definition should state its scope.", "These standards and regulatory references are recalled, not checked; editions, applicability, and legal obligations require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of data loss 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": [ "Accidental deletion or overwriting", "Loss through storage media or hardware failure", "Logical corruption caused by software or filesystem faults", "Malicious destruction or ransomware-related loss", "Loss through physical destruction or disappearance of storage", "Loss of access through destruction of necessary cryptographic keys" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of data loss this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "ISO/IEC 27001, issued by ISO and IEC, specifies information security management system requirements relevant to managing data-loss risk.", "ISO/IEC 27002, issued by ISO and IEC, provides information security control guidance covering information backup and related safeguards.", "NIST SP 800-34, issued by the US National Institute of Standards and Technology, provides contingency planning guidance for federal information systems.", "ISO 22301, issued by ISO, specifies business continuity management system requirements relevant to recovery from data-loss incidents.", "The European Union General Data Protection Regulation includes accidental or unlawful destruction or loss of personal data within its definition of a personal data breach." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of data loss 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": [ "Designing backup, retention, and restoration arrangements", "Setting recovery objectives for business continuity and disaster recovery", "Investigating incidents and determining which records require reconstruction", "Assessing storage durability, replication, and application recovery behavior", "Evaluating the consequences of losing personal, operational, or archival records" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of data loss 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": "Amount of data lost", "typical_range": "Incident-dependent; from individual records to entire datasets", "unit": "bytes or records" }, { "quantity": "Proportion of the relevant dataset lost", "typical_range": "0-100, with the dataset and counting method specified", "unit": "percent" }, { "quantity": "Recovery point objective", "typical_range": "System-specific target for the maximum acceptable age of the recovery point; not a measurement of actual loss", "unit": "time" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of data loss 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": [ "Replication can propagate deletions or corruption to every replica.", "Backups may be incomplete, unreadable, or unusable without missing keys, software, or configuration.", "Shared credentials or infrastructure can expose production data and backups to the same destructive incident.", "Undetected corruption can persist until usable recovery copies expire.", "Incomplete recovery can leave related records inconsistent, undermining subsequent decisions or transactions." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of data loss 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": [ "Legal duties concerning lost personal data vary by jurisdiction, including breach definitions and notification thresholds.", "Sector-specific retention and recordkeeping duties affect the consequences of data loss." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of data loss 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": "Data unavailability", "difference": "Data may be intact but temporarily unreachable; an outage alone does not establish destruction or loss of the underlying information." }, { "name": "Data corruption", "difference": "Corruption changes data improperly; it constitutes data loss when required information can no longer be retrieved correctly." }, { "name": "Data leakage", "difference": "Leakage concerns unauthorized disclosure, which can occur while all original data remains intact." }, { "name": "Data erasure", "difference": "Erasure can be an authorized, intended lifecycle operation; data loss is unintended relative to the requirement to retain the information." }, { "name": "Packet loss", "difference": "Packet loss concerns missing transmission units; retransmission or redundancy may prevent any lasting loss of application data." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of data loss this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which definitions used in storage engineering, security practice, and business continuity should this registry entry represent, particularly for recoverable deletion and temporary unavailability?", "What evidence threshold should justify describing information as permanently lost rather than unrecovered within a bounded search?", "How should the model distinguish never-captured information from loss of acknowledged or contractually expected writes?", "When should missing encryption keys, schemas, or software dependencies count as data loss rather than a separate access or interpretability failure?", "How should reconstructed or re-entered information be judged equivalent to an original when exact content, provenance, or evidential value cannot be restored?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }