{ "model": { "rank": 4875, "code": "thing-q11288", "model_id": "vr.tr.web-server", "name": "web server", "purpose": "Enable an agent to recognise a web-serving host, assess its ability to serve intended HTTP requests, and determine which operational actions are authorised.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q11288/", "tier": 2, "score": 72, "payload": { "layer": "wikidata", "aliases": [ "HTTP server", "GNU libmicrohttpd", "Embedded HTTP server", "ad server", "personal web server", "in-kernel web server" ], "aliasCount": 6, "merged": 6, "knownIn": 72, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q11288", "url": "https://www.wikidata.org/wiki/Q11288", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:11:03Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.6, "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: 01a08801-9085-73d2-9664-0547a94bbcc2\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: web server\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\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.6, "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: 01a08801-907d-70f3-9db7-faf32cbb8326\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: web server\nRegistry id: vr.tr.web-server\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q11288", "registryId": "vr.tr.web-server", "name": "web server", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q11288/", "model": { "registry_id": "vr.tr.web-server", "name": "web server", "purpose": "Enable an agent to recognise a web-serving host, assess its ability to serve intended HTTP requests, and determine which operational actions are authorised.", "definition": "A web server, in the physical-object sense, is a computer configured to run software that accepts HTTP requests from clients and returns responses containing web resources, application results, or status information.", "scope_statement": "This model covers the registered kind 'web server' as a physical computing host configured for web serving, consistent with PHY / PHY.OBJ; it records the host's relationship to HTTP server software and hosted services while leaving the unresolved software-only sense explicit.", "in_scope": [ "Physical host identity and assignment to a web-serving role", "HTTP listeners, network reachability and request routing", "Relationships to server software, hosted sites, content and application upstreams", "Transport security, administrative control and request-handling restrictions", "Resource capacity, service health, maintenance and recovery" ], "out_of_scope": [ "HTTP server software packages as independently versioned software products", "Website content, editorial meaning and application business logic", "Browsers and other HTTP clients", "DNS infrastructure, certificate authorities and external network infrastructure", "Complete hosting platforms, server fleets and distributed delivery services", "Virtual machines and containers as independently managed computing resources" ], "distinguishing_features": [ "The host has an assigned HTTP-serving role supported by configuration or deployment evidence; an installed but unused server package alone does not establish that role.", "Its configured listeners can receive HTTP requests and produce or relay HTTP responses when the required dependencies are available; TCP reachability alone does not demonstrate web serving.", "The physical host is distinguishable from the server executable, deployment instance and hosted website through separate identities and relationships.", "A reverse-proxy-only host may qualify, but its forwarding role must be distinguished from originating static content or executing application requests.", "A host running only a database, file-sharing service or unrelated network service does not qualify unless a web-serving role is also established." ], "characteristics": [ { "name": "Host identity and deployment relationships", "kind": "relation", "unit_or_values": "Physical asset identifier linked to operating-system instances, virtual machines, containers and HTTP-serving processes where applicable", "why_it_matters": "Prevents a host, a software process and a website from being treated as the same entity." }, { "name": "Web-serving role", "kind": "category", "unit_or_values": "Static origin, application gateway, reverse proxy, caching proxy, or documented combination", "why_it_matters": "Determines which requests the host handles locally and which depend on other services." }, { "name": "Listener configuration", "kind": "relation", "unit_or_values": "Bind address, transport, port, HTTP protocol configuration and TLS termination point", "why_it_matters": "Identifies how requests enter the service and where connection failures can occur." }, { "name": "Hosted authority and route mappings", "kind": "relation", "unit_or_values": "Hostnames and path rules linked to virtual hosts, document roots or upstream services", "why_it_matters": "Establishes which site or application a request should reach." }, { "name": "Observed service state", "kind": "state", "unit_or_values": "Unverified, serving, degraded, draining, stopped or unreachable; qualified by observation time and vantage point", "why_it_matters": "Separates operational evidence from configuration and avoids equating one failed probe with host failure." }, { "name": "Request throughput", "kind": "measurement", "unit_or_values": "Requests/s, with workload, response mix and observation interval", "why_it_matters": "Supports capacity assessment without treating unlike workloads as equivalent." }, { "name": "Response latency", "kind": "measurement", "unit_or_values": "Milliseconds at stated percentiles, with measurement boundary and request class", "why_it_matters": "Shows whether representative requests meet the service's performance expectations." }, { "name": "Request outcomes", "kind": "measurement", "unit_or_values": "Counts or proportions of HTTP status classes, timeouts and connection failures over a stated interval", "why_it_matters": "Distinguishes successful delivery, rejected requests and failures that produce no HTTP response." }, { "name": "Resource headroom", "kind": "measurement", "unit_or_values": "CPU utilisation %, available RAM bytes, free storage bytes, network bit/s and active connections relative to configured limits", "why_it_matters": "Helps locate saturation and determine whether additional load or maintenance is tolerable." }, { "name": "Transport protection", "kind": "state", "unit_or_values": "Plain HTTP, TLS terminated locally, TLS terminated upstream, or mixed; with certificate and protocol configuration references", "why_it_matters": "Identifies which connection segments are protected and who controls that protection." }, { "name": "Operational authority", "kind": "relation", "unit_or_values": "Owners and permitted principals linked to inspect, deploy, reload, restart, drain and retire actions", "why_it_matters": "Makes technical capability distinct from permission to act." } ], "affordances": [ "Inspect host-to-service relationships and test HTTP behaviour for a specified hostname, route and network vantage point.", "Trace a request through local routing, TLS termination, content delivery and application upstreams.", "Compare observed demand and resource headroom against documented service targets.", "Validate and apply authorised listener, route, content or certificate changes with a defined rollback.", "Drain traffic, reload or restart the relevant service when authorised and operationally supported.", "Diagnose failures and verify restoration using representative requests and dependency checks." ] }, "sources": [], "structure": { "bundles": [ { "id": "host-and-web-serving-identity", "name": "Host and web-serving identity", "description": "Establishes the physical entity and the web-serving responsibilities assigned to it.", "rationale": "Web server can name hardware, software or a service; the model must make its chosen entity and role inspectable.", "layers": [ { "id": "physical-host-boundary", "name": "Physical host boundary", "description": "Connects the registered physical kind to identifiable hosts and their execution environments.", "findings": [ { "id": "host-to-runtime-assignment", "name": "Host-to-runtime assignment", "description": "Record evidence linking a physical host to the environments and processes that perform web serving.", "questions": [ { "text": "Which physical asset is being described, and which operating-system instances, virtual machines or containers run its HTTP-serving processes?", "kind": "boundary", "id": "host-to-runtime-assignment-q01" }, { "text": "Which inventory or deployment record establishes that assignment, and when was it last verified?", "kind": "provenance", "id": "host-to-runtime-assignment-q02" } ] } ] }, { "id": "serving-role-and-tenancy", "name": "Serving role and tenancy", "description": "Identifies what the host serves and how distinct hosted services share it.", "findings": [ { "id": "origin-proxy-and-site-responsibilities", "name": "Origin, proxy and site responsibilities", "description": "Record whether the host originates responses, forwards requests, caches responses or combines these roles for particular sites.", "questions": [ { "text": "For each hosted service, does this host serve files, invoke application code, forward requests or return cached responses?", "kind": "definition", "id": "origin-proxy-and-site-responsibilities-q01" }, { "text": "Which sites or tenants share this host, and which resources or configuration changes can affect more than one of them?", "kind": "boundary", "id": "origin-proxy-and-site-responsibilities-q02" } ] } ] } ] }, { "id": "http-ingress-and-routing", "name": "HTTP ingress and routing", "description": "Describes how requests reach the host and select a destination.", "rationale": "An active server process does not establish that the intended client can reach the correct site.", "layers": [ { "id": "listeners-and-reachability", "name": "Listeners and reachability", "description": "Records exposed listeners and the network paths through which they are available.", "findings": [ { "id": "reachable-http-endpoints", "name": "Reachable HTTP endpoints", "description": "Record configured endpoints separately from observed reachability through firewalls, address translation and external front ends.", "questions": [ { "text": "Which addresses, transports, ports and HTTP protocol configurations accept requests, and which are intended to be publicly reachable?", "kind": "definition", "id": "reachable-http-endpoints-q01" }, { "text": "From which client locations have the intended endpoints been tested, and what response or connection failure was observed?", "kind": "measurement", "id": "reachable-http-endpoints-q02" } ] } ] }, { "id": "authority-and-path-dispatch", "name": "Authority and path dispatch", "description": "Explains selection of virtual hosts, routes and upstream destinations.", "findings": [ { "id": "request-destination-selection", "name": "Request destination selection", "description": "Record how hostname, TLS server-name selection where applicable, and path rules determine the request destination.", "questions": [ { "text": "How do the requested hostname and path select a virtual host, document root, redirect or upstream?", "kind": "definition", "id": "request-destination-selection-q01" }, { "text": "What happens for an unknown hostname, unmatched path or inconsistent TLS server name and HTTP authority?", "kind": "boundary", "id": "request-destination-selection-q02" } ] } ] } ] }, { "id": "response-production-and-dependencies", "name": "Response production and dependencies", "description": "Captures how the host obtains response data and what it requires to deliver it.", "rationale": "Correct HTTP handling depends on content mappings, application availability and response transformations.", "layers": [ { "id": "content-and-application-bindings", "name": "Content and application bindings", "description": "Connects request routes to files, applications and external dependencies.", "findings": [ { "id": "response-source-binding", "name": "Response source binding", "description": "Record the source of responses and the credentials, permissions and dependencies needed to obtain them.", "questions": [ { "text": "Which filesystem locations or application endpoints provide responses for each route, and under which service identity are they accessed?", "kind": "boundary", "id": "response-source-binding-q01" }, { "text": "Which request checks demonstrate that required content and upstream services are available through the web server?", "kind": "measurement", "id": "response-source-binding-q02" } ] } ] }, { "id": "response-policy-and-upstream-failure", "name": "Response policy and upstream failure", "description": "Records caching, transformation and failure behaviour relevant to delivered responses.", "findings": [ { "id": "delivery-and-fallback-rules", "name": "Delivery and fallback rules", "description": "Record configured cache behaviour, compression, upstream timeouts and error handling without assuming they are enabled.", "questions": [ { "text": "Which responses may be cached or compressed, and what determines cache keys, freshness and invalidation?", "kind": "definition", "id": "delivery-and-fallback-rules-q01" }, { "text": "What response is produced when an upstream is slow or unavailable, and under what conditions may a request be retried?", "kind": "action", "id": "delivery-and-fallback-rules-q02" } ] } ] } ] }, { "id": "transport-trust-and-access", "name": "Transport trust and access", "description": "Describes connection protection, exposed capabilities and authority over the server.", "rationale": "A functioning web endpoint can still expose unintended content, trust unverified request metadata or permit unauthorised changes.", "layers": [ { "id": "tls-and-proxy-trust", "name": "TLS and proxy trust", "description": "Locates encryption boundaries and identifies trusted intermediaries.", "findings": [ { "id": "connection-protection-boundaries", "name": "Connection protection boundaries", "description": "Record TLS termination, certificate responsibility and the rules for trusting metadata supplied by proxies.", "questions": [ { "text": "Where does TLS terminate on each request path, which names must the certificate cover, and who manages renewal?", "kind": "boundary", "id": "connection-protection-boundaries-q01" }, { "text": "Which intermediaries may supply trusted client-address or scheme information, and how is that trust restricted?", "kind": "definition", "id": "connection-protection-boundaries-q02" } ] } ] }, { "id": "request-and-administration-controls", "name": "Request and administration controls", "description": "Separates public request permissions from privileges to operate the host and service.", "findings": [ { "id": "permitted-exposure-and-changes", "name": "Permitted exposure and changes", "description": "Record access restrictions, request limits and operational permissions for the web-serving deployment.", "questions": [ { "text": "Which methods, paths, upload sizes and request rates are permitted, and where are authentication and access checks enforced?", "kind": "definition", "id": "permitted-exposure-and-changes-q01" }, { "text": "Which principals may change routes, read logs, deploy content, replace certificates or restart services, and what approval conditions apply?", "kind": "action", "id": "permitted-exposure-and-changes-q02" } ] } ] } ] }, { "id": "capacity-health-and-recovery", "name": "Capacity, health and recovery", "description": "Connects request-level performance to host resources and operational recovery.", "rationale": "The model must distinguish a responsive process from a service that can meet demand and survive maintenance or failure.", "layers": [ { "id": "request-health-and-host-headroom", "name": "Request health and host headroom", "description": "Relates representative HTTP outcomes to resource constraints and physical operating conditions.", "findings": [ { "id": "observed-serving-capacity", "name": "Observed serving capacity", "description": "Record workload-qualified performance alongside resource saturation and relevant power, cooling or hardware alerts.", "questions": [ { "text": "For which request mix and observation window are throughput, latency, error rate and concurrent connections measured against a service target?", "kind": "measurement", "id": "observed-serving-capacity-q01" }, { "text": "Do CPU, memory, storage, connection limits, network utilisation or power and thermal alerts explain the observed degradation?", "kind": "measurement", "id": "observed-serving-capacity-q02" } ] } ] }, { "id": "safe-change-and-restoration", "name": "Safe change and restoration", "description": "Defines how service changes and failures are handled with evidence of successful recovery.", "findings": [ { "id": "validated-maintenance-and-recovery", "name": "Validated maintenance and recovery", "description": "Record configuration validation, traffic draining, rollback and restoration procedures for the actual hosting arrangement.", "questions": [ { "text": "How are configuration changes validated and rolled back, and how are active requests or long-lived connections handled during reload, restart or host maintenance?", "kind": "action", "id": "validated-maintenance-and-recovery-q01" }, { "text": "Which configuration, content, secrets and external dependencies are needed to restore serving, and which representative requests verify recovery?", "kind": "action", "id": "validated-maintenance-and-recovery-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 term commonly denotes software as well as hardware; the physical sense is selected here because the supplied domain is PHY.OBJ.", "The listed protocol standards apply to implemented capabilities; a web server need not support every HTTP version.", "No typical capacity, dimensions, power consumption, or throughput range is supplied because embedded devices and data-centre systems differ substantially." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of web server 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": [ "Dedicated physical web server", "Shared-purpose computer hosting a web service", "Embedded web server in a device" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of web server this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Manufacturer serial number", "value_or_pattern": "Manufacturer-assigned alphanumeric identifier", "note": "Identifies a physical unit, not the websites or services it hosts." }, { "scheme": "Domain Name System (DNS)", "value_or_pattern": "Dot-separated domain labels", "note": "Names a service endpoint; one name may resolve to multiple servers, and one server may host multiple names." }, { "scheme": "Internet Protocol addressing", "value_or_pattern": "IPv4 or IPv6 address", "note": "Identifies a network interface or reachable endpoint, not a permanent physical-unit identity." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of web server 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": [ "IETF RFC 9110, HTTP Semantics.", "IETF RFC 9112, HTTP/1.1.", "IETF RFC 9113, HTTP/2.", "IETF RFC 9114, HTTP/3.", "IETF RFC 8446, Transport Layer Security (TLS) 1.3." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of web server 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": [ "Serving websites and downloadable files.", "Hosting web applications and HTTP APIs.", "Providing browser-based administration for routers, printers, and other devices.", "Hosting internal organisational portals.", "Terminating HTTPS connections and forwarding requests to application services." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of web server 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": [ "Power, cooling, storage, or network failures interrupt service.", "Traffic surges or denial-of-service attacks exhaust connection, processing, memory, or bandwidth capacity.", "Software vulnerabilities or configuration errors permit unauthorised access, data exposure, or code execution.", "Expired certificates or incorrect TLS configuration prevent secure connections.", "Application or upstream-service failures produce errors, timeouts, or incorrect responses." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of web server 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": [ "Privacy, logging, and data-residency obligations depend on jurisdiction and the data processed.", "Mains power, plug types, and applicable electrical and electromagnetic-compatibility requirements vary by deployment region." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of web server 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 server software", "difference": "The program implements HTTP handling; the physical web server is the computer running it." }, { "name": "Application server", "difference": "Its defining role is executing application logic; a web server's defining role is handling HTTP requests, although one system can do both." }, { "name": "Website", "difference": "A website is a collection of related web resources and experiences, rather than the computer that serves them." }, { "name": "Reverse proxy", "difference": "A reverse proxy primarily forwards client requests to upstream servers; a web server may serve resources directly or also perform that proxy role." }, { "name": "Virtual server", "difference": "A virtual server is a software-defined computing instance rather than a distinct physical computer." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of web server this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend the physical host sense adopted here, the HTTP server software sense, or a broader service sense despite its PHY / PHY.OBJ assignment?", "Does an existing Vercy world model already cover this concept, requiring a registry link instead of a separate publication?", "Should a physical host with only an incidental embedded management web interface qualify, or must web serving be an explicitly assigned operational role?", "Which HTTP, TLS and deployment-specific standards and versions should be cited after primary-source research, and which requirements apply to each serving role?", "Which representative workloads, availability objectives and recovery targets should be used to judge state without inventing universal capacity thresholds?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "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 server, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a web-serving host, assess its ability to serve intended HTTP requests, and determine which operational actions are authorised.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: HTTP server, GNU libmicrohttpd, Embedded HTTP server, ad server, personal web server, in-kernel web server.", "6 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 72 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 server, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "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": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "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": [ "HTTP server", "GNU libmicrohttpd", "Embedded HTTP server", "ad server", "personal web server", "in-kernel web server" ] } ], "standing": "Described in 72 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 6 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 server from another, and a web server 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 server, 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 server, 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 server 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 server, 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 server, 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 server 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 server 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 server, 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 server, 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 server 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 server from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a web server, 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 server, 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 server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a web server is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a web server, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a web server, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a web server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a web server is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a web server, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a web server, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a web server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a web server is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a web server, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a web server, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a web server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a web server is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a web server is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a web server, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a web server, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a web server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a web server is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a web server, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a web server, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a web server 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 server 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 server between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a web server, 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 server, 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 server 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 server, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a web server 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 server, 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 server, 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 server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What web server is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does web server perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise web server, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How web server is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does web server have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does web server need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about web server is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about web server hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern web server, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a web server 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 server and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a web server, 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 server, 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 server 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 server is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a web server, 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 server, 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 server is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }