{ "model": { "rank": 3828, "code": "thing-q175263", "model_id": "vr.tr.data-structure", "name": "data structure", "purpose": "Let an agent handle data structures by type, operations, complexity and use cases.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q175263/", "tier": 2, "score": 81, "payload": { "layer": "wikidata", "aliases": [ "codebook", "word net", "semantic network", "definitional network", "assertional network", "person-persistent data", "bit array", "array data structure", "system image", "virtual object", "data frame", "continuation", "process control block", "map", "page table", "circular buffer", "probabilistic data structure", "Python tuple", "index structure", "Iliffe vector", "implicit data structure", "hash tree", "device tree", "Retroactive data structures", "symbol table", "feature data", "conflict-free replicated data type", "triangulated irregular network", "persistent data structure", "intermediate representation", "graph data structure", "User Electronic Signature", "Conc-Tree list", "Judy array", "purely functional data structure", "Linear Data Set", "Thread control block", "Bridge Protocol Data Units", "passive data structure", "bidirectional map" ], "aliasCount": 117, "merged": 117, "knownIn": 81, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q175263", "url": "https://www.wikidata.org/wiki/Q175263", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T07:34:04Z", "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": 1, "engine": "claude" }, "metaModel": { "id": "THING-Q175263", "registryId": "vr.tr.data-structure", "name": "data structure", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q175263/", "model": { "registry_id": "vr.tr.data-structure", "name": "data structure", "purpose": "Let an agent handle data structures by type, operations, complexity and use cases.", "definition": "A way of organising and storing data in a computer so it can be accessed and modified efficiently, such as arrays, linked lists, trees, graphs, hash tables and semantic networks.", "what_it_is_for": "Efficient storage and retrieval of data in software.", "affordances": [ "choose a structure for a task", "implement and test it", "analyse operation complexity", "serialise and persist it" ], "distinguishing_features": [ "Organises data for operations", "Trade-offs in time and memory", "Abstract data types versus implementations", "Language-independent" ], "appearance": "Diagrams of nodes and links, tables and code.", "visual_identification": [ "Names such as tree, heap, hash table", "Operation complexity tables", "Semantic networks are knowledge structures" ], "physical_properties": [], "families_and_kinds": [ "linear structures: arrays, lists, stacks, queues", "trees and heaps", "hash tables", "graphs and networks", "persistent and concurrent structures" ], "related_models": [ { "relation": "is a kind of", "target": "software component and structure", "why": "category" }, { "relation": "is used by", "target": "algorithm", "why": "counterpart" }, { "relation": "is studied in", "target": "computer science", "why": "field" }, { "relation": "implements", "target": "abstract data type", "why": "concept" } ], "identifiers": [], "standards_and_regulation": [], "failure_modes_and_hazards": [ "Wrong structure causing slow performance", "Memory leaks", "Concurrency bugs" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "type", "name": "Type", "description": "Which structure.", "rationale": "Type decides operations.", "layers": [ { "id": "kind", "name": "Kind", "description": "Array, tree, graph.", "findings": [ { "id": "kind-finding", "name": "Kind", "description": "Structure type.", "questions": [ { "text": "Which data structure is it?", "kind": "definition" }, { "text": "Which abstract data type does it implement?", "kind": "definition" } ] } ] }, { "id": "operations", "name": "Operations", "description": "Supported operations.", "findings": [ { "id": "operations-finding", "name": "Operations", "description": "Operations.", "questions": [ { "text": "Which operations does it support?", "kind": "definition" }, { "text": "At what cost?", "kind": "measurement" } ] } ] } ] }, { "id": "performance", "name": "Performance", "description": "Complexity.", "rationale": "Complexity guides choice.", "layers": [ { "id": "complexity", "name": "Complexity", "description": "Big O.", "findings": [ { "id": "complexity-finding", "name": "Complexity", "description": "Complexity.", "questions": [ { "text": "What are the time and space complexities?", "kind": "measurement" }, { "text": "Average or worst case?", "kind": "definition" } ] } ] }, { "id": "practice", "name": "Practice", "description": "Benchmarks.", "findings": [ { "id": "practice-finding", "name": "Practice", "description": "Real performance.", "questions": [ { "text": "How does it perform on real data?", "kind": "measurement" }, { "text": "What about cache behaviour?", "kind": "boundary" } ] } ] } ] }, { "id": "choice", "name": "Choice", "description": "Selecting a structure.", "rationale": "The task decides.", "layers": [ { "id": "fit", "name": "Fit", "description": "Use case.", "findings": [ { "id": "fit-finding", "name": "Fit", "description": "Fit for task.", "questions": [ { "text": "Which structure suits this access pattern?", "kind": "action" }, { "text": "What are the trade-offs?", "kind": "boundary" } ] } ] }, { "id": "libraries", "name": "Libraries", "description": "Implementations.", "findings": [ { "id": "libraries-finding", "name": "Libraries", "description": "Libraries.", "questions": [ { "text": "Is there a well-tested library implementation?", "kind": "provenance" }, { "text": "In which language?", "kind": "definition" } ] } ] } ] }, { "id": "correctness", "name": "Correctness", "description": "Bugs.", "rationale": "Structures must be correct.", "layers": [ { "id": "invariants", "name": "Invariants", "description": "Rules.", "findings": [ { "id": "invariants-finding", "name": "Invariants", "description": "Invariants.", "questions": [ { "text": "What invariants must the structure maintain?", "kind": "definition" }, { "text": "How are they tested?", "kind": "provenance" } ] } ] }, { "id": "concurrency", "name": "Concurrency", "description": "Threads.", "findings": [ { "id": "concurrency-finding", "name": "Concurrency", "description": "Concurrency.", "questions": [ { "text": "Is it safe for concurrent use?", "kind": "boundary" }, { "text": "How is access synchronised?", "kind": "definition" } ] } ] } ] } ] }, "openQuestions": [ "Should each structure be a separate entry?", "How should complexity be recorded?", "How should knowledge structures be split off?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "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 data structure, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent handle data structures by type, operations, complexity and use cases.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: codebook, word net, semantic network, definitional network, assertional network, person-persistent data, bit array, array data structure, system image, virtual object, data frame, continuation.", "117 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 81 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 data structure, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "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": [ "read it and act on what it says" ], "howItIsRecognised": [], "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": [ "codebook", "word net", "semantic network", "definitional network", "assertional network", "person-persistent data", "bit array", "array data structure", "system image", "virtual object", "data frame", "continuation" ] } ], "standing": "Described in 81 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 117 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 data structure from another, and a data structure 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 data structure, 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 data structure, 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 data structure 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 data structure, 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 data structure, 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 data structure 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 data structure 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 data structure, 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 data structure, 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 data structure 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 data structure from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a data structure, 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 data structure, 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 data structure 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 data structure 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 data structure between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a data structure, 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 data structure, 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 data structure 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 data structure, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a data structure 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 data structure, 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 data structure, 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 data structure is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a data structure says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a data structure contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a data structure, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a data structure, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a data structure is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a data structure and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a data structure, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a data structure, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a data structure is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What data structure studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does data structure take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does data structure establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where data structure is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark data structure as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place data structure, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a data structure 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 data structure and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a data structure, 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 data structure, 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 data structure 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 data structure is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a data structure, 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 data structure, 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 data structure is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }