{ "model": { "rank": 3392, "code": "thing-q483639", "model_id": "vr.tr.cloud-computing", "name": "cloud computing", "purpose": "Enable an AI agent to recognise cloud computing arrangements, assess their operational and governance state, and determine which resource and service actions are justified.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q483639/", "tier": 2, "score": 86, "payload": { "layer": "wikidata", "aliases": [ "cloud storage", "hybrid cloud storage", "Oracle Cloud Storage", "personal cloud", "block-level storage", "Elastic cloud storage", "CloudLocker", "Developer Portal", "Green cloud computing", "serverless computing", "mobile cloud computing", "platform as a service", "infrastructure as a service", "recovery as a service", "GeoAIaaS", "cloud hosting", "private cloud computing infrastructure", "Intel Tiber Developer Cloud", "private cloud", "Combat cloud", "model as a service", "cooperative storage cloud", "HP ePrint", "public cloud", "Managed private cloud", "Cloud native computing", "Secure Access Service Edge" ], "aliasCount": 27, "merged": 27, "knownIn": 86, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q483639", "url": "https://www.wikidata.org/wiki/Q483639", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:38:25Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.7, "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: 01a07c4c-fe84-7db1-b705-63efe6bc00ec\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: cloud computing\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 546 things:\n# Batch 003: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 89.9, "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: 01a07c4c-fe72-7f43-9062-5fae1277da78\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: cloud computing\nRegistry id: vr.tr.cloud-computing\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (" } } }, "metaModel": { "id": "THING-Q483639", "registryId": "vr.tr.cloud-computing", "name": "cloud computing", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q483639/", "model": { "registry_id": "vr.tr.cloud-computing", "name": "cloud computing", "purpose": "Enable an AI agent to recognise cloud computing arrangements, assess their operational and governance state, and determine which resource and service actions are justified.", "definition": "Cloud computing is a model for enabling on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service-provider interaction.", "scope_statement": "This model owns cloud computing as a way of providing and consuming configurable computing resources as services, including provisioning, shared capacity, elasticity, metering, and responsibility boundaries; it does not treat cloud computing as a single physical device despite its registry placement in PHY / PHY.OBJ.", "in_scope": [ "Cloud qualification and service delivery characteristics", "Service and deployment models and their responsibility boundaries", "Resource placement, tenancy, connectivity, and dependencies", "Provisioning, scaling, resilience, and service lifecycle", "Identity, data governance, consumption accounting, and exit conditions" ], "out_of_scope": [ "Physical design and maintenance of servers, storage devices, and data centres", "Application business logic and domain-specific correctness", "General internet infrastructure and telecommunications service models", "Virtualisation and container technology considered independently of cloud service delivery", "Cloud provider corporate structure and general procurement processes" ], "distinguishing_features": [ "A consumer can obtain configurable resources through an on-demand service interface without a separate manual provider intervention for every allocation.", "Resources are accessible over a network through defined service interfaces; remote access alone does not establish that an arrangement is cloud computing.", "Capacity comes from a managed resource pool with allocations abstracted from particular physical machines; virtualisation alone is insufficient.", "Capacity can expand and contract through supported allocation mechanisms, subject to quotas and actual availability; a fixed hosted server does not establish elasticity.", "Resource use is measured at defined service boundaries, even when the charging arrangement is not pay-per-use." ], "characteristics": [ { "name": "Service model", "kind": "category", "unit_or_values": "IaaS, PaaS, SaaS, mixed, or unresolved; record the capabilities exposed", "why_it_matters": "Determines which infrastructure and software layers the consumer can configure and must operate." }, { "name": "Deployment model", "kind": "category", "unit_or_values": "Public, private, community, hybrid, or unresolved", "why_it_matters": "Distinguishes access and organisational arrangements from the service model." }, { "name": "Provisioning latency", "kind": "measurement", "unit_or_values": "Seconds or minutes from accepted request to usable resource, with resource type and percentile", "why_it_matters": "Tests whether capacity can arrive within workload and recovery deadlines." }, { "name": "Elasticity envelope", "kind": "measurement", "unit_or_values": "Minimum and maximum capacity in service-specific units, plus scale-out and scale-in rates", "why_it_matters": "Makes scaling limits explicit instead of assuming unlimited capacity." }, { "name": "Allocation headroom", "kind": "measurement", "unit_or_values": "Quota minus current allocation, in vCPU, GiB, requests per second, or other defined service units", "why_it_matters": "Identifies quota constraints while keeping quota distinct from guaranteed physical capacity." }, { "name": "Tenancy isolation", "kind": "category", "unit_or_values": "Shared or dedicated at specified compute, storage, network, and control-plane boundaries; unknown where unverified", "why_it_matters": "Supports assessment of interference, access separation, and placement requirements." }, { "name": "Responsibility allocation", "kind": "relation", "unit_or_values": "Provider, consumer, and third-party duties mapped to each service component", "why_it_matters": "Prevents security, recovery, and maintenance tasks from falling between parties." }, { "name": "Resource lifecycle state", "kind": "state", "unit_or_values": "Requested, provisioning, ready, degraded, suspended, deleting, deleted, or failed", "why_it_matters": "Constrains valid operations and distinguishes requested changes from completed changes." }, { "name": "Service availability", "kind": "measurement", "unit_or_values": "Successful eligible requests or available time as a percentage over a specified window", "why_it_matters": "Allows evaluation against workload objectives using an explicit measurement boundary." }, { "name": "Recovery objectives", "kind": "measurement", "unit_or_values": "Recovery time objective and recovery point objective in seconds, minutes, or hours", "why_it_matters": "Connects outage and data-loss tolerances to recovery design and testing." }, { "name": "Data location", "kind": "relation", "unit_or_values": "Data classes linked to primary, replica, backup, log, and processing locations", "why_it_matters": "Exposes data movement that a single selected region may not describe." }, { "name": "Consumption and cost", "kind": "measurement", "unit_or_values": "Metered units and currency per billing interval, with rates, commitments, and transfer charges", "why_it_matters": "Supports attribution, forecasting, and comparison of feasible deployment actions." } ], "affordances": [ "Classify an arrangement as cloud computing, another hosting arrangement, or unresolved using recorded evidence.", "Provision, resize, scale, suspend, or retire resources within verified permissions and service limits.", "Select service and placement options against workload, isolation, location, and recovery requirements.", "Evaluate service health and initiate authorised failover or restoration procedures.", "Attribute consumption and estimate the cost consequences of scaling, replication, and data transfer.", "Assess and execute authorised workload and data migration using verified export and deletion capabilities." ] }, "sources": [], "structure": { "bundles": [ { "id": "cloud-service-identity", "name": "Cloud service identity", "description": "Establishes what makes the arrangement cloud computing and identifies the service boundary being modelled.", "rationale": "Remote hosting, virtual machines, and cloud-branded products cannot be distinguished reliably by their names.", "layers": [ { "id": "cloud-qualification", "name": "Cloud qualification", "description": "Examines observable resource delivery characteristics.", "findings": [ { "id": "essential-service-behaviours", "name": "Essential service behaviours", "description": "Record evidence for on-demand self-service, network access, resource pooling, elasticity, and measured use.", "questions": [ { "text": "Which interfaces and observed behaviours demonstrate each cloud characteristic for this arrangement?", "kind": "definition", "id": "essential-service-behaviours-q01" }, { "text": "Which missing or unverified characteristics leave its classification as cloud computing unresolved?", "kind": "boundary", "id": "essential-service-behaviours-q02" } ] } ] }, { "id": "service-abstraction", "name": "Service abstraction", "description": "Separates the cloud delivery model from individual offerings and deployed resources.", "findings": [ { "id": "consumer-control-surface", "name": "Consumer control surface", "description": "Describe the capabilities supplied and the configuration authority retained by the consumer.", "questions": [ { "text": "Does the consumer control infrastructure, an application deployment environment, application settings, or a combination?", "kind": "boundary", "id": "consumer-control-surface-q01" }, { "text": "Which service documentation and version establish the available configuration and operating responsibilities?", "kind": "provenance", "id": "consumer-control-surface-q02" } ] } ] } ] }, { "id": "resource-pooling-and-placement", "name": "Resource pooling and placement", "description": "Captures how pooled capacity is partitioned, located, and connected.", "rationale": "Cloud resource identifiers conceal physical placement and shared dependencies that affect isolation and failure exposure.", "layers": [ { "id": "tenancy-and-allocation", "name": "Tenancy and allocation", "description": "Identifies sharing boundaries and constraints on obtaining capacity.", "findings": [ { "id": "pool-isolation-and-capacity", "name": "Pool isolation and capacity", "description": "Distinguish logical isolation, dedicated allocation, administrative quotas, and actual capacity availability.", "questions": [ { "text": "At which compute, storage, network, and management boundaries are resources shared or dedicated?", "kind": "boundary", "id": "pool-isolation-and-capacity-q01" }, { "text": "What quotas, reservations, and observed allocation failures limit usable capacity in the selected location?", "kind": "measurement", "id": "pool-isolation-and-capacity-q02" } ] } ] }, { "id": "placement-and-connectivity", "name": "Placement and connectivity", "description": "Maps resource locations, network paths, and dependencies relevant to workload behaviour.", "findings": [ { "id": "location-and-dependency-map", "name": "Location and dependency map", "description": "Record regions, failure domains, endpoints, and cross-location service dependencies without assuming provider labels imply independence.", "questions": [ { "text": "Which regions, failure domains, network paths, and external services does the deployment depend on?", "kind": "boundary", "id": "location-and-dependency-map-q01" }, { "text": "What measured latency, throughput, and transfer volume constrain placement or cross-location operation?", "kind": "measurement", "id": "location-and-dependency-map-q02" } ] } ] } ] }, { "id": "provisioning-and-elasticity", "name": "Provisioning and elasticity", "description": "Models resource requests, lifecycle transitions, and changes in allocated capacity.", "rationale": "Cloud actions are often asynchronous and constrained by quotas, warm-up time, and stateful workload behaviour.", "layers": [ { "id": "resource-lifecycle", "name": "Resource lifecycle", "description": "Tracks requested configuration, observed state, and completion evidence.", "findings": [ { "id": "provisioning-state-and-reconciliation", "name": "Provisioning state and reconciliation", "description": "Record how resource operations complete, fail, retry, and converge on intended configuration.", "questions": [ { "text": "What evidence establishes that a requested resource is usable rather than merely accepted by the control plane?", "kind": "measurement", "id": "provisioning-state-and-reconciliation-q01" }, { "text": "How can an agent retry or reconcile a failed operation without creating duplicate resources or orphaned charges?", "kind": "action", "id": "provisioning-state-and-reconciliation-q02" } ] } ] }, { "id": "elastic-capacity-control", "name": "Elastic capacity control", "description": "Connects demand signals to supported scaling actions and limits.", "findings": [ { "id": "scaling-envelope-and-triggers", "name": "Scaling envelope and triggers", "description": "Specify scaling dimensions, trigger signals, delays, and conditions for safely removing capacity.", "questions": [ { "text": "What capacity range and response time can scaling achieve under the relevant quotas and workload conditions?", "kind": "measurement", "id": "scaling-envelope-and-triggers-q01" }, { "text": "Which signals permit scale-out or scale-in, and what draining or state-transfer steps must precede capacity removal?", "kind": "action", "id": "scaling-envelope-and-triggers-q02" } ] } ] } ] }, { "id": "service-continuity-and-recovery", "name": "Service continuity and recovery", "description": "Relates cloud service health and dependency failures to workload availability and recoverability.", "rationale": "A provider service commitment does not establish that a particular deployment survives outages or data loss.", "layers": [ { "id": "health-and-failure-boundaries", "name": "Health and failure boundaries", "description": "Distinguishes workload health, service commitments, and shared failure exposure.", "findings": [ { "id": "availability-evidence", "name": "Availability evidence", "description": "Record health indicators and availability calculations at the consumer-visible service boundary.", "questions": [ { "text": "Which indicators distinguish application failure, data-plane failure, and loss of management access?", "kind": "measurement", "id": "availability-evidence-q01" }, { "text": "Which dependencies can fail together, and how does that affect claims of zone or region redundancy?", "kind": "boundary", "id": "availability-evidence-q02" } ] } ] }, { "id": "backup-and-failover", "name": "Backup and failover", "description": "Examines whether recovery mechanisms meet stated workload objectives.", "findings": [ { "id": "tested-recovery-capability", "name": "Tested recovery capability", "description": "Separate replication, backup, restoration, and failover, recording evidence of their outcomes.", "questions": [ { "text": "What recovery time and recoverable data point were demonstrated by the most recent relevant recovery test?", "kind": "measurement", "id": "tested-recovery-capability-q01" }, { "text": "What permissions, dependencies, and consistency checks are required before failover or restoration can proceed?", "kind": "action", "id": "tested-recovery-capability-q02" } ] } ] } ] }, { "id": "cloud-trust-and-data-governance", "name": "Cloud trust and data governance", "description": "Defines administrative authority, shared duties, and controls over data across managed services.", "rationale": "Cloud consumers delegate operation while retaining responsibilities that vary by service and data flow.", "layers": [ { "id": "identity-and-shared-responsibility", "name": "Identity and shared responsibility", "description": "Maps actors, privileges, and security duties to the cloud service boundary.", "findings": [ { "id": "authority-and-control-ownership", "name": "Authority and control ownership", "description": "Identify who may operate resources and who owns patching, configuration, access review, and incident response.", "questions": [ { "text": "Which provider, consumer, and third-party actors own each relevant security and operational control?", "kind": "boundary", "id": "authority-and-control-ownership-q01" }, { "text": "Which identity, role, and approval conditions authorise an agent to change resources or access their data?", "kind": "action", "id": "authority-and-control-ownership-q02" } ] } ] }, { "id": "data-location-and-protection", "name": "Data location and protection", "description": "Tracks data copies, processing locations, encryption control, and retention behaviour.", "findings": [ { "id": "data-custody-across-services", "name": "Data custody across services", "description": "Account for primary data, replicas, backups, logs, and service-generated copies as distinct custody paths.", "questions": [ { "text": "Where are each data class and its derived copies stored or processed, and who controls access and encryption keys?", "kind": "boundary", "id": "data-custody-across-services-q01" }, { "text": "Which read contractual terms, configuration records, or audit evidence support location, retention, and deletion claims?", "kind": "provenance", "id": "data-custody-across-services-q02" } ] } ] } ] }, { "id": "cloud-economics-and-exit", "name": "Cloud economics and exit", "description": "Connects metered consumption to cost and assesses the practical ability to leave or replace services.", "rationale": "Elastic consumption, transfer charges, commitments, and proprietary dependencies can change which actions are feasible.", "layers": [ { "id": "metering-and-cost-attribution", "name": "Metering and cost attribution", "description": "Identifies chargeable dimensions and attributes them to workloads and decisions.", "findings": [ { "id": "usage-to-charge-reconciliation", "name": "Usage-to-charge reconciliation", "description": "Record meter definitions, rate applicability, commitments, and costs that persist after compute stops.", "questions": [ { "text": "Which compute, storage, request, licence, and data-transfer meters contribute to the workload's cost?", "kind": "measurement", "id": "usage-to-charge-reconciliation-q01" }, { "text": "What incremental and continuing charges would follow scaling, suspension, replication, or deletion?", "kind": "action", "id": "usage-to-charge-reconciliation-q02" } ] } ] }, { "id": "portability-and-service-exit", "name": "Portability and service exit", "description": "Examines export, replacement dependencies, migration effort, and termination completion.", "findings": [ { "id": "workload-and-data-exit-path", "name": "Workload and data exit path", "description": "Assess whether data, configuration, identities, and service behaviour can be transferred or reconstructed elsewhere.", "questions": [ { "text": "Which proprietary APIs, formats, identity bindings, and managed behaviours require replacement during migration?", "kind": "boundary", "id": "workload-and-data-exit-path-q01" }, { "text": "What verified export, cutover, retained-copy handling, and resource-closure steps complete an exit within time and cost limits?", "kind": "action", "id": "workload-and-data-exit-path-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": [ "This describes the computing service model, not a physical object; the supplied PHY.OBJ classification warrants review.", "The kinds list combines two independent classifications: service models and deployment models; community cloud is another recognized deployment model.", "Standards are recalled without source inspection; editions and applicability need verification. No universal capacity, latency or availability range applies." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of cloud computing 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": [ "Infrastructure as a service (IaaS)", "Platform as a service (PaaS)", "Software as a service (SaaS)", "Public cloud", "Private cloud", "Hybrid cloud" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of cloud computing 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": [ "NIST SP 800-145, The NIST Definition of Cloud Computing - National Institute of Standards and Technology.", "ISO/IEC 22123-1, Cloud computing - Vocabulary - ISO and IEC.", "ISO/IEC 27017, guidance on information security controls for cloud services - ISO and IEC.", "ISO/IEC 27018, protection of personally identifiable information in public clouds acting as PII processors - ISO and IEC." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of cloud computing 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": [ "Hosting applications and websites with capacity adjusted to demand.", "Storing data and supporting backup and disaster recovery.", "Running analytics, scientific workloads and machine-learning training.", "Delivering business software through network-accessible services.", "Provisioning development and testing environments." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of cloud computing 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": [ "Provider, regional or network outages can make services unavailable.", "Misconfigured access controls or compromised credentials can expose data and resources.", "Resource contention, quotas and service limits can impair performance or prevent scaling.", "Uncontrolled consumption and data-transfer charges can produce unexpected costs.", "Provider-specific interfaces and data dependencies can make migration difficult." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of cloud computing 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": [ "Data residency, privacy and cross-border transfer requirements vary by jurisdiction.", "Available regions, services, network connectivity and prices differ geographically." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of cloud computing 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": "Virtualization", "difference": "Virtualization abstracts computing resources; cloud computing adds a service model with on-demand access, resource pooling, elasticity and measured usage." }, { "name": "Traditional hosting", "difference": "Hosting alone need not provide on-demand self-service, rapid elasticity or pooled resources characteristic of cloud computing." }, { "name": "Distributed computing", "difference": "Distributed computing concerns coordinated computation across multiple computers; it does not necessarily provide cloud service characteristics." }, { "name": "Edge computing", "difference": "Edge computing places processing near data sources or users; cloud computing describes resource delivery and management, and the two can overlap." }, { "name": "Data center", "difference": "A data center is a physical facility housing computing infrastructure; cloud computing is a service-delivery model that can use such facilities." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of cloud computing this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own cloud computing or its service-delivery abstraction, requiring this registry entry to link to it?", "How should the registry's PHY / PHY.OBJ placement relate to cloud computing's service and operational aspects without duplicating neighbouring models?", "Which authoritative definitions and versions should govern qualification, especially for arrangements with limited elasticity or dedicated capacity?", "Which provider-specific evidence is sufficient to substantiate isolation, failure-domain independence, data location, and deletion?", "How should composite, serverless, edge, and hybrid arrangements be represented when their components expose different responsibility and metering boundaries?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 19, "questions": 31 } }, "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 cloud computing, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise cloud computing arrangements, assess their operational and governance state, and determine which resource and service actions are justified.", "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: cloud storage, hybrid cloud storage, Oracle Cloud Storage, personal cloud, block-level storage, Elastic cloud storage, CloudLocker, Developer Portal, Green cloud computing, serverless computing, mobile cloud computing, platform as a service.", "27 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 86 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 cloud computing, 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": [ "cloud storage", "hybrid cloud storage", "Oracle Cloud Storage", "personal cloud", "block-level storage", "Elastic cloud storage", "CloudLocker", "Developer Portal", "Green cloud computing", "serverless computing", "mobile cloud computing", "platform as a service" ] } ], "standing": "Described in 86 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 27 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 cloud computing from another, and a cloud computing 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 cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a cloud computing 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 cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing 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 cloud computing, 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 cloud computing 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 cloud computing 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 cloud computing 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 cloud computing 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 cloud computing 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 cloud computing, 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 cloud computing 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 cloud computing and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a cloud computing, 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 cloud computing, 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 cloud computing 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 cloud computing is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a cloud computing, 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 cloud computing, 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 cloud computing 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 } } } }