{
  "vercy": "1.0-draft",
  "publication": {
    "status": "research-draft",
    "adjudicationStatus": "unreviewed",
    "publishableCanonical": false,
    "generatedAt": "2026-09-13T12:55:08Z",
    "providers": [
      "Claude"
    ],
    "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify",
    "pass": 2,
    "wave": 4,
    "engine": "claude",
    "enrichment": {
      "pass": 3,
      "engine": "claude",
      "producedAt": "2026-10-06T10:00:00Z",
      "ingestedAt": "2026-10-06T07:12:59+00:00",
      "fields": [
        "agent_conduct",
        "ethics",
        "owners"
      ]
    }
  },
  "metaModel": {
    "id": "THING-BAD-BLOCK",
    "registryId": "vr.tr.bad-block",
    "name": "bad block",
    "version": "0.2.0-wave.4",
    "entryKind": "thing",
    "family": "Thing Registry",
    "domain": [
      "XCT.QTY"
    ],
    "status": "research-draft"
  },
  "canonicalUrl": "https://ver.cy/models/thing/bad-block/",
  "model": {
    "registry_id": "vr.tr.bad-block",
    "name": "bad block",
    "purpose": "Let an agent explain bad blocks and how they arise, relay detection, remapping and management from storage references, describe warning signs and data recovery practice in general terms, and distinguish physical bad blocks from logical errors, file corruption and bad clusters at the file system level.",
    "definition": "In computer storage, a block, usually one sector, that cannot reliably hold data because of physical damage, wear or manufacturing defects, found on hard disks, solid-state drives and flash memory, detected by error-correcting codes and firmware and remapped to spare areas or marked in a bad block table by the file system; a growing number of bad blocks is a warning sign of drive failure.",
    "what_it_is_for": "Not applicable; a storage defect.",
    "affordances": [
      "explain causes",
      "relay detection and remapping",
      "describe warning signs",
      "distinguish related errors"
    ],
    "distinguishing_features": [
      "Physical defect",
      "Remapping",
      "Failure predictor",
      "Media-specific"
    ],
    "appearance": "Not a visible object; a defective storage sector.",
    "visual_identification": [
      "Sector that cannot reliably hold data",
      "Remapped sectors, bad block tables, SMART counts",
      "Logical errors are software; file corruption may be unrelated; bad clusters are file system units"
    ],
    "physical_properties": [
      {
        "quantity": "typical sector size",
        "typical_range": "512 or 4096",
        "unit": "bytes",
        "note": ""
      },
      {
        "quantity": "SMART attribute",
        "typical_range": "reallocated sector count",
        "unit": "note",
        "note": ""
      },
      {
        "quantity": "NAND flash",
        "typical_range": "wears with program-erase cycles",
        "unit": "note",
        "note": ""
      }
    ],
    "families_and_kinds": [
      "factory bad blocks on flash",
      "grown bad blocks from wear or damage",
      "pending and reallocated sectors on hard disks",
      "bad blocks marked by file systems",
      "bad blocks in RAID and SSD firmware management"
    ],
    "related_models": [
      {
        "relation": "is a kind of",
        "target": "storage defect",
        "why": "in general terms"
      },
      {
        "relation": "occurs on",
        "target": "hard disk drive",
        "why": "and solid-state drives"
      },
      {
        "relation": "is reported by",
        "target": "SMART",
        "why": "monitoring"
      },
      {
        "relation": "is contrasted with",
        "target": "file corruption",
        "why": "a logical error"
      }
    ],
    "identifiers": [
      {
        "scheme": "WordNet",
        "value_or_pattern": "oewn-13647935-n",
        "note": "a block that cannot reliably hold data"
      }
    ],
    "standards_and_regulation": [
      "ATA and NVMe specifications for SMART and remapping",
      "JEDEC flash endurance standards"
    ],
    "failure_modes_and_hazards": [
      "Data loss when bad blocks grow",
      "Ignoring SMART warnings",
      "Confusing physical and logical errors"
    ],
    "in_scope": [],
    "out_of_scope": [],
    "characteristics": [],
    "agent_conduct": {
      "may": [
        "Read SMART data and bad block counts from drives the agent is authorized to manage.",
        "Warn the owner and recommend a backup when bad blocks increase."
      ],
      "must_not": [
        "Ignore or hide growing bad block counts on drives holding important data.",
        "Run destructive surface tests on a drive without a backup and the owner's approval.",
        "Present a logical file system error as physical damage or the reverse.",
        "Claim deleted or damaged data is unrecoverable without checking."
      ],
      "requires_human": [
        "Wiping, reformatting or replacing a failing drive."
      ]
    },
    "ethics": {
      "considerations": [
        "Failing drives can take irreplaceable photos, records and work with them.",
        "Drives sold or discarded may still hold readable data in remapped blocks."
      ],
      "affected_parties": [
        "Data owners",
        "Users of shared storage",
        "Buyers of used drives"
      ]
    },
    "owners": {
      "steward": "The owner of the storage device.",
      "master_systems": []
    }
  },
  "sources": [
    {
      "id": "oewn",
      "title": "Open English WordNet 2024, synset oewn-13648260-n",
      "url": "https://en-word.net/id/oewn-13648260-n",
      "what_it_supports": "sense and gloss of the concept",
      "url_status": "live",
      "checked_by": "http 200"
    }
  ],
  "structure": {
    "bundles": [
      {
        "id": "understand",
        "name": "Understand",
        "description": "What a bad block is.",
        "rationale": "Science.",
        "layers": [
          {
            "id": "definition",
            "name": "Definition",
            "description": "Definition.",
            "findings": [
              {
                "id": "definition-finding",
                "name": "Definition",
                "description": "Definition.",
                "questions": [
                  {
                    "text": "What is a bad block, and how does it differ from logical errors and file corruption?",
                    "kind": "definition"
                  },
                  {
                    "text": "Is the question about the concept, a drive type or a data recovery situation?",
                    "kind": "boundary"
                  }
                ]
              }
            ]
          },
          {
            "id": "causes",
            "name": "Causes",
            "description": "Causes.",
            "findings": [
              {
                "id": "causes-finding",
                "name": "Causes",
                "description": "Causes.",
                "questions": [
                  {
                    "text": "What causes bad blocks on hard disks and flash memory?",
                    "kind": "definition"
                  },
                  {
                    "text": "Which entry fits NAND flash memory?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "manage",
        "name": "Manage",
        "description": "Detection and management.",
        "rationale": "Practice.",
        "layers": [
          {
            "id": "detection",
            "name": "Detection",
            "description": "Detection.",
            "findings": [
              {
                "id": "detection-finding",
                "name": "Detection",
                "description": "Detection.",
                "questions": [
                  {
                    "text": "How do ECC, SMART and disk checking tools detect bad blocks?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which references are standard?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          },
          {
            "id": "remapping",
            "name": "Remapping",
            "description": "Remapping.",
            "findings": [
              {
                "id": "remapping-finding",
                "name": "Remapping",
                "description": "Remapping.",
                "questions": [
                  {
                    "text": "How do drives and file systems remap or mark bad blocks?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which sources are cited?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "respond",
        "name": "Respond",
        "description": "Responding to bad blocks.",
        "rationale": "Application.",
        "layers": [
          {
            "id": "warning",
            "name": "Warning",
            "description": "Warning signs.",
            "findings": [
              {
                "id": "warning-finding",
                "name": "Warning",
                "description": "Warning.",
                "questions": [
                  {
                    "text": "When do bad blocks indicate imminent failure, and what should be done, in general terms?",
                    "kind": "action"
                  },
                  {
                    "text": "Which entry fits backup?",
                    "kind": "action"
                  }
                ]
              }
            ]
          },
          {
            "id": "recovery",
            "name": "Recovery",
            "description": "Data recovery.",
            "findings": [
              {
                "id": "recovery-finding",
                "name": "Recovery",
                "description": "Recovery.",
                "questions": [
                  {
                    "text": "How is data recovered from drives with bad blocks?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits data recovery?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "context",
        "name": "Context",
        "description": "Media and history.",
        "rationale": "Context.",
        "layers": [
          {
            "id": "media",
            "name": "Media",
            "description": "Media differences.",
            "findings": [
              {
                "id": "media-finding",
                "name": "Media",
                "description": "Media.",
                "questions": [
                  {
                    "text": "How do HDDs, SSDs and older media differ in bad block behaviour?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits solid-state drive?",
                    "kind": "action"
                  }
                ]
              }
            ]
          },
          {
            "id": "history",
            "name": "History",
            "description": "History.",
            "findings": [
              {
                "id": "history-finding",
                "name": "History",
                "description": "History.",
                "questions": [
                  {
                    "text": "How was bad block handling done on early disks and floppy disks?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits the history of data storage?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  },
  "openQuestions": [
    "Should SMART and wear levelling be the primary linked entries?",
    "How should storage references be linked?",
    "How should SSD and HDD handling be distinguished?"
  ],
  "statistics": {
    "bundles": 4,
    "layers": 8,
    "findings": 8,
    "questions": 16
  }
}
