{ "model": { "rank": 12211, "code": "thing-q729138", "model_id": "vr.tr.integer-data-type", "name": "integer data type", "purpose": "Let an agent explain integer data types, relay sizes, ranges, representations and language rules from programming references, describe the types the registry aliases name, and distinguish integer types from floating-point types, mathematical integers, enumerations and exit status as a convention, without exploit detail.", "family": "Thing Registry", "category": "Cross-cutting context", "status": "research-draft", "kind": "thing", "plane": "XCT", "domain": "XCT.QLT", "industry": "", "version": "", "url": "/models/thing/q729138/", "tier": 2, "score": 40, "payload": { "layer": "wikidata", "aliases": [ "exit status", "32-bit integer data type", "128-bit unsigned integer", "128-bit signed integer", "C integer data type", "128-bit unsigned integer data type", "unsigned integer data type", "signed integer data type", "short int", "big integer", "64-bit integer", "32-bit unsigned integer", "64-bit unsigned integer", "16-bit unsigned integer data type", "64-bit signed integer" ], "aliasCount": 15, "merged": 15, "knownIn": 40, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q729138", "url": "https://www.wikidata.org/wiki/Q729138", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T19:22: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" }, "metaModel": { "id": "THING-Q729138", "registryId": "vr.tr.integer-data-type", "name": "integer data type", "version": "0.2.0-wave.4", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.QLT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q729138/", "model": { "registry_id": "vr.tr.integer-data-type", "name": "integer data type", "purpose": "Let an agent explain integer data types, relay sizes, ranges, representations and language rules from programming references, describe the types the registry aliases name, and distinguish integer types from floating-point types, mathematical integers, enumerations and exit status as a convention, without exploit detail.", "definition": "A data type representing a range of whole numbers in computing, defined by size and signedness, such as 8, 16, 32, 64 and 128-bit signed and unsigned integers, with language-specific types such as the C int, long and uint32_t, arbitrary-precision integers in some languages, and uses such as process exit status codes stored as small integers; integer overflow and signedness errors are common sources of bugs and vulnerabilities.", "what_it_is_for": "Representing whole numbers in programs.", "affordances": [ "explain sizes and signedness", "relay language rules", "describe named types", "distinguish related types" ], "distinguishing_features": [ "Fixed width or arbitrary", "Signed or unsigned", "Overflow behaviour", "Language-specific" ], "appearance": "Not a visible object; a type in code.", "visual_identification": [ "Computer type for whole numbers", "32-bit integer, 128-bit signed and unsigned integers, C integer types, exit status", "Floating-point types store approximations; mathematical integers are unbounded; enums name values; exit status is a convention using integers" ], "physical_properties": [ { "quantity": "32-bit signed range", "typical_range": "-2147483648 to 2147483647", "unit": "note", "note": "" }, { "quantity": "64-bit unsigned max", "typical_range": "18446744073709551615", "unit": "note", "note": "" }, { "quantity": "representation", "typical_range": "usually two s complement", "unit": "note", "note": "mandated in C23" } ], "families_and_kinds": [ "fixed-width signed integers", "fixed-width unsigned integers", "128-bit integers", "C and C++ integer types", "arbitrary-precision integers", "exit status codes as an integer use" ], "related_models": [ { "relation": "is a kind of", "target": "number data type", "why": "in registry terms" }, { "relation": "is represented using", "target": "two s complement", "why": "" }, { "relation": "is contrasted with", "target": "floating-point arithmetic", "why": "" }, { "relation": "can suffer", "target": "integer overflow", "why": "" } ], "identifiers": [], "standards_and_regulation": [ "ISO C and C++ standards", "Language specifications such as Java and Rust" ], "failure_modes_and_hazards": [ "Integer overflow bugs and vulnerabilities", "Signedness conversion errors", "Registry alias exit status is a use, not a type" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What an integer data type is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is an integer data type, and how does it differ from floating-point types, mathematical integers, enums and exit status?", "kind": "definition" }, { "text": "Is the question about a language, a size, overflow or security, answered without exploit detail?", "kind": "boundary" } ] } ] }, { "id": "types", "name": "Types", "description": "Named types.", "findings": [ { "id": "types-finding", "name": "Types", "description": "Types.", "questions": [ { "text": "What are 32-bit, 128-bit signed and unsigned and C integer types, and what is an exit status?", "kind": "definition" }, { "text": "Which entry fits the specific type?", "kind": "action" } ] } ] } ] }, { "id": "representation", "name": "Representation", "description": "Representation.", "rationale": "Science.", "layers": [ { "id": "binary", "name": "Binary", "description": "Binary representation.", "findings": [ { "id": "binary-finding", "name": "Binary", "description": "Binary.", "questions": [ { "text": "How are integers represented with two s complement and endianness?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "ranges", "name": "Ranges", "description": "Ranges.", "findings": [ { "id": "ranges-finding", "name": "Ranges", "description": "Ranges.", "questions": [ { "text": "How are ranges computed from bit width and signedness?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] } ] }, { "id": "practice", "name": "Practice", "description": "Practice.", "rationale": "Application.", "layers": [ { "id": "languages", "name": "Languages", "description": "Languages.", "findings": [ { "id": "languages-finding", "name": "Languages", "description": "Languages.", "questions": [ { "text": "How do C, Java, Python and Rust define integer types?", "kind": "provenance" }, { "text": "Which entry fits C data types?", "kind": "action" } ] } ] }, { "id": "bugs", "name": "Bugs", "description": "Overflow and safety.", "findings": [ { "id": "bugs-finding", "name": "Bugs", "description": "Bugs.", "questions": [ { "text": "Why do integer overflows cause bugs, and how do languages mitigate them, at a general level?", "kind": "provenance" }, { "text": "Which entry fits integer overflow?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "Conventions and history.", "rationale": "Context.", "layers": [ { "id": "exit", "name": "Exit status", "description": "Exit status.", "findings": [ { "id": "exit-finding", "name": "Exit status", "description": "Exit status.", "questions": [ { "text": "What are process exit status codes and their conventions?", "kind": "provenance" }, { "text": "Which entry fits exit status?", "kind": "action" } ] } ] }, { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did word sizes evolve from 8-bit to 64-bit computers?", "kind": "provenance" }, { "text": "Which entry fits word (computer architecture)?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should 128-bit integer be a separate entry?", "How should programming references be linked?", "The registry alias exit status names a convention; should it be split off?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 integer data type, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain integer data types, relay sizes, ranges, representations and language rules from programming references, describe the types the registry aliases name, and distinguish integer types from floating-point types, mathematical integers, enumerations and exit status as a convention, without exploit detail.", "characteristics": { "substance": "abstract", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: exit status, 32-bit integer data type, 128-bit unsigned integer, 128-bit signed integer, C integer data type, 128-bit unsigned integer data type, unsigned integer data type, signed integer data type, short int, big integer, 64-bit integer, 32-bit unsigned integer.", "15 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 40 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 integer data type, and on what evidence are they told apart?" ], "whatItIsMadeOf": "an abstraction with no physical instance", "physicalCharacter": [ "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": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "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": [ "exit status", "32-bit integer data type", "128-bit unsigned integer", "128-bit signed integer", "C integer data type", "128-bit unsigned integer data type", "unsigned integer data type", "signed integer data type", "short int", "big integer", "64-bit integer", "32-bit unsigned integer" ] } ], "standing": "Described in 40 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 15 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 integer data type from another, and a integer data type 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 integer data type, 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 integer data type, 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 integer data type 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 integer data type, 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 integer data type, 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 integer data type 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 integer data type 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 integer data type, 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 integer data type, 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 integer data type 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 integer data type from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a integer data type, 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 integer data type, 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 integer data type 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 integer data type 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 integer data type between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a integer data type, 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 integer data type, 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 integer data type 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 integer data type, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a integer data type 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 integer data type, 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 integer data type, 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 integer data type is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What integer data type is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of integer data type are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is integer data type operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of integer data type and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of integer data type?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as integer data type?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a integer data type 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 integer data type and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a integer data type, 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 integer data type, 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 integer data type 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 integer data type is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a integer data type, 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 integer data type, 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 integer data type is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 5, "layers": 10, "findings": 12, "questions": 32 } } } }