{ "model": { "rank": 1077, "code": "thing-q9135", "model_id": "vr.tr.operating-system", "name": "operating system", "purpose": "Let an agent identify which operating system and version a device runs, explain what the system is responsible for, relay support lifecycles, security update and compatibility information from vendors, and separate the operating system from firmware, applications and hardware.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q9135/", "tier": 2, "score": 186, "payload": { "layer": "wikidata", "aliases": [ "BIOS", "ABIOS", "Flash BIOS", "IBM PC ROM BIOS", "television operating system", "mobile operating system", "proprietary operating system", "operating environment", "smartwatch operating system", "free operating system", "AmigaDOS", "Guardian", "embedded operating system", "WebAssembly System Interface", "visionOS", "Debian derivatives", "Microsoft Windows", "Unix-like operating system", "cross-platform", "real-time operating system", "network operating system", "single-user operating system", "multi-user operating system", "multi-tasking operating system", "single-tasking operating system", "library operating system", "templated operating system", "single address space operating system", "live distribution", "Trusted operating system", "security-focused operating system", "operating system distribution", "WoW64", "Mac operating system", "hobbyist operating system", "distributed operating system", "disk operating system", "AmigaOS-like operating system", "NewDos/80", "Object-oriented operating system" ], "aliasCount": 79, "merged": 79, "knownIn": 186, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q9135", "url": "https://www.wikidata.org/wiki/Q9135", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T19:36:31Z", "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": 3, "engine": "claude" }, "metaModel": { "id": "THING-Q9135", "registryId": "vr.tr.operating-system", "name": "operating system", "version": "0.2.0-wave.3", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q9135/", "model": { "registry_id": "vr.tr.operating-system", "name": "operating system", "purpose": "Let an agent identify which operating system and version a device runs, explain what the system is responsible for, relay support lifecycles, security update and compatibility information from vendors, and separate the operating system from firmware, applications and hardware.", "definition": "The system software that manages a computer or device: it controls hardware, schedules processes, manages memory, storage, files, devices, networking and security, and provides the interfaces that application programs and users depend on; examples include Windows, macOS, Linux distributions, Android, iOS and real-time systems for embedded devices.", "what_it_is_for": "Running a computer and the programs on it.", "affordances": [ "identify the system and version on a device", "explain what the operating system does", "relay support and update information", "compare systems for a use case" ], "distinguishing_features": [ "Sits between hardware and applications", "Owns processes, memory, files, devices and access control", "Has a version and a support lifecycle", "Firmware and applications are separate layers" ], "appearance": "Not visible as an object; seen through its user interface, its name and version in settings, and its command shell.", "visual_identification": [ "Name and version shown in system settings or by a command", "Kernel, shell and package manager identify a Linux distribution", "Firmware such as BIOS or UEFI starts the machine and is not the operating system" ], "physical_properties": [], "families_and_kinds": [ "desktop and laptop systems such as Windows, macOS and Linux distributions", "mobile systems such as Android and iOS", "server systems", "real-time and embedded systems", "systems for televisions, cars and appliances" ], "related_models": [ { "relation": "is a kind of", "target": "system software", "why": "the category" }, { "relation": "runs on", "target": "computer", "why": "the hardware it manages" }, { "relation": "is confused with", "target": "firmware", "why": "BIOS and UEFI start the machine but are a different layer" }, { "relation": "runs", "target": "application software", "why": "what the system exists to host" } ], "identifiers": [ { "scheme": "name and version", "value_or_pattern": "vendor naming", "note": "shown in settings" }, { "scheme": "kernel version", "value_or_pattern": "numeric", "note": "for Linux and similar systems" }, { "scheme": "build number", "value_or_pattern": "vendor specific", "note": "identifies the exact release" } ], "standards_and_regulation": [ "POSIX from IEEE for interfaces", "Vendor support lifecycle policies", "Security certification schemes such as Common Criteria", "Accessibility requirements in public procurement" ], "failure_modes_and_hazards": [ "Unsupported versions without security updates", "Driver and hardware incompatibility", "Data loss during upgrades", "Malware exploiting system vulnerabilities" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "identify", "name": "Identify", "description": "Which system this is.", "rationale": "Everything depends on the system and version.", "layers": [ { "id": "which", "name": "Which system", "description": "Name and version.", "findings": [ { "id": "which-finding", "name": "Which", "description": "Which.", "questions": [ { "text": "Which operating system and version does the device run, and how is that read?", "kind": "definition" }, { "text": "Is the question about the operating system, the firmware or an application?", "kind": "boundary" } ] } ] }, { "id": "lifecycle", "name": "Lifecycle", "description": "Support status.", "findings": [ { "id": "lifecycle-finding", "name": "Lifecycle", "description": "Lifecycle.", "questions": [ { "text": "Is this version still supported, and when does support end according to the vendor?", "kind": "provenance" }, { "text": "Where is the lifecycle policy published?", "kind": "action" } ] } ] } ] }, { "id": "function", "name": "Function", "description": "What it does.", "rationale": "Responsibilities define the system.", "layers": [ { "id": "core", "name": "Core", "description": "Kernel duties.", "findings": [ { "id": "core-finding", "name": "Core", "description": "Core.", "questions": [ { "text": "How does the system manage processes, memory, storage and devices?", "kind": "definition" }, { "text": "Which entry fits file systems or networking in depth?", "kind": "action" } ] } ] }, { "id": "interfaces", "name": "Interfaces", "description": "User and program interfaces.", "findings": [ { "id": "interfaces-finding", "name": "Interfaces", "description": "Interfaces.", "questions": [ { "text": "What interfaces does the system offer to users and to programs?", "kind": "definition" }, { "text": "Which standards govern those interfaces?", "kind": "provenance" } ] } ] } ] }, { "id": "operate", "name": "Operate", "description": "Running and securing.", "rationale": "Systems need care.", "layers": [ { "id": "updates", "name": "Updates", "description": "Updates and patches.", "findings": [ { "id": "updates-finding", "name": "Updates", "description": "Updates.", "questions": [ { "text": "How are updates delivered, and what does the vendor advise about applying them?", "kind": "provenance" }, { "text": "Is the user asking for help with a specific device, which needs its vendor support?", "kind": "boundary" } ] } ] }, { "id": "security", "name": "Security", "description": "Security.", "findings": [ { "id": "security-finding", "name": "Security", "description": "Security.", "questions": [ { "text": "What security features and hardening guidance do vendors and agencies publish?", "kind": "provenance" }, { "text": "Which entry fits malware and incidents?", "kind": "action" } ] } ] } ] }, { "id": "choose", "name": "Choose", "description": "Comparing and learning.", "rationale": "Choice and study.", "layers": [ { "id": "compare", "name": "Compare", "description": "Comparison.", "findings": [ { "id": "compare-finding", "name": "Compare", "description": "Compare.", "questions": [ { "text": "How do systems compare for a given use case in compatibility, licensing and support?", "kind": "measurement" }, { "text": "Which criteria matter for the user?", "kind": "action" } ] } ] }, { "id": "learn", "name": "Learn", "description": "Study.", "findings": [ { "id": "learn-finding", "name": "Learn", "description": "Learn.", "questions": [ { "text": "How are operating systems taught and studied, and which references are standard?", "kind": "provenance" }, { "text": "How did operating systems develop historically?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should each operating system be a separate entry?", "How should support lifecycle dates be linked?", "The registry entry has merged BIOS aliases, which are firmware; should they be split off?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "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 operating system, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent identify which operating system and version a device runs, explain what the system is responsible for, relay support lifecycles, security update and compatibility information from vendors, and separate the operating system from firmware, applications and hardware.", "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: BIOS, ABIOS, Flash BIOS, IBM PC ROM BIOS, television operating system, mobile operating system, proprietary operating system, operating environment, smartwatch operating system, free operating system, AmigaDOS, Guardian.", "79 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 186 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 operating system, 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": [ "BIOS", "ABIOS", "Flash BIOS", "IBM PC ROM BIOS", "television operating system", "mobile operating system", "proprietary operating system", "operating environment", "smartwatch operating system", "free operating system", "AmigaDOS", "Guardian" ] } ], "standing": "Described in 186 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 79 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 operating system from another, and a operating system 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 operating system, 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 operating system, 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 operating system 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 operating system, 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 operating system, 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 operating system 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 operating system 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 operating system, 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 operating system, 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 operating system 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 operating system from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a operating system, 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 operating system, 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 operating system 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 operating system 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 operating system, 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 operating system, 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 operating system 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 operating system is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a operating system, 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 operating system, 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 operating system 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 operating system is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a operating system, 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 operating system, 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 operating system 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 operating system 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 operating system is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a operating system, 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 operating system, 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 operating system 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 operating system 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 operating system, 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 operating system, 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 operating system 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 operating system 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 operating system between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a operating system, 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 operating system, 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 operating system 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 operating system, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a operating system 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 operating system, 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 operating system, 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 operating system 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 operating system 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 operating system 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 operating system, 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 operating system 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 operating system 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 operating system 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 operating system 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 operating system 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 operating system, 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 operating system 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 operating system and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a operating system, 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 operating system, 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 operating system 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 operating system is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a operating system, 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 operating system, 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 operating system 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 } } } }