{ "model": { "rank": 996, "code": "thing-q21198", "model_id": "vr.tr.computer-science", "name": "computer science", "purpose": "Let an agent handle computer science as a discipline with fields, methods and ethics, and separate established results from hype.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q21198/", "tier": 2, "score": 204, "payload": { "layer": "wikidata", "aliases": [ "virtual influencer", "distributed social network", "data management and data science", "music informatics", "computational sustainability", "theoretical computer science", "human–computer interaction", "genome informatics", "video game science", "volunteer computing", "security engineering", "forensic software engineering", "personalization", "human-machine relationship", "baby duck syndrome", "Usable security", "human–computer match", "Relational Co-Authorship (RCA) Method", "Human-AI Relationality (HAIR)", "digital stress threshold", "cognitive friction", "human-AI interaction", "human–computer interaction in security", "gender HCI", "3D interaction", "3D user interaction", "feminist HCI", "mobile interaction", "non-speech audio input", "multimodal interaction", "usable privacy and security", "Māori computing technology use and design", "split-and-stitch video encoding", "distributed computing", "mechatronics", "cybersecurity engineering", "Privacy engineering", "fallback level", "model-driven engineering", "software engineering" ], "aliasCount": 133, "merged": 133, "knownIn": 204, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q21198", "url": "https://www.wikidata.org/wiki/Q21198", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T06:31:18Z", "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-Q21198", "registryId": "vr.tr.computer-science", "name": "computer science", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q21198/", "model": { "registry_id": "vr.tr.computer-science", "name": "computer science", "purpose": "Let an agent handle computer science as a discipline with fields, methods and ethics, and separate established results from hype.", "definition": "The study of computation, information and automation, including algorithms, programming languages, systems, data, artificial intelligence and theory.", "what_it_is_for": "Understanding and building computational systems.", "affordances": [ "study and teach it", "design algorithms and systems", "research AI and data", "assess societal impacts" ], "distinguishing_features": [ "Formal and engineering discipline", "Theory and practice", "Rapidly changing", "Ethical and security dimensions" ], "appearance": "Code, algorithms, systems and papers.", "visual_identification": [ "Fields such as theory, systems, AI", "ACM classifications", "Applied areas such as music informatics" ], "physical_properties": [], "families_and_kinds": [ "theoretical computer science", "systems and networks", "artificial intelligence and machine learning", "data management and data science", "human-computer interaction", "applied informatics" ], "related_models": [ { "relation": "is a kind of", "target": "formal science", "why": "discipline" }, { "relation": "produces", "target": "computer program", "why": "artefacts" }, { "relation": "uses", "target": "mathematics", "why": "foundations" }, { "relation": "studies", "target": "data and computation", "why": "subjects" } ], "identifiers": [ { "scheme": "ACM CCS code", "value_or_pattern": "classification", "note": "ACM Computing Classification System" } ], "standards_and_regulation": [ "EU AI Act", "Data protection law", "Computing ethics codes such as the ACM Code of Ethics" ], "failure_modes_and_hazards": [ "Hype presented as fact", "Security vulnerabilities", "Biased systems" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "field", "name": "Field", "description": "Which area.", "rationale": "Field locates the question.", "layers": [ { "id": "area", "name": "Area", "description": "Sub-discipline.", "findings": [ { "id": "area-finding", "name": "Area", "description": "Field.", "questions": [ { "text": "Which area of computer science applies?", "kind": "definition" }, { "text": "Which ACM class?", "kind": "provenance" } ] } ] }, { "id": "methods", "name": "Methods", "description": "Theory and experiment.", "findings": [ { "id": "methods-finding", "name": "Methods", "description": "Methods.", "questions": [ { "text": "Which methods are used?", "kind": "definition" }, { "text": "How are results validated?", "kind": "provenance" } ] } ] } ] }, { "id": "results", "name": "Results", "description": "What is known.", "rationale": "Results vary in maturity.", "layers": [ { "id": "established", "name": "Established", "description": "Proven results.", "findings": [ { "id": "established-finding", "name": "Established", "description": "Established knowledge.", "questions": [ { "text": "Is this an established result or a claim?", "kind": "boundary" }, { "text": "Which sources support it?", "kind": "provenance" } ] } ] }, { "id": "open", "name": "Open problems", "description": "Unsolved.", "findings": [ { "id": "open-finding", "name": "Open problems", "description": "Open problems.", "questions": [ { "text": "Which related problems are open?", "kind": "boundary" }, { "text": "What progress has been made?", "kind": "provenance" } ] } ] } ] }, { "id": "practice", "name": "Practice", "description": "Building systems.", "rationale": "Practice has standards.", "layers": [ { "id": "engineering", "name": "Engineering", "description": "Software and systems.", "findings": [ { "id": "engineering-finding", "name": "Engineering", "description": "Engineering practice.", "questions": [ { "text": "Which engineering practices apply?", "kind": "provenance" }, { "text": "How is quality assured?", "kind": "action" } ] } ] }, { "id": "security", "name": "Security", "description": "Safety.", "findings": [ { "id": "security-finding", "name": "Security", "description": "Security.", "questions": [ { "text": "What security risks arise?", "kind": "boundary" }, { "text": "How are they mitigated?", "kind": "action" } ] } ] } ] }, { "id": "ethics", "name": "Ethics", "description": "Impacts.", "rationale": "Computing affects society.", "layers": [ { "id": "impact", "name": "Impact", "description": "Society.", "findings": [ { "id": "impact-finding", "name": "Impact", "description": "Societal impact.", "questions": [ { "text": "What societal impacts does this have?", "kind": "boundary" }, { "text": "Who is affected?", "kind": "boundary" } ] } ] }, { "id": "regulation", "name": "Regulation", "description": "Law.", "findings": [ { "id": "regulation-finding", "name": "Regulation", "description": "Applicable law.", "questions": [ { "text": "Which laws apply, such as the AI Act?", "kind": "provenance" }, { "text": "What obligations follow?", "kind": "boundary" } ] } ] } ] } ] }, "openQuestions": [ "Should fields be separate entries?", "How should agents present AI capabilities honestly?", "The registry entry has merged aliases such as virtual influencer; should they 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 computer science, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent handle computer science as a discipline with fields, methods and ethics, and separate established results from hype.", "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: virtual influencer, distributed social network, data management and data science, music informatics, computational sustainability, theoretical computer science, human–computer interaction, genome informatics, video game science, volunteer computing, security engineering, forensic software engineering.", "133 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 204 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 computer science, 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": [ "virtual influencer", "distributed social network", "data management and data science", "music informatics", "computational sustainability", "theoretical computer science", "human–computer interaction", "genome informatics", "video game science", "volunteer computing", "security engineering", "forensic software engineering" ] } ], "standing": "Described in 204 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 133 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 computer science from another, and a computer science 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 computer science, 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 computer science, 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 computer science 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 computer science, 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 computer science, 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 computer science 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 computer science 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 computer science, 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 computer science, 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 computer science 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 computer science from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a computer science, 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 computer science, 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 computer science 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 computer science 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 computer science between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a computer science, 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 computer science, 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 computer science 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 computer science, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a computer science 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 computer science, 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 computer science, 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 computer science 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 computer science 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 computer science contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a computer science, 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 computer science, 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 computer science 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 computer science and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a computer science, 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 computer science, 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 computer science 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 computer science 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 computer science 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 computer science 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 computer science 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 computer science 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 computer science, 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 computer science 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 computer science and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a computer science, 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 computer science, 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 computer science 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 computer science is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a computer science, 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 computer science, 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 computer science 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 } } } }