{ "model": { "rank": 5070, "code": "thing-q131669", "model_id": "vr.tr.linux-distribution", "name": "Linux distribution", "purpose": "Enable an agent to recognise a Linux distribution, assess its suitability and maintenance state, and determine supported ways to obtain, deploy, update and retire it.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q131669/", "tier": 2, "score": 70, "payload": { "layer": "wikidata", "aliases": [ "Android distribution", "Linux on embedded systems", "LNX-BBC", "AOSC OS", "PuppyRus Linux", "FSF-endorsed operating systems", "lightweight Linux distribution", "Red Hat Enterprise Linux derivative" ], "aliasCount": 8, "merged": 8, "knownIn": 70, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q131669", "url": "https://www.wikidata.org/wiki/Q131669", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:36:11Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 22.6, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08818-9bcd-7ff0-a0ad-1850789001b7\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Linux distribution\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1", "usd": 0, "recall": true }, "codex": { "seconds": 62.2, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08818-9bcb-7f02-ad45-aed48b284f0b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Linux distribution\nRegistry id: vr.tr.linux-distribution\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this en" } } }, "metaModel": { "id": "THING-Q131669", "registryId": "vr.tr.linux-distribution", "name": "Linux distribution", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q131669/", "model": { "registry_id": "vr.tr.linux-distribution", "name": "Linux distribution", "purpose": "Enable an agent to recognise a Linux distribution, assess its suitability and maintenance state, and determine supported ways to obtain, deploy, update and retire it.", "definition": "A Linux distribution is a maintained collection of software built around the Linux kernel, with selected user-space components and mechanisms for installation, configuration and updates, supplied for use as an operating system.", "scope_statement": "This model owns Linux distribution as a kind of integrated operating-system offering built around the Linux kernel, including its composition, delivery, maintenance and governance; named distributions and releases are instances or versions described using this model.", "in_scope": [ "Distribution identity, lineage and integration boundaries", "Kernel, user-space and package composition policies", "Installation artifacts, repositories and software delivery mechanisms", "Release lifecycle, updates and security maintenance", "Supported deployment targets and distribution governance" ], "out_of_scope": [ "Linux kernel development and internal implementation", "Individual machines, virtual machines and their installed runtime state", "Standalone applications and upstream software projects", "Maintaining organisations as institutions", "Hardware design and physical device maintenance", "Non-Linux operating-system distributions" ], "distinguishing_features": [ "Uses the Linux kernel as its operating-system kernel; a Unix-like interface alone is insufficient.", "Integrates a selected user space and a delivery or assembly process; a kernel source tree alone is insufficient.", "Has an identifiable distribution boundary, such as an integrated release, repository set or reproducible build configuration, rather than an arbitrary collection of installed software.", "Separates the distribution identity from particular releases, installation images and running installations.", "Can deliver packages, complete system images or build recipes; neither a desktop interface nor GNU user-space components are required by the proposed scope." ], "characteristics": [ { "name": "Distribution lineage", "kind": "relation", "unit_or_values": "Independent origin or named upstream distribution, with the nature of derivation recorded", "why_it_matters": "Shows where integration choices and inherited maintenance dependencies originate." }, { "name": "User-space composition", "kind": "category", "unit_or_values": "Recorded C library, core utilities, init or service manager, and optional desktop stack", "why_it_matters": "Determines important runtime and administration compatibility boundaries." }, { "name": "System delivery model", "kind": "category", "unit_or_values": "Binary packages, source-based assembly, system images, declarative builds or a documented combination", "why_it_matters": "Determines how software is installed, changed and recovered." }, { "name": "Release model", "kind": "category", "unit_or_values": "Fixed releases, rolling updates, snapshots or a documented hybrid", "why_it_matters": "Determines how an agent interprets version identity and plans upgrades." }, { "name": "Supported execution targets", "kind": "relation", "unit_or_values": "Architecture, ABI, hardware platform and deployment environment, qualified by release", "why_it_matters": "Prevents selection of artifacts that cannot run on the intended target." }, { "name": "Maintenance status", "kind": "state", "unit_or_values": "Development, maintained, restricted maintenance, end of support or unknown, qualified by release and component scope", "why_it_matters": "Distinguishes available software from software that still receives relevant maintenance." }, { "name": "Declared support duration", "kind": "measurement", "unit_or_values": "Months or years from a specified milestone; indefinite or unspecified recorded explicitly", "why_it_matters": "Supports lifecycle planning without assuming that every component has the same support window." }, { "name": "Artifact verification mechanism", "kind": "category", "unit_or_values": "Signed repository metadata, signed packages, signed images, checksums or documented combinations", "why_it_matters": "Determines what authenticity and integrity checks are possible before installation or update." }, { "name": "System mutation policy", "kind": "category", "unit_or_values": "Mutable system, image-managed base, declarative system or hybrid, with writable boundaries recorded", "why_it_matters": "Determines which changes persist and which update or recovery operations are supported." }, { "name": "Maintenance authority", "kind": "relation", "unit_or_values": "Named project, organisation or maintainer group responsible for identified artifacts and channels", "why_it_matters": "Identifies whose support statements, signing keys and release decisions apply." } ], "affordances": [ "Compare distributions against workload, hardware and maintenance requirements.", "Select an appropriate release, architecture and installation artifact.", "Verify artifact provenance using the distribution's documented trust mechanism.", "Plan installation and configuration through supported interfaces.", "Determine supported update, upgrade and recovery procedures.", "Identify unsupported components and plan migration before maintenance ends." ] }, "sources": [], "structure": { "bundles": [ { "id": "identity-and-lineage", "name": "Identity and lineage", "description": "Recognises the distribution and separates its identity from derivatives and delivery artifacts.", "rationale": "Similar names and shared packages do not establish identical distribution identity or maintenance responsibility.", "layers": [ { "id": "distribution-boundary", "name": "Distribution boundary", "description": "Establishes what constitutes the integrated operating-system offering.", "findings": [ { "id": "integrated-system-identity", "name": "Integrated system identity", "description": "Record the identity under which a Linux kernel, user space and delivery or assembly process are integrated.", "questions": [ { "text": "What integration and delivery commitments make this a Linux distribution?", "kind": "definition", "id": "integrated-system-identity-q01" }, { "text": "Is the item a distribution, a release, an edition, a build system or an artifact produced by one?", "kind": "boundary", "id": "integrated-system-identity-q02" } ] } ] }, { "id": "derivation-and-editions", "name": "Derivation and editions", "description": "Captures inherited foundations and distinctions within a distribution family.", "findings": [ { "id": "upstream-and-variant-relationships", "name": "Upstream and variant relationships", "description": "Record derivation and edition relationships without treating shared ancestry as shared support.", "questions": [ { "text": "Which upstream distribution, repositories or build recipes are reused, and what is changed?", "kind": "provenance", "id": "upstream-and-variant-relationships-q01" }, { "text": "Which named variants are editions of this distribution, and which have independent release or maintenance authority?", "kind": "boundary", "id": "upstream-and-variant-relationships-q02" } ] } ] } ] }, { "id": "system-composition-and-compatibility", "name": "System composition and compatibility", "description": "Describes the integrated software stack and the targets on which it is supported.", "rationale": "Linux kernel use alone does not determine application, hardware or administration compatibility.", "layers": [ { "id": "kernel-and-user-space", "name": "Kernel and user space", "description": "Captures the components and policies that define the operating environment.", "findings": [ { "id": "base-system-contract", "name": "Base system contract", "description": "Record kernel policy, C library, core utilities and service-management choices for the relevant release or edition.", "questions": [ { "text": "Which kernel variants, C libraries, core utilities and init systems are supplied or supported?", "kind": "definition", "id": "base-system-contract-q01" }, { "text": "Which compatibility guarantees are documented for applications, kernel modules and administrative interfaces?", "kind": "boundary", "id": "base-system-contract-q02" } ] } ] }, { "id": "execution-targets", "name": "Execution targets", "description": "Distinguishes supported architectures and deployment environments.", "findings": [ { "id": "target-support-envelope", "name": "Target support envelope", "description": "Record supported processor and platform combinations, including the distinction between bootable systems and user-space images.", "questions": [ { "text": "Which architectures, ABIs, firmware interfaces and deployment environments are supported for this release?", "kind": "boundary", "id": "target-support-envelope-q01" }, { "text": "What documented memory and storage requirements apply to each installation profile?", "kind": "measurement", "id": "target-support-envelope-q02" }, { "text": "Does the selected artifact provide its own kernel or depend on a host-provided Linux kernel?", "kind": "definition", "id": "target-support-envelope-q03" } ] } ] } ] }, { "id": "software-delivery-and-system-change", "name": "Software delivery and system change", "description": "Models how a distribution is obtained, assembled and modified.", "rationale": "Package-based, source-built and image-managed distributions require different agent actions.", "layers": [ { "id": "artifacts-and-repositories", "name": "Artifacts and repositories", "description": "Identifies official delivery units and software sources.", "findings": [ { "id": "delivery-units-and-channel-boundaries", "name": "Delivery units and channel boundaries", "description": "Record installation images, packages, source recipes and repositories together with their release and support relationships.", "questions": [ { "text": "Which artifacts or build inputs are required to obtain a usable system?", "kind": "definition", "id": "delivery-units-and-channel-boundaries-q01" }, { "text": "Which repositories and channels are maintained by the distribution, and which are independently maintained additions?", "kind": "provenance", "id": "delivery-units-and-channel-boundaries-q02" } ] } ] }, { "id": "installation-and-mutation", "name": "Installation and mutation", "description": "Captures supported provisioning and software-change mechanisms.", "findings": [ { "id": "supported-change-paths", "name": "Supported change paths", "description": "Record how an agent installs the system and changes its software while respecting the distribution's managed boundaries.", "questions": [ { "text": "Which installer, package manager, build process or declarative interface should an agent use for the selected target?", "kind": "action", "id": "supported-change-paths-q01" }, { "text": "Which system areas can be changed directly, and which must be replaced or regenerated through distribution tooling?", "kind": "boundary", "id": "supported-change-paths-q02" }, { "text": "How are configuration changes preserved or reconciled when packages or base images are replaced?", "kind": "action", "id": "supported-change-paths-q03" } ] } ] } ] }, { "id": "release-maintenance-and-recovery", "name": "Release maintenance and recovery", "description": "Relates release identity to maintenance coverage and supported transitions.", "rationale": "An installable distribution release can be unsupported, and a successful update does not imply a recoverable system.", "layers": [ { "id": "release-and-support-lifecycle", "name": "Release and support lifecycle", "description": "Records versioning, channel progression and maintenance commitments.", "findings": [ { "id": "maintenance-coverage", "name": "Maintenance coverage", "description": "Record release or snapshot identity and support terms at the component and channel granularity actually promised.", "questions": [ { "text": "How are releases or rolling snapshots identified, and which channels are intended for routine use?", "kind": "definition", "id": "maintenance-coverage-q01" }, { "text": "What support dates, eligibility conditions and package exclusions apply to the selected release?", "kind": "boundary", "id": "maintenance-coverage-q02" } ] } ] }, { "id": "updates-and-recovery", "name": "Updates and recovery", "description": "Captures supported transitions and ways to recover from failed changes.", "findings": [ { "id": "upgrade-and-rollback-contract", "name": "Upgrade and rollback contract", "description": "Record allowed update sequences, restart requirements and recovery limits.", "questions": [ { "text": "Which update and cross-release upgrade paths are supported, including any required intermediate releases?", "kind": "action", "id": "upgrade-and-rollback-contract-q01" }, { "text": "Which rollback or rescue mechanisms exist, and what configuration or user data lies outside their coverage?", "kind": "boundary", "id": "upgrade-and-rollback-contract-q02" }, { "text": "How should an agent determine whether an update requires service restarts or a reboot?", "kind": "action", "id": "upgrade-and-rollback-contract-q03" } ] } ] } ] }, { "id": "trust-security-and-governance", "name": "Trust, security and governance", "description": "Identifies authorities and evidence used to trust artifacts and interpret security maintenance.", "rationale": "Repository availability and software version numbers alone cannot establish authenticity or security status.", "layers": [ { "id": "artifact-trust", "name": "Artifact trust", "description": "Captures the trust chain for installation and update inputs.", "findings": [ { "id": "verification-and-key-authority", "name": "Verification and key authority", "description": "Record what signatures or checksums cover and how their authoritative verification material is obtained.", "questions": [ { "text": "Where are authoritative signing keys or other verification anchors published, and who controls them?", "kind": "provenance", "id": "verification-and-key-authority-q01" }, { "text": "How should an agent verify installation artifacts and repository metadata, including key rotation or revocation?", "kind": "action", "id": "verification-and-key-authority-q02" } ] } ] }, { "id": "security-and-maintainer-responsibility", "name": "Security and maintainer responsibility", "description": "Connects security assessments and distribution policy to accountable maintainers.", "findings": [ { "id": "security-evidence-and-distribution-policy", "name": "Security evidence and distribution policy", "description": "Record advisory sources, package revision evidence and policies governing included software.", "questions": [ { "text": "Which distribution advisories and package revision records establish whether a vulnerability is fixed, including through backported patches?", "kind": "provenance", "id": "security-evidence-and-distribution-policy-q01" }, { "text": "Who decides release acceptance and security maintenance, and where are those responsibilities documented?", "kind": "provenance", "id": "security-evidence-and-distribution-policy-q02" }, { "text": "Which policies govern inclusion and redistribution of proprietary firmware, drivers and other restricted components?", "kind": "boundary", "id": "security-evidence-and-distribution-policy-q03" } ] } ] } ] }, { "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 software-distribution sense; the supplied PHY.OBJ domain code should be reviewed because a distribution is not intrinsically a physical object.", "The listed kinds overlap: release cadence, intended use and update architecture are independent classification dimensions.", "No sources were consulted. Standards conformance, identifier coverage, support periods and hardware requirements need verification for a named distribution and release." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Linux distribution 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": [ "General-purpose desktop distributions", "Server and enterprise distributions", "Embedded distributions", "Rolling-release distributions", "Fixed-release distributions", "Image-based or immutable-system distributions" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Linux distribution this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "os-release", "value_or_pattern": "ID, VERSION_ID and ID_LIKE fields", "note": "Machine-readable distribution identity and ancestry; VERSION_ID and ID_LIKE are optional." }, { "scheme": "Common Platform Enumeration (CPE)", "value_or_pattern": "cpe:2.3:o::::...", "note": "Operating-system product identifiers used in security inventories; coverage and naming vary by distribution." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Linux distribution 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": [ "GNU General Public License version 2, published by the Free Software Foundation: governs distribution of the Linux kernel; other included components have their own licenses.", "Filesystem Hierarchy Standard, maintained by the Linux Foundation: defines conventional filesystem organization, with distribution-specific departures.", "POSIX, standardized by IEEE and ISO/IEC: provides operating-system interface specifications relevant to compatibility; Linux distribution status alone does not establish conformance or certification." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Linux distribution 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": [ "Desktop and developer workstations", "Web, application and database servers", "Cloud virtual machines and container host systems", "Embedded equipment and network appliances", "Scientific computing and high-performance computing clusters" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Linux distribution 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": [ "Unpatched vulnerabilities or continued use after security support ends", "Dependency conflicts, interrupted updates or incompatible repositories leaving software unusable", "Kernel, driver or firmware incompatibilities causing boot failures or unavailable hardware", "Compromised installation images, repositories or signing credentials introducing malicious software", "Configuration errors exposing services, weakening access controls or causing data loss" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Linux distribution 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": [ "Default languages, input methods, mirrors and localization differ among distributions and deployment regions.", "Patent and redistribution constraints can affect availability of codecs, firmware and other bundled components." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Linux distribution 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": "Linux kernel", "difference": "The kernel manages hardware and core system resources; a distribution combines it with user-space software and a maintenance system." }, { "name": "Operating system", "difference": "Operating system is the broader category; a Linux distribution specifically assembles an operating system around the Linux kernel." }, { "name": "Distribution release", "difference": "A release is a particular published version or snapshot of a distribution; the distribution can span many releases." }, { "name": "Installed operating-system instance", "difference": "An instance is a particular deployed and configured system; a distribution is the maintained software collection from which instances are built." }, { "name": "Container image", "difference": "A container image packages a filesystem and execution metadata, often derived from a distribution, but normally uses the host kernel." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Linux distribution this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should the registry retain PHY / PHY.OBJ for this software-system kind, or relate it to an information-plane classification while preserving its registered identity?", "What minimum integration and maintenance boundary distinguishes a distribution from a Linux image-building toolkit or a one-off system image?", "How should container-only user-space offerings be related to distributions when they depend on a host kernel?", "Which evidence should determine whether a derivative or branded edition has become a distinct distribution rather than a variant?", "How should support coverage be represented when repositories, architectures and packages within one release have different maintainers and end dates?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 32 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "unclassified", "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 Linux distribution, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a Linux distribution, assess its suitability and maintenance state, and determine supported ways to obtain, deploy, update and retire it.", "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: Android distribution, Linux on embedded systems, LNX-BBC, AOSC OS, PuppyRus Linux, FSF-endorsed operating systems, lightweight Linux distribution, Red Hat Enterprise Linux derivative.", "8 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 70 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 Linux distribution, 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 and material. The registry holds no appearance data, so what a Linux distribution looks like has to come from research." ], "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": [ "Android distribution", "Linux on embedded systems", "LNX-BBC", "AOSC OS", "PuppyRus Linux", "FSF-endorsed operating systems", "lightweight Linux distribution", "Red Hat Enterprise Linux derivative" ] } ], "standing": "Described in 70 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 8 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 Linux distribution from another, and a Linux distribution 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 Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution 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 Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution 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 Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution 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 Linux distribution is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution 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 Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution 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 Linux distribution between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Linux distribution 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 Linux distribution, 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 Linux distribution, 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 Linux distribution is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "use-and-operation", "name": "Use and operation", "description": "What can be done with a Linux distribution and what it takes to do it.", "rationale": "An agent that can recognise a thing but not act on it has only half a model.", "layers": [ { "id": "intended-use", "name": "Intended use and function", "description": "What a Linux distribution is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Linux distribution performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Linux distribution, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "function-and-purpose-q02", "text": "Who or what asserted this about the use of a Linux distribution, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "function-and-purpose-q03", "text": "What may an agent decide or do once the use of a Linux distribution is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "handling-and-procedure", "name": "Handling and procedure", "description": "The steps, skills and tools involved in using a Linux distribution.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Linux distribution at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Linux distribution, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "procedures-and-skills-q02", "text": "Who or what asserted this about handling a Linux distribution, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "procedures-and-skills-q03", "text": "What may an agent decide or do once handling a Linux distribution is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Linux distribution 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 Linux distribution and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Linux distribution, 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 Linux distribution, 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 Linux distribution 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 Linux distribution is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Linux distribution, 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 Linux distribution, 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 Linux distribution is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 13, "findings": 15, "questions": 45 } } } }