{ "model": { "rank": 5996, "code": "thing-q219320", "model_id": "vr.tr.input-output", "name": "input/output", "purpose": "Enable an AI agent to recognise what enters or leaves an activity, judge whether those inputs and outputs are usable and accounted for, and decide whether to accept, supply, transform, release or withhold them.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q219320/", "tier": 2, "score": 63, "payload": { "layer": "wikidata", "aliases": [ "standard streams", "programmed input/output", "port-mapped I/O", "asynchronous I/O", "bit banging", "memory-mapped I/O" ], "aliasCount": 6, "merged": 6, "knownIn": 63, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q219320", "url": "https://www.wikidata.org/wiki/Q219320", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:39:03Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00942922, "turns": 1, "seconds": 232.2, "error": null }, "codex": { "seconds": 182.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a07b6c-f3db-71b0-a9cb-b56174a9cf87\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: input/output\nRegistry id: vr.tr.input-output\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n" } } }, "metaModel": { "id": "THING-Q219320", "registryId": "vr.tr.input-output", "name": "input/output", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q219320/", "model": { "registry_id": "vr.tr.input-output", "name": "input/output", "purpose": "Enable an AI agent to recognise what enters or leaves an activity, judge whether those inputs and outputs are usable and accounted for, and decide whether to accept, supply, transform, release or withhold them.", "definition": "Input/output (I/O) is the transfer of material, energy, signals or data across the boundary of a process, device or system, treated as one concern because the same ports, channels and models ordinarily describe both what the unit receives and what it emits.", "scope_statement": "This draft models input/output as the boundary-relative role of something supplied to or produced by an activity, including its requirements, movement, transformation relationship and acceptance; whether the registry intends this broader activity meaning or a computing-specific meaning remains unresolved.", "in_scope": [ "The activity and boundary relative to which something is an input or output", "Required, optional, actual and missing inputs and outputs", "The form, quantity and condition needed for something to enter or leave the activity", "Supply, consumption, production, delivery and acceptance states", "Traceable relationships between inputs used and outputs produced", "Unintended outputs, rejected inputs and incomplete transfers" ], "out_of_scope": [ "The internal procedure or algorithm that performs the activity", "The full identity and lifecycle of the resource, material or information carrying the input/output role", "The design and operation of an interface, channel or transport mechanism", "The wider outcomes, benefits or impacts caused by using an output", "The complete capabilities and governance of the agents supplying or receiving items" ], "distinguishing_features": [ "An input or output must be identifiable relative to a named activity and boundary; the same item can be one activity's output and another's input.", "An input is supplied to or made available for use by the activity; an output is produced or emitted by it. Mere proximity or ownership does not establish either role.", "The input/output is what is supplied or produced; the interface or channel is how that supply or production is exposed or transferred.", "An output can be identified at the activity boundary even when its downstream outcome or benefit has not occurred.", "A constraint governs how an activity may operate; it is also an input only when the activity actually receives or reads some representation of it." ], "characteristics": [ { "name": "Role relative to activity", "kind": "relation", "unit_or_values": "Named activity and boundary, with input or output role", "why_it_matters": "Prevents direction from being assigned without a reference point or treated as an intrinsic property of an item." }, { "name": "Carrier category", "kind": "category", "unit_or_values": "Information, material, energy, mixed or unresolved", "why_it_matters": "Determines what it means to supply, consume, copy, measure or transfer the item." }, { "name": "Expectation status", "kind": "category", "unit_or_values": "Required, optional, conditional, unintended or unresolved", "why_it_matters": "Separates necessary contributions and deliverables from optional or unexpected boundary flows." }, { "name": "Input readiness", "kind": "state", "unit_or_values": "Unknown, missing, available but unchecked, acceptable, unacceptable or expired", "why_it_matters": "Supports a decision about whether the activity can start or continue." }, { "name": "Output disposition", "kind": "state", "unit_or_values": "Expected, produced, withheld, released, delivered, accepted or rejected; distinguish concurrent conditions where needed", "why_it_matters": "Prevents production from being mistaken for successful delivery or acceptance." }, { "name": "Quantity or extent", "kind": "measurement", "unit_or_values": "Carrier-appropriate units such as items, kilograms, joules, bytes or records, with measurement basis and uncertainty", "why_it_matters": "Makes shortages, partial completion and unexplained differences assessable without imposing one unit on unlike flows." }, { "name": "Timing and freshness", "kind": "measurement", "unit_or_values": "Availability and delivery timestamps, deadlines, age and validity duration with stated time basis", "why_it_matters": "An otherwise suitable input or output may be unusable when it arrives late or becomes stale." }, { "name": "Transformation trace", "kind": "relation", "unit_or_values": "Links between identified input instances or versions, activity executions and output instances or versions", "why_it_matters": "Supports explanation, reproduction and identification of outputs affected by a defective input." } ], "affordances": [ "Assign or inspect an input/output role relative to a specific activity boundary.", "Check whether required inputs are present, suitable and timely enough to permit execution.", "Request, select or substitute an input when the activity's requirements and permissions allow it.", "Trace an output to the inputs and execution that produced it.", "Validate and route an output, or withhold it when release conditions are unmet.", "Reconcile missing, partial, duplicate, rejected or unintended boundary flows and propose recovery actions." ] }, "sources": [ { "id": "wikipedia-io", "title": "Input/output", "url": "https://en.wikipedia.org/wiki/Input/output", "what_it_supports": "Computing sense of I/O, device classes, and the blocking/memory-mapped distinctions", "url_status": "live" }, { "id": "wikipedia-io-model", "title": "Input-output model", "url": "https://en.wikipedia.org/wiki/Input–output_model", "what_it_supports": "That the same name also denotes Leontief inter-industry accounts, a neighbour rather than a subtype of device I/O", "url_status": "unverified" }, { "id": "posix-2017", "title": "IEEE Std 1003.1-2017, Standard for Information Technology - Portable Operating System Interface (POSIX®) Base Specifications, Issue 7", "url": "", "what_it_supports": "Standard stream identifiers and the file-descriptor model of I/O" }, { "id": "fips-183", "title": "FIPS Publication 183: Integration Definition for Function Modeling (IDEF0)", "url": "https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub183.pdf", "what_it_supports": "Activity-model I/O as left-edge inputs and right-edge outputs, distinct from controls and mechanisms", "url_status": "live" }, { "id": "iec-61131-1", "title": "IEC 61131-1, Programmable controllers - Part 1: General information", "url": "", "what_it_supports": "Process I/O as a defined part of programmable-controller equipment" } ], "structure": { "bundles": [ { "id": "activity-boundary-and-direction", "name": "Activity boundary and direction", "description": "Establishes what receives or produces the item and where its input/output role applies.", "rationale": "Input and output are relative roles; without an explicit activity boundary, direction and responsibility are ambiguous.", "layers": [ { "id": "reference-activity", "name": "Reference activity", "description": "Identifies the activity and the level at which its boundary is being considered.", "findings": [ { "id": "role-at-a-stated-boundary", "name": "Role at a stated boundary", "description": "Record the receiving or producing activity and whether the role refers to a whole activity, a step or a particular execution.", "questions": [ { "text": "Which activity receives or produces this item, and is the reference a whole activity, a step or one execution?", "kind": "definition", "id": "role-at-a-stated-boundary-q01" }, { "text": "What makes this item an input or output at that boundary rather than an internal intermediate?", "kind": "boundary", "id": "role-at-a-stated-boundary-q02" } ] } ] }, { "id": "handoffs-and-return-paths", "name": "Handoffs and return paths", "description": "Distinguishes connected roles when an item moves between activities or returns as feedback.", "findings": [ { "id": "connected-input-output-roles", "name": "Connected input/output roles", "description": "Record the supplying and receiving sides of a handoff, including cases where an output returns as a later input.", "questions": [ { "text": "Whose output supplies this input, or whose input is this output intended to become?", "kind": "provenance", "id": "connected-input-output-roles-q01" }, { "text": "If the item returns to the same activity, what separates its output event from its later input use?", "kind": "boundary", "id": "connected-input-output-roles-q02" } ] } ] } ] }, { "id": "input-and-output-requirements", "name": "Input and output requirements", "description": "Captures the conditions that make an input usable and an output acceptable.", "rationale": "Presence alone does not establish readiness, and production alone does not establish completion.", "layers": [ { "id": "input-readiness", "name": "Input readiness", "description": "Determines which inputs are necessary and whether available candidates satisfy their intended use.", "findings": [ { "id": "required-and-usable-inputs", "name": "Required and usable inputs", "description": "Record mandatory or conditional inputs, their suitability criteria and the consequences of missing or unsuitable supply.", "questions": [ { "text": "Which inputs are required under the current conditions, and what form, quantity, quality or freshness must each have?", "kind": "definition", "id": "required-and-usable-inputs-q01" }, { "text": "What evidence shows that the available inputs satisfy those requirements?", "kind": "measurement", "id": "required-and-usable-inputs-q02" }, { "text": "If an input is missing or unsuitable, may the activity wait, proceed partially or use an approved substitute?", "kind": "action", "id": "required-and-usable-inputs-q03" } ] } ] }, { "id": "output-acceptance", "name": "Output acceptance", "description": "Defines what counts as a satisfactory output for the receiving party or next activity.", "findings": [ { "id": "deliverable-and-acceptance-conditions", "name": "Deliverable and acceptance conditions", "description": "Record expected outputs and the checks and authority needed to accept them.", "questions": [ { "text": "What must be produced, in what form and quantity, and by what deadline for the output obligation to be met?", "kind": "definition", "id": "deliverable-and-acceptance-conditions-q01" }, { "text": "Which checks establish acceptability, and who or what can accept or reject the output?", "kind": "action", "id": "deliverable-and-acceptance-conditions-q02" }, { "text": "Which expectations concern the output itself, and which concern downstream outcomes outside this model?", "kind": "boundary", "id": "deliverable-and-acceptance-conditions-q03" } ] } ] } ] }, { "id": "supply-production-and-transfer", "name": "Supply, production and transfer", "description": "Tracks what has actually become available, been used, been produced and reached its destination.", "rationale": "An agent must distinguish intended flows from observed events and avoid treating availability, use, production and receipt as equivalent.", "layers": [ { "id": "input-availability-and-use", "name": "Input availability and use", "description": "Separates offered or accessible inputs from those actually used by an execution.", "findings": [ { "id": "observed-input-use", "name": "Observed input use", "description": "Record when and how much input was available and used, including whether use consumed, changed or merely read it.", "questions": [ { "text": "What quantity or version was available when needed, and what quantity or version was actually used?", "kind": "measurement", "id": "observed-input-use-q01" }, { "text": "Did use consume, alter, copy or read the input, and what remained available afterward?", "kind": "measurement", "id": "observed-input-use-q02" } ] } ] }, { "id": "output-release-and-receipt", "name": "Output release and receipt", "description": "Separates creation of an output from permission to release it and evidence of receipt.", "findings": [ { "id": "verified-output-handoff", "name": "Verified output handoff", "description": "Record production, release and receipt evidence, including partial or repeated transfers.", "questions": [ { "text": "What evidence establishes that the output was produced, released and received, and when did each occur?", "kind": "provenance", "id": "verified-output-handoff-q01" }, { "text": "What destination and release conditions apply before the agent may transfer this output?", "kind": "action", "id": "verified-output-handoff-q02" }, { "text": "How can a partial, failed or repeated handoff be detected before deciding whether to retry?", "kind": "measurement", "id": "verified-output-handoff-q03" } ] } ] } ] }, { "id": "transformation-trace-and-reconciliation", "name": "Transformation trace and reconciliation", "description": "Connects actual inputs to actual outputs and examines gaps, defects and unintended production.", "rationale": "Input/output modelling must support explanations of what was produced from what, while exposing discrepancies that require intervention.", "layers": [ { "id": "input-output-dependencies", "name": "Input/output dependencies", "description": "Captures the evidence connecting particular inputs, executions and outputs.", "findings": [ { "id": "supported-transformation-links", "name": "Supported transformation links", "description": "Record which inputs contributed to an output and the strength and limits of the available trace.", "questions": [ { "text": "Which input instances or versions and which execution produced this output, and what records support those links?", "kind": "provenance", "id": "supported-transformation-links-q01" }, { "text": "If an input is corrected, withdrawn or found defective, which outputs require review or regeneration?", "kind": "action", "id": "supported-transformation-links-q02" } ] } ] }, { "id": "discrepancies-and-unintended-outputs", "name": "Discrepancies and unintended outputs", "description": "Accounts for missing results, excess production, rejected material and other boundary flows beyond the intended deliverable.", "findings": [ { "id": "accounted-and-unexplained-differences", "name": "Accounted and unexplained differences", "description": "Record expected versus observed flows using a valid comparison basis, without assuming that all input and output quantities must balance.", "questions": [ { "text": "Which expected outputs are missing, and which unintended, excess or rejected outputs were observed?", "kind": "measurement", "id": "accounted-and-unexplained-differences-q01" }, { "text": "What balance or correspondence, if any, should hold between these inputs and outputs, and what evidence explains deviations?", "kind": "measurement", "id": "accounted-and-unexplained-differences-q02" }, { "text": "Which discrepancies require containment, rework, disposal or escalation before the activity can be considered complete?", "kind": "action", "id": "accounted-and-unexplained-differences-q03" } ] } ] } ] }, { "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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Blocking (synchronous) versus non-blocking or asynchronous I/O", "Memory-mapped versus port-mapped hardware I/O", "Digital versus analogue process I/O on industrial controllers", "Standard character streams (stdin, stdout, stderr)", "Human-computer I/O (keyboards, displays, pointing, speech)", "Activity-boundary I/O in function modelling (IDEF0 inputs and outputs, as distinct from controls and mechanisms)", "Network and socket I/O versus local device or file I/O", "Inter-industry economic input-output flows in national accounts" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "POSIX / ISO C stdio", "value_or_pattern": "file descriptors 0 (stdin), 1 (stdout), 2 (stderr)", "note": "Canonical stream identifiers on Unix-like systems and hosted ISO C implementations" }, { "scheme": "Unix device node", "value_or_pattern": "/dev/* (e.g. /dev/stdin, /dev/tty, character and block devices)", "note": "Filesystem names for I/O devices, not a globally unique product code" } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "ISO/IEC 2382:2015 Information technology - Vocabulary (ISO/IEC) - defines input-output and related IT terms", "IEEE Std 1003.1 (POSIX) (IEEE / The Open Group) - portable file, stream and device I/O", "ISO/IEC 9899 (C language) (ISO/IEC) - stdio and hosted I/O library", "FIPS PUB 183 IDEF0 (NIST, withdrawn as a FIPS in 2008 but still the IDEF0 reference) - inputs and outputs of a function box", "IEC 61131 series, especially 61131-1 and 61131-2 (IEC) - programmable controllers and their I/O equipment", "IEC 61158 (IEC) - industrial fieldbus communications that carry process I/O", "USB specifications (USB Implementers Forum) - host-to-peripheral I/O interconnect" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "A Unix pipeline connecting one process's stdout to the next process's stdin", "A PLC scan that reads a limit-switch as a digital input and writes a 4-20 mA analogue output to a control valve", "An IDEF0 activity box with left-edge arrows (inputs transformed by the activity) and right-edge arrows (outputs produced)", "An instrumentation I/O list on a plant project, enumerating every signal from field device to controller channel", "A program reading a file or writing a printer, disk or network socket", "National-accounts input-output tables recording how one industry's outputs become another's inputs" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Data throughput", "typical_range": "kilobytes per second (serial/legacy) to tens of gigabytes per second (modern buses and NVMe)", "unit": "B/s (usually reported as MB/s or GB/s)" }, { "quantity": "I/O operations per second", "typical_range": "about 10^2 (spinning disk) to 10^6 (NVMe SSD)", "unit": "IOPS" }, { "quantity": "I/O latency", "typical_range": "microseconds (local SSD or memory-mapped register) to milliseconds (disk, many networks) to seconds (human I/O)", "unit": "s" }, { "quantity": "Analogue current-loop signal", "typical_range": "4-20 (live) with 0 or <4 often meaning fault/break", "unit": "mA" }, { "quantity": "Analogue voltage signal", "typical_range": "0-10 or 0-5, sometimes ±10", "unit": "V" }, { "quantity": "Controller I/O update / scan interval", "typical_range": "about 1-100", "unit": "ms" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Process hang or deadlock from blocking I/O that never completes", "Silent data loss when writes are not flushed before crash or close", "Buffer overrun or truncation on reads and writes of unbounded streams", "Electrical overvoltage, short or miswiring of field I/O channels", "Ground-loop noise and drift on analogue I/O", "Stuck-at faults on digital inputs (welded contact, broken wire read as the safe or the unsafe state)", "Priority inversion or thread starvation while waiting on I/O", "Modelling error: treating an IDEF0 control or mechanism as an input, so constraints or resources are drawn as consumed material" ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "French practice names it entrée/sortie (E/S); German Ein-/Ausgabe (E/A); Japanese 入出力 (nyūshutsuryoku), often still written I/O", "Computing writes input/output or I/O; economics writes input-output (hyphen) for Leontief tables - same words, different objects", "Analogue field I/O is commonly 4-20 mA in process plants and 0-10 V in many building-automation and OEM machine panels", "Remote versus local I/O is a plant-architecture distinction (I/O dropped in the field versus in the controller cabinet) that naming in office IT does not make" ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Interface (port or contract)", "difference": "An interface is the named boundary and its rules; I/O is the traffic that actually crosses it" }, { "name": "IDEF0 control", "difference": "A control constrains or governs the activity (conditions, setpoints, procedures) but is not transformed into the output; an input is" }, { "name": "IDEF0 mechanism (resource)", "difference": "A mechanism performs the activity (people, machines, software) and is not consumed as material; an input is consumed or transformed" }, { "name": "Throughput (bandwidth)", "difference": "Throughput is a performance measure of I/O, not the I/O itself" }, { "name": "Main-memory access", "difference": "Load/store to RAM is not I/O on architectures that separate the memory bus from I/O space, even though memory-mapped I/O uses load/store encodings to reach devices" }, { "name": "Input-output model (economics)", "difference": "Leontief tables record inter-industry commodity flows in accounts; they do not name device or process ports" }, { "name": "API", "difference": "An API is a software contract that may hide I/O; calling an API is not by itself an I/O operation unless it crosses a process, device or network boundary" } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of input/output this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend activity inputs and outputs generally, computing I/O specifically, or another meaning of the combined name?", "Is the primary modelled instance an individual input/output role, a handoff event or the complete input/output profile of an activity?", "Which existing world model, if any, already owns this concept and should be linked instead of creating a separate publication?", "Where should this registry draw the boundary between inputs, enabling resources and governing constraints, especially for tools, labour and standing instructions?", "Which domain-specific conventions are needed for continuous flows, copying, shared inputs and unintended outputs without assuming conservation or one-to-one transformation?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 28 } }, "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 input/output, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise what enters or leaves an activity, judge whether those inputs and outputs are usable and accounted for, and decide whether to accept, supply, transform, release or withhold them.", "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: standard streams, programmed input/output, port-mapped I/O, asynchronous I/O, bit banging, memory-mapped I/O.", "6 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 63 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 input/output, 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": [ "standard streams", "programmed input/output", "port-mapped I/O", "asynchronous I/O", "bit banging", "memory-mapped I/O" ] } ], "standing": "Described in 63 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 6 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 input/output from another, and a input/output 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 input/output, 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 input/output, 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 input/output 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 input/output, 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 input/output, 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 input/output 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 input/output 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 input/output, 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 input/output, 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 input/output 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 input/output from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a input/output, 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 input/output, 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 input/output 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 input/output 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 input/output between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a input/output, 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 input/output, 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 input/output 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 input/output, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a input/output 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 input/output, 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 input/output, 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 input/output 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 input/output 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 input/output, 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 input/output and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a input/output, 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 input/output, 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 input/output 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 input/output consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a input/output 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 input/output, 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 input/output, 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 input/output 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 input/output 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 input/output 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 input/output 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 input/output 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 input/output?", "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 input/output?", "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 input/output 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 input/output and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a input/output, 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 input/output, 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 input/output 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 input/output is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a input/output, 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 input/output, 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 input/output 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 } } } }