{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T10:01:40Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 21.0, "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: 01a0950f-5eaf-70e0-9e6a-422434e82887\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: GNU Guix System\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 1001", "usd": 0.0, "recall": true }, "codex": { "seconds": 93.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: 01a0950f-5eaa-7c50-b5eb-b5ceac9e2d70\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: GNU Guix System\nRegistry id: vr.tr.gnu-guix-system\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:55:52+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:28+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q19597382", "registryId": "vr.tr.gnu-guix-system", "name": "GNU Guix System", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q19597382/", "model": { "registry_id": "vr.tr.gnu-guix-system", "name": "GNU Guix System", "purpose": "Enable an agent to recognise GNU Guix System, assess the configuration and recoverability of an installation, and plan justified changes to its declared operating system.", "definition": "GNU Guix System is a GNU/Linux operating-system distribution that uses the GNU Guix package manager and declarative configurations written in Guile Scheme to manage software, services, and system generations, with support for transactional upgrades and rollbacks.", "scope_statement": "This model owns GNU Guix System as the operating-system distribution identified by vr.tr.gnu-guix-system, including the evidence needed to assess its installations; the supplied PHY / PHY.OBJ classification remains registry metadata pending review of its software identity.", "in_scope": [ "Identity of GNU Guix System and boundaries with the Guix package manager", "Scheme operating-system declarations and their configuration dependencies", "Channel revisions, store dependencies and build provenance", "System generations, activation, boot selection and recovery", "Declared services, hardware compatibility and persistent-state boundaries" ], "out_of_scope": [ "GNU Guix used solely as a package manager on another distribution", "Guix Home configurations and personal package profiles except their interfaces with the system", "Physical computers, storage devices and network equipment", "Application business logic and application data schemas", "GNU Project governance and individual software-package models" ], "distinguishing_features": [ "Establish whether Guix manages the operating system itself; the presence of the guix command or /gnu/store alone does not establish GNU Guix System.", "Look for a Guile Scheme operating-system declaration governing system composition, distinguishing it from NixOS configuration.", "Check for system generations managed through guix system, distinguishing them from generations of a user's package profile.", "Examine the GNU Shepherd service configuration and its relationship to Guix service declarations.", "Check the kernel and added channels against the distribution's Linux-libre and free-software orientation, recording installation-specific departures." ], "characteristics": [ { "name": "System configuration origin", "kind": "relation", "unit_or_values": "Operating-system declaration, repository revision and imported local modules", "why_it_matters": "Identifies the inputs an agent must inspect before proposing a system change." }, { "name": "Guix channel identity", "kind": "relation", "unit_or_values": "Channel names, repository URLs, commits and authentication introductions where applicable", "why_it_matters": "A configuration file alone does not identify all software definitions used to build a system." }, { "name": "Generation alignment", "kind": "state", "unit_or_values": "Built candidate, selected system generation, booted generation and next-boot selection", "why_it_matters": "Separates a successful build from the system actually running." }, { "name": "Execution target", "kind": "category", "unit_or_values": "Architecture and target; physical installation, virtual machine, container or image", "why_it_matters": "Determines which hardware, boot and isolation checks apply." }, { "name": "Kernel and firmware composition", "kind": "relation", "unit_or_values": "Declared kernel package, firmware packages and originating channels", "why_it_matters": "Supports hardware compatibility and distribution-conformance assessment." }, { "name": "Service agreement", "kind": "state", "unit_or_values": "Declared service extensions and observed Shepherd service status; aligned, divergent or unknown", "why_it_matters": "Detects differences between intended composition and operational behaviour." }, { "name": "Substitute trust", "kind": "relation", "unit_or_values": "Configured substitute servers, authorised signing keys and applicable policy", "why_it_matters": "Identifies whose prebuilt artifacts the installation accepts." }, { "name": "Store capacity", "kind": "measurement", "unit_or_values": "Bytes available, bytes occupied and estimated reclaimable bytes at a recorded time", "why_it_matters": "Helps judge whether builds and retained recovery generations fit available storage." }, { "name": "Persistent-state recovery coverage", "kind": "state", "unit_or_values": "Protected, partially protected, unprotected or unverified, per state location", "why_it_matters": "System generation recovery must be assessed separately from restoration of mutable data." } ], "affordances": [ "Inspect a declaration and its channel inputs to identify the intended system.", "Build a candidate system or suitable test image before activation.", "Compare generations and assess the consequences of reconfiguration.", "Inspect service composition and reconcile it with runtime observations.", "Plan generation switching or rollback together with persistent-data recovery.", "Assess retained generations and garbage-collection roots before reclaiming store space." ], "agent_conduct": { "may": [ "Install, configure and update a Guix System machine the agent is authorized to administer.", "Describe its declarative and reproducible design from official documentation." ], "must_not": [ "Change system configuration on machines it does not administer.", "Disable security updates or roll back to vulnerable generations without the administrator's decision.", "Distribute modified packages in breach of their free software licences.", "Present it as supporting hardware or features it does not support." ], "requires_human": [ "Reconfiguring production systems or deleting old system generations." ] }, "ethics": { "considerations": [ "Free software freedoms depend on honouring licences.", "Administrative mistakes on servers affect everyone who relies on them." ], "affected_parties": [ "System users", "Administrators", "Free software developers" ] }, "owners": { "steward": "The administrator of each installation; the project maintains the distribution.", "master_systems": [] }, "visual_identification": [ "Not a physical object; seen as a Linux system configured by a Scheme file and managed with the guix command." ], "failure_modes_and_hazards": [ "Configuration errors can leave a system unbootable until rolled back.", "Missing proprietary drivers can leave some hardware unusable." ], "what_it_is_for": [ "This operating system is used on computers where packages, services and system configuration are managed through declarative definitions.", "It supports maintaining reproducible environments and returning to earlier system generations, although rollback does not necessarily restore application data." ], "standards_and_regulation": [ "ISO/IEC 9945, issued by the International Organization for Standardization and the International Electrotechnical Commission, specifies operating system interfaces relevant to its Unix-like software environment without establishing full distribution conformance." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q19597382: GNU Guix System", "url": "https://www.wikidata.org/wiki/Q19597382", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: GNU Guix System", "url": "https://en.wikipedia.org/wiki/GNU_Guix_System", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "system-identity", "name": "System identity", "description": "Establish what qualifies as GNU Guix System and what represents a particular installation.", "rationale": "Guix tooling can exist on another distribution, so package-manager detection alone gives a false identity.", "layers": [ { "id": "distribution-boundary", "name": "Distribution boundary", "description": "Separate the operating-system distribution from adjacent Guix facilities.", "findings": [ { "id": "system-ownership", "name": "System ownership", "description": "Require evidence that Guix supplies the system configuration and lifecycle.", "questions": [ { "text": "What evidence establishes that this installation is GNU Guix System rather than another distribution running Guix?", "kind": "definition", "id": "system-ownership-q01" }, { "text": "Which observed configurations belong to the system, Guix Home or personal package profiles?", "kind": "boundary", "id": "system-ownership-q02" } ] } ] }, { "id": "installation-lineage", "name": "Installation lineage", "description": "Relate installation evidence to the registered distribution without creating a model for every machine.", "findings": [ { "id": "variant-and-target", "name": "Variant and target", "description": "Record the target environment and departures introduced by custom channels or system components.", "questions": [ { "text": "Which image, configuration repository and channel revisions establish this installation's origin?", "kind": "provenance", "id": "variant-and-target-q01" }, { "text": "Which custom components affect whether the installation should be described as stock GNU Guix System or a derivative?", "kind": "boundary", "id": "variant-and-target-q02" } ] } ] } ] }, { "id": "declarative-composition", "name": "Declarative composition", "description": "Capture the inputs and extension relationships that produce the intended operating system.", "rationale": "An agent must understand executable Scheme configuration and service composition before editing them.", "layers": [ { "id": "configuration-inputs", "name": "Configuration inputs", "description": "Identify the complete input boundary of the operating-system declaration.", "findings": [ { "id": "declaration-completeness", "name": "Declaration completeness", "description": "Assess whether the retained declaration and supporting inputs explain the generated system.", "questions": [ { "text": "Which operating-system expression, imported modules, local files and invocation options produced this generation?", "kind": "provenance", "id": "declaration-completeness-q01" }, { "text": "Which inputs depend on local paths, environment values or external resources that another builder would lack?", "kind": "boundary", "id": "declaration-completeness-q02" } ] } ] }, { "id": "service-extension", "name": "Service extension", "description": "Connect Guix service declarations to generated configuration and runtime responsibilities.", "findings": [ { "id": "service-effects", "name": "Service effects", "description": "Trace how declared services contribute accounts, files, activation work and runtime services.", "questions": [ { "text": "Which service types and extensions supply each relevant account, configuration file and Shepherd service?", "kind": "definition", "id": "service-effects-q01" }, { "text": "What dependent configuration or runtime behaviour would change if this service declaration were modified?", "kind": "action", "id": "service-effects-q02" } ] } ] } ] }, { "id": "build-provenance-and-trust", "name": "Build provenance and trust", "description": "Connect a system result to software definitions, build inputs and accepted artifacts.", "rationale": "Recreating a declaration requires more evidence than a release label or a list of installed package names.", "layers": [ { "id": "channel-pinning", "name": "Channel pinning", "description": "Identify the precise Guix and additional-channel definitions used for a system.", "findings": [ { "id": "revision-reconstruction", "name": "Revision reconstruction", "description": "Require recoverable channel revisions and distinguish recorded inputs from demonstrated reproducibility.", "questions": [ { "text": "Which exact channel commits and authentication information accompanied the Guix used to build this system?", "kind": "provenance", "id": "revision-reconstruction-q01" }, { "text": "Can those revisions and the configuration inputs still be retrieved and evaluated with an appropriate Guix invocation?", "kind": "action", "id": "revision-reconstruction-q02" } ] } ] }, { "id": "artifact-acceptance", "name": "Artifact acceptance", "description": "Assess the provenance and trust basis of store items entering the system.", "findings": [ { "id": "substitutes-and-build-evidence", "name": "Substitutes and build evidence", "description": "Separate acceptance of signed substitutes from evidence that independent builds agree.", "questions": [ { "text": "Which system dependencies were built locally, obtained from substitutes or imported through another route?", "kind": "provenance", "id": "substitutes-and-build-evidence-q01" }, { "text": "Which keys authorise accepted substitutes, and what independent rebuild evidence exists for critical outputs?", "kind": "provenance", "id": "substitutes-and-build-evidence-q02" } ] } ] } ] }, { "id": "generation-lifecycle", "name": "Generation lifecycle", "description": "Assess system builds, activation and recovery through generations; the relevant command family is documented in the [GNU Guix Reference Manual](https://guix.gnu.org/manual/en/guix.pdf).", "rationale": "An agent must distinguish an available system result from a selected or running system before deciding what to activate or recover.", "layers": [ { "id": "build-and-activation", "name": "Build and activation", "description": "Track candidate, selected and running states across a proposed change.", "findings": [ { "id": "transition-readiness", "name": "Transition readiness", "description": "Establish evidence and authority for moving a candidate into service.", "questions": [ { "text": "Which generation is built, selected, booted and scheduled for the next boot?", "kind": "measurement", "id": "transition-readiness-q01" }, { "text": "Which changes require service intervention or reboot, and what validation must precede reconfiguration?", "kind": "action", "id": "transition-readiness-q02" } ] } ] }, { "id": "rollback-boundary", "name": "Rollback boundary", "description": "Assess recovery generations together with data and access requirements.", "findings": [ { "id": "recoverable-generation", "name": "Recoverable generation", "description": "Identify a usable recovery target without assuming that switching generations restores mutable state.", "questions": [ { "text": "Which retained generation has evidence of successful operation, and are its required store items and boot entry available?", "kind": "provenance", "id": "recoverable-generation-q01" }, { "text": "Which database migrations, secrets or persistent files could prevent that generation from working after a rollback?", "kind": "boundary", "id": "recoverable-generation-q02" }, { "text": "How can an authorised operator select the recovery generation if normal boot or remote access fails?", "kind": "action", "id": "recoverable-generation-q03" } ] } ] } ] }, { "id": "host-fit-and-runtime", "name": "Host fit and runtime", "description": "Assess whether the declared Guix System can boot and deliver its intended services on the target.", "rationale": "A successful system build does not establish hardware support, successful boot or service availability.", "layers": [ { "id": "boot-and-hardware", "name": "Boot and hardware", "description": "Connect target hardware to declared kernel, firmware, storage and boot components.", "findings": [ { "id": "boot-path-fit", "name": "Boot path fit", "description": "Assess the path from firmware to a mounted root filesystem and usable system.", "questions": [ { "text": "Do the declared kernel, firmware and initrd support the target's storage, network and other required devices?", "kind": "measurement", "id": "boot-path-fit-q01" }, { "text": "Do bootloader targets, filesystem identifiers and mapped-device declarations match the intended installation?", "kind": "measurement", "id": "boot-path-fit-q02" } ] } ] }, { "id": "runtime-agreement", "name": "Runtime agreement", "description": "Compare generated service intent with observed behaviour.", "findings": [ { "id": "shepherd-service-health", "name": "Shepherd service health", "description": "Relate Shepherd observations and service-specific probes to the selected system configuration.", "questions": [ { "text": "Which expected Shepherd services are running, stopped or failing, and what do application-level probes show?", "kind": "measurement", "id": "shepherd-service-health-q01" }, { "text": "Which intervention belongs in the operating-system declaration, and which is a temporary runtime action?", "kind": "action", "id": "shepherd-service-health-q02" } ] } ] } ] }, { "id": "persistent-state-and-store-retention", "name": "Persistent state and store retention", "description": "Separate reproducible system artifacts from mutable information and recovery dependencies.", "rationale": "Store cleanup and configuration retention must preserve the evidence and artifacts required for recovery.", "layers": [ { "id": "mutable-state", "name": "Mutable state", "description": "Identify data and secrets outside the recoverable system declaration.", "findings": [ { "id": "state-and-secret-boundary", "name": "State and secret boundary", "description": "Assess persistence, backup and secret provisioning independently of system generations.", "questions": [ { "text": "Which service data, home directories and machine-specific files require separate backup and restoration?", "kind": "boundary", "id": "state-and-secret-boundary-q01" }, { "text": "How are credentials provisioned without embedding sensitive contents in readable store artifacts or shared configuration?", "kind": "action", "id": "state-and-secret-boundary-q02" } ] } ] }, { "id": "store-retention", "name": "Store retention", "description": "Connect storage reclamation to profiles, generations and garbage-collection roots.", "findings": [ { "id": "collection-consequences", "name": "Collection consequences", "description": "Evaluate what can be reclaimed while retaining required rollback and rebuild options.", "questions": [ { "text": "Which profiles, generations and explicit garbage-collection roots retain the store items required for recovery?", "kind": "relation", "id": "collection-consequences-q01" }, { "text": "How much space could be reclaimed, and which recovery options would disappear after deleting generations and collecting unreferenced items?", "kind": "measurement", "id": "collection-consequences-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The supplied PHY.OBJ domain suggests a physical object, whereas this entry denotes a software distribution; its registry classification should be checked.", "Supported hardware architectures, release identifiers, and package availability are version-dependent and are intentionally omitted.", "Reproducible package builds, reproducible environment specifications, and rollback are distinct capabilities and should not be treated as interchangeable guarantees." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of GNU Guix System 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 Free System Distribution Guidelines, maintained by the GNU Project, govern the distribution's commitment to free software.", "GNU Guix itself is licensed under the GNU General Public License, version 3 or later; distributed packages retain their respective licenses." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of GNU Guix System 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": [ "Running desktop and server operating systems configured through declarative Scheme files.", "Maintaining versioned system configurations with upgrade and rollback capabilities.", "Creating controlled development environments with explicitly selected software dependencies.", "Supporting reproducible scientific computing through recorded package definitions and channel revisions.", "Building virtual-machine images and installation media from system configurations." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of GNU Guix System 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": [ "Hardware that requires proprietary firmware or drivers may be unsupported by the distribution's free-software stack.", "Building packages locally can require substantial computation, storage, and time when suitable prebuilt substitutes are unavailable.", "Retained generations and dependencies can consume considerable disk space; garbage collection removes store items no longer protected by roots.", "Rolling back packages or system configuration does not automatically undo changes to application data, database schemas, or external services.", "Declarative configuration alone does not guarantee identical builds; reproducibility also depends on pinned inputs, build behavior, and the execution environment." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of GNU Guix System 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": "GNU Guix", "difference": "GNU Guix is the package manager and associated tooling, which can run on another GNU/Linux distribution; Guix System is the complete operating-system distribution built around it." }, { "name": "NixOS", "difference": "Both provide declarative system management and generations, but NixOS uses Nix and its configuration language, while Guix System uses GNU Guix and Guile Scheme." }, { "name": "GNU Shepherd", "difference": "GNU Shepherd manages services and acts as the init system in Guix System; it is a component rather than the complete distribution." }, { "name": "Linux-libre", "difference": "Linux-libre is the kernel variant used by Guix System, with nonfree components removed; it does not provide the distribution's package management or system configuration." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of GNU Guix System this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should the registry's PHY / PHY.OBJ assignment be corrected to represent an operating-system distribution, and does an existing world model already cover this concept?", "Which Guix revision should anchor version-sensitive details of generation switching, activation and bootloader behaviour?", "What evidence and terminology should distinguish GNU Guix System with custom channels from a separately identified derivative?", "Which target architectures, hardware configurations and recovery paths have actually been tested for the installations this model will assess?", "What reproducibility threshold is required: reconstructing declared inputs, obtaining an equivalent working system or independently reproducing identical build outputs?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 17, "questions": 30 } }