{ "model": { "rank": 3883, "code": "thing-q83370", "model_id": "vr.tr.windows-95", "name": "Windows 95", "purpose": "Enable an agent to identify a Windows 95 release or installation, assess its compatibility and operating state, and choose appropriate preservation, recovery or controlled-use actions.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q83370/", "tier": 2, "score": 81, "payload": { "layer": "wikidata", "aliases": [], "aliasCount": 0, "merged": 0, "knownIn": 81, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q83370", "url": "https://www.wikidata.org/wiki/Q83370", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T18:58:54Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 23.3, "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: 01a08788-a63c-79b2-bb40-4a1aed59f754\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Windows 95\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 regis", "usd": 0, "recall": true }, "codex": { "seconds": 60.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: 01a08788-a628-79b1-ab13-f966d729a45a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Windows 95\nRegistry id: vr.tr.windows-95\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q83370", "registryId": "vr.tr.windows-95", "name": "Windows 95", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q83370/", "model": { "registry_id": "vr.tr.windows-95", "name": "Windows 95", "purpose": "Enable an agent to identify a Windows 95 release or installation, assess its compatibility and operating state, and choose appropriate preservation, recovery or controlled-use actions.", "definition": "Windows 95 is a Microsoft operating system for IBM PC-compatible personal computers, released in 1995, that combines a graphical desktop and support for 32-bit Windows applications with substantial MS-DOS and 16-bit Windows compatibility.", "scope_statement": "This model owns Windows 95 as a Microsoft operating-system product family and the evidence needed to assess its releases and installations; it preserves registry identity vr.tr.windows-95 while treating physical computers and installation media as related objects.", "in_scope": [ "Windows 95 release, build, language and distribution identity", "Installed operating-system components, configuration and boot state", "DOS, Windows application and device-driver compatibility", "Storage, networking and resource conditions affecting operation", "Installation provenance, recovery and preservation decisions" ], "out_of_scope": [ "Physical computer construction, ownership and hardware maintenance", "Physical installation disks, packaging and manuals as collectible objects", "Application functionality beyond its interaction with Windows 95", "Other Windows families, including Windows NT and Windows 98", "Microsoft corporate history and the broader personal-computing market" ], "distinguishing_features": [ "System-reported identity and installation evidence identify Windows 95; a Start menu or Windows-themed desktop alone is insufficient.", "Its DOS-integrated Windows architecture distinguishes it from the Windows NT family even when their desktop interfaces resemble one another.", "Release and component evidence distinguishes Windows 95 from Windows 98; application compatibility alone does not establish identity.", "A Windows 95 installation is software deployed on a host, whereas a computer advertised as a Windows 95 PC is a related hardware object.", "Retail, OEM and updated installations must be distinguished through release evidence rather than assumed to have identical capabilities." ], "characteristics": [ { "name": "Registry classification fit", "kind": "state", "unit_or_values": "PHY / PHY.OBJ recorded; software classification review pending", "why_it_matters": "Prevents the registry plane from causing the operating system to be modeled as a physical computer or disk." }, { "name": "Release identity", "kind": "category", "unit_or_values": "Observed version string, build identifier, distribution variant and language; unknown permitted", "why_it_matters": "Compatibility and recovery decisions require a more precise identity than the Windows 95 name." }, { "name": "Deployment host", "kind": "relation", "unit_or_values": "Physical computer, virtual machine or emulator, linked to its own model", "why_it_matters": "Separates operating-system behavior from limitations introduced by hardware or emulation." }, { "name": "Boot outcome", "kind": "state", "unit_or_values": "Untested, fails before Windows startup, command environment only, safe mode, normal desktop, intermittent failure", "why_it_matters": "Identifies the accessible recovery route and the stage requiring investigation." }, { "name": "Installed memory", "kind": "measurement", "unit_or_values": "MiB, recording host allocation and guest-reported availability separately", "why_it_matters": "Resource configuration can affect startup and application behavior." }, { "name": "Volume configuration", "kind": "category", "unit_or_values": "Observed filesystem, partition arrangement, boot role and free space for each volume", "why_it_matters": "Storage support and repair choices depend on both the release and the actual disk layout." }, { "name": "Application compatibility", "kind": "relation", "unit_or_values": "Application and version linked to tested, failed, conditional or untested execution results", "why_it_matters": "Avoids treating all DOS or Windows applications as interchangeable compatibility targets." }, { "name": "Driver configuration", "kind": "relation", "unit_or_values": "Device linked to driver version, origin, installation state and observed conflicts", "why_it_matters": "Device recognition does not establish that the device operates correctly." }, { "name": "Network exposure", "kind": "state", "unit_or_values": "Disconnected, isolated local network, restricted gateway or externally reachable; verification timestamp required", "why_it_matters": "Determines which transfers and demonstrations are appropriate for the installation." }, { "name": "Recovery readiness", "kind": "state", "unit_or_values": "No recovery copy, unverified copy, verified disk image or successfully tested restoration", "why_it_matters": "Determines whether configuration changes can be reversed without losing the installation." } ], "affordances": [ "Identify a release by comparing reported identity with installation and distribution evidence.", "Test a specified application or peripheral in a controlled environment and record the result.", "Diagnose startup failure using the last successful boot stage and recent configuration changes.", "Inspect driver, storage and network configuration before enabling a capability.", "Preserve an installation through verified imaging and a documented restoration procedure.", "Choose whether to retain, isolate, restore or migrate an installation according to its required workload." ] }, "sources": [], "structure": { "bundles": [ { "id": "release-and-installation-identity", "name": "Release and installation identity", "description": "Establish which Windows 95 variant is represented and how the observed installation relates to its distribution.", "rationale": "Windows 95 branding alone does not resolve release-dependent behavior or establish installation provenance.", "layers": [ { "id": "product-boundary", "name": "Product boundary", "description": "Separate the operating-system family from neighboring software and physical artifacts.", "findings": [ { "id": "windows-95-identity-evidence", "name": "Windows 95 identity evidence", "description": "Record evidence identifying the software as Windows 95 and distinguish the product family from a particular installation.", "questions": [ { "text": "Which system-reported identifiers and installation artifacts establish that this is Windows 95?", "kind": "definition", "id": "windows-95-identity-evidence-q01" }, { "text": "Does the record describe the software family, a release, an installed copy or a physical artifact carrying it?", "kind": "boundary", "id": "windows-95-identity-evidence-q02" } ] } ] }, { "id": "distribution-and-modification-history", "name": "Distribution and modification history", "description": "Connect release identity to OEM customization, updates and later alterations.", "findings": [ { "id": "installation-lineage", "name": "Installation lineage", "description": "Record distribution origin and subsequent changes without assuming that the displayed version describes every installed component.", "questions": [ { "text": "What evidence identifies the original distribution variant, language and installation source?", "kind": "provenance", "id": "installation-lineage-q01" }, { "text": "Which updates, OEM additions or unofficial modifications changed the installation after its original setup?", "kind": "provenance", "id": "installation-lineage-q02" } ] } ] } ] }, { "id": "boot-and-runtime-behavior", "name": "Boot and runtime behavior", "description": "Represent Windows 95 startup, its DOS relationship and execution conditions for legacy applications.", "rationale": "A usable desktop, a functioning DOS environment and successful application execution are distinct outcomes.", "layers": [ { "id": "startup-and-recovery-paths", "name": "Startup and recovery paths", "description": "Locate failures within the path from boot selection to the Windows desktop.", "findings": [ { "id": "boot-stage-observation", "name": "Boot stage observation", "description": "Record the last successful startup stage, visible errors and behavior under available diagnostic startup options.", "questions": [ { "text": "What is the last reproducibly successful startup stage, and what exact error or symptom follows it?", "kind": "measurement", "id": "boot-stage-observation-q01" }, { "text": "Which available startup or recovery option can test the suspected cause while preserving the current configuration?", "kind": "action", "id": "boot-stage-observation-q02" } ] } ] }, { "id": "dos-and-windows-execution", "name": "DOS and Windows execution", "description": "Distinguish application requirements across DOS execution modes and Windows application interfaces.", "findings": [ { "id": "workload-execution-contract", "name": "Workload execution contract", "description": "Capture the exact environment required by a workload, including execution mode, shared components and resource dependencies.", "questions": [ { "text": "Does the target application require a Windows session, a DOS session within Windows or a separate DOS startup configuration?", "kind": "boundary", "id": "workload-execution-contract-q01" }, { "text": "Which application version, dependencies and representative operations have been tested successfully on this installation?", "kind": "measurement", "id": "workload-execution-contract-q02" } ] } ] } ] }, { "id": "hardware-drivers-and-storage", "name": "Hardware, drivers and storage", "description": "Capture the host interfaces and disk conditions on which this Windows 95 installation depends.", "rationale": "Hardware detection, driver compatibility and filesystem support must be assessed for the actual release and host.", "layers": [ { "id": "device-and-host-fit", "name": "Device and host fit", "description": "Relate physical or emulated devices to their drivers and observed operating behavior.", "findings": [ { "id": "device-driver-operability", "name": "Device-driver operability", "description": "Distinguish detected hardware from verified operation, including resource conflicts and host-emulation effects.", "questions": [ { "text": "Which display, audio, storage and network devices are presented to Windows 95, and which drivers serve them?", "kind": "provenance", "id": "device-driver-operability-q01" }, { "text": "Which devices pass functional checks, and which show missing drivers, resource conflicts or host-dependent failures?", "kind": "measurement", "id": "device-driver-operability-q02" } ] } ] }, { "id": "volume-and-file-compatibility", "name": "Volume and file compatibility", "description": "Assess disk layout and file handling against the installed release and maintenance tools.", "findings": [ { "id": "storage-access-and-preservation", "name": "Storage access and preservation", "description": "Record readable and bootable volumes, filesystem evidence and the handling of long filenames during transfers or repairs.", "questions": [ { "text": "Which filesystems and partition arrangements are present, and which can this specific release read and boot from?", "kind": "measurement", "id": "storage-access-and-preservation-q01" }, { "text": "Which transfer or repair procedure preserves file contents, long filenames and required boot information?", "kind": "action", "id": "storage-access-and-preservation-q02" } ] } ] } ] }, { "id": "controlled-use-and-preservation", "name": "Controlled use and preservation", "description": "Determine how a Windows 95 installation can support its intended workload and remain recoverable.", "rationale": "Legacy operation requires explicit decisions about connectivity, trusted inputs and restoration rather than merely successful startup.", "layers": [ { "id": "network-and-transfer-boundaries", "name": "Network and transfer boundaries", "description": "Record installed networking components and the actual paths by which data enters or leaves the system.", "findings": [ { "id": "connectivity-decision", "name": "Connectivity decision", "description": "Tie network access and file transfer to a documented workload, observed configuration and available isolation controls.", "questions": [ { "text": "Which networking components, shares and routes are enabled, and what systems can actually reach the installation?", "kind": "measurement", "id": "connectivity-decision-q01" }, { "text": "What connectivity or transfer method is sufficient for the intended workload, given the installed components and available isolation?", "kind": "action", "id": "connectivity-decision-q02" } ] } ] }, { "id": "restoration-and-continuity", "name": "Restoration and continuity", "description": "Preserve the software environment and assess whether its required behavior can be recovered or transferred.", "findings": [ { "id": "recoverable-installation", "name": "Recoverable installation", "description": "Connect a preserved installation to boot media, drivers, configuration evidence and a tested recovery target.", "questions": [ { "text": "Which disk images, installation materials, drivers and configuration records are available, and what is their provenance?", "kind": "provenance", "id": "recoverable-installation-q01" }, { "text": "Has restoration reproduced the required workload on the intended physical or emulated host, and what differences remain?", "kind": "measurement", "id": "recoverable-installation-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": [ "This describes the software product, not an installation disc, packaged copy or individual installed instance; the supplied PHY.OBJ classification should be reviewed.", "Release-specific features, especially FAT32 and USB support, must be checked against the exact OEM release and installed supplements.", "These statements are recalled knowledge, not findings verified against sources in this response." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Windows 95 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": [ "Original retail release", "OEM Service Release 1 (OSR1)", "OEM Service Release 2 (OSR2)", "OEM Service Release 2.1 (OSR2.1)", "OEM Service Release 2.5 (OSR2.5)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Windows 95 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": "Microsoft Windows version numbering", "value_or_pattern": "4.00.950", "note": "Version associated with the original Windows 95 release; later servicing and OEM releases have distinguishing version information." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Windows 95 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 contemporary office, educational and home productivity applications", "Playing DOS and Windows PC games", "Providing graphical file management through Windows Explorer", "Connecting personal computers to local networks and dial-up internet services", "Preserving or demonstrating legacy software and computing environments" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Windows 95 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": [ "Faulty drivers and applications can cause system freezes or crashes.", "Legacy compatibility mechanisms and shared system resources limit isolation between applications.", "Exhaustion of finite USER and GDI resources can destabilize the desktop even when memory remains available.", "Abrupt shutdowns can corrupt files and FAT filesystem structures.", "The system no longer receives vendor security updates and is unsuitable for unprotected exposure to modern networks." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Windows 95 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": [ "Localized editions differ in interface language, keyboard layouts and regional settings.", "Some East Asian editions provide language-specific input methods and character-handling support." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Windows 95 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": "Microsoft Windows", "difference": "Microsoft Windows is the broader operating-system family; Windows 95 is a particular historical product within it." }, { "name": "Windows 3.1", "difference": "Windows 3.1 is the earlier DOS-based graphical environment; Windows 95 introduced the Start menu and taskbar and substantially expanded 32-bit application support." }, { "name": "Windows 98", "difference": "Windows 98 is a later Windows 9x release with expanded hardware support and other system changes." }, { "name": "Windows NT", "difference": "Windows NT uses a distinct operating-system architecture with stronger process isolation and security; Windows 95 belongs to the DOS-derived Windows 9x line." }, { "name": "MS-DOS", "difference": "MS-DOS is a command-line operating system and a foundational component of Windows 95, rather than the complete Windows 95 graphical operating environment." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Windows 95 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Should the registry retain PHY / PHY.OBJ for Windows 95, or classify the software separately from its physical carriers?", "Which authoritative release references establish the build, distribution and component distinctions that this model should recognize?", "What release-specific limits and update prerequisites govern storage, memory, peripheral support and networking?", "Which original installation materials and modification records remain available to establish provenance and reproducibility?", "Which workloads require original hardware behavior, and what evidence would make an emulated or migrated environment an acceptable substitute?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }, "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 Windows 95, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to identify a Windows 95 release or installation, assess its compatibility and operating state, and choose appropriate preservation, recovery or controlled-use actions.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Described in 81 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 Windows 95, 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 Windows 95 looks like has to come from research." ], "relatedModels": [], "standing": "Described in 81 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 Windows 95 from another, and a Windows 95 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 Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95 is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95 between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Windows 95 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 Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95 is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a Windows 95 performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a Windows 95 at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 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 Windows 95 and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Windows 95, 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 Windows 95, 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 Windows 95 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 Windows 95 is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Windows 95, 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 Windows 95, 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 Windows 95 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 } } } }