{ "model": { "rank": 15705, "code": "thing-q1079196", "model_id": "vr.tr.command", "name": "command", "purpose": "Let an agent explain computer commands and their structure and kinds, support finding and using commands safely, describe shells and command-line conventions, and separate this sense from commands in other contexts.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q1079196/", "tier": 2, "score": 33, "payload": { "layer": "wikidata", "aliases": [ "type command", "CMD.EXE command", "standard UNIX utility or command", "internal command", "directive", "external command", "find", "constant-time instruction", "AI prompt", "cheat code", "Windows Terminal color combination", "type conversion", "subcommand", "user interface command", "commit", "machine instruction", "noclip mode", "xargs", "telecommand", "constraint", "Blind write", "Undo", "browser command", "data export", "data import", "updatedb", "G-code", "file saving", "locate", "yield", "SCSI command", "instruction", "trim command", "GNU Emacs command", "meta refresh", "include directive", "zero-shot prompt", "few-shot prompt", "chain-of-thought prompt", "type cast in Java" ], "aliasCount": 74, "merged": 74, "knownIn": 33, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.command-cognition", "source": { "dataset": "wikidata", "item": "Q1079196", "url": "https://www.wikidata.org/wiki/Q1079196", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T04:08:37Z", "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": 2, "engine": "claude" }, "metaModel": { "id": "THING-Q1079196", "registryId": "vr.tr.command", "name": "command", "version": "0.2.0-wave.2", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1079196/", "model": { "registry_id": "vr.tr.command", "name": "command", "purpose": "Let an agent explain computer commands and their structure and kinds, support finding and using commands safely, describe shells and command-line conventions, and separate this sense from commands in other contexts.", "definition": "An instruction given to a computer program, operating system or device to perform a specific action, typically typed at a command line or issued through a script, including internal commands built into a shell or command interpreter, external commands implemented as separate programs, standard utilities of Unix-like systems, directives in configuration and markup, and commands in applications; commands have names, arguments and options, and their conventions are documented in manuals.", "what_it_is_for": "Instructions to programs and systems.", "affordances": [ "explain structure and kinds", "support finding and using commands", "describe shells and conventions", "separate other senses" ], "distinguishing_features": [ "Named instruction", "Arguments and options", "Internal or external", "Documented conventions" ], "appearance": "Text typed at a prompt or written in scripts.", "visual_identification": [ "Instruction to a program or system", "Name, arguments, options", "A programming statement is part of source code; a military command is an order" ], "physical_properties": [], "families_and_kinds": [ "shell built-in commands", "external commands and utilities", "standard Unix utilities", "directives in configuration and markup", "application and device commands" ], "related_models": [ { "relation": "is a kind of", "target": "command", "why": "category" }, { "relation": "is related to", "target": "free software", "why": "utilities distributed as free software" }, { "relation": "is related to", "target": "microcomputer", "why": "early command-line systems" }, { "relation": "is related to", "target": "software bug", "why": "errors in command use" } ], "identifiers": [], "standards_and_regulation": [ "POSIX and shell standards", "Documentation conventions such as manual pages", "No regulation of the concept" ], "failure_modes_and_hazards": [ "Destructive commands run by mistake", "Confusing commands across systems", "Running untrusted commands" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What commands are.", "rationale": "Computing.", "layers": [ { "id": "structure", "name": "Structure", "description": "Structure and kinds.", "findings": [ { "id": "structure-finding", "name": "Structure", "description": "Structure.", "questions": [ { "text": "How are commands structured with names, arguments and options, and how do internal, external and utility commands differ?", "kind": "definition" }, { "text": "Is a computer command or another sense meant?", "kind": "boundary" } ] } ] }, { "id": "shells", "name": "Shells", "description": "Shells and interpreters.", "findings": [ { "id": "shells-finding", "name": "Shells", "description": "Shells.", "questions": [ { "text": "How do shells and command interpreters such as Unix shells and Windows command processors execute commands?", "kind": "definition" }, { "text": "Which entry fits a specific shell?", "kind": "action" } ] } ] } ] }, { "id": "use", "name": "Use", "description": "Using commands.", "rationale": "Practice.", "layers": [ { "id": "find", "name": "Find", "description": "Finding the right command.", "findings": [ { "id": "find-finding", "name": "Find", "description": "Finding.", "questions": [ { "text": "Which command performs this task on this system, and how is its documentation read?", "kind": "action" }, { "text": "Which entry fits a specific command?", "kind": "action" } ] } ] }, { "id": "safety", "name": "Safety", "description": "Safe use.", "findings": [ { "id": "safety-finding", "name": "Safety", "description": "Safety.", "questions": [ { "text": "How can destructive or untrusted commands be avoided, and what precautions apply?", "kind": "action" }, { "text": "Could this command cause data loss, requiring confirmation?", "kind": "boundary" } ] } ] } ] }, { "id": "script", "name": "Script", "description": "Scripting and automation.", "rationale": "Engineering.", "layers": [ { "id": "scripts", "name": "Scripts", "description": "Scripts.", "findings": [ { "id": "scripts-finding", "name": "Scripts", "description": "Scripts.", "questions": [ { "text": "How are commands combined in scripts, pipelines and automation?", "kind": "action" }, { "text": "Which entry fits shell scripting?", "kind": "action" } ] } ] }, { "id": "portability", "name": "Portability", "description": "Portability.", "findings": [ { "id": "portability-finding", "name": "Portability", "description": "Portability.", "questions": [ { "text": "How do commands differ across operating systems, and how is portability achieved?", "kind": "provenance" }, { "text": "Which entry fits POSIX?", "kind": "action" } ] } ] } ] }, { "id": "learn", "name": "Learn", "description": "History and teaching.", "rationale": "Education.", "layers": [ { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did command-line interfaces develop from early systems to modern shells?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "teach", "name": "Teach", "description": "Teaching.", "findings": [ { "id": "teach-finding", "name": "Teach", "description": "Teaching.", "questions": [ { "text": "How can command-line skills be taught to beginners?", "kind": "action" }, { "text": "Which misconceptions arise?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should shells be a separate entry?", "How should command references be linked?", "How should safety practices be documented?" ], "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 command, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain computer commands and their structure and kinds, support finding and using commands safely, describe shells and command-line conventions, and separate this sense from commands in other contexts.", "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: type command, CMD.EXE command, standard UNIX utility or command, internal command, directive, external command, find, constant-time instruction, AI prompt, cheat code, Windows Terminal color combination, type conversion.", "74 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 33 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 command, 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": [ "type command", "CMD.EXE command", "standard UNIX utility or command", "internal command", "directive", "external command", "find", "constant-time instruction", "AI prompt", "cheat code", "Windows Terminal color combination", "type conversion" ] } ], "standing": "Described in 33 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 74 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 command from another, and a command 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 command, 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 command, 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 command 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 command, 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 command, 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 command 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 command 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 command, 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 command, 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 command 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 command from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a command, 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 command, 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 command 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 command 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 command between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a command, 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 command, 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 command 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 command, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a command 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 command, 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 command, 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 command 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 command 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 command contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a command, 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 command, 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 command 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 command and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a command, 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 command, 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 command 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 command 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 command 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 command 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 command 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 command 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 command, 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 command 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 command and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a command, 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 command, 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 command 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 command is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a command, 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 command, 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 command 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 } } } }