{ "model": { "rank": 6622, "code": "thing-q193564", "model_id": "vr.tr.game-engine", "name": "game engine", "purpose": "Enable an agent to recognise a game engine, assess its suitability and operational state, and determine how it may be used, extended, upgraded or distributed.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q193564/", "tier": 2, "score": 59, "payload": { "layer": "wikidata", "aliases": [ "server software for MUD-like games", "game engine version", "proprietary engine", "isometric engine", "general game system", "game engine recreation", "tile engine", "sound engine", "first-person shooter engine" ], "aliasCount": 9, "merged": 9, "knownIn": 59, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q193564", "url": "https://www.wikidata.org/wiki/Q193564", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T23:09:14Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.4, "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: 01a0886d-d126-7041-a867-d0ade99b77b4\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: game engine\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 007: 1001 reg", "usd": 0, "recall": true }, "codex": { "seconds": 60.9, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a0886d-d135-78d1-8a05-1b17cd6fdc06\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: game engine\nRegistry id: vr.tr.game-engine\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } } }, "metaModel": { "id": "THING-Q193564", "registryId": "vr.tr.game-engine", "name": "game engine", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q193564/", "model": { "registry_id": "vr.tr.game-engine", "name": "game engine", "purpose": "Enable an agent to recognise a game engine, assess its suitability and operational state, and determine how it may be used, extended, upgraded or distributed.", "definition": "A game engine is a software framework that supplies reusable runtime systems and often development tools for building and executing interactive games, separating general capabilities such as rendering, input and resource management from game-specific content and rules.", "scope_statement": "This model owns the reusable software system that supplies a game's execution foundation and associated development interfaces, distinguishing the engine family, a particular release, a configured build and its use by a game project.", "in_scope": [ "Engine identity, release lineage and boundaries between runtime, editor, tools and optional modules", "Game execution architecture, world representation and gameplay integration", "Supported rendering, simulation, input, audio and networking capabilities", "Asset processing, project authoring, build and deployment workflows", "Compatibility, operational evidence, maintenance and permitted use" ], "out_of_scope": [ "A particular game's rules, narrative, progression and player experience", "Authored assets and their independent ownership or licensing", "Standalone graphics, physics or audio libraries except as engine dependencies", "Storefront operation, publishing campaigns and platform certification regimes", "Host hardware and operating systems except as compatibility requirements" ], "distinguishing_features": [ "Provides a reusable foundation for executing interactive games, with a defined way to integrate game-specific behaviour.", "Coordinates game execution and world state across supporting subsystems, rather than supplying only a rendering, physics or audio function.", "Can be distinguished from a completed game by identifying which execution services remain reusable when that game's content and rules are replaced.", "Has an identifiable runtime architecture or integration contract; an asset collection or authoring tool alone does not establish an engine.", "May include an editor and project tools, but their presence is not required; an engine can expose its development workflow through code and external tools." ], "characteristics": [ { "name": "Engine identity level", "kind": "category", "unit_or_values": "engine family | release | configured build | project-integrated instance", "why_it_matters": "Prevents capabilities or defects observed in one build from being attributed to every version of the engine." }, { "name": "Execution and world architecture", "kind": "category", "unit_or_values": "Recorded update scheduling, world representation, object composition and ownership mechanisms", "why_it_matters": "Determines how gameplay integrates with engine-managed state and execution." }, { "name": "Subsystem capability", "kind": "state", "unit_or_values": "Per capability: built in | optional module | external integration | unsupported | unknown", "why_it_matters": "Separates available engine functions from functions requiring additional components." }, { "name": "Development and deployment compatibility", "kind": "relation", "unit_or_values": "Release-specific links to editor hosts, runtime targets, graphics APIs, SDKs and toolchain versions", "why_it_matters": "A supported development host does not automatically imply support for deploying games to that platform." }, { "name": "Gameplay extension interface", "kind": "category", "unit_or_values": "Documented native APIs, scripting interfaces, visual scripting systems, plugin interfaces and source modification routes", "why_it_matters": "Establishes how an agent can implement behaviour and the compatibility constraints on extensions." }, { "name": "Runtime performance envelope", "kind": "measurement", "unit_or_values": "Frame time in ms, memory in MiB and loading time in s, with workload, hardware, build configuration and percentile specified", "why_it_matters": "Supports suitability judgments using comparable evidence rather than unqualified performance claims." }, { "name": "Maintenance condition", "kind": "state", "unit_or_values": "Recorded support status, unresolved relevant defects, security advisories and available migration routes", "why_it_matters": "Helps decide whether to adopt, retain, isolate or upgrade a release." }, { "name": "Use and distribution entitlement", "kind": "relation", "unit_or_values": "Links to applicable engine, module and service terms for the identified release and intended activity", "why_it_matters": "Determines whether development, modification, deployment and redistribution are permitted." } ], "affordances": [ "Evaluate an identified release and configuration against a game's technical requirements using documented capabilities and representative prototypes.", "Create or configure a project and integrate gameplay through supported extension interfaces.", "Import assets and produce target-specific runtime packages through the engine's supported pipeline.", "Profile execution, inspect world state and diagnose subsystem or integration failures.", "Assess and perform a version migration after checking project, asset and plugin compatibility.", "Determine permitted modification and distribution actions from the applicable terms." ] }, "sources": [], "structure": { "bundles": [ { "id": "engine-identity-and-composition", "name": "Engine identity and composition", "description": "Establishes which engine artifact is being assessed and which components belong to it.", "rationale": "Engine names commonly cover multiple releases, forks and configurations with different capabilities.", "layers": [ { "id": "release-and-build-identity", "name": "Release and build identity", "description": "Separates the engine family from the actual software used.", "findings": [ { "id": "identifiable-engine-artifact", "name": "Identifiable engine artifact", "description": "Record the release, revision, fork ancestry and build configuration needed to identify the assessed artifact.", "questions": [ { "text": "Does this record describe an engine family, a release, a configured build or an instance integrated into a game?", "kind": "definition", "id": "identifiable-engine-artifact-q01" }, { "text": "Which publisher record, source revision or build manifest establishes its identity and fork ancestry?", "kind": "provenance", "id": "identifiable-engine-artifact-q02" } ] } ] }, { "id": "runtime-and-tool-boundaries", "name": "Runtime and tool boundaries", "description": "Locates the runtime, editor, build tools, modules and external dependencies.", "findings": [ { "id": "component-membership", "name": "Component membership", "description": "Identify which components execute in the shipped game and which are development-only or separately supplied.", "questions": [ { "text": "Which components form the runtime, and which exist only for authoring, importing, building or debugging?", "kind": "boundary", "id": "component-membership-q01" }, { "text": "Which required functions depend on optional modules, external libraries or hosted services?", "kind": "boundary", "id": "component-membership-q02" } ] } ] } ] }, { "id": "game-execution-and-world-state", "name": "Game execution and world state", "description": "Describes how the engine advances a game and represents its active world.", "rationale": "Execution order and state ownership constrain gameplay correctness and integration.", "layers": [ { "id": "execution-scheduling", "name": "Execution scheduling", "description": "Captures timing, update phases and concurrency contracts.", "findings": [ { "id": "update-and-timing-contract", "name": "Update and timing contract", "description": "Record how gameplay, input, simulation and presentation are scheduled and synchronised.", "questions": [ { "text": "How are frame-driven updates, fixed-step simulation and input processing ordered?", "kind": "definition", "id": "update-and-timing-contract-q01" }, { "text": "Where may gameplay code run, and which thread, timing or re-entrancy constraints must it obey?", "kind": "action", "id": "update-and-timing-contract-q02" } ] } ] }, { "id": "world-and-object-lifecycle", "name": "World and object lifecycle", "description": "Captures world composition, object ownership and persistence boundaries.", "findings": [ { "id": "world-state-representation", "name": "World state representation", "description": "Record scene, entity or other world abstractions and how their state is created, loaded and destroyed.", "questions": [ { "text": "Which abstractions represent game worlds, objects, behaviour and relationships, and who owns their lifetimes?", "kind": "definition", "id": "world-state-representation-q01" }, { "text": "Which state can the engine serialise or stream, and which save, restore or replication behaviour must the game implement?", "kind": "boundary", "id": "world-state-representation-q02" } ] } ] } ] }, { "id": "interactive-subsystems-and-extension", "name": "Interactive subsystems and extension", "description": "Maps engine capabilities and the supported routes for adding game-specific behaviour.", "rationale": "Suitability depends on how subsystem features and extension mechanisms work together in a particular configuration.", "layers": [ { "id": "subsystem-coverage", "name": "Subsystem coverage", "description": "Records available presentation, simulation and interaction services without assuming a universal feature set.", "findings": [ { "id": "capability-and-integration-map", "name": "Capability and integration map", "description": "Identify rendering, physics, animation, audio, input, navigation and networking support, including their dependencies and limits.", "questions": [ { "text": "Which required subsystems are built in, supplied by modules, externally integrated, unsupported or unverified?", "kind": "boundary", "id": "capability-and-integration-map-q01" }, { "text": "Which release-specific documentation or executable example demonstrates each capability required by the intended game?", "kind": "provenance", "id": "capability-and-integration-map-q02" } ] } ] }, { "id": "gameplay-and-plugin-integration", "name": "Gameplay and plugin integration", "description": "Describes supported extension surfaces and their operational constraints.", "findings": [ { "id": "extension-contract", "name": "Extension contract", "description": "Record how game code and plugins call engine services, receive events and remain compatible.", "questions": [ { "text": "Which native, scripted, visual or source-level mechanisms can add gameplay behaviour or replace engine services?", "kind": "action", "id": "extension-contract-q01" }, { "text": "What API, binary compatibility, memory ownership and reload constraints apply to those extensions?", "kind": "boundary", "id": "extension-contract-q02" } ] } ] } ] }, { "id": "content-pipeline-and-deployment", "name": "Content pipeline and deployment", "description": "Tracks how editable project inputs become executable game packages.", "rationale": "An engine must be assessed through its asset and build workflows as well as its runtime features.", "layers": [ { "id": "asset-and-project-processing", "name": "Asset and project processing", "description": "Separates source assets, project metadata, imported resources and generated caches.", "findings": [ { "id": "asset-transformation-contract", "name": "Asset transformation contract", "description": "Record supported imports, dependency tracking and target-specific transformations needed to reconstruct runtime content.", "questions": [ { "text": "Which source formats and project metadata are authoritative, and which runtime resources or caches are generated from them?", "kind": "boundary", "id": "asset-transformation-contract-q01" }, { "text": "How can an agent detect failed imports, missing dependencies or stale generated resources and rebuild them?", "kind": "action", "id": "asset-transformation-contract-q02" } ] } ] }, { "id": "target-build-and-packaging", "name": "Target build and packaging", "description": "Captures the concrete prerequisites and outputs of deploying a game.", "findings": [ { "id": "deployable-build-requirements", "name": "Deployable build requirements", "description": "Record target support, required toolchains and the distinctions between editor, development and release execution.", "questions": [ { "text": "Which runtime targets can this release and configuration build for, and which SDKs, export modules or credentials are required?", "kind": "action", "id": "deployable-build-requirements-q01" }, { "text": "What runtime dependencies and behaviour differ between editor execution, development builds and release packages?", "kind": "boundary", "id": "deployable-build-requirements-q02" } ] } ] } ] }, { "id": "operational-fitness-and-permitted-change", "name": "Operational fitness and permitted change", "description": "Combines evidence of runtime suitability with maintenance and usage constraints.", "rationale": "An agent needs concrete evidence before recommending adoption, upgrade, modification or distribution.", "layers": [ { "id": "performance-and-correctness-evidence", "name": "Performance and correctness evidence", "description": "Records representative measurements and diagnostic evidence for the intended workload.", "findings": [ { "id": "verified-runtime-envelope", "name": "Verified runtime envelope", "description": "Assess frame pacing, resource use, loading and correctness under identified conditions.", "questions": [ { "text": "What frame-time percentiles, peak memory use and loading times occur for the representative workload on the intended hardware and build?", "kind": "measurement", "id": "verified-runtime-envelope-q01" }, { "text": "Which profiler captures, logs or reproductions support the assessment, including any relevant simulation or networking failures?", "kind": "provenance", "id": "verified-runtime-envelope-q02" } ] } ] }, { "id": "maintenance-migration-and-rights", "name": "Maintenance, migration and rights", "description": "Establishes the technical and contractual conditions for continued use and change.", "findings": [ { "id": "release-maintenance-and-migration", "name": "Release maintenance and migration", "description": "Record support evidence, relevant unresolved defects and the consequences of moving to another release.", "questions": [ { "text": "Which dated support notices, issue records or advisories establish this release's maintenance condition?", "kind": "provenance", "id": "release-maintenance-and-migration-q01" }, { "text": "What project, asset and plugin changes are required for an upgrade, and how can the migration be validated and reversed?", "kind": "action", "id": "release-maintenance-and-migration-q02" } ] }, { "id": "engine-use-and-distribution-rights", "name": "Engine use and distribution rights", "description": "Identify terms governing engine development use, modification and inclusion in distributed games.", "questions": [ { "text": "Which terms apply to the identified engine release, included modules and intended use, and where were those terms obtained?", "kind": "provenance", "id": "engine-use-and-distribution-rights-q01" }, { "text": "What permissions, payments, notices or source-disclosure obligations apply to the proposed modification or distribution?", "kind": "action", "id": "engine-use-and-distribution-rights-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 is recall-based; no sources were consulted.", "The kind labels overlap, and neither an integrated editor nor any particular subsystem is universally required.", "The listed standards are optional interoperability technologies, not universal game-engine requirements; performance comparisons require specified hardware, content and settings." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of game engine 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": [ "2D game engines", "3D game engines", "General-purpose game engines", "Genre-specific game engines", "Proprietary in-house game engines", "Open-source game engines" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of game engine 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": [ "Vulkan and OpenGL specifications, maintained by the Khronos Group, define graphics interfaces that engines may implement backends for.", "glTF 2.0, maintained by the Khronos Group, defines an interchange format for 3D assets that engines may import or export.", "OpenXR, maintained by the Khronos Group, defines interfaces for augmented and virtual reality platforms that engines may support." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of game engine 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": [ "Developing and running video games across supported hardware platforms.", "Prototyping interactive mechanics and environments.", "Building training applications and interactive simulations.", "Producing real-time architectural and product visualizations.", "Supporting virtual production and real-time cinematic rendering." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of game engine 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": "Frame time", "typical_range": "Target-dependent; approximately 33.3, 16.7 and 8.3 milliseconds correspond to 30, 60 and 120 frames per second.", "unit": "ms" }, { "quantity": "Runtime memory consumption", "typical_range": "No generally applicable range; depends on content, platform and enabled systems.", "unit": "MiB or GiB" }, { "quantity": "Input-to-display latency", "typical_range": "Hardware- and workload-dependent; includes delays outside the engine.", "unit": "ms" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of game engine 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": [ "CPU or GPU bottlenecks, shader compilation and asset loading can cause slow frames or visible stuttering.", "Memory leaks, excessive allocations and resource exhaustion can cause crashes or instability.", "Incorrect physics integration or collision handling can produce tunnelling, unstable motion or inconsistent gameplay.", "Platform differences and incompatible engine upgrades can break builds, assets or runtime behaviour.", "Vulnerabilities in networking, scripting, plugins or asset parsers can expose games and development environments to attacks." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of game engine 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": "Video game", "difference": "A video game supplies particular rules, content and player experiences; an engine supplies reusable systems that execute them." }, { "name": "Rendering engine", "difference": "A rendering engine generates visual output; a game engine integrates rendering or another presentation system with broader interactive runtime capabilities." }, { "name": "Physics engine", "difference": "A physics engine simulates physical behaviour and collisions; it may be one subsystem within a game engine." }, { "name": "Game editor", "difference": "An editor provides authoring tools; the engine provides runtime execution, although both may be distributed together." }, { "name": "Game development framework", "difference": "Frameworks often provide libraries with fewer integrated tools and architectural assumptions; the terminology overlaps and has no universal dividing line." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of game engine this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend game engine to include minimal game frameworks, or should inclusion require responsibility for coordinating runtime execution and world state?", "Does an existing Vercy world model already own this concept, requiring this registry entry to link to that model?", "How should shared runtimes used for games, simulation and virtual production be related to neighbouring models without duplicating the same engine?", "Which authoritative engine examples and release-specific documentation should establish the architecture categories and capability vocabulary?", "Which representative workloads and acceptance thresholds should govern suitability judgments for different game types and deployment targets?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 29 } }, "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 game engine, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a game engine, assess its suitability and operational state, and determine how it may be used, extended, upgraded or distributed.", "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: server software for MUD-like games, game engine version, proprietary engine, isometric engine, general game system, game engine recreation, tile engine, sound engine, first-person shooter engine.", "9 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 59 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 game engine, 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": [ "server software for MUD-like games", "game engine version", "proprietary engine", "isometric engine", "general game system", "game engine recreation", "tile engine", "sound engine", "first-person shooter engine" ] } ], "standing": "Described in 59 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 9 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 game engine from another, and a game engine 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 game engine, 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 game engine, 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 game engine 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 game engine, 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 game engine, 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 game engine 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 game engine 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 game engine, 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 game engine, 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 game engine 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 game engine from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a game engine, 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 game engine, 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 game engine 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 game engine 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 game engine between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a game engine, 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 game engine, 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 game engine 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 game engine, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a game engine 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 game engine, 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 game engine, 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 game engine 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 game engine 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 game engine contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a game engine, 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 game engine, 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 game engine 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 game engine and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a game engine, 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 game engine, 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 game engine 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 game engine 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 game engine, 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 game engine 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 game engine 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 game engine, 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 game engine, 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 game engine 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 game engine and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a game engine, 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 game engine, 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 game engine 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 game engine is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a game engine, 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 game engine, 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 game engine 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 } } } }