{ "model": { "rank": 4002, "code": "thing-q782543", "model_id": "vr.tr.graphical-user-interface", "name": "graphical user interface", "purpose": "Let an agent explain graphical user interfaces and their elements, relay history, design principles and patterns from human-computer interaction sources, describe windowing systems and toolkits, and distinguish GUIs from command-line, voice and touch interfaces.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q782543/", "tier": 2, "score": 79, "payload": { "layer": "wikidata", "aliases": [ "GNU Emacs user interface", "tabbed browsing", "windowing system", "single document interface", "Synaptic Package Manager", "TkRev", "Workplace Shell", "Immediate Mode GUI", "Windows shell", "multiple document interface" ], "aliasCount": 10, "merged": 10, "knownIn": 79, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q782543", "url": "https://www.wikidata.org/wiki/Q782543", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T04:27:06Z", "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-Q782543", "registryId": "vr.tr.graphical-user-interface", "name": "graphical user interface", "version": "0.2.0-wave.3", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q782543/", "model": { "registry_id": "vr.tr.graphical-user-interface", "name": "graphical user interface", "purpose": "Let an agent explain graphical user interfaces and their elements, relay history, design principles and patterns from human-computer interaction sources, describe windowing systems and toolkits, and distinguish GUIs from command-line, voice and touch interfaces.", "definition": "A form of user interface that lets people interact with computers and devices through visual elements such as windows, icons, menus, buttons and pointers rather than text commands, provided by windowing systems and desktop environments, with patterns such as single and multiple document interfaces and tabbed browsing, and implemented in applications from package managers such as Synaptic to editors such as GNU Emacs and version control tools; graphical user interfaces became dominant with the Macintosh and Windows and now extend to touch and mobile interfaces.", "what_it_is_for": "Interacting with computers visually.", "affordances": [ "explain elements and patterns", "relay history and principles", "describe windowing systems and toolkits", "distinguish from other interfaces" ], "distinguishing_features": [ "WIMP paradigm", "Direct manipulation", "Windowing systems", "Design patterns" ], "appearance": "Windows, icons, menus and pointers on a screen.", "visual_identification": [ "Visual computer interface", "Windowing systems, desktop environments, SDI and tabbed interfaces; applications such as Synaptic, Emacs GUI, TkRev", "Command-line interfaces use text; touch interfaces extend GUIs; voice interfaces use speech" ], "physical_properties": [ { "quantity": "Xerox Alto", "typical_range": "1973", "unit": "year", "note": "first GUI workstation" }, { "quantity": "Macintosh", "typical_range": "1984", "unit": "year", "note": "mass-market GUI" }, { "quantity": "Windows 1.0", "typical_range": "1985", "unit": "year", "note": "" } ], "families_and_kinds": [ "desktop GUIs with windowing systems such as X11, Wayland, Windows and macOS", "desktop environments and window managers", "application patterns such as single document interface, multiple document interface and tabbed browsing", "toolkits such as GTK, Qt and Tk", "application GUIs such as Synaptic Package Manager, GNU Emacs GUI and TkRev", "touch and mobile GUIs" ], "related_models": [ { "relation": "is a kind of", "target": "user interface", "why": "in registry terms" }, { "relation": "is provided by", "target": "windowing system", "why": "and desktop environments" }, { "relation": "is contrasted with", "target": "command-line interface", "why": "using text" }, { "relation": "is designed by", "target": "human-computer interaction", "why": "principles" } ], "identifiers": [], "standards_and_regulation": [ "Accessibility standards such as WCAG and platform accessibility guidelines", "Platform human interface guidelines", "ISO 9241 ergonomics of human-system interaction" ], "failure_modes_and_hazards": [ "Inaccessible interfaces", "Inconsistent design", "Dark patterns", "Registry aliases naming specific applications" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What a GUI is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition and elements.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is a graphical user interface, and what are windows, icons, menus, pointers and widgets?", "kind": "definition" }, { "text": "Is the question about GUIs in general, a windowing system, a pattern or a specific application?", "kind": "boundary" } ] } ] }, { "id": "patterns", "name": "Patterns", "description": "Patterns.", "findings": [ { "id": "patterns-finding", "name": "Patterns", "description": "Patterns.", "questions": [ { "text": "What are single and multiple document interfaces, tabbed browsing and other GUI patterns?", "kind": "definition" }, { "text": "Which entry fits the specific pattern?", "kind": "action" } ] } ] } ] }, { "id": "build", "name": "Build", "description": "Systems and toolkits.", "rationale": "Practice.", "layers": [ { "id": "systems", "name": "Systems", "description": "Windowing systems.", "findings": [ { "id": "systems-finding", "name": "Systems", "description": "Systems.", "questions": [ { "text": "How do windowing systems such as X11, Wayland and the Windows and macOS systems work?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "toolkits", "name": "Toolkits", "description": "Toolkits and applications.", "findings": [ { "id": "toolkits-finding", "name": "Toolkits", "description": "Toolkits.", "questions": [ { "text": "How do toolkits such as GTK, Qt and Tk build GUIs for applications such as Synaptic, Emacs and TkRev?", "kind": "provenance" }, { "text": "Which entry fits the specific toolkit?", "kind": "action" } ] } ] } ] }, { "id": "design", "name": "Design", "description": "Design and accessibility.", "rationale": "Regulation.", "layers": [ { "id": "principles", "name": "Principles", "description": "Design principles.", "findings": [ { "id": "principles-finding", "name": "Principles", "description": "Principles.", "questions": [ { "text": "What principles from HCI and platform guidelines make GUIs usable?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] }, { "id": "accessibility", "name": "Accessibility", "description": "Accessibility.", "findings": [ { "id": "accessibility-finding", "name": "Accessibility", "description": "Accessibility.", "questions": [ { "text": "How are GUIs made accessible under WCAG and platform guidelines?", "kind": "provenance" }, { "text": "Which entry fits computer accessibility?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "History and future.", "rationale": "Context.", "layers": [ { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did GUIs develop from Sketchpad and Xerox PARC to the Macintosh, Windows and mobile interfaces?", "kind": "provenance" }, { "text": "Which entry fits the history of the graphical user interface?", "kind": "action" } ] } ] }, { "id": "future", "name": "Future", "description": "Beyond WIMP.", "findings": [ { "id": "future-finding", "name": "Future", "description": "Future.", "questions": [ { "text": "How are touch, voice, gesture and spatial interfaces extending or replacing GUIs?", "kind": "provenance" }, { "text": "Which entry fits natural user interface?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should windowing system and tabbed browsing be separate primary entries?", "How should HCI sources be linked?", "The registry entry has merged aliases naming specific applications; 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": "work, medium or creative form", "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 graphical user interface, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain graphical user interfaces and their elements, relay history, design principles and patterns from human-computer interaction sources, describe windowing systems and toolkits, and distinguish GUIs from command-line, voice and touch interfaces.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: GNU Emacs user interface, tabbed browsing, windowing system, single document interface, Synaptic Package Manager, TkRev, Workplace Shell, Immediate Mode GUI, Windows shell, multiple document interface.", "10 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 79 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 graphical user interface, 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", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "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": [ "GNU Emacs user interface", "tabbed browsing", "windowing system", "single document interface", "Synaptic Package Manager", "TkRev", "Workplace Shell", "Immediate Mode GUI", "Windows shell", "multiple document interface" ] } ], "standing": "Described in 79 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 10 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 graphical user interface from another, and a graphical user interface 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 graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface 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 graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface 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 graphical user interface between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a graphical user interface 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 graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface 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 graphical user interface contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a graphical user interface, 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 graphical user interface, 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 graphical user interface is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of graphical user interface a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For graphical user interface, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of graphical user interface exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made graphical user interface and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to graphical user interface, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in graphical user interface, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a graphical user interface 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 graphical user interface and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a graphical user interface, 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 graphical user interface, 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 graphical user interface 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 graphical user interface is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a graphical user interface, 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 graphical user interface, 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 graphical user interface 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 } } } }