{
  "vercy": "1.0-draft",
  "publication": {
    "status": "research-draft",
    "adjudicationStatus": "unreviewed",
    "publishableCanonical": false,
    "generatedAt": "2026-09-13T05:29:44Z",
    "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": 3,
    "engine": "claude",
    "enrichment": {
      "pass": 3,
      "engine": "claude",
      "producedAt": "2026-10-06T10:00:00Z",
      "ingestedAt": "2026-10-06T07:08:05+00:00",
      "fields": [
        "agent_conduct",
        "ethics",
        "owners"
      ]
    },
    "revisions": [
      {
        "at": "2026-10-08T18:42:31+00:00",
        "engine": "codex",
        "fields": [
          "definition"
        ],
        "answering_review": "bc7a95d99b386e1cfb48df3ca8d4b3b84e7033816142c29d64b6b85cc956d94a"
      }
    ],
    "gate": {
      "passed": true,
      "version": "1.0",
      "at": "2026-10-08T18:54:34+00:00",
      "evidence": [
        "completeness 1.00",
        "sense: WordNet gloss",
        "2 live sources",
        "review by codex: pass"
      ]
    }
  },
  "metaModel": {
    "id": "THING-ALLOCATION-UNIT",
    "registryId": "vr.tr.allocation-unit",
    "name": "allocation unit",
    "version": "0.2.0-wave.3",
    "entryKind": "thing",
    "family": "Thing Registry",
    "domain": [
      "XCT.QTY"
    ],
    "status": "research-draft"
  },
  "canonicalUrl": "https://ver.cy/models/thing/allocation-unit/",
  "model": {
    "registry_id": "vr.tr.allocation-unit",
    "name": "allocation unit",
    "purpose": "Let an agent explain allocation units and their role in file systems, relay sizes, trade-offs and formatting choices from computing references, describe slack space and fragmentation, and distinguish allocation units from sectors, blocks in other senses and partitions.",
    "definition": "The smallest unit of disk space that a file system can allocate to a file, consisting of a group of one or more sectors on a magnetic or solid-state disk that is reserved as a whole, also called a cluster in FAT and NTFS or a block in Unix file systems; file data allocated this way occupies whole allocation units, with any unused remainder of the last unit forming slack space, but inline or resident data and tail packing are exceptions to this allocation pattern; the allocation unit size is chosen when a volume is formatted and affects capacity efficiency and performance.",
    "what_it_is_for": "Allocating disk space to files.",
    "affordances": [
      "explain the concept",
      "relay sizes and trade-offs",
      "describe slack and fragmentation",
      "distinguish related terms"
    ],
    "distinguishing_features": [
      "Whole-unit allocation",
      "Set at formatting",
      "Slack space",
      "File system dependent"
    ],
    "appearance": "Not a visible object; a unit of storage allocation.",
    "visual_identification": [
      "Smallest allocatable group of sectors",
      "Clusters in FAT and NTFS, blocks in ext4 and other Unix file systems",
      "A sector is the hardware unit; a partition is a volume; a memory block is a different concept"
    ],
    "physical_properties": [
      {
        "quantity": "common NTFS default",
        "typical_range": "4",
        "unit": "KB",
        "note": "for most volumes"
      },
      {
        "quantity": "sector size",
        "typical_range": "512 or 4096",
        "unit": "bytes",
        "note": ""
      },
      {
        "quantity": "FAT32 cluster range",
        "typical_range": "512 bytes to 32 KB",
        "unit": "range",
        "note": "typical"
      }
    ],
    "families_and_kinds": [
      "clusters in FAT and NTFS",
      "blocks in ext and other Unix file systems",
      "allocation units in exFAT and ReFS",
      "allocation groups and extents as higher-level structures"
    ],
    "related_models": [
      {
        "relation": "is a kind of",
        "target": "unit of data storage",
        "why": "in general terms"
      },
      {
        "relation": "is made of",
        "target": "disk sector",
        "why": "one or more"
      },
      {
        "relation": "is defined by",
        "target": "file system",
        "why": "at formatting"
      },
      {
        "relation": "produces",
        "target": "slack space",
        "why": "in partially filled units"
      }
    ],
    "identifiers": [
      {
        "scheme": "WordNet",
        "value_or_pattern": "oewn-13622839-n",
        "note": "a group of sectors on a magnetic disk that can be reserved for the use of a particular file"
      }
    ],
    "standards_and_regulation": [
      "File system specifications such as FAT, NTFS and ext4 documentation",
      "No regulation"
    ],
    "failure_modes_and_hazards": [
      "Wasted space from large units and small files",
      "Fragmentation",
      "Confusing allocation units with sectors"
    ],
    "in_scope": [],
    "out_of_scope": [],
    "characteristics": [],
    "agent_conduct": {
      "may": [
        "Explain allocation units and how cluster size affects storage efficiency, citing file system documentation.",
        "Report the cluster size and wasted space on a volume it is authorized to inspect."
      ],
      "must_not": [
        "Reformat or resize a volume to change cluster size without a verified backup.",
        "Read file contents when only asked for allocation statistics.",
        "Recover deleted data from slack space on a disk it does not own or administer."
      ],
      "requires_human": [
        "Reformatting a volume that holds other people's data."
      ]
    },
    "ethics": {
      "considerations": [
        "Data in slack space can expose deleted private files.",
        "Mistakes in disk formatting lose data permanently."
      ],
      "affected_parties": [
        "Data owners",
        "System users"
      ]
    },
    "owners": {
      "steward": "Nobody owns the concept; the owner of each disk answers for it.",
      "master_systems": []
    }
  },
  "sources": [
    {
      "id": "oewn",
      "title": "Open English WordNet 2024, synset oewn-13648413-n",
      "url": "https://en-word.net/id/oewn-13648413-n",
      "what_it_supports": "sense and gloss of the concept",
      "url_status": "live",
      "checked_by": "http 200"
    },
    {
      "id": "wiktionary-en",
      "title": "Wiktionary: allocation unit",
      "url": "https://en.wiktionary.org/wiki/allocation_unit",
      "what_it_supports": "word senses and usage",
      "url_status": "live",
      "checked_by": "http 200"
    }
  ],
  "structure": {
    "bundles": [
      {
        "id": "understand",
        "name": "Understand",
        "description": "What an allocation unit is.",
        "rationale": "Science.",
        "layers": [
          {
            "id": "definition",
            "name": "Definition",
            "description": "Definition.",
            "findings": [
              {
                "id": "definition-finding",
                "name": "Definition",
                "description": "Definition.",
                "questions": [
                  {
                    "text": "What is an allocation unit, and how does it differ from a sector, a partition and a memory block?",
                    "kind": "definition"
                  },
                  {
                    "text": "Is the question about file system allocation or another sense of block or cluster?",
                    "kind": "boundary"
                  }
                ]
              }
            ]
          },
          {
            "id": "sizes",
            "name": "Sizes",
            "description": "Sizes.",
            "findings": [
              {
                "id": "sizes-finding",
                "name": "Sizes",
                "description": "Sizes.",
                "questions": [
                  {
                    "text": "What allocation unit sizes do common file systems use, and how are they chosen?",
                    "kind": "measurement"
                  },
                  {
                    "text": "Which entry fits the specific file system?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "effects",
        "name": "Effects",
        "description": "Effects.",
        "rationale": "Science.",
        "layers": [
          {
            "id": "slack",
            "name": "Slack",
            "description": "Slack space.",
            "findings": [
              {
                "id": "slack-finding",
                "name": "Slack",
                "description": "Slack.",
                "questions": [
                  {
                    "text": "What is slack space, and how much capacity is lost with different unit sizes?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which references are standard?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          },
          {
            "id": "performance",
            "name": "Performance",
            "description": "Performance.",
            "findings": [
              {
                "id": "performance-finding",
                "name": "Performance",
                "description": "Performance.",
                "questions": [
                  {
                    "text": "How do allocation unit size and fragmentation affect performance on disks and SSDs?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which sources are cited?",
                    "kind": "provenance"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "practice",
        "name": "Practice",
        "description": "Practice.",
        "rationale": "Practice.",
        "layers": [
          {
            "id": "formatting",
            "name": "Formatting",
            "description": "Formatting.",
            "findings": [
              {
                "id": "formatting-finding",
                "name": "Formatting",
                "description": "Formatting.",
                "questions": [
                  {
                    "text": "How is the allocation unit size set when formatting a volume, and when should defaults be changed?",
                    "kind": "action"
                  },
                  {
                    "text": "Which entry fits disk formatting?",
                    "kind": "action"
                  }
                ]
              }
            ]
          },
          {
            "id": "forensics",
            "name": "Forensics",
            "description": "Forensics.",
            "findings": [
              {
                "id": "forensics-finding",
                "name": "Forensics",
                "description": "Forensics.",
                "questions": [
                  {
                    "text": "Why does slack space matter in digital forensics and data recovery?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits digital forensics?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      },
      {
        "id": "context",
        "name": "Context",
        "description": "History.",
        "rationale": "Context.",
        "layers": [
          {
            "id": "history",
            "name": "History",
            "description": "History.",
            "findings": [
              {
                "id": "history-finding",
                "name": "History",
                "description": "History.",
                "questions": [
                  {
                    "text": "How did clusters and blocks develop from early file systems to modern ones?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits the history of file systems?",
                    "kind": "action"
                  }
                ]
              }
            ]
          },
          {
            "id": "terms",
            "name": "Terms",
            "description": "Terminology.",
            "findings": [
              {
                "id": "terms-finding",
                "name": "Terms",
                "description": "Terms.",
                "questions": [
                  {
                    "text": "Why do different systems call the unit a cluster, block or allocation unit?",
                    "kind": "provenance"
                  },
                  {
                    "text": "Which entry fits file system terminology?",
                    "kind": "action"
                  }
                ]
              }
            ]
          }
        ]
      }
    ]
  },
  "openQuestions": [
    "Should cluster and block be separate entries?",
    "How should file system documentation be linked?",
    "How should solid-state considerations be recorded?"
  ],
  "statistics": {
    "bundles": 4,
    "layers": 8,
    "findings": 8,
    "questions": 16
  }
}
