{ "model": { "rank": 5003, "code": "thing-q190637", "model_id": "vr.tr.web-design", "name": "web design", "purpose": "Enable an AI agent to recognise a web design activity, assess how well its decisions support intended users and tasks, and identify justified changes or unresolved constraints.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q190637/", "tier": 2, "score": 71, "payload": { "layer": "wikidata", "aliases": [ "responsive web design" ], "aliasCount": 1, "merged": 1, "knownIn": 71, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q190637", "url": "https://www.wikidata.org/wiki/Q190637", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:27:33Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08810-ad44-7763-a4f1-7b8450377e6a\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: web design\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 64.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08810-ad47-7ec2-bbf6-7ab2bf8f6bd9\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: web design\nRegistry id: vr.tr.web-design\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q190637", "registryId": "vr.tr.web-design", "name": "web design", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q190637/", "model": { "registry_id": "vr.tr.web-design", "name": "web design", "purpose": "Enable an AI agent to recognise a web design activity, assess how well its decisions support intended users and tasks, and identify justified changes or unresolved constraints.", "definition": "Web design is the activity of planning and specifying the content organisation, visual presentation and interactive behaviour of websites and web interfaces to support their users' tasks.", "scope_statement": "This model owns web design as the activity of shaping a website's information, visual presentation, interaction and adaptation across browsing contexts, including the design artefacts and evidence used to judge those decisions.", "in_scope": [ "Website purposes, intended audiences, user tasks and design constraints", "Content organisation, page relationships, navigation and wayfinding", "Visual hierarchy, typography, layout and reusable interface patterns", "Interactive behaviours, feedback and journeys across pages or interface states", "Responsive and accessible presentation across devices and input methods", "Design validation, revision and correspondence between intended and delivered experiences" ], "out_of_scope": [ "Backend architecture, database design and server operation", "General software implementation except where it constrains or realises design decisions", "Brand strategy and identity creation beyond their application to web interfaces", "Editorial production and factual verification of website content", "Search marketing, advertising campaigns and commercial strategy", "Native application design except for explicitly shared interface conventions" ], "distinguishing_features": [ "The activity makes decisions about an experience delivered through web pages or browser-based interfaces; a standalone poster or native application screen does not establish this scope.", "Its outputs specify how people encounter, understand or act on web content; code that only changes server processing is insufficient.", "It addresses linked pages or interactive states and browsing conditions, rather than treating appearance as a single fixed composition.", "It translates user tasks and content needs into interface decisions; an organisation-wide customer journey study alone belongs to a broader experience-design model.", "It can exist before implementation as wireframes, prototypes or specifications, but its decisions must be assessable against an intended web experience." ], "characteristics": [ { "name": "Design target", "kind": "category", "unit_or_values": "Informational site, publication, storefront, service portal, web application, mixed, or explicitly described other", "why_it_matters": "Different targets require different navigation, content and interaction priorities." }, { "name": "Supported user tasks", "kind": "relation", "unit_or_values": "Links from identified user groups and tasks to relevant pages, journeys and success criteria", "why_it_matters": "Makes the purpose of a design decision traceable to something a person needs to accomplish." }, { "name": "Content and navigation structure", "kind": "relation", "unit_or_values": "Relationships among content types, pages, navigation labels, entry points and destinations", "why_it_matters": "Allows an agent to assess whether users can locate and understand relevant information." }, { "name": "Responsive behaviour", "kind": "category", "unit_or_values": "Specified reflow, resizing, reordering, substitution, overflow and navigation changes by browsing condition", "why_it_matters": "Records how the experience adapts beyond a single screenshot or device size." }, { "name": "Interaction state coverage", "kind": "measurement", "unit_or_values": "Percentage of enumerated required states with specified behaviour; record the state inventory and denominator", "why_it_matters": "Exposes missing loading, empty, error, success, focus and recovery experiences." }, { "name": "Accessibility evaluation state", "kind": "state", "unit_or_values": "Not assessed, partially assessed, assessed with unresolved barriers, or assessed against a named target; include methods and scope", "why_it_matters": "Separates design intent from evidence that people using different modes of access can complete tasks." }, { "name": "Task completion evidence", "kind": "measurement", "unit_or_values": "Completion rate and time in seconds for named tasks, with participant context, sample size and test conditions", "why_it_matters": "Supports evaluation of usability without treating an isolated metric as a universal quality score." }, { "name": "Design maturity", "kind": "state", "unit_or_values": "Exploratory, specified, prototyped, evaluated, delivered, or under revision; record state per artefact", "why_it_matters": "Distinguishes proposals from decisions that have been tested or implemented." } ], "affordances": [ "Map an intended user task to the pages, content and interactions needed to complete it.", "Generate or revise wireframes, page compositions and interactive prototypes within recorded constraints.", "Identify missing navigation routes, interface states and responsive behaviours.", "Inspect designs and delivered pages for usability and accessibility barriers.", "Compare design alternatives using explicit task outcomes and browsing conditions.", "Prepare implementation guidance and record discrepancies between the specified and delivered experience." ] }, "sources": [], "structure": { "bundles": [ { "id": "web-purpose-and-task-fit", "name": "Web purpose and task fit", "description": "Connects the website's intended role to the people, tasks and constraints its design must serve.", "rationale": "An agent needs to distinguish purposeful interface decisions from visual preferences unsupported by the website's use.", "layers": [ { "id": "audiences-and-entry-contexts", "name": "Audiences and entry contexts", "description": "Records who arrives, where they enter and what they need from the web experience.", "findings": [ { "id": "user-task-and-entry-map", "name": "User task and entry map", "description": "Record intended user groups, priority tasks and plausible entry pages, distinguishing observed behaviour from assumptions.", "questions": [ { "text": "Which tasks should each intended user group be able to complete, including when arriving directly on an internal page?", "kind": "definition", "id": "user-task-and-entry-map-q01" }, { "text": "What research, service evidence or stakeholder assumption supports each audience and entry-context claim?", "kind": "provenance", "id": "user-task-and-entry-map-q02" } ] } ] }, { "id": "design-success-and-constraints", "name": "Design success and constraints", "description": "Defines desired outcomes and the conditions that limit feasible web design choices.", "findings": [ { "id": "web-design-decision-criteria", "name": "Web design decision criteria", "description": "Record task success criteria and constraints imposed by content, branding, existing platforms and delivery conditions.", "questions": [ { "text": "What observable result would show that the proposed page or journey supports its intended task?", "kind": "measurement", "id": "web-design-decision-criteria-q01" }, { "text": "Which design choices can change, and which depend on decisions owned by content, brand or engineering teams?", "kind": "boundary", "id": "web-design-decision-criteria-q02" } ] } ] } ] }, { "id": "content-structure-and-wayfinding", "name": "Content structure and wayfinding", "description": "Models how web content is grouped, labelled, connected and exposed through navigation.", "rationale": "A visually coherent site can still fail when users cannot locate a destination or understand where they are.", "layers": [ { "id": "page-and-content-organisation", "name": "Page and content organisation", "description": "Captures content groupings, page purposes and relationships among destinations.", "findings": [ { "id": "content-to-page-allocation", "name": "Content-to-page allocation", "description": "Record which content belongs on each page or template and why its grouping supports a user task.", "questions": [ { "text": "What distinct purpose does each page or template serve, and which content is necessary for that purpose?", "kind": "definition", "id": "content-to-page-allocation-q01" }, { "text": "Where do duplicated, fragmented or missing content groups obstruct a task, and should pages be merged, split or linked?", "kind": "action", "id": "content-to-page-allocation-q02" } ] } ] }, { "id": "navigation-and-location-cues", "name": "Navigation and location cues", "description": "Captures routes to destinations and cues that explain the current location.", "findings": [ { "id": "destination-findability", "name": "Destination findability", "description": "Record navigation labels, links, search entry points where applicable, and evidence that users can interpret them.", "questions": [ { "text": "Can users locate priority destinations from relevant entry pages using the proposed labels and routes?", "kind": "measurement", "id": "destination-findability-q01" }, { "text": "Which location cues and return routes remain available on deep pages and compact navigation layouts?", "kind": "definition", "id": "destination-findability-q02" } ] } ] } ] }, { "id": "visual-composition-and-responsive-behaviour", "name": "Visual composition and responsive behaviour", "description": "Models the visible organisation of pages and its adaptation to changing content and display conditions.", "rationale": "Web layouts must communicate priority while accommodating variable viewports, text sizes and content lengths.", "layers": [ { "id": "visual-hierarchy-and-patterns", "name": "Visual hierarchy and patterns", "description": "Records how typography, spacing, colour and repeated components convey meaning and priority.", "findings": [ { "id": "page-hierarchy-and-pattern-consistency", "name": "Page hierarchy and pattern consistency", "description": "Record intended reading order, primary actions and reusable visual patterns, including justified exceptions.", "questions": [ { "text": "Which information and actions should receive attention first, and how does the composition communicate that order?", "kind": "definition", "id": "page-hierarchy-and-pattern-consistency-q01" }, { "text": "Which repeated elements share a design-system pattern, and what task-specific reason supports each exception?", "kind": "provenance", "id": "page-hierarchy-and-pattern-consistency-q02" } ] } ] }, { "id": "layout-adaptation-and-content-stress", "name": "Layout adaptation and content stress", "description": "Specifies behaviour when viewport dimensions, text settings or content size change.", "findings": [ { "id": "responsive-transformation-rules", "name": "Responsive transformation rules", "description": "Record how page regions, navigation and controls reflow or transform, including overflow and long-content cases.", "questions": [ { "text": "How do layout, navigation and action placement change as available space narrows or text grows?", "kind": "definition", "id": "responsive-transformation-rules-q01" }, { "text": "Under which tested combinations of viewport, zoom and content length do clipping, overlap or unusable controls occur?", "kind": "measurement", "id": "responsive-transformation-rules-q02" } ] } ] } ] }, { "id": "interaction-and-inclusive-access", "name": "Interaction and inclusive access", "description": "Models task behaviour across interface states and access through different input and perception modes.", "rationale": "Static compositions do not establish whether a web experience can be operated, understood or recovered from when something goes wrong.", "layers": [ { "id": "task-flows-and-feedback", "name": "Task flows and feedback", "description": "Records user actions, state transitions, feedback and recovery within web journeys.", "findings": [ { "id": "interaction-state-and-recovery-specification", "name": "Interaction state and recovery specification", "description": "Record the states and transitions required for links, forms and interactive components, including navigation history where relevant.", "questions": [ { "text": "What should users see and be able to do before, during and after each action, including loading, empty, error and success states?", "kind": "definition", "id": "interaction-state-and-recovery-specification-q01" }, { "text": "How can users correct input, retry a failed action or return to an earlier step without unexpectedly losing their work?", "kind": "action", "id": "interaction-state-and-recovery-specification-q02" } ] } ] }, { "id": "access-modes-and-barriers", "name": "Access modes and barriers", "description": "Records requirements and evidence for perceiving, understanding and operating the interface through different access modes.", "findings": [ { "id": "equivalent-task-access", "name": "Equivalent task access", "description": "Record keyboard and touch operation, focus behaviour, semantic requirements, text alternatives and presentation barriers with an explicit assessment scope.", "questions": [ { "text": "Can priority tasks be completed using keyboard navigation and relevant assistive technologies, and what evidence supports the assessment?", "kind": "measurement", "id": "equivalent-task-access-q01" }, { "text": "Which design revisions address barriers involving focus, labels, contrast, motion, target size or information conveyed only visually?", "kind": "action", "id": "equivalent-task-access-q02" } ] } ] } ] }, { "id": "validation-and-delivered-experience", "name": "Validation and delivered experience", "description": "Connects design alternatives and revisions to evaluation evidence and the behaviour of delivered pages.", "rationale": "An agent must distinguish design assumptions, prototype results and implementation outcomes before recommending further changes.", "layers": [ { "id": "prototype-and-task-evaluation", "name": "Prototype and task evaluation", "description": "Records what was tested, with whom, under which conditions and with which limitations.", "findings": [ { "id": "design-evidence-and-revision", "name": "Design evidence and revision", "description": "Record observations against named tasks and design versions, then connect proposed revisions to those observations.", "questions": [ { "text": "Which design version, tasks, participants and browsing conditions produced each evaluation result?", "kind": "provenance", "id": "design-evidence-and-revision-q01" }, { "text": "Which observed difficulties justify a revision, and what follow-up evaluation would show whether it helped?", "kind": "action", "id": "design-evidence-and-revision-q02" } ] } ] }, { "id": "implementation-correspondence", "name": "Implementation correspondence", "description": "Checks whether delivered web pages preserve specified layout, interaction and access behaviour.", "findings": [ { "id": "delivered-design-discrepancies", "name": "Delivered design discrepancies", "description": "Record consequential differences between design intent and delivered pages, including behaviour under slow loading or unavailable resources.", "questions": [ { "text": "Where do delivered pages diverge from specified content hierarchy, responsive rules, interaction states or access requirements?", "kind": "measurement", "id": "delivered-design-discrepancies-q01" }, { "text": "Which discrepancies require a design revision, and which require implementation or content correction by a neighbouring owner?", "kind": "boundary", "id": "delivered-design-discrepancies-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The activity sense is inferred from the domain code and name; no registry definition was supplied.", "The listed kinds are overlapping areas of practice, not a mutually exclusive taxonomy.", "Standards are named from recall; applicability, editions and jurisdiction-specific obligations require verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Visual interface design", "Responsive web design", "Adaptive web design", "Interaction design for web interfaces", "Information architecture for websites", "Accessible web design" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Web Content Accessibility Guidelines (WCAG), issued by the World Wide Web Consortium (W3C).", "HTML Living Standard, maintained by the Web Hypertext Application Technology Working Group (WHATWG).", "Cascading Style Sheets (CSS) specifications, developed by W3C.", "Accessible Rich Internet Applications (WAI-ARIA), issued by W3C.", "ISO 9241-210, Human-centred design for interactive systems, issued by the International Organization for Standardization (ISO)." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Organising content and navigation so visitors can find information.", "Designing online purchasing, booking and registration flows.", "Presenting organisational identity through typography, colour and layout.", "Making interfaces usable across screen sizes and input methods.", "Supporting access for people using assistive technologies." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Task completion rate in usability testing", "typical_range": "0-100% possible; desirable performance depends on the task and user population.", "unit": "%" }, { "quantity": "Time required to complete a specified task", "typical_range": "No universal typical range; compare equivalent tasks and testing conditions.", "unit": "seconds" }, { "quantity": "Text-to-background contrast ratio", "typical_range": "1:1-21:1 possible; this is the scale's extent, not an observed typical range.", "unit": "dimensionless ratio" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Unclear navigation or content hierarchy prevents users from finding information or completing tasks.", "Insufficient contrast, missing labels or inaccessible interactions exclude users with disabilities.", "Layouts fail when text is enlarged, screens are narrow or content changes.", "Deceptive interface patterns steer users into unintended purchases, disclosures or subscriptions.", "Heavy visual assets and disruptive motion impair usability, especially on constrained devices or connections." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Writing direction, scripts and text expansion affect typography, navigation and layout.", "Date formats, number formats, address structures and cultural conventions require localisation.", "Accessibility, privacy and consumer-protection obligations vary by jurisdiction." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Web development", "difference": "Web design specifies presentation and interaction; web development implements working web systems, although practitioners and tasks often overlap." }, { "name": "Graphic design", "difference": "Graphic design concerns visual communication across media; web design additionally addresses browser-based interaction and adaptable interfaces." }, { "name": "User experience design", "difference": "User experience design addresses the broader experience of a product or service; web design concerns its website or web-interface component." }, { "name": "User interface design", "difference": "User interface design applies to interactive systems generally; web design is specific to the web and can also include content organisation." }, { "name": "Information architecture", "difference": "Information architecture focuses on organising, labelling and connecting information; web design also specifies visual presentation and interaction." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of web design this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend web design to cover the professional discipline as well as the activity, or should this ACT model remain limited to activities and their artefacts?", "Where should web design end and broader user-experience or service design begin for journeys that cross websites, native applications and offline services?", "Which accessibility targets and evaluation methods apply to a particular deployment, audience and jurisdiction?", "What evidence is sufficient to judge task suitability when representative users or a functioning implementation are unavailable?", "How should competing user needs, organisational objectives, visual identity and delivery constraints be prioritised when no design satisfies all of them?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "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 web design, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a web design activity, assess how well its decisions support intended users and tasks, and identify justified changes or unresolved constraints.", "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: responsive web design.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 71 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 web design, 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": [ "responsive web design" ] } ], "standing": "Described in 71 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 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 web design from another, and a web design 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 web design, 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 web design, 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 web design 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 web design, 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 web design, 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 web design 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 web design 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 web design, 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 web design, 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 web design 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 web design from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a web design, 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 web design, 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 web design 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 web design 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 web design between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a web design, 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 web design, 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 web design 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 web design, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a web design 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 web design, 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 web design, 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 web design 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 web design 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 web design, 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 web design and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a web design, 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 web design, 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 web design 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 web design consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a web design 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 web design, 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 web design, 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 web design 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 web design 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 web design 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 web design 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 web design 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 web design?", "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 web design?", "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 web design 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 web design and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a web design, 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 web design, 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 web design 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 web design is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a web design, 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 web design, 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 web design 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 } } } }