{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T21:02:59Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 4, "engine": "claude", "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T11:00:00Z", "ingestedAt": "2026-10-06T07:33:41+00:00", "fields": [ "agent_conduct", "ethics", "owners" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-06T19:52:00+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q44127", "registryId": "vr.tr.server", "name": "server", "version": "0.2.0-wave.4", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q44127/", "model": { "registry_id": "vr.tr.server", "name": "server", "purpose": "Let an agent explain servers, relay architectures, types, hardware, software and security practices from computing sources, describe the named server types, and distinguish servers from clients, personal computers, data centres, cloud services and waiters in restaurants.", "definition": "A computer or software program that provides services, data or resources to other programs or devices called clients over a network, such as web, email, file, database, communications and remote desktop servers, running on dedicated servers, virtual machines or cloud infrastructure in data centres; the term covers both server computers and server software, and related infrastructure such as package repositories serves software packages to clients. Servers must be secured and maintained, and security incidents should be handled through incident response procedures.", "what_it_is_for": "Providing services to clients over networks.", "affordances": [ "explain client-server architecture", "relay types and hardware", "describe named server types", "relay security practices" ], "distinguishing_features": [ "Serves clients", "Always-on operation", "Hardware or software", "Security critical" ], "appearance": "Rack-mounted computers in data centres, or software processes with no visible form.", "visual_identification": [ "Computer or program serving clients over a network", "Package repository, communications server, server computer, remote desktop server, dedicated server, server software", "Clients request services; PCs serve individual users; data centres house servers; cloud services abstract servers; waiters serve food" ], "physical_properties": [ { "quantity": "common rack unit height", "typical_range": "1.75", "unit": "inches", "note": "1U" }, { "quantity": "client-server model", "typical_range": "dominant since the 1980s", "unit": "note", "note": "" }, { "quantity": "first web server", "typical_range": "1990", "unit": "year", "note": "CERN httpd" } ], "families_and_kinds": [ "web servers", "mail and communications servers", "database servers", "file servers", "remote desktop servers", "dedicated, virtual and cloud servers" ], "related_models": [ { "relation": "is a kind of", "target": "data processing system", "why": "in registry terms" }, { "relation": "is part of", "target": "client-server model", "why": "" }, { "relation": "is housed in", "target": "data center", "why": "" }, { "relation": "is contrasted with", "target": "client (computing)", "why": "" } ], "identifiers": [], "standards_and_regulation": [ "Information security standards such as ISO/IEC 27001", "Data protection laws such as GDPR", "Data centre energy efficiency rules" ], "failure_modes_and_hazards": [ "Security breaches and misconfiguration", "Outages and data loss", "Energy use of data centres" ], "in_scope": [], "out_of_scope": [], "characteristics": [], "agent_conduct": { "may": [ "Monitor, patch and back up servers it is authorized to administer.", "Report outages, security alerts and capacity problems to the operator." ], "must_not": [ "Access, scan or attack a server it is not authorized to use.", "Disable logging, backups or security controls to hide its own actions.", "Copy personal data from a server beyond the purpose it was given access for.", "Restart or shut down a production server without following the operator's change rules.", "Leave credentials or open services exposed after maintenance." ], "requires_human": [ "Deleting data or decommissioning a server.", "Granting new people administrative access." ] }, "ethics": { "considerations": [ "Servers hold other people's data; a breach exposes users who never chose the server.", "Outages can stop services people depend on, such as health or payments." ], "affected_parties": [ "Users whose data it holds", "Operators and administrators", "Services that depend on it" ] }, "owners": { "steward": "The operator who runs it; the owner of the hardware for physical servers.", "master_systems": [] } }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q44127: server", "url": "https://www.wikidata.org/wiki/Q44127", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Server (computing)", "url": "https://en.wikipedia.org/wiki/Server_%28computing%29", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What a server is.", "rationale": "Definition.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is a server, and how does it differ from clients, PCs, data centres, cloud services and restaurant servers?", "kind": "definition" }, { "text": "Is the question about setting one up, a security incident, hardware or concepts?", "kind": "boundary" } ] } ] }, { "id": "types", "name": "Types", "description": "Named types.", "findings": [ { "id": "types-finding", "name": "Types", "description": "Types.", "questions": [ { "text": "What are package repositories, communications, remote desktop and dedicated servers, and server software versus hardware?", "kind": "definition" }, { "text": "Which entry fits the specific type?", "kind": "action" } ] } ] } ] }, { "id": "architecture", "name": "Architecture", "description": "Architecture.", "rationale": "Sources.", "layers": [ { "id": "clientserver", "name": "Client-server", "description": "Client-server model.", "findings": [ { "id": "clientserver-finding", "name": "Client-server", "description": "Client-server.", "questions": [ { "text": "How does the client-server model work compared with peer-to-peer?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "hardware", "name": "Hardware", "description": "Server hardware.", "findings": [ { "id": "hardware-finding", "name": "Hardware", "description": "Hardware.", "questions": [ { "text": "How does server hardware differ from desktop hardware?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] } ] }, { "id": "operations", "name": "Operations", "description": "Operations and security.", "rationale": "Regulation.", "layers": [ { "id": "security", "name": "Security", "description": "Security.", "findings": [ { "id": "security-finding", "name": "Security", "description": "Security.", "questions": [ { "text": "What basic hardening and patching practices do security frameworks recommend?", "kind": "provenance" }, { "text": "Which entry fits hardening (computing)?", "kind": "action" } ] } ] }, { "id": "cloud", "name": "Cloud", "description": "Cloud and virtualisation.", "findings": [ { "id": "cloud-finding", "name": "Cloud", "description": "Cloud.", "questions": [ { "text": "How have virtualisation and cloud computing changed servers?", "kind": "provenance" }, { "text": "Which entry fits cloud computing?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "Impact.", "rationale": "Context.", "layers": [ { "id": "energy", "name": "Energy", "description": "Energy use.", "findings": [ { "id": "energy-finding", "name": "Energy", "description": "Energy.", "questions": [ { "text": "How much energy do data centres use, as the IEA reports?", "kind": "provenance" }, { "text": "Which entry fits data center?", "kind": "action" } ] } ] }, { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did servers evolve from mainframes to rack servers?", "kind": "provenance" }, { "text": "Which entry fits mainframe computer?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should server hardware and server software be separate entries?", "How should computing standards be linked?", "Should package repository be moved to software distribution?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }