{ "model": { "rank": 5826, "code": "thing-q170434", "model_id": "vr.tr.dos", "name": "DOS", "purpose": "Provisionally treating DOS as a disk operating system, this model enables an agent to identify a DOS environment, assess its usability and compatibility, and determine which operations it can safely perform.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q170434/", "tier": 2, "score": 64, "payload": { "layer": "wikidata", "aliases": [ "DOS/V", "ZDOS", "FreeDOS", "Svarog386" ], "aliasCount": 4, "merged": 4, "knownIn": 64, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q170434", "url": "https://www.wikidata.org/wiki/Q170434", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:29:48Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": 0.01714242, "turns": 3, "seconds": 38.3, "error": "model did not produce structured output", "retried": true }, "codex": { "seconds": 78.5, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07b32-9245-7ac1-8b26-76bd9a55be09\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: DOS\nRegistry id: vr.tr.dos\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model say" } } }, "metaModel": { "id": "THING-Q170434", "registryId": "vr.tr.dos", "name": "DOS", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q170434/", "model": { "registry_id": "vr.tr.dos", "name": "DOS", "purpose": "Provisionally treating DOS as a disk operating system, this model enables an agent to identify a DOS environment, assess its usability and compatibility, and determine which operations it can safely perform.", "definition": "", "scope_statement": "This model owns the identity, execution behaviour, disk organisation, configuration and operational state of a DOS operating-system installation or running environment; this interpretation remains provisional because the registry supplies no definition and classifies DOS under PHY / PHY.OBJ.", "in_scope": [ "DOS implementation, release and installation identity", "Boot sequence, system components and command interpreter", "Drive addressing, filesystem behaviour and file attributes", "Executable compatibility and memory requirements", "Drivers, startup configuration and session state" ], "out_of_scope": [ "Physical computer construction and hardware condition", "Storage-device manufacture, wear and physical repair", "Application-specific functionality and user documents", "Emulator implementation and host operating-system administration", "Denial-of-service events or other concepts abbreviated DOS" ], "distinguishing_features": [ "Confirm that DOS names an operating system in the originating registry context; acronym spelling alone does not establish the referent.", "Distinguish a DOS operating environment from a command prompt by establishing which system supplies its program-loading and operating-system services.", "Distinguish an installed system from an installation disk or disk image by recording whether the referent is software, its physical carrier or a runnable environment.", "Distinguish implementations and releases through component evidence and observed behaviour rather than treating every DOS-labelled environment as interchangeable.", "Distinguish native boot, emulation and a host-provided compatibility environment because identical commands can operate under different constraints." ], "characteristics": [ { "name": "Referent interpretation", "kind": "state", "unit_or_values": "disk-operating-system interpretation confirmed | provisional | rejected", "why_it_matters": "Prevents an acronym-based assumption from becoming an authoritative model of the wrong registered thing." }, { "name": "Implementation and release", "kind": "category", "unit_or_values": "Evidence-supported implementation name, release and component variants; unknown permitted", "why_it_matters": "Determines which commands, configuration rules and compatibility expectations apply." }, { "name": "Execution context", "kind": "category", "unit_or_values": "native boot | emulator | virtual machine | host compatibility environment | offline installation | unresolved", "why_it_matters": "Identifies which system controls devices, memory and recovery." }, { "name": "Boot progress", "kind": "state", "unit_or_values": "not attempted | boot failure | startup configuration failure | command interpreter available | application running | unresolved", "why_it_matters": "Separates failure to start the operating system from failure to start an application." }, { "name": "Command interpreter", "kind": "relation", "unit_or_values": "Identified interpreter executable, version evidence and invocation configuration", "why_it_matters": "Command syntax and batch behaviour depend on the interpreter actually in use." }, { "name": "Available program memory", "kind": "measurement", "unit_or_values": "Bytes available by supported memory class, including largest allocatable conventional-memory block where applicable", "why_it_matters": "A program may fail despite sufficient installed RAM if the required memory class or contiguous block is unavailable." }, { "name": "Drive-letter mapping", "kind": "relation", "unit_or_values": "Drive letter to volume, image, removable medium, network resource or host mapping", "why_it_matters": "A path must be resolved to its actual target before reading, modifying or deleting files." }, { "name": "Filesystem and filename capabilities", "kind": "category", "unit_or_values": "Observed filesystem formats, filename rules, attributes and implementation-specific extensions", "why_it_matters": "Controls whether files can be addressed, transferred and modified without losing meaning or data." } ], "affordances": [ "Inspect version evidence and system components to identify the DOS implementation.", "Trace boot and startup processing to locate a failure.", "Evaluate whether a specified executable can run with the available services and memory.", "Resolve DOS paths to their backing storage before performing authorised file operations.", "Inspect and adjust startup configuration or driver loading with a recovery route.", "Run supported commands and batch files after checking interpreter behaviour and write targets." ] }, "sources": [], "structure": { "bundles": [ { "id": "dos-identity-and-context", "name": "DOS identity and context", "description": "Establishes what DOS denotes and which operating environment is being assessed.", "rationale": "The undefined acronym and physical-object classification make referent confirmation essential before applying operating-system assumptions.", "layers": [ { "id": "registry-referent", "name": "Registry referent", "description": "Connects the registered name to an evidenced meaning.", "findings": [ { "id": "dos-meaning-and-boundary", "name": "DOS meaning and boundary", "description": "Record evidence establishing whether DOS denotes an operating system, a physical carrier or another thing.", "questions": [ { "text": "What originating registry context establishes the intended meaning of DOS?", "kind": "provenance", "id": "dos-meaning-and-boundary-q01" }, { "text": "Does PHY / PHY.OBJ describe the intended thing, its carrier, or a classification error?", "kind": "boundary", "id": "dos-meaning-and-boundary-q02" } ] } ] }, { "id": "implementation-context", "name": "Implementation context", "description": "Identifies the implementation and the system supplying its execution services.", "findings": [ { "id": "implementation-and-runtime", "name": "Implementation and runtime", "description": "Record implementation evidence separately from reported version strings and hosting conditions.", "questions": [ { "text": "Which implementation and release are supported by the installed system components?", "kind": "provenance", "id": "implementation-and-runtime-q01" }, { "text": "Which services come from DOS itself, and which come from an emulator, virtual machine or host compatibility environment?", "kind": "boundary", "id": "implementation-and-runtime-q02" } ] } ] } ] }, { "id": "boot-and-startup", "name": "Boot and startup", "description": "Captures the path from the boot source to a usable command interpreter or application.", "rationale": "DOS usability depends on the boot components and startup choices actually activated.", "layers": [ { "id": "boot-chain", "name": "Boot chain", "description": "Identifies the selected boot source and the last successful startup stage.", "findings": [ { "id": "boot-source-and-progress", "name": "Boot source and progress", "description": "Record the boot target, required components and observable point of failure.", "questions": [ { "text": "Which volume or image supplies the boot components for this DOS environment?", "kind": "provenance", "id": "boot-source-and-progress-q01" }, { "text": "What is the last confirmed successful stage before a boot failure or usable prompt?", "kind": "measurement", "id": "boot-source-and-progress-q02" } ] } ] }, { "id": "startup-configuration", "name": "Startup configuration", "description": "Captures interpreter selection and configuration-driven startup behaviour.", "findings": [ { "id": "effective-startup-sequence", "name": "Effective startup sequence", "description": "Record the startup files and selected branches that load drivers, set the environment and launch commands.", "questions": [ { "text": "Which configuration and batch files are processed, in what order, by this implementation?", "kind": "definition", "id": "effective-startup-sequence-q01" }, { "text": "How can a suspect startup command or driver be bypassed while preserving a recoverable boot path?", "kind": "action", "id": "effective-startup-sequence-q02" } ] } ] } ] }, { "id": "dos-storage-and-paths", "name": "DOS storage and paths", "description": "Captures how drive letters, directories and filesystem rules identify data.", "rationale": "DOS file operations require an accurate mapping from command-visible paths to backing storage.", "layers": [ { "id": "drive-resolution", "name": "Drive resolution", "description": "Resolves drive letters and relative paths within the current session.", "findings": [ { "id": "effective-path-target", "name": "Effective path target", "description": "Record drive mappings and directory context sufficient to determine a command's actual file target.", "questions": [ { "text": "What backing volume, image or redirected resource does each relevant drive letter identify?", "kind": "boundary", "id": "effective-path-target-q01" }, { "text": "How do the current drive and directory state resolve the exact path supplied to the proposed command?", "kind": "measurement", "id": "effective-path-target-q02" } ] } ] }, { "id": "filesystem-behaviour", "name": "Filesystem behaviour", "description": "Captures supported naming, attributes and storage constraints.", "findings": [ { "id": "file-operation-constraints", "name": "File operation constraints", "description": "Record the filesystem and implementation rules that affect file access and mutation.", "questions": [ { "text": "Which filename, attribute and volume-size rules apply to the target volume in this environment?", "kind": "definition", "id": "file-operation-constraints-q01" }, { "text": "Will the proposed copy, rename or deletion encounter unsupported names, write protection or insufficient free space?", "kind": "action", "id": "file-operation-constraints-q02" } ] } ] } ] }, { "id": "program-execution-and-resources", "name": "Program execution and resources", "description": "Determines whether commands and programs can execute under the available DOS services and resource configuration.", "rationale": "A working prompt does not establish application compatibility or adequate program memory.", "layers": [ { "id": "program-compatibility", "name": "Program compatibility", "description": "Connects a particular executable or batch file to its required execution behaviour.", "findings": [ { "id": "executable-service-fit", "name": "Executable service fit", "description": "Record program requirements for executable loading, system services, processor features and interpreter behaviour.", "questions": [ { "text": "What executable format, DOS services, processor capabilities or runtime extensions does the target program require?", "kind": "definition", "id": "executable-service-fit-q01" }, { "text": "What controlled execution check would establish compatibility without risking the program's working data?", "kind": "action", "id": "executable-service-fit-q02" } ] } ] }, { "id": "memory-and-resident-components", "name": "Memory and resident components", "description": "Captures usable memory and the effects of loaded drivers and resident programs.", "findings": [ { "id": "usable-program-resources", "name": "Usable program resources", "description": "Record available memory by relevant class and identify loaded components affecting execution.", "questions": [ { "text": "How much memory is available in each class required by the program, and what is the largest usable conventional-memory block where applicable?", "kind": "measurement", "id": "usable-program-resources-q01" }, { "text": "Which driver or resident-program changes could satisfy the requirement, and which required services would those changes remove?", "kind": "action", "id": "usable-program-resources-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does DOS actually mean disk operating system in this registry, or does the PHY / PHY.OBJ placement identify a different physical thing?", "If the operating-system interpretation is confirmed, does the entry cover a family of systems, a particular implementation, an installation or a running instance?", "Does an existing Vercy world model already own this concept, requiring a registry link rather than another publication?", "Which implementation-specific sources must be read to establish boot, filesystem, memory and command behaviour without generalising across incompatible DOS variants?", "Should installation media and bootable disk images be related neighbouring things, and where does the registry place their ownership boundary?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "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 DOS, record what state it is in, and decide what may be done with it.", "whatItIs": "Provisionally treating DOS as a disk operating system, this model enables an agent to identify a DOS environment, assess its usability and compatibility, and determine which operations it can safely perform.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: DOS/V, ZDOS, FreeDOS, Svarog386.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 64 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 DOS, 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 DOS looks like has to come from research." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "DOS/V", "ZDOS", "FreeDOS", "Svarog386" ] } ], "standing": "Described in 64 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 4 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one DOS from another, and a DOS 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 DOS, 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 DOS, 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 DOS 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 DOS, 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 DOS, 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 DOS 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 DOS 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 DOS, 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 DOS, 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 DOS 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 DOS from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a DOS, 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 DOS, 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 DOS 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 DOS 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 DOS, 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 DOS, 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 DOS 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 DOS is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a DOS, 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 DOS, 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 DOS 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 DOS is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a DOS, 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 DOS, 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 DOS 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 DOS 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 DOS is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a DOS, 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 DOS, 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 DOS 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 DOS 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 DOS, 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 DOS, 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 DOS 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 DOS 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 DOS between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a DOS, 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 DOS, 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 DOS 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 DOS, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a DOS 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 DOS, 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 DOS, 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 DOS 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 DOS 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 DOS is for, and what it is used for anyway.", "findings": [ { "id": "function-and-purpose", "name": "Function, purpose and misuse", "description": "The function a DOS performs and the uses that fall outside it.", "questions": [ { "id": "function-and-purpose-q01", "text": "What identifies and describes the use of a DOS, 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 DOS, 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 DOS 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 DOS.", "findings": [ { "id": "procedures-and-skills", "name": "Procedures, skills and required tools", "description": "What an agent needs before it can act on a DOS at all.", "questions": [ { "id": "procedures-and-skills-q01", "text": "What identifies and describes handling a DOS, 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 DOS, 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 DOS 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 DOS 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 DOS and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a DOS, 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 DOS, 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 DOS 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 DOS is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a DOS, 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 DOS, 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 DOS 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 } } } }