{ "model": { "rank": 5934, "code": "thing-q5892272", "model_id": "vr.tr.web-hosting-service", "name": "web hosting service", "purpose": "Enable an AI agent to recognise a web hosting service, assess its ability to serve a particular website or web application, and determine which deployment, operational and lifecycle actions are permitted.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q5892272/", "tier": 2, "score": 64, "payload": { "layer": "wikidata", "aliases": [ "website hosting", "backup hosting", "free web hosting service", "reseller web hosting", "dedicated hosting service", "wiki hosting service", "shared web hosting service", "Bulletproof hosting", "Clustered web hosting", "Peer-to-peer web hosting", "self-hosting", "phlog hosting service" ], "aliasCount": 12, "merged": 12, "knownIn": 64, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q5892272", "url": "https://www.wikidata.org/wiki/Q5892272", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:10:53Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00276998, "turns": 1, "seconds": 26.3, "error": null }, "codex": { "seconds": 88, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07b58-1867-74c2-893a-a4c1e9fc77c1\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: web hosting service\nRegistry id: vr.tr.web-hosting-service\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this " } } }, "metaModel": { "id": "THING-Q5892272", "registryId": "vr.tr.web-hosting-service", "name": "web hosting service", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q5892272/", "model": { "registry_id": "vr.tr.web-hosting-service", "name": "web hosting service", "purpose": "Enable an AI agent to recognise a web hosting service, assess its ability to serve a particular website or web application, and determine which deployment, operational and lifecycle actions are permitted.", "definition": "A commercially or organizationally operated service that provisions and operates Internet-connected compute, storage, and network resources so that a customer's websites, web applications, and related content remain continuously reachable over HTTP/HTTPS.", "scope_statement": "This model owns the service arrangement that accepts web content or application workloads and makes them available over HTTP or HTTPS, including its hosting capabilities, delivery boundaries, operational state, customer controls and service commitments.", "in_scope": [ "The hosting service instance, its provider, customer and hosted-site relationships", "Supported web workloads, runtime constraints and resource entitlements", "Deployment, domain binding, HTTPS configuration and request delivery", "Operational health, recovery capabilities and division of operational responsibility", "Hosting-specific access controls, charges, restrictions and exit conditions" ], "out_of_scope": [ "The website's content, information architecture and editorial lifecycle", "The application's business logic and software development lifecycle", "Domain registration, ownership transfer and the authoritative DNS service", "The internal design and lifecycle of underlying servers, networks and data centres", "Independent database, email, identity and content-delivery services beyond their hosting integration", "The provider organisation's overall business and governance" ], "distinguishing_features": [ "The service accepts content or an application workload for web publication; a domain registration service alone does not provide this execution or serving capability.", "The service supplies a serving environment behind an HTTP or HTTPS endpoint; a website is the hosted product rather than the hosting arrangement.", "The service explicitly supports web serving as a customer capability; a general-purpose compute instance may require the customer to establish that capability separately.", "The service's boundary includes where deployable content resides or application requests execute; a forwarding proxy or CDN alone may only route or cache another host's responses.", "The arrangement exposes identifiable hosting entitlements and operational responsibilities, even when hosting is bundled with a site builder or another product." ], "characteristics": [ { "name": "Supported workload classes", "kind": "category", "unit_or_values": "Static files, server-rendered application, managed CMS, request-triggered functions, or other explicitly supported classes; multiple values allowed", "why_it_matters": "Determines whether the intended website or application can operate on the service." }, { "name": "Operational responsibility split", "kind": "relation", "unit_or_values": "Provider, customer or third party responsible for each of runtime patching, application updates, TLS, backups and incident response", "why_it_matters": "Prevents an agent from assuming that a hosting capability includes its ongoing management." }, { "name": "Runtime compatibility", "kind": "category", "unit_or_values": "Supported runtimes and versions, frameworks, extensions and execution restrictions; unsupported or unknown where applicable", "why_it_matters": "Identifies deployment blockers and maintenance requirements." }, { "name": "Resource entitlement", "kind": "measurement", "unit_or_values": "Named limits with units, such as storage bytes, memory bytes, CPU allocation, concurrent requests and execution seconds; record shared or dedicated allocation", "why_it_matters": "Makes workload fit and capacity constraints assessable." }, { "name": "Web delivery state", "kind": "state", "unit_or_values": "Unconfigured, provisioning, serving, degraded, unavailable, suspended, retiring or unknown, with observation time", "why_it_matters": "Distinguishes a purchased entitlement from a functioning public service." }, { "name": "Domain and certificate bindings", "kind": "relation", "unit_or_values": "Hostnames linked to deployment targets and certificates, with validation and renewal states", "why_it_matters": "Shows whether visitors reach the intended deployment through the intended secure endpoint." }, { "name": "Observed request performance", "kind": "measurement", "unit_or_values": "Latency in milliseconds, error proportion and successful-check proportion, each with endpoint, observation window and measurement location", "why_it_matters": "Supports health judgments without confusing a sampled observation with a contractual guarantee." }, { "name": "Recovery coverage", "kind": "category", "unit_or_values": "Covered content, configuration and persistent data; backup retention, restore method and last verified restoration", "why_it_matters": "Reveals whether rollback or restoration can recover the whole hosted site." }, { "name": "Hosting charge basis", "kind": "category", "unit_or_values": "Subscription and metered dimensions, currency, billing interval, included allowances and overage treatment", "why_it_matters": "Allows an agent to judge the cost implications of deployment and traffic changes." } ], "affordances": [ "Assess whether a proposed website or application fits the supported runtime, resource and policy constraints.", "Deploy or promote a release, or roll it back, using authorised hosting controls.", "Bind a hostname and configure HTTPS after checking ownership validation and related DNS dependencies.", "Inspect delivery health, logs and quota consumption to diagnose hosting failures.", "Adjust hosting capacity or restore covered content and data within recorded authority and service capabilities.", "Export hosted assets, prepare a migration, or retire the service after checking dependencies and retention obligations." ] }, "sources": [ { "id": "iso-17788", "title": "ISO/IEC 17788:2014 Information technology - Cloud computing - Overview and vocabulary", "url": "https://www.iso.org/standard/60544.html", "what_it_supports": "Places web hosting in the cloud-service vocabulary as a common IaaS/PaaS offering and supplies the service-model distinctions used in kinds and neighbours.", "url_status": "blocked" } ], "structure": { "bundles": [ { "id": "hosting-boundary-and-control", "name": "Hosting boundary and control", "description": "Identifies the hosting arrangement and who controls each part of web publication.", "rationale": "Hosting can be bundled, resold or partly managed, so an agent needs an explicit service boundary and responsibility split.", "layers": [ { "id": "service-identity-and-targets", "name": "Service identity and targets", "description": "Connects the hosting entitlement to the sites and environments it serves.", "findings": [ { "id": "hosting-unit", "name": "Hosting unit", "description": "Records the identifiable service instance, provider, customer and associated production or non-production targets.", "questions": [ { "text": "What identifies this hosting service instance, and which websites, applications and environments does it host?", "kind": "definition", "id": "hosting-unit-q01" }, { "text": "Which account record, order or service configuration establishes the provider and customer relationship?", "kind": "provenance", "id": "hosting-unit-q02" } ] } ] }, { "id": "responsibility-and-authority", "name": "Responsibility and authority", "description": "Separates operational duties from permission to change the hosting service.", "findings": [ { "id": "hosting-control-boundaries", "name": "Hosting control boundaries", "description": "Records responsibility for each hosting function and the authority available to the agent.", "questions": [ { "text": "Who maintains the web server, runtime, application, certificates and backups, and where do those responsibilities end?", "kind": "boundary", "id": "hosting-control-boundaries-q01" }, { "text": "Which deployment, domain, access, billing and deletion operations may the agent perform, and under what approval conditions?", "kind": "action", "id": "hosting-control-boundaries-q02" } ] } ] } ] }, { "id": "workload-fit-and-isolation", "name": "Workload fit and isolation", "description": "Captures whether the service can safely execute or serve the intended workload.", "rationale": "A reachable web endpoint does not establish runtime compatibility, sufficient capacity or appropriate separation between hosted workloads.", "layers": [ { "id": "execution-and-persistence", "name": "Execution and persistence", "description": "Describes supported application behaviour and the persistence of hosted data.", "findings": [ { "id": "web-workload-contract", "name": "Web workload contract", "description": "Records supported runtimes, request execution limits, background work and storage behaviour.", "questions": [ { "text": "Which static or executable workloads, runtime versions, background tasks and connection types are supported?", "kind": "definition", "id": "web-workload-contract-q01" }, { "text": "Which files and application data survive restarts, redeployments and scaling, and which require an external persistence service?", "kind": "boundary", "id": "web-workload-contract-q02" } ] } ] }, { "id": "capacity-and-tenant-separation", "name": "Capacity and tenant separation", "description": "Captures allocation limits and separation between sites, accounts and environments.", "findings": [ { "id": "resource-and-isolation-envelope", "name": "Resource and isolation envelope", "description": "Records resource ceilings, contention behaviour and the boundaries protecting hosted workloads.", "questions": [ { "text": "What resource limits and current consumption apply, and what happens when storage, traffic, execution or concurrency allowances are exceeded?", "kind": "measurement", "id": "resource-and-isolation-envelope-q01" }, { "text": "How are hosted sites and environments separated for processes, files, credentials and resource consumption, and which protections remain unverified?", "kind": "boundary", "id": "resource-and-isolation-envelope-q02" } ] } ] } ] }, { "id": "deployment-and-web-delivery", "name": "Deployment and web delivery", "description": "Connects deployed releases to the hostnames and request paths through which visitors reach them.", "rationale": "Deployment success, domain routing and HTTPS readiness are separate conditions that must align for a site to be served correctly.", "layers": [ { "id": "release-publication", "name": "Release publication", "description": "Captures how content or application releases enter service.", "findings": [ { "id": "deployment-state-and-reversibility", "name": "Deployment state and reversibility", "description": "Records the active release, its origin and the conditions for safe promotion or rollback.", "questions": [ { "text": "Which artifact, repository revision or content snapshot is currently served in each environment, and what deployment record establishes that?", "kind": "provenance", "id": "deployment-state-and-reversibility-q01" }, { "text": "How can the agent validate, promote or roll back a release, and what happens to persistent data and in-flight requests during those operations?", "kind": "action", "id": "deployment-state-and-reversibility-q02" } ] } ] }, { "id": "hostname-and-request-routing", "name": "Hostname and request routing", "description": "Captures the route from a requested hostname to the intended hosted release.", "findings": [ { "id": "public-delivery-chain", "name": "Public delivery chain", "description": "Records domain bindings, certificate status and any proxy or cache dependencies affecting delivery.", "questions": [ { "text": "Which hostnames, redirects, TLS termination points and optional CDN or proxy services lead to each deployment, and which components are outside this hosting service?", "kind": "boundary", "id": "public-delivery-chain-q01" }, { "text": "Do current checks confirm that each intended hostname serves the expected release over HTTPS with a valid certificate?", "kind": "measurement", "id": "public-delivery-chain-q02" } ] } ] } ] }, { "id": "hosting-health-and-recovery", "name": "Hosting health and recovery", "description": "Captures evidence of usable web delivery and the means to recover from failure or compromise.", "rationale": "Provider status, site reachability and application correctness can diverge, while backups may cover only part of a hosted site.", "layers": [ { "id": "delivery-observation-and-incidents", "name": "Delivery observation and incidents", "description": "Separates measured site behaviour from provider reports and contractual availability targets.", "findings": [ { "id": "serving-health-evidence", "name": "Serving health evidence", "description": "Records endpoint observations, hosting diagnostics and unresolved incident attribution.", "questions": [ { "text": "What do recent endpoint checks show about reachability, latency and errors, and from which locations and time windows?", "kind": "measurement", "id": "serving-health-evidence-q01" }, { "text": "Which logs, provider notices or diagnostic observations support attributing a failure to hosting, deployment, DNS or an external dependency?", "kind": "provenance", "id": "serving-health-evidence-q02" } ] } ] }, { "id": "restoration-and-containment", "name": "Restoration and containment", "description": "Captures practical recovery coverage and hosting controls available during an incident.", "findings": [ { "id": "recoverable-hosted-state", "name": "Recoverable hosted state", "description": "Records recoverable content, configuration and data, together with authorised containment and restoration actions.", "questions": [ { "text": "Which hosted assets and settings have recoverable copies, how old are they, and what evidence shows that restoration has been tested?", "kind": "measurement", "id": "recoverable-hosted-state-q01" }, { "text": "Which controls can isolate a compromised site, revoke deployment credentials or restore a known release, and what downtime or data loss could follow?", "kind": "action", "id": "recoverable-hosted-state-q02" } ] } ] } ] }, { "id": "service-terms-and-exit", "name": "Service terms and exit", "description": "Captures the commitments and lifecycle conditions governing continued hosting and departure.", "rationale": "An agent must account for hosting charges, use restrictions and data-retention consequences before changing capacity or ending service.", "layers": [ { "id": "entitlements-and-restrictions", "name": "Entitlements and restrictions", "description": "Records the applicable plan, commitments and constraints on hosted activity.", "findings": [ { "id": "hosting-service-commitments", "name": "Hosting service commitments", "description": "Connects the active hosting arrangement to its applicable commercial and operational terms.", "questions": [ { "text": "Which current plan and terms establish charges, allowances, support coverage, availability commitments and suspension triggers?", "kind": "provenance", "id": "hosting-service-commitments-q01" }, { "text": "Which restrictions on hosted content, workload behaviour, processing location or traffic affect the intended use?", "kind": "boundary", "id": "hosting-service-commitments-q02" } ] } ] }, { "id": "migration-and-retirement", "name": "Migration and retirement", "description": "Captures what must be preserved, transferred or disconnected when hosting ends.", "findings": [ { "id": "hosting-exit-readiness", "name": "Hosting exit readiness", "description": "Records exportability, dependencies and the consequences of cancellation or expiration.", "questions": [ { "text": "Which content, application data, configuration and domain bindings can be transferred, and which depend on provider-specific facilities?", "kind": "boundary", "id": "hosting-exit-readiness-q01" }, { "text": "What verified export, cutover and retention conditions must be satisfied before cancellation, and when would serving access and stored data be lost?", "kind": "action", "id": "hosting-exit-readiness-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Shared hosting", "Virtual private server (VPS) hosting", "Dedicated-server hosting", "Cloud / IaaS web hosting", "Managed WordPress and CMS hosting", "Reseller hosting", "Colocation", "Platform-as-a-Service (PaaS) application hosting" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q1851760", "note": "item 'web hosting service'" } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ISO/IEC 17788:2014 - ISO/IEC (cloud vocabulary covering hosting as a cloud service)" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "A small business buys a shared-hosting plan so its public website and email stay online without running its own server." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Monthly uptime", "typical_range": "99.9-99.99", "unit": "%" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Provider outage takes customer sites offline" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "EU hosting is commonly sold with GDPR-bound data-residency options; US commodity hosting is more often priced without a residency guarantee." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Content delivery network (CDN)", "difference": "A CDN caches and distributes copies of content; a web hosting service originates and stores the canonical site or application." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of web hosting service this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should this registry entry cover general-purpose virtual servers configured for web serving, or only offerings with an explicit web-hosting service boundary?", "When hosting is embedded in a site builder, managed CMS or application platform, what criterion determines whether it warrants a separate service model instance?", "What is the authoritative unit of identity: a hosting subscription, an independently managed site allocation, or another provider-defined service unit?", "Which adjacent Vercy models already own deployment releases, CDN services, certificates and service agreements, and what should this model record only by reference?", "What minimum evidence and freshness requirements should govern claims that hosting is healthy, isolated or recoverable?" ], "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 hosting service, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a web hosting service, assess its ability to serve a particular website or web application, and determine which deployment, operational and lifecycle actions are permitted.", "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: website hosting, backup hosting, free web hosting service, reseller web hosting, dedicated hosting service, wiki hosting service, shared web hosting service, Bulletproof hosting, Clustered web hosting, Peer-to-peer web hosting, self-hosting, phlog hosting service.", "12 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 64 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 hosting service, 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": [ "website hosting", "backup hosting", "free web hosting service", "reseller web hosting", "dedicated hosting service", "wiki hosting service", "shared web hosting service", "Bulletproof hosting", "Clustered web hosting", "Peer-to-peer web hosting", "self-hosting", "phlog hosting service" ] } ], "standing": "Described in 64 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 12 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 hosting service from another, and a web hosting service 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 hosting service, 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 hosting service, 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 hosting service 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 hosting service, 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 hosting service, 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 hosting service 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 hosting service 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 hosting service, 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 hosting service, 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 hosting service 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 hosting service from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a web hosting service, 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 hosting service, 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 hosting service 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 hosting service 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 hosting service between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a web hosting service, 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 hosting service, 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 hosting service 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 hosting service, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a web hosting service 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 hosting service, 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 hosting service, 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 hosting service 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 hosting service 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 hosting service, 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 hosting service and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a web hosting service, 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 hosting service, 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 hosting service 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 hosting service consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a web hosting service 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 hosting service, 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 hosting service, 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 hosting service 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 hosting service 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 hosting service 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 hosting service 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 hosting service 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 hosting service?", "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 hosting service?", "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 hosting service 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 hosting service and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a web hosting service, 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 hosting service, 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 hosting service 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 hosting service is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a web hosting service, 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 hosting service, 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 hosting service 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 } } } }