{ "model": { "rank": 5579, "code": "thing-q183065", "model_id": "vr.tr.interpreter", "name": "interpreter", "purpose": "Enable an agent to identify a software interpreter, assess its execution capabilities and state, and decide whether and how to run a given program with it.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q183065/", "tier": 2, "score": 66, "payload": { "layer": "wikidata", "aliases": [ "visual novel engine", "command-line interpreter", "meta-circular evaluator", "BASIC interpreter" ], "aliasCount": 4, "merged": 4, "knownIn": 66, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.interpreter-person", "source": { "dataset": "wikidata", "item": "Q183065", "url": "https://www.wikidata.org/wiki/Q183065", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:41:41Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.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: 01a08854-a788-7481-91a6-6842f6f14005\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: interpreter\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 188 things:\n# Batch 006: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 57.1, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a08854-a791-75f1-b5ec-0c50a3358c37\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: interpreter\nRegistry id: vr.tr.interpreter\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } } }, "metaModel": { "id": "THING-Q183065", "registryId": "vr.tr.interpreter", "name": "interpreter", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q183065/", "model": { "registry_id": "vr.tr.interpreter", "name": "interpreter", "purpose": "Enable an agent to identify a software interpreter, assess its execution capabilities and state, and decide whether and how to run a given program with it.", "definition": "An interpreter is a software system that executes a program by evaluating its source text or an intermediate representation, rather than requiring a separately generated native executable before execution.", "scope_statement": "This draft provisionally treats interpreter as software that executes instructions according to a programming or command language; it owns the interpreter's language contract, execution mechanisms, runtime dependencies, operational state and execution controls, pending confirmation of the registry's intended sense.", "in_scope": [ "Supported languages, dialects, versions and extensions", "Execution of source text, syntax trees, bytecode or other intermediate instructions", "Evaluation rules, runtime state and interaction modes", "Dependencies, host interfaces and resource access", "Execution diagnostics, limits and isolation controls" ], "out_of_scope": [ "Human language interpreters and interpreting services", "The programming language specification as an independent information artifact", "Programs executed by the interpreter and their application-specific correctness", "Standalone compilers and their independently distributed output", "Editors, development environments and operating systems that host the interpreter" ], "distinguishing_features": [ "It executes supplied instructions under a language's rules; a parser alone only recognizes or structures input.", "Its relevant role is running programs, whereas a standalone compiler's relevant role is producing another program representation for subsequent use.", "It may combine interpretation with compilation, so the presence of bytecode or just-in-time compilation does not by itself exclude it.", "It applies programmable execution semantics rather than merely displaying, decoding or translating content.", "A shell or virtual machine falls within this model only for its instruction-execution role; command orchestration or machine abstraction may require neighbouring models." ], "characteristics": [ { "name": "Accepted language contract", "kind": "relation", "unit_or_values": "Language specifications, dialects, versions and enabled extensions", "why_it_matters": "Determines which programs the interpreter is intended to accept and what their instructions mean." }, { "name": "Accepted instruction representation", "kind": "category", "unit_or_values": "Source text, syntax tree, bytecode, other intermediate representation, or documented combination", "why_it_matters": "Determines which preparation steps and input artifacts execution requires." }, { "name": "Execution strategy", "kind": "category", "unit_or_values": "Direct interpretation, intermediate-code interpretation, mixed interpretation and compilation, or unresolved", "why_it_matters": "Helps explain execution behaviour and boundaries with compilers and virtual machines." }, { "name": "Invocation modes", "kind": "category", "unit_or_values": "Batch execution, interactive session, embedded API, service endpoint, or implementation-specific modes", "why_it_matters": "Determines how an agent can submit instructions and obtain results." }, { "name": "Runtime readiness", "kind": "state", "unit_or_values": "Unverified, ready, missing dependencies, incompatible configuration, failed, or unavailable", "why_it_matters": "Separates an installed artifact from an execution environment that can actually run the intended program." }, { "name": "State persistence", "kind": "category", "unit_or_values": "Per invocation, per session, shared across sessions, explicitly checkpointed, or unknown", "why_it_matters": "Determines whether earlier execution can affect later results." }, { "name": "Effective host capabilities", "kind": "relation", "unit_or_values": "Accessible filesystem locations, network interfaces, processes, native libraries and privileged host APIs", "why_it_matters": "Establishes what executed instructions can affect beyond interpreter-managed state." }, { "name": "Configured execution limits", "kind": "measurement", "unit_or_values": "Time in seconds, memory in bytes, instruction or recursion counts where supported; unspecified limits recorded explicitly", "why_it_matters": "Supports bounded execution and distinguishes configured limits from measured resource consumption." } ], "affordances": [ "Check whether a program's required language features and dependencies match the interpreter.", "Prepare an invocation with explicit arguments, environment, input representation and module paths.", "Execute instructions in a fresh or deliberately reused runtime context.", "Inspect results, exceptions, traces and exit status.", "Apply supported resource limits and host-access restrictions before execution.", "Interrupt execution or reset a session using documented controls." ] }, "sources": [], "structure": { "bundles": [ { "id": "language-contract", "name": "Language contract", "description": "What instructions this interpreter accepts and which semantic commitments govern their execution.", "rationale": "An interpreter cannot be selected reliably from its product name alone; language compatibility must be established.", "layers": [ { "id": "language-and-dialect", "name": "Language and dialect", "description": "Supported language identities and the scope of compatibility.", "findings": [ { "id": "supported-language-boundary", "name": "Supported language boundary", "description": "Record the claimed language versions, dialects and extensions separately from compatibility demonstrated by evidence.", "questions": [ { "text": "Which language specifications, versions and optional extensions does this interpreter claim to implement?", "kind": "definition", "id": "supported-language-boundary-q01" }, { "text": "What documentation or conformance evidence supports those claims and identifies deviations?", "kind": "provenance", "id": "supported-language-boundary-q02" } ] } ] }, { "id": "accepted-program-forms", "name": "Accepted program forms", "description": "The representations and preparation requirements at the execution boundary.", "findings": [ { "id": "executable-input-contract", "name": "Executable input contract", "description": "Identify accepted instruction representations and distinguish interpreter inputs from artifacts requiring another tool first.", "questions": [ { "text": "Does execution accept source text, syntax trees, bytecode or another representation, and with what format or version constraints?", "kind": "definition", "id": "executable-input-contract-q01" }, { "text": "Which parsing, translation or compilation steps occur inside the interpreter, and which require a separate component?", "kind": "boundary", "id": "executable-input-contract-q02" } ] } ] } ] }, { "id": "evaluation-and-runtime-state", "name": "Evaluation and runtime state", "description": "How instructions are evaluated and how execution state persists.", "rationale": "The same input can behave differently under different evaluation settings or previously established runtime state.", "layers": [ { "id": "evaluation-behaviour", "name": "Evaluation behaviour", "description": "Execution mechanisms and implementation choices relevant to observable program behaviour.", "findings": [ { "id": "semantic-execution-profile", "name": "Semantic execution profile", "description": "Record evaluation choices and configurable behaviours that affect the meaning or outcome of accepted instructions.", "questions": [ { "text": "Which evaluation rules are fixed by the language contract, and which depend on interpreter options or implementation choices?", "kind": "boundary", "id": "semantic-execution-profile-q01" }, { "text": "What checks demonstrate the behaviour of relevant numeric operations, evaluation order and exception handling?", "kind": "measurement", "id": "semantic-execution-profile-q02" } ] } ] }, { "id": "session-state", "name": "Session state", "description": "The lifetime and sharing of bindings, loaded modules and other interpreter-managed state.", "findings": [ { "id": "state-lifetime-and-reset", "name": "State lifetime and reset", "description": "Describe which execution effects persist and what is required to obtain a fresh runtime context.", "questions": [ { "text": "Which bindings, module instances, caches and execution settings survive between submissions or are shared between sessions?", "kind": "definition", "id": "state-lifetime-and-reset-q01" }, { "text": "How can an agent reset interpreter-managed state, and which external effects remain after that reset?", "kind": "action", "id": "state-lifetime-and-reset-q02" } ] } ] } ] }, { "id": "invocation-and-integration", "name": "Invocation and integration", "description": "How an agent starts execution and supplies the surrounding runtime environment.", "rationale": "Language support is insufficient when invocation conventions, module resolution or host dependencies prevent execution.", "layers": [ { "id": "execution-entry-points", "name": "Execution entry points", "description": "Batch, interactive and embedded interfaces exposed by the interpreter.", "findings": [ { "id": "submission-and-result-protocol", "name": "Submission and result protocol", "description": "Record how programs and arguments enter the interpreter and how completion and outputs are communicated.", "questions": [ { "text": "Which command-line, interactive, embedded or service interfaces accept instructions, arguments and standard input?", "kind": "action", "id": "submission-and-result-protocol-q01" }, { "text": "How does each interface distinguish returned values, ordinary output, diagnostics and completion status?", "kind": "definition", "id": "submission-and-result-protocol-q02" } ] } ] }, { "id": "dependency-and-host-binding", "name": "Dependency and host binding", "description": "Required runtime components and resolution of imported or host-provided functionality.", "findings": [ { "id": "runtime-resolution-context", "name": "Runtime resolution context", "description": "Identify the environment that determines which modules, libraries and host interfaces executed instructions receive.", "questions": [ { "text": "Which runtime components and host versions are required for this interpreter build and intended program?", "kind": "definition", "id": "runtime-resolution-context-q01" }, { "text": "How are module paths, native libraries, working directories and environment variables resolved for an invocation?", "kind": "action", "id": "runtime-resolution-context-q02" } ] } ] } ] }, { "id": "execution-control-and-isolation", "name": "Execution control and isolation", "description": "What interpreted instructions may access and how execution can be bounded or stopped.", "rationale": "An interpreter mediates executable instructions, making effective authority and interruption behaviour central to permitted actions.", "layers": [ { "id": "host-access", "name": "Host access", "description": "Capabilities exposed to programs and the mechanisms enforcing restrictions.", "findings": [ { "id": "effective-program-authority", "name": "Effective program authority", "description": "Record accessible host resources and distinguish interpreter-enforced restrictions from protections supplied by its host.", "questions": [ { "text": "Can executed code access files, networks, subprocesses, native extensions or privileged host objects in this configuration?", "kind": "boundary", "id": "effective-program-authority-q01" }, { "text": "Which restrictions are enforced by the interpreter, which by external isolation, and what evidence establishes their coverage?", "kind": "provenance", "id": "effective-program-authority-q02" } ] } ] }, { "id": "limits-and-interruption", "name": "Limits and interruption", "description": "Resource budgets, cancellation mechanisms and behaviour when execution is terminated.", "findings": [ { "id": "bounded-execution-controls", "name": "Bounded execution controls", "description": "Identify enforceable execution budgets and the state left behind by limit violations or cancellation.", "questions": [ { "text": "Which time, memory, recursion or instruction limits can be enforced, and do they cover native calls and spawned work?", "kind": "measurement", "id": "bounded-execution-controls-q01" }, { "text": "How can execution be interrupted, and must the runtime be discarded before another program can safely run?", "kind": "action", "id": "bounded-execution-controls-q02" } ] } ] } ] }, { "id": "diagnostics-and-reproducibility", "name": "Diagnostics and reproducibility", "description": "Evidence needed to explain execution outcomes and reproduce them under a known interpreter configuration.", "rationale": "An agent must distinguish program failures from interpreter failures and preserve enough execution context to investigate either.", "layers": [ { "id": "failure-observation", "name": "Failure observation", "description": "Errors and traces exposed across parsing, loading and execution.", "findings": [ { "id": "failure-classification-and-location", "name": "Failure classification and location", "description": "Capture failure categories and their association with the instructions or runtime components involved.", "questions": [ { "text": "How are syntax errors, dependency failures, runtime exceptions and interpreter crashes distinguished?", "kind": "definition", "id": "failure-classification-and-location-q01" }, { "text": "Which source locations, stack frames or execution traces can an agent retrieve for diagnosis?", "kind": "action", "id": "failure-classification-and-location-q02" } ] } ] }, { "id": "execution-context-evidence", "name": "Execution context evidence", "description": "Interpreter identity and environmental factors needed to compare or repeat executions.", "findings": [ { "id": "reproducible-runtime-record", "name": "Reproducible runtime record", "description": "Link observed behaviour to a specific interpreter artifact, configuration and relevant runtime inputs.", "questions": [ { "text": "What build identifiers, artifact provenance, flags and dependency versions identify the interpreter used for this execution?", "kind": "provenance", "id": "reproducible-runtime-record-q01" }, { "text": "Which state, random seeds, locale, clock inputs or scheduling factors must be controlled to repeat the observed result?", "kind": "measurement", "id": "reproducible-runtime-record-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 name has no recorded sense. This description assumes the software meaning; the registry classification should be checked before adopting it.", "Interpretation and compilation are implementation techniques that often coexist, rather than mutually exclusive properties of a programming language.", "These are recalled facts, not researched findings; no sources were consulted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of interpreter 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": [ "Tree-walking interpreter", "Bytecode interpreter", "Interpreter combined with just-in-time compilation" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of interpreter 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": [ "ECMA-262, issued by Ecma International, specifies ECMAScript semantics that an ECMAScript interpreter must implement to conform; it does not require interpretation as the execution method." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of interpreter 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 scripts and automating tasks", "Providing interactive programming environments", "Embedding programmable behavior in applications", "Executing portable bytecode", "Implementing and experimenting with programming languages" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of interpreter this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Program execution time", "typical_range": "Depends on the workload, implementation and hardware; no general range applies.", "unit": "seconds" }, { "quantity": "Peak memory consumption", "typical_range": "Depends on program state and runtime implementation; no general range applies.", "unit": "bytes" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of interpreter 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": [ "Incorrect implementation of language semantics produces wrong results.", "Untrusted programs can access host resources unless access is effectively restricted.", "Programs can exhaust memory or execution time.", "Differences between versions or implementations can break compatibility.", "Interpreter overhead can make performance inadequate for a workload." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of interpreter 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": "compiler", "difference": "A compiler translates a program into another representation; an interpreter executes it. A single implementation can combine both functions." }, { "name": "virtual machine", "difference": "A virtual machine provides an abstract execution environment; interpretation is one way to implement that environment." }, { "name": "runtime system", "difference": "A runtime system supplies execution services such as memory management; it need not interpret program instructions." }, { "name": "human language interpreter", "difference": "A human language interpreter mediates communication between languages rather than executing computer programs." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of interpreter this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.interpreter denote a software interpreter, a human interpreting role or another sense, and what registry evidence resolves this ambiguity?", "Does an existing Vercy world model already cover this concept and therefore need to be linked instead of creating a separate publication?", "Where does this registry draw the boundaries between interpreter, runtime, virtual machine, shell and mixed compiler-interpreter implementations?", "Should the model primarily describe an interpreter implementation, a distributed build or a running instance, and how should those identities be related?", "Which authoritative specifications, implementation documentation and observed tests should substantiate language compatibility, isolation and interruption claims during research?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 17, "questions": 27 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "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 interpreter, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to identify a software interpreter, assess its execution capabilities and state, and decide whether and how to run a given program with it.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: visual novel engine, command-line interpreter, meta-circular evaluator, BASIC interpreter.", "4 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 66 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 interpreter, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "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": [ "read it and act on what it says", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "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": [ "visual novel engine", "command-line interpreter", "meta-circular evaluator", "BASIC interpreter" ] } ], "standing": "Described in 66 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 interpreter from another, and a interpreter 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 interpreter, 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 interpreter, 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 interpreter 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 interpreter, 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 interpreter, 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 interpreter 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 interpreter 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 interpreter, 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 interpreter, 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 interpreter 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 interpreter from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a interpreter, 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 interpreter, 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 interpreter 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 interpreter 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 interpreter between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a interpreter, 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 interpreter, 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 interpreter 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 interpreter, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a interpreter 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 interpreter, 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 interpreter, 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 interpreter is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a interpreter says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a interpreter contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a interpreter, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a interpreter, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a interpreter is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a interpreter and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a interpreter, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a interpreter, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a interpreter is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of interpreter a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For interpreter, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of interpreter exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made interpreter and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to interpreter, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in interpreter, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a interpreter 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 interpreter and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a interpreter, 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 interpreter, 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 interpreter 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 interpreter is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a interpreter, 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 interpreter, 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 interpreter is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }