{ "model": { "rank": 6824, "code": "thing-q170378", "model_id": "vr.tr.gentoo-linux", "name": "Gentoo Linux", "purpose": "Enable an agent to recognise a Gentoo Linux installation, assess its configuration and maintenance state, and determine which package, build and system changes are appropriate.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q170378/", "tier": 2, "score": 58, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 58, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q170378", "url": "https://www.wikidata.org/wiki/Q170378", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:34:54Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 16.9, "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: 01a08885-3f82-7d03-a171-7c7e205e87a5\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Gentoo Linux\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 007: 1001 re", "usd": 0, "recall": true }, "codex": { "seconds": 66.1, "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: 01a08885-3f8d-7532-85fa-045e4f40753a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Gentoo Linux\nRegistry id: vr.tr.gentoo-linux\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } } }, "metaModel": { "id": "THING-Q170378", "registryId": "vr.tr.gentoo-linux", "name": "Gentoo Linux", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q170378/", "model": { "registry_id": "vr.tr.gentoo-linux", "name": "Gentoo Linux", "purpose": "Enable an agent to recognise a Gentoo Linux installation, assess its configuration and maintenance state, and determine which package, build and system changes are appropriate.", "definition": "Gentoo Linux is a Linux distribution built around the Portage package management system, enabling users to customize installed software through source-based builds, selectable features and binary packages.", "scope_statement": "This model owns Gentoo Linux as a configurable operating-system distribution and the Gentoo-specific evidence needed to assess its installations, while distinguishing the distribution from individual hosts, upstream software and the Gentoo organisation.", "in_scope": [ "Distribution identity, installation provenance and relationships to Gentoo derivatives", "Portage configuration, ebuild repositories and installed-package state", "Profiles, USE flags and package-specific configuration", "Source builds, binary-package provenance and target compatibility", "Gentoo installation, update, recovery and security-maintenance decisions" ], "out_of_scope": [ "Physical host hardware, power systems and peripheral maintenance", "General Linux kernel architecture and upstream kernel development", "Internal behaviour and application data of individual software packages", "Governance and legal identity of the Gentoo organisation", "Independent distributions derived from Gentoo", "Generic network and service administration beyond Gentoo integration" ], "distinguishing_features": [ "Establish Gentoo identity from installation provenance, release metadata and package-management evidence together; Portage use alone does not settle whether a system is Gentoo or a derivative.", "Check whether package management uses Portage with ebuild repositories and Gentoo profile configuration, rather than identifying the distribution merely from its Linux kernel.", "Check whether effective USE flags participate in package feature selection and dependency decisions; record their resolved values rather than only a global configuration file.", "Represent maintenance through repository state, installed versions and outstanding transitions rather than assuming a single distribution release number describes the system.", "Separate distribution identity from package acquisition method: source builds and binary-package installation require different provenance checks without necessarily implying different distributions." ], "characteristics": [ { "name": "Identity and installation context", "kind": "category", "unit_or_values": "Gentoo Linux host installation | Gentoo Linux container root | derivative | unresolved", "why_it_matters": "Prevents treating a derivative or an isolated filesystem as an ordinary Gentoo host." }, { "name": "Selected profile", "kind": "relation", "unit_or_values": "Repository-qualified profile path and its parent profile relationships", "why_it_matters": "Provides context for inherited defaults, package constraints and system configuration." }, { "name": "Target architecture and ABI", "kind": "category", "unit_or_values": "Recorded architecture, CHOST and applicable ABI selections", "why_it_matters": "Constrains compatible packages, toolchains and binary artifacts." }, { "name": "Effective package feature selection", "kind": "state", "unit_or_values": "Per-package enabled, disabled, forced and masked USE flags with configuration origins", "why_it_matters": "Explains feature availability, dependency changes and rebuild requirements." }, { "name": "Repository provenance", "kind": "relation", "unit_or_values": "Repository name, upstream location, revision or snapshot, and local modifications", "why_it_matters": "Identifies the package definitions on which an installation or update decision depends." }, { "name": "Package acceptance policy", "kind": "state", "unit_or_values": "Effective keyword, mask, unmask and license acceptance settings with per-package exceptions", "why_it_matters": "Explains why candidate versions are available or excluded." }, { "name": "Package acquisition policy", "kind": "category", "unit_or_values": "Source preferred | binaries preferred with source fallback | binaries required | package-specific policy", "why_it_matters": "Determines artifact checks, build requirements and fallback behaviour." }, { "name": "Requested and installed package sets", "kind": "relation", "unit_or_values": "World selections and named sets related to installed package versions, slots and repositories", "why_it_matters": "Distinguishes intentionally retained software from dependency state." }, { "name": "Last successful repository synchronisation age", "kind": "measurement", "unit_or_values": "Hours since recorded successful synchronisation, per repository; unknown if unrecorded", "why_it_matters": "Qualifies how current package and update assessments are." }, { "name": "Maintenance readiness", "kind": "state", "unit_or_values": "Assessed ready | blocked | partially completed | unassessed, with recorded reasons", "why_it_matters": "Connects unresolved Gentoo maintenance tasks to permission for further changes." } ], "affordances": [ "Identify a Gentoo installation and assemble evidence for its profile, repositories and package state.", "Explain why Portage selects, excludes or rebuilds a package under the effective configuration.", "Preview package, USE-flag and profile changes and identify dependency or compatibility consequences.", "Assess whether a binary package or local build is suitable for the installation target.", "Plan authorised updates, configuration merges and dependency cleanup with recovery checkpoints.", "Evaluate installed packages against applicable Gentoo security information and record unresolved exposure." ] }, "sources": [], "structure": { "bundles": [ { "id": "gentoo-identity-and-boundaries", "name": "Gentoo identity and boundaries", "description": "Establishes what is being recognised as Gentoo and which installation context is under assessment.", "rationale": "Gentoo identity must remain distinct from its Linux kernel, its package manager and distributions that reuse its tooling.", "layers": [ { "id": "distribution-identity", "name": "Distribution identity", "description": "Collects evidence identifying Gentoo and distinguishing derivative systems.", "findings": [ { "id": "identity-evidence", "name": "Identity evidence", "description": "Record installation origin, release metadata and repository relationships, including conflicting evidence.", "questions": [ { "text": "Which installation artifacts and system metadata support identifying this system as Gentoo Linux?", "kind": "provenance", "id": "identity-evidence-q01" }, { "text": "Does the system follow Gentoo directly, or does a derivative supply its identity and maintenance policy?", "kind": "boundary", "id": "identity-evidence-q02" } ] } ] }, { "id": "installation-context", "name": "Installation context", "description": "Separates distribution-level properties from the environment of a particular installation.", "findings": [ { "id": "managed-root-and-host", "name": "Managed root and host", "description": "Identify the filesystem and execution environment to which Gentoo package and boot decisions apply.", "questions": [ { "text": "Which root filesystem and Portage configuration are the subject of this assessment?", "kind": "boundary", "id": "managed-root-and-host-q01" }, { "text": "Is this a booted host, container root or installation environment, and which kernel and boot responsibilities belong to its surrounding host?", "kind": "boundary", "id": "managed-root-and-host-q02" } ] } ] } ] }, { "id": "profiles-and-feature-policy", "name": "Profiles and feature policy", "description": "Models how profile inheritance and local configuration determine the effective Gentoo package policy.", "rationale": "Gentoo installations cannot be assessed reliably from package names alone because profile and USE choices alter their meaning.", "layers": [ { "id": "profile-inheritance", "name": "Profile inheritance", "description": "Records the selected profile and the defaults or constraints it contributes.", "findings": [ { "id": "effective-profile-context", "name": "Effective profile context", "description": "Relate the profile to architecture, ABI, system package requirements and local overrides.", "questions": [ { "text": "Which repository-qualified profile and parent profiles supply this installation's effective defaults?", "kind": "provenance", "id": "effective-profile-context-q01" }, { "text": "Which architecture, ABI, C library and init-system choices must remain compatible when changing this profile?", "kind": "action", "id": "effective-profile-context-q02" } ] } ] }, { "id": "package-feature-and-acceptance-policy", "name": "Package feature and acceptance policy", "description": "Resolves package features and version eligibility across inherited and local settings.", "findings": [ { "id": "resolved-package-policy", "name": "Resolved package policy", "description": "Record effective USE selections, keyword acceptance, masks and license acceptance with their origins.", "questions": [ { "text": "For the package under consideration, which USE flags are effective, and which are forced or masked by inherited policy?", "kind": "definition", "id": "resolved-package-policy-q01" }, { "text": "Which keyword, mask or license settings explain why a candidate version is accepted or rejected?", "kind": "definition", "id": "resolved-package-policy-q02" }, { "text": "What dependency and rebuild changes would follow from the proposed package-specific exception?", "kind": "action", "id": "resolved-package-policy-q03" } ] } ] } ] }, { "id": "portage-package-graph", "name": "Portage package graph", "description": "Connects ebuild provenance, requested software and installed dependency state.", "rationale": "An agent needs to distinguish what the user requested from what dependency resolution installed before recommending upgrades or removal.", "layers": [ { "id": "ebuild-repositories", "name": "Ebuild repositories", "description": "Identifies which repositories and package definitions inform Portage decisions.", "findings": [ { "id": "repository-selection-and-origin", "name": "Repository selection and origin", "description": "Track official and additional repositories, their observed states and local changes.", "questions": [ { "text": "Which repository and ebuild revision provide each package selected for the proposed operation?", "kind": "provenance", "id": "repository-selection-and-origin-q01" }, { "text": "Where repositories offer overlapping packages, which configuration determines selection and what local modifications affect it?", "kind": "definition", "id": "repository-selection-and-origin-q02" } ] } ] }, { "id": "requested-and-installed-state", "name": "Requested and installed state", "description": "Relates world selections and package sets to installed versions and dependency constraints.", "findings": [ { "id": "dependency-and-retention-intent", "name": "Dependency and retention intent", "description": "Record package retention intent, slots, dependency blockers and proposed graph changes.", "questions": [ { "text": "Which packages are explicitly selected through world or named sets, and which remain solely as dependencies?", "kind": "definition", "id": "dependency-and-retention-intent-q01" }, { "text": "Which slot, subslot, blocker or dependency constraints prevent the intended package transaction?", "kind": "action", "id": "dependency-and-retention-intent-q02" }, { "text": "Which packages would dependency cleanup remove, and does that match the operator's retention intent?", "kind": "action", "id": "dependency-and-retention-intent-q03" } ] } ] } ] }, { "id": "builds-and-binary-artifacts", "name": "Builds and binary artifacts", "description": "Assesses how Gentoo packages are produced or acquired and whether resulting artifacts fit their target.", "rationale": "Build configuration and binary compatibility directly affect whether a Gentoo package operation can succeed and produce usable software.", "layers": [ { "id": "source-build-environment", "name": "Source build environment", "description": "Records the toolchain, target settings and resources relevant to package compilation.", "findings": [ { "id": "build-feasibility", "name": "Build feasibility", "description": "Assess target compatibility and practical build capacity without assuming aggressive compiler settings are appropriate.", "questions": [ { "text": "Which compiler, CHOST and effective build flags apply to the selected package and intended execution target?", "kind": "definition", "id": "build-feasibility-q01" }, { "text": "What measured memory, free build-space and concurrency constraints determine whether this build is feasible?", "kind": "measurement", "id": "build-feasibility-q02" }, { "text": "Which build logs and package-specific instructions support diagnosing a failed compilation?", "kind": "provenance", "id": "build-feasibility-q03" } ] } ] }, { "id": "binary-package-suitability", "name": "Binary package suitability", "description": "Records artifact origin and compatibility checks before binary-package installation.", "findings": [ { "id": "artifact-provenance-and-fit", "name": "Artifact provenance and fit", "description": "Relate binary-package metadata and verification evidence to the target installation and acquisition policy.", "questions": [ { "text": "Who supplied the binary package, and what available integrity or signature evidence has been verified?", "kind": "provenance", "id": "artifact-provenance-and-fit-q01" }, { "text": "Do the artifact's architecture, ABI, USE configuration and dependency requirements fit the target installation?", "kind": "boundary", "id": "artifact-provenance-and-fit-q02" }, { "text": "If no suitable binary is available, does the configured policy allow a source build or require the operation to stop?", "kind": "action", "id": "artifact-provenance-and-fit-q03" } ] } ] } ] }, { "id": "maintenance-security-and-recovery", "name": "Maintenance, security and recovery", "description": "Turns Gentoo update evidence into bounded maintenance actions and records their completion.", "rationale": "Successful package installation alone does not establish that configuration transitions, security remediation or boot recovery are complete.", "layers": [ { "id": "update-and-transition-readiness", "name": "Update and transition readiness", "description": "Assesses repository freshness, applicable Gentoo news and unfinished package or configuration transitions.", "findings": [ { "id": "maintenance-obligations", "name": "Maintenance obligations", "description": "Track instructions and pending work that affect whether an update is ready or complete.", "questions": [ { "text": "Which applicable Gentoo news items or profile-transition instructions must be satisfied before the planned update?", "kind": "action", "id": "maintenance-obligations-q01" }, { "text": "Which protected configuration files, preserved-library rebuilds or interrupted package operations remain unresolved?", "kind": "measurement", "id": "maintenance-obligations-q02" }, { "text": "What evidence will demonstrate that the package transaction and its required follow-up steps completed successfully?", "kind": "action", "id": "maintenance-obligations-q03" } ] } ] }, { "id": "security-and-boot-recovery", "name": "Security and boot recovery", "description": "Relates installed versions to security information and preserves a usable recovery route for system changes.", "findings": [ { "id": "remediation-and-recovery-evidence", "name": "Remediation and recovery evidence", "description": "Record advisory applicability, remedial actions and recovery dependencies for the installation's kernel and boot arrangement.", "questions": [ { "text": "Which Gentoo Linux Security Advisories apply to installed versions and configurations, and what exposure remains uncertain?", "kind": "provenance", "id": "remediation-and-recovery-evidence-q01" }, { "text": "Which package updates, rebuilds, service restarts or reboots are required to complete the identified remediation?", "kind": "action", "id": "remediation-and-recovery-evidence-q02" }, { "text": "Before changing the kernel or boot-related packages, which known-working kernel, initramfs where required, boot entry and rescue access are available?", "kind": "action", "id": "remediation-and-recovery-evidence-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": [ "The supplied PHY.OBJ domain merits review: Gentoo Linux denotes a software distribution, not a physical device.", "The listed kinds are overlapping installation choices, not mutually exclusive editions.", "No universal hardware capacity, installation size or build-time range is meaningful without specifying architecture, package selection and build configuration." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Gentoo Linux 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": [ "Gentoo installations using glibc", "Gentoo installations using musl", "Gentoo installations using OpenRC", "Gentoo installations using systemd" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Gentoo Linux 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 operating system identifier", "value_or_pattern": "ID=gentoo", "note": "Identifies the distribution rather than a particular machine or installed package set." }, { "scheme": "Gentoo package atom", "value_or_pattern": "category/package", "note": "Portage package references can additionally specify versions, slots, repositories and USE dependencies." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Gentoo Linux 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": [ "Gentoo Package Manager Specification, maintained by the Gentoo project, defines package-manager behavior and ebuild interfaces.", "GNU General Public License version 2, published by the Free Software Foundation, governs the Linux kernel; other included packages have their own licenses." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Gentoo Linux 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": [ "Customized desktop and server operating systems.", "Software development and testing with selectable compiler and dependency configurations.", "Systems requiring explicit control over optional software features.", "Learning Linux installation, compilation and system administration." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Gentoo Linux 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": [ "Package builds can fail because of unsupported compiler options, missing dependencies or incompatible configurations.", "Dependency conflicts and incompatible USE flag selections can obstruct upgrades.", "Incorrect bootloader, kernel or init-system configuration can prevent booting.", "Source compilation can consume substantial processor time, memory and temporary storage.", "Delayed security updates or exposed services with unsafe configurations can leave systems vulnerable." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Gentoo Linux 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", "difference": "Linux is the kernel; Gentoo Linux combines that kernel with package management, user-space software and distribution policies." }, { "name": "Portage", "difference": "Portage is Gentoo's package management system, not the complete operating-system distribution." }, { "name": "Gentoo Prefix", "difference": "Gentoo Prefix installs Gentoo-managed software beneath a chosen directory on an existing operating system rather than necessarily providing a complete Gentoo Linux installation." }, { "name": "Arch Linux", "difference": "Arch primarily distributes prebuilt packages through pacman; Gentoo centers customization on Portage ebuilds and USE flags while also supporting binary packages." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Gentoo Linux this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the existing Vercy catalogue already contain an authoritative Gentoo or Linux-distribution model that this registry entry should reference or specialise?", "Should the registry's PHY / PHY.OBJ classification remain authoritative for this software distribution, or be reviewed separately without changing this entry's identity?", "Which currently supported profiles, architectures and installation contexts should the researched model explicitly cover?", "What are the current authoritative rules for Gentoo binary-package compatibility and verification across official and third-party providers?", "What coverage limits apply to Gentoo security advisories and assessment tools for additional repositories, local ebuilds and unusual package configurations?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 33 } }, "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 Gentoo Linux, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a Gentoo Linux installation, assess its configuration and maintenance state, and determine which package, build and system changes are appropriate.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 58 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 Gentoo Linux, 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 Gentoo Linux looks like has to come from research." ], "relatedModels": [], "standing": "Described in 58 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one Gentoo Linux from another, and a Gentoo Linux 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 Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Gentoo Linux 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 Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Gentoo Linux performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Gentoo Linux at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux 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 Gentoo Linux and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 Gentoo Linux is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Gentoo Linux, 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 Gentoo Linux, 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 Gentoo Linux 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 } } } }