{ "model": { "rank": 4005, "code": "thing-q131303", "model_id": "vr.tr.hello-world", "name": "Hello world", "purpose": "Enable an agent to recognise a Hello world programming example, assess what its execution demonstrates, and identify the next useful learning or setup action.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q131303/", "tier": 2, "score": 79, "payload": { "layer": "wikidata", "aliases": [ "GNU Hello" ], "aliasCount": 1, "merged": 1, "knownIn": 79, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q131303", "url": "https://www.wikidata.org/wiki/Q131303", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T19:15:58Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 14.7, "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: 01a08798-5a1e-7101-a861-6296188c4594\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Hello world\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 54.5, "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: 01a08798-5a2b-7831-8ec1-12ef2c318b7b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Hello world\nRegistry id: vr.tr.hello-world\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\n" } } }, "metaModel": { "id": "THING-Q131303", "registryId": "vr.tr.hello-world", "name": "Hello world", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q131303/", "model": { "registry_id": "vr.tr.hello-world", "name": "Hello world", "purpose": "Enable an agent to recognise a Hello world programming example, assess what its execution demonstrates, and identify the next useful learning or setup action.", "definition": "In programming, a \"Hello, world!\" program is a minimal introductory example that outputs a short greeting, conventionally \"Hello, world!\", to demonstrate basic program execution and output.", "scope_statement": "This draft provisionally interprets Hello world as the minimal programming demonstration that produces a recognisable greeting, covering its instructional intent, implementation, execution and limited evidential value; the registry provides no definition confirming this sense.", "in_scope": [ "The greeting-producing example and its intended first-program role", "Language-specific source or other executable representation", "The minimal build and execution path required by the example", "The expected greeting and the channel through which it appears", "Execution outcomes and the limited capabilities they demonstrate" ], "out_of_scope": [ "Ordinary conversational greetings", "Creative works or products titled Hello World", "General programming-language specifications", "Complete development-environment installation and administration", "Production application architecture and comprehensive software testing" ], "distinguishing_features": [ "Its central observable result is a recognisable greeting, conventionally a variant of Hello, world!, rather than a substantive computation.", "Its stated or contextual purpose is an introductory demonstration or a minimal check of an execution path.", "The greeting is produced through program execution or rendering, rather than merely appearing in source text or documentation.", "Necessary scaffolding serves the greeting demonstration; unrelated application features are not essential to the example.", "A successful run demonstrates the exercised output path, without establishing broader application correctness or production readiness." ], "characteristics": [ { "name": "Interpretation of the registered name", "kind": "state", "unit_or_values": "programming-example sense provisional | confirmed | rejected", "why_it_matters": "The entry has no definition, so the intended sense must remain explicit." }, { "name": "Demonstration role", "kind": "category", "unit_or_values": "first-language example | environment check | framework introduction | other stated role", "why_it_matters": "The role determines what success is supposed to teach or establish." }, { "name": "Implementation language and version", "kind": "relation", "unit_or_values": "reference to the language, dialect and relevant version", "why_it_matters": "Syntax and required scaffolding depend on the implementation context." }, { "name": "Execution context", "kind": "relation", "unit_or_values": "references to the runtime, compiler, browser, framework or device used", "why_it_matters": "The same source may behave differently or fail outside its intended context." }, { "name": "Expected greeting", "kind": "category", "unit_or_values": "declared text, including punctuation, case, encoding and newline expectations", "why_it_matters": "An agent needs a concrete output expectation while distinguishing exact matching from acceptable greeting variants." }, { "name": "Output channel", "kind": "category", "unit_or_values": "standard output | browser view | application window | device display | other declared channel", "why_it_matters": "The channel determines where execution evidence must be observed." }, { "name": "Observed run state", "kind": "state", "unit_or_values": "not attempted | preparation failed | launch failed | ran without expected greeting | greeting observed", "why_it_matters": "These states support different corrective actions and prevent preparation success from being mistaken for demonstration success." }, { "name": "Greeting occurrence count", "kind": "measurement", "unit_or_values": "number of observed greeting emissions per defined run or interaction", "why_it_matters": "Missing or repeated output can reveal an incorrect launch, repeated rendering or an unintended loop." } ], "affordances": [ "Explain how the example causes the greeting to appear.", "Adapt the greeting demonstration to a specified language and execution context.", "Execute the example in an authorised environment and compare observed output with its declared expectation.", "Locate a failed demonstration within preparation, launch or greeting production.", "State exactly which execution capabilities a successful run exercised.", "Propose a small follow-up exercise that extends the demonstrated mechanism." ] }, "sources": [], "structure": { "bundles": [ { "id": "hello-world-identity", "name": "Hello world identity", "description": "Establishes the programming-example sense and the boundary around acceptable greeting demonstrations.", "rationale": "The name alone could identify a greeting, a title or a programming example, and the registry does not resolve that ambiguity.", "layers": [ { "id": "registered-sense", "name": "Registered sense", "description": "Connects the provisional interpretation to evidence about the registry entry.", "findings": [ { "id": "programming-example-interpretation", "name": "Programming-example interpretation", "description": "Record whether the entry denotes a greeting-producing programming demonstration and what supports that interpretation.", "questions": [ { "text": "Does the registry's originating record identify Hello world as a programming example?", "kind": "provenance", "id": "programming-example-interpretation-q01" }, { "text": "What evidence distinguishes this entry from an ordinary greeting or a work titled Hello World?", "kind": "boundary", "id": "programming-example-interpretation-q02" } ] } ] }, { "id": "greeting-variant-boundary", "name": "Greeting variant boundary", "description": "Determines which changes preserve the identity of the demonstration.", "findings": [ { "id": "recognisable-greeting-contract", "name": "Recognisable greeting contract", "description": "Record whether identity depends on literal text, a translated greeting or the introductory demonstration convention.", "questions": [ { "text": "Must this example emit the literal text Hello, world!, or are specified variants acceptable?", "kind": "definition", "id": "recognisable-greeting-contract-q01" }, { "text": "Would replacing the greeting with an arbitrary status message still count as Hello world in the intended context?", "kind": "boundary", "id": "recognisable-greeting-contract-q02" } ] } ] } ] }, { "id": "greeting-implementation", "name": "Greeting implementation", "description": "Captures the mechanism that produces the greeting and the scaffolding needed to invoke it.", "rationale": "An agent must distinguish the small greeting operation from language or framework machinery surrounding it.", "layers": [ { "id": "greeting-producing-mechanism", "name": "Greeting-producing mechanism", "description": "Identifies the executable or rendered operation responsible for the visible result.", "findings": [ { "id": "text-to-output-path", "name": "Text-to-output path", "description": "Record where the greeting is represented and how it reaches the declared output channel.", "questions": [ { "text": "Which expression, statement, template or component causes the greeting to appear?", "kind": "definition", "id": "text-to-output-path-q01" }, { "text": "Is the greeting emitted as process output, rendered into a view or delivered through another mechanism?", "kind": "definition", "id": "text-to-output-path-q02" } ] } ] }, { "id": "required-scaffolding", "name": "Required scaffolding", "description": "Separates required entry points and dependencies from incidental tutorial additions.", "findings": [ { "id": "minimal-valid-wrapper", "name": "Minimal valid wrapper", "description": "Record the imports, entry point, project files or framework setup required for this implementation.", "questions": [ { "text": "Which surrounding elements are required by the declared language or framework version?", "kind": "boundary", "id": "minimal-valid-wrapper-q01" }, { "text": "Which elements can an agent remove while preserving the intended greeting demonstration?", "kind": "action", "id": "minimal-valid-wrapper-q02" } ] } ] } ] }, { "id": "first-run-verification", "name": "First-run verification", "description": "Connects the example's representation to an observed greeting through a reproducible execution path.", "rationale": "A Hello world example is useful as an execution demonstration only when the expected output can be tied to the intended artifact and run.", "layers": [ { "id": "prepare-and-launch", "name": "Prepare and launch", "description": "Records the minimum steps needed to build, interpret, load or start this example.", "findings": [ { "id": "reproducible-invocation", "name": "Reproducible invocation", "description": "Record the relevant environment, invocation and artifact so an agent can reproduce the demonstration.", "questions": [ { "text": "What exact command or interaction starts this example, and from which working context?", "kind": "action", "id": "reproducible-invocation-q01" }, { "text": "How is the launched artifact tied to the current source rather than an older build or unrelated process?", "kind": "provenance", "id": "reproducible-invocation-q02" } ] } ] }, { "id": "observe-the-greeting", "name": "Observe the greeting", "description": "Assesses greeting content, destination and lifecycle against explicit expectations.", "findings": [ { "id": "greeting-success-condition", "name": "Greeting success condition", "description": "Record what appeared, where it appeared and whether the example's expected completion or continuing operation occurred.", "questions": [ { "text": "Did the expected greeting appear in the declared channel with the required text and occurrence count?", "kind": "measurement", "id": "greeting-success-condition-q01" }, { "text": "Should this example terminate after output or remain active to display or serve the greeting?", "kind": "definition", "id": "greeting-success-condition-q02" }, { "text": "If the greeting is absent, what evidence locates the failure in preparation, launch or output production?", "kind": "action", "id": "greeting-success-condition-q03" } ] } ] } ] }, { "id": "demonstration-value", "name": "Demonstration value", "description": "Captures what the example teaches or verifies and how an agent should use the result.", "rationale": "The tiny output is valuable because of the learning or setup claim it supports; that claim needs an explicit limit.", "layers": [ { "id": "capabilities-demonstrated", "name": "Capabilities demonstrated", "description": "Bounds conclusions drawn from producing the greeting.", "findings": [ { "id": "successful-run-evidence", "name": "Successful-run evidence", "description": "Record the specific parsing, compilation, execution, rendering or output mechanisms exercised by the observed run.", "questions": [ { "text": "Which capabilities were actually exercised to produce this greeting?", "kind": "measurement", "id": "successful-run-evidence-q01" }, { "text": "Which proposed conclusions, such as database connectivity or production readiness, remain unsupported by this run?", "kind": "boundary", "id": "successful-run-evidence-q02" } ] } ] }, { "id": "introductory-learning-step", "name": "Introductory learning step", "description": "Relates the example's simplicity to its intended learner and next exercise.", "findings": [ { "id": "next-small-modification", "name": "Next small modification", "description": "Record the intended lesson and a follow-up change that makes the greeting mechanism understandable.", "questions": [ { "text": "Is the intended lesson source editing, program execution, output syntax, component rendering or another stated first step?", "kind": "definition", "id": "next-small-modification-q01" }, { "text": "What small change, such as editing the greeting or inserting a variable, would let the learner test that lesson?", "kind": "action", "id": "next-small-modification-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 programming sense is inferred from the name; no recorded sense confirms it, and the supplied domain code alone does not resolve the ambiguity.", "The listed kinds are common implementation forms, not a standardized taxonomy.", "Greeting capitalization, punctuation, and exact wording vary; they do not define a strict conformance requirement." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Hello world 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": [ "Console-output example", "Graphical-interface example", "Web-page or web-service example" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Hello world 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": [ "Introducing a programming language's basic syntax and output mechanism.", "Checking that a development environment can build or execute a simple program.", "Demonstrating the smallest working application for a framework or platform.", "Providing a starting point for a programming tutorial." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Hello world 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": [ "Successful greeting output can be mistaken for evidence that a complete application or deployment is correctly configured.", "Minimal examples omit error handling, security controls, and other requirements of production software.", "Version or environment differences can prevent a copied example from running." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Hello world this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Teaching materials may translate the greeting, while many retain the conventional English wording." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Hello world 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": "Smoke test", "difference": "A smoke test checks basic system functionality; a Hello, world! program may serve that purpose but is also used purely for instruction." }, { "name": "Minimal reproducible example", "difference": "A minimal reproducible example isolates a particular problem or behavior; a Hello, world! program ordinarily demonstrates successful basic execution." }, { "name": "Boilerplate code", "difference": "Boilerplate supplies recurring application structure; a Hello, world! example demonstrates observable output and may include boilerplate." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Hello world this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the originating registry record confirm the programming-example sense, and how does that sense relate to the assigned ACT / ACT.ACT classification?", "Does an existing Vercy world model already cover this concept, requiring a link rather than a separate publication?", "Which authoritative descriptions define the boundary between Hello world, translated greeting variants and other minimal first programs?", "Should purely declarative rendered greetings count within this entry, or does the intended registry sense require a program with an explicit execution step?", "Which language and framework examples should research examine to establish representative scaffolding and success conditions without privileging one ecosystem?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 14, "questions": 23 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 Hello world, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a Hello world programming example, assess what its execution demonstrates, and identify the next useful learning or setup action.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: GNU Hello.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 79 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 Hello world, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "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": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "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": [ "GNU Hello" ] } ], "standing": "Described in 79 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 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 Hello world from another, and a Hello world 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 Hello world, 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 Hello world, 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 Hello world 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 Hello world, 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 Hello world, 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 Hello world 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 Hello world 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 Hello world, 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 Hello world, 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 Hello world 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 Hello world from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Hello world, 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 Hello world, 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 Hello world 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 Hello world 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 Hello world between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Hello world, 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 Hello world, 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 Hello world 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 Hello world, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Hello world 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 Hello world, 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 Hello world, 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 Hello world is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a Hello world proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a Hello world, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a Hello world and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a Hello world, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a Hello world, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a Hello world is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a Hello world consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a Hello world takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a Hello world, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a Hello world, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a Hello world is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What Hello world is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of Hello world are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is Hello world operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of Hello world and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of Hello world?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as Hello world?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Hello world 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 Hello world and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Hello world, 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 Hello world, 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 Hello world 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 Hello world is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Hello world, 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 Hello world, 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 Hello world 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 } } } }