{ "model": { "rank": 3720, "code": "thing-q179310", "model_id": "vr.tr.computing", "name": "computing", "purpose": "Let an agent explain computing as an activity and discipline, describe its branches, paradigms and history, relay professional and educational frameworks, and route to entries for specific technologies and fields.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q179310/", "tier": 2, "score": 82, "payload": { "layer": "wikidata", "aliases": [ "retrocomputing", "cash cow legacy software", "remote access", "tuple relational calculus", "thermodynamic computing", "pen computing", "Connected Device Configuration", "computing by natural language", "high-performance computing", "decompilation", "human-centered computing", "voice recognition technology", "relational calculus", "bio-inspired computing", "DNA computing", "reversible computing", "neuromorphic engineering", "automatic content recognition", "fog computing", "grid computing", "mobile computing", "Indic computing", "real-time computing", "centralized computing", "legacy system", "development informatics", "domain relational calculus", "ubiquitous computing", "load balancing", "Voice computing", "social computing", "batch processing", "Medical image computing", "metacomputing", "soft computing", "technical computing", "Urban computing", "spatial computing", "DNS lookups", "Trusted Computing" ], "aliasCount": 47, "merged": 47, "knownIn": 82, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q179310", "url": "https://www.wikidata.org/wiki/Q179310", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T01:17:34Z", "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" }, "metaModel": { "id": "THING-Q179310", "registryId": "vr.tr.computing", "name": "computing", "version": "0.2.0-wave.3", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q179310/", "model": { "registry_id": "vr.tr.computing", "name": "computing", "purpose": "Let an agent explain computing as an activity and discipline, describe its branches, paradigms and history, relay professional and educational frameworks, and route to entries for specific technologies and fields.", "definition": "The activity of using, developing and studying computers and computation, spanning hardware, software, networks and data, from mainframe and personal computing to mobile, cloud, pen and remote computing, historical practice preserved as retrocomputing, and theoretical foundations such as relational calculus and emerging paradigms such as thermodynamic computing; computing is both a professional discipline covered by bodies such as the ACM and an everyday activity across society.", "what_it_is_for": "Processing information by machine.", "affordances": [ "explain the activity and discipline", "describe branches and paradigms", "relay professional frameworks", "route to specific fields" ], "distinguishing_features": [ "Machine information processing", "Discipline and everyday activity", "Rapid paradigm change", "Professional bodies" ], "appearance": "Not a visible object; people using computers and the systems they build.", "visual_identification": [ "Use and study of computers and computation", "Hardware, software, networks, data, theory, applications", "Computer science is the theoretical core; information technology is the applied service side; mathematics is the foundation" ], "physical_properties": [ { "quantity": "internet users", "typical_range": "about 5.5 billion", "unit": "people", "note": "ITU estimates" } ], "families_and_kinds": [ "computer science and theory including relational calculus", "software engineering and programming", "computer engineering and hardware", "information technology, networks and remote access", "paradigms such as personal, mobile, cloud, pen and thermodynamic computing", "retrocomputing and legacy software", "computing in society and education" ], "related_models": [ { "relation": "is a kind of", "target": "information and communications technology", "why": "in registry terms" }, { "relation": "is a kind of", "target": "activity", "why": "in registry terms" }, { "relation": "is studied by", "target": "computer science", "why": "the core discipline" }, { "relation": "is performed with", "target": "computer", "why": "the machine" } ], "identifiers": [ { "scheme": "ACM CCS", "value_or_pattern": "classification", "note": "Computing Classification System" } ], "standards_and_regulation": [ "ACM and IEEE curricula and codes of ethics", "ISO/IEC information technology standards", "Data protection, cybersecurity and accessibility laws" ], "failure_modes_and_hazards": [ "Security breaches and failures", "Obsolescence and legacy dependence", "Confusing computing with computer science or IT", "Digital divides" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What computing is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition and scope.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is computing, and how does it relate to computer science, IT and engineering?", "kind": "definition" }, { "text": "Is the question about computing broadly or a specific field or technology?", "kind": "boundary" } ] } ] }, { "id": "branches", "name": "Branches", "description": "Branches.", "findings": [ { "id": "branches-finding", "name": "Branches", "description": "Branches.", "questions": [ { "text": "What are the main branches of computing, per classification schemes such as the ACM CCS?", "kind": "definition" }, { "text": "Which entry fits the specific branch?", "kind": "action" } ] } ] } ] }, { "id": "paradigms", "name": "Paradigms", "description": "Paradigms and history.", "rationale": "Context.", "layers": [ { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did computing develop from mechanical calculators through mainframes and personal computers to mobile and cloud?", "kind": "provenance" }, { "text": "Which entry fits the history of computing?", "kind": "action" } ] } ] }, { "id": "emerging", "name": "Emerging", "description": "Emerging paradigms.", "findings": [ { "id": "emerging-finding", "name": "Emerging", "description": "Emerging.", "questions": [ { "text": "What are quantum, neuromorphic and thermodynamic computing, and how established are they, with claims attributed?", "kind": "provenance" }, { "text": "Is the presentation clear about maturity?", "kind": "boundary" } ] } ] } ] }, { "id": "profession", "name": "Profession", "description": "Profession and education.", "rationale": "Regulation.", "layers": [ { "id": "profession", "name": "Profession", "description": "Profession.", "findings": [ { "id": "profession-finding", "name": "Profession", "description": "Profession.", "questions": [ { "text": "How is computing organised as a profession, with bodies, ethics codes and certifications?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "education", "name": "Education", "description": "Education.", "findings": [ { "id": "education-finding", "name": "Education", "description": "Education.", "questions": [ { "text": "How is computing taught, from school to university curricula?", "kind": "provenance" }, { "text": "Which entry fits computing education?", "kind": "action" } ] } ] } ] }, { "id": "society", "name": "Society", "description": "Society and legacy.", "rationale": "Attribution.", "layers": [ { "id": "impact", "name": "Impact", "description": "Social impact.", "findings": [ { "id": "impact-finding", "name": "Impact", "description": "Impact.", "questions": [ { "text": "What do studies say about computing impacts on work, privacy and society, with positions attributed?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] }, { "id": "legacy", "name": "Legacy", "description": "Legacy and retrocomputing.", "findings": [ { "id": "legacy-finding", "name": "Legacy", "description": "Legacy.", "questions": [ { "text": "How are legacy systems maintained, and what is retrocomputing?", "kind": "provenance" }, { "text": "Which entry fits retrocomputing?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should computer science and information technology be the primary linked entries?", "How should classification schemes be linked?", "The registry entry has merged aliases naming unrelated specific topics; 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": "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 computing, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain computing as an activity and discipline, describe its branches, paradigms and history, relay professional and educational frameworks, and route to entries for specific technologies and fields.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: retrocomputing, cash cow legacy software, remote access, tuple relational calculus, thermodynamic computing, pen computing, Connected Device Configuration, computing by natural language, high-performance computing, decompilation, human-centered computing, voice recognition technology.", "47 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 82 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 computing, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "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": [ "retrocomputing", "cash cow legacy software", "remote access", "tuple relational calculus", "thermodynamic computing", "pen computing", "Connected Device Configuration", "computing by natural language", "high-performance computing", "decompilation", "human-centered computing", "voice recognition technology" ] } ], "standing": "Described in 82 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 47 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 computing from another, and a computing 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 computing, 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 computing, 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 computing 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 computing, 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 computing, 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 computing 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 computing 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 computing, 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 computing, 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 computing 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 computing from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a computing, 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 computing, 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 computing 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 computing 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 computing between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a computing, 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 computing, 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 computing 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 computing, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a computing 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 computing, 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 computing, 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 computing is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a computing proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a computing, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a computing and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a computing, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a computing, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a computing is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a computing consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a computing takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a computing, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a computing, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a computing 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 computing 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 computing 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 computing 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 computing 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 computing?", "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 computing?", "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 computing 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 computing and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a computing, 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 computing, 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 computing 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 computing is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a computing, 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 computing, 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 computing 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 } } } }