{ "model": { "rank": 4809, "code": "thing-q170451", "model_id": "vr.tr.logic-gate", "name": "logic gate", "purpose": "Enable an AI agent to recognise a physical logic gate, record its logical and electrical behaviour, assess whether it can operate reliably, and judge compatible connections and uses.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q170451/", "tier": 2, "score": 72, "payload": { "layer": "wikidata", "aliases": [ "Transcriptor", "molecular logic gate", "scan cell", "XNOR gate", "XOR gate", "IMPLY gate", "Toffoli gate", "YES gate", "Fredkin gate", "coincidence circuit", "AND gate", "OR gate", "NAND gate", "NIMPLY gate", "inverter", "magnetic logic", "NOR gate", "barrel shifter" ], "aliasCount": 18, "merged": 18, "knownIn": 72, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q170451", "url": "https://www.wikidata.org/wiki/Q170451", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T21:02:17Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.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: 01a087f9-8cea-7422-8da8-2d4b06de2f64\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: logic gate\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 regi", "usd": 0, "recall": true }, "codex": { "seconds": 64.2, "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: 01a087f9-8cd8-72a0-92a2-7a84725dde33\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: logic gate\nRegistry id: vr.tr.logic-gate\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCo" } } }, "metaModel": { "id": "THING-Q170451", "registryId": "vr.tr.logic-gate", "name": "logic gate", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q170451/", "model": { "registry_id": "vr.tr.logic-gate", "name": "logic gate", "purpose": "Enable an AI agent to recognise a physical logic gate, record its logical and electrical behaviour, assess whether it can operate reliably, and judge compatible connections and uses.", "definition": "A logic gate is a physical device or circuit that implements a Boolean function by mapping one or more binary-valued input signals to an output signal under specified operating conditions.", "scope_statement": "This model covers logic gate as a kind of physical device or circuit that implements a Boolean function through physically encoded logic states, with electronic gates as the primary case; it distinguishes the gate function from its implementation, package and individual instance.", "in_scope": [ "Boolean function, input count, output behaviour and polarity", "Physical implementation and encoding of logical states", "Power, signal thresholds, output drive and connection compatibility", "Propagation delay, switching behaviour and operating conditions", "Gate-level verification, fault symptoms and handling constraints" ], "out_of_scope": [ "Boolean algebra and abstract logical operators independently of physical implementation", "Transistor physics and fabrication processes as complete subjects", "Complete processors, programmable logic devices and digital systems containing gates", "Latches, flip-flops and other circuits whose defining function requires stored state", "Product catalogues, package inventories and individual component maintenance histories" ], "distinguishing_features": [ "Has a specified Boolean mapping from input logic states to output logic states, including identity for a buffer.", "Physically realises logic states and transitions; a truth-table symbol or software expression alone is not this physical sense of logic gate.", "Its intended settled output follows current inputs rather than a stored state, distinguishing an ordinary combinational gate from a latch or flip-flop.", "Is identified at the gate-function boundary; one integrated-circuit package may contain several gates.", "Uses signals as representations of logical values, distinguishing its intended role from a switch or amplifier without a specified logic interpretation." ], "characteristics": [ { "name": "Boolean function", "kind": "category", "unit_or_values": "AND, OR, NOT, NAND, NOR, XOR, XNOR, buffer or explicitly specified function", "why_it_matters": "Determines the expected settled output for each valid input combination." }, { "name": "Input count", "kind": "measurement", "unit_or_values": "Integer count of functional inputs, with enable inputs recorded separately", "why_it_matters": "Defines the function's arity and the combinations required for verification." }, { "name": "Implementation and logic family", "kind": "category", "unit_or_values": "Physical technology and, where applicable, documented electronic logic family", "why_it_matters": "Constrains signal interpretation, power requirements and compatibility." }, { "name": "Supply operating range", "kind": "measurement", "unit_or_values": "V for electronic implementations, including rail references", "why_it_matters": "Establishes the supply conditions under which operation is specified." }, { "name": "Input logic thresholds", "kind": "measurement", "unit_or_values": "V for electronic implementations; guaranteed low and high limits with conditions", "why_it_matters": "Determines whether an incoming signal has an unambiguous logical interpretation." }, { "name": "Output configuration", "kind": "category", "unit_or_values": "Push-pull, open-drain, open-collector, three-state or implementation-specific configuration", "why_it_matters": "Determines required external components and whether outputs may share a connection." }, { "name": "Guaranteed output drive", "kind": "measurement", "unit_or_values": "Output voltage in V at specified source or sink current in mA", "why_it_matters": "Supports compatibility checks under actual loading." }, { "name": "Propagation delay", "kind": "measurement", "unit_or_values": "s, commonly ns or ps; transition direction, load and operating conditions attached", "why_it_matters": "Determines when downstream circuitry can rely on the new output." }, { "name": "Input hysteresis", "kind": "measurement", "unit_or_values": "Separate rising and falling thresholds in V where specified; otherwise unspecified or not applicable", "why_it_matters": "Affects behaviour with slow or noisy input transitions." }, { "name": "Gate-to-package mapping", "kind": "relation", "unit_or_values": "Gate channel linked to package terminals, shared supply rails and shared controls", "why_it_matters": "Prevents confusing a logical gate with the component that houses it." }, { "name": "Observed functional condition", "kind": "state", "unit_or_values": "Untested, conforms under stated test conditions, intermittent, failed or indeterminate", "why_it_matters": "Separates verified operation from assumed or incomplete evidence." } ], "affordances": [ "Derive expected settled outputs from the specified function and input polarity.", "Check supply, input threshold and output loading compatibility before connecting gates.", "Estimate a gate's contribution to a signal path delay under specified conditions.", "Identify required pull resistors, enable states and treatment of unused inputs.", "Construct a truth-table and transition test appropriate to the implementation.", "Assess a proposed replacement against function, pin mapping, electrical limits and timing." ] }, "sources": [], "structure": { "bundles": [ { "id": "logical-function", "name": "Logical function", "description": "The Boolean behaviour that identifies the gate independently of its physical construction.", "rationale": "An agent must know which logical transformation the gate promises before evaluating an implementation.", "layers": [ { "id": "function-and-polarity", "name": "Function and polarity", "description": "Functional inputs, output expressions and signal conventions.", "findings": [ { "id": "boolean-contract", "name": "Boolean contract", "description": "Record the intended truth table or Boolean expression, input count and interpretation of inverted or active-low signals.", "questions": [ { "text": "Which truth table defines the gate, and how many functional inputs does it have?", "kind": "definition", "id": "boolean-contract-q01" }, { "text": "Which input or output labels denote inversion or active-low meaning, and how do they map to physical signal levels?", "kind": "definition", "id": "boolean-contract-q02" } ] } ] }, { "id": "controls-and-boundaries", "name": "Controls and boundaries", "description": "Auxiliary controls and the boundary between combinational function and stored state.", "findings": [ { "id": "enabled-and-settled-behaviour", "name": "Enabled and settled behaviour", "description": "Separate the Boolean output from disabled, high-impedance and invalid-input behaviour, and identify any history dependence.", "questions": [ { "text": "Does an enable input place the output in high impedance or another specified condition?", "kind": "definition", "id": "enabled-and-settled-behaviour-q01" }, { "text": "Does the proposed boundary contain feedback or retained state that belongs to a latch or sequential-circuit model?", "kind": "boundary", "id": "enabled-and-settled-behaviour-q02" } ] } ] } ] }, { "id": "physical-realisation", "name": "Physical realisation", "description": "How the logical function is embodied and how its terminals are identified.", "rationale": "Identical truth tables can have materially different power, wiring and signal requirements.", "layers": [ { "id": "technology-and-encoding", "name": "Technology and encoding", "description": "Implementation technology and the physical quantities used to represent logic.", "findings": [ { "id": "physical-logic-encoding", "name": "Physical logic encoding", "description": "Identify the implementation and record how physical signal ranges correspond to logical values.", "questions": [ { "text": "What technology or documented logic family implements the gate?", "kind": "provenance", "id": "physical-logic-encoding-q01" }, { "text": "What physical quantity represents each logic value, and what reference or polarity convention is required?", "kind": "definition", "id": "physical-logic-encoding-q02" } ] } ] }, { "id": "terminals-and-containment", "name": "Terminals and containment", "description": "The gate's connection points and relationship to a containing component.", "findings": [ { "id": "gate-channel-mapping", "name": "Gate channel mapping", "description": "Record which terminals belong to the gate and which supplies or controls it shares with other channels.", "questions": [ { "text": "Which terminals are functional inputs, outputs, enables and supply connections for this gate channel?", "kind": "definition", "id": "gate-channel-mapping-q01" }, { "text": "Does the identified component contain one gate, several independent gates or a larger circuit requiring a different boundary?", "kind": "boundary", "id": "gate-channel-mapping-q02" } ] } ] } ] }, { "id": "electrical-compatibility", "name": "Electrical compatibility", "description": "The conditions needed for powered operation and reliable exchange of logic signals.", "rationale": "A logical match alone cannot establish whether two physical gates can be connected successfully.", "layers": [ { "id": "supply-and-input-acceptance", "name": "Supply and input acceptance", "description": "Operating rails, input thresholds and permitted input conditions.", "findings": [ { "id": "valid-input-envelope", "name": "Valid input envelope", "description": "Record guaranteed operating supply and input limits separately from damage limits.", "questions": [ { "text": "What supply range and input low/high thresholds are guaranteed over the intended operating conditions?", "kind": "measurement", "id": "valid-input-envelope-q01" }, { "text": "What restrictions apply to slow, floating, over-rail or powered inputs when the gate supply is absent?", "kind": "action", "id": "valid-input-envelope-q02" } ] } ] }, { "id": "output-drive-and-loading", "name": "Output drive and loading", "description": "Output topology, guaranteed signal levels and attached loads.", "findings": [ { "id": "compatible-output-connection", "name": "Compatible output connection", "description": "Relate the output configuration and drive guarantees to receiver requirements, pull resistors and shared connections.", "questions": [ { "text": "What output voltages are guaranteed at the required source and sink currents, and do they satisfy the receiving inputs?", "kind": "measurement", "id": "compatible-output-connection-q01" }, { "text": "Does this output require a pull resistor, and under what documented conditions may it share a line with other outputs?", "kind": "action", "id": "compatible-output-connection-q02" }, { "text": "What receiver count and total capacitive load remain compatible with both electrical and timing requirements?", "kind": "measurement", "id": "compatible-output-connection-q03" } ] } ] } ] }, { "id": "switching-and-timing", "name": "Switching and timing", "description": "How the physical output changes between settled logic states.", "rationale": "Truth tables omit delays and transient behaviour that can make an otherwise correct gate unsuitable in a circuit.", "layers": [ { "id": "delay-and-edge-quality", "name": "Delay and edge quality", "description": "Propagation delays, output transition times and their measurement conditions.", "findings": [ { "id": "transition-timing-envelope", "name": "Transition timing envelope", "description": "Record timing by input-to-output path and transition direction with supply, temperature and loading conditions.", "questions": [ { "text": "What propagation-delay limits apply to each relevant input-to-output path and output transition direction?", "kind": "measurement", "id": "transition-timing-envelope-q01" }, { "text": "Under what load, input edge rate, supply and temperature were the timing values specified or measured?", "kind": "provenance", "id": "transition-timing-envelope-q02" } ] } ] }, { "id": "transients-and-noise", "name": "Transients and noise", "description": "Behaviour during ambiguous inputs, noise and overlapping transitions.", "findings": [ { "id": "nonideal-transition-behaviour", "name": "Nonideal transition behaviour", "description": "Record hysteresis and transition restrictions, and assess whether input timing can produce consequential output pulses.", "questions": [ { "text": "Are hysteresis, input transition-rate limits or minimum pulse-width requirements specified for this implementation?", "kind": "measurement", "id": "nonideal-transition-behaviour-q01" }, { "text": "Could relative timing of changing inputs produce an output glitch that downstream circuitry would interpret as an event?", "kind": "boundary", "id": "nonideal-transition-behaviour-q02" } ] } ] } ] }, { "id": "verification-and-use", "name": "Verification and use", "description": "Evidence of correct operation and constraints on testing, handling and substitution.", "rationale": "An agent needs a basis for distinguishing a suitable functioning gate from an incorrectly connected, damaged or inadequately tested one.", "layers": [ { "id": "functional-and-electrical-tests", "name": "Functional and electrical tests", "description": "Checks that distinguish logical correctness from electrical and timing adequacy.", "findings": [ { "id": "conformance-evidence", "name": "Conformance evidence", "description": "Record test conditions and results for input combinations, control states, output levels and relevant transitions.", "questions": [ { "text": "Which truth-table combinations and enable states were exercised, and what output levels were observed?", "kind": "measurement", "id": "conformance-evidence-q01" }, { "text": "What evidence distinguishes a stuck output, weak drive or excessive delay from a wiring, supply or loading problem?", "kind": "action", "id": "conformance-evidence-q02" } ] } ] }, { "id": "operating-and-replacement-constraints", "name": "Operating and replacement constraints", "description": "Implementation-specific limits that constrain handling and continued use.", "findings": [ { "id": "safe-use-and-substitution", "name": "Safe use and substitution", "description": "Record documented environmental, power and handling limits and the conditions a replacement must satisfy.", "questions": [ { "text": "What temperature, power-dissipation and electrostatic-handling limits apply, and which document establishes them?", "kind": "provenance", "id": "safe-use-and-substitution-q01" }, { "text": "Does a proposed replacement satisfy function, pin mapping, thresholds, output topology, drive and timing requirements?", "kind": "action", "id": "safe-use-and-substitution-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 PHY.OBJ sense is interpreted as a physical implementation, primarily electronic; the term also denotes an abstract logic element.", "Voltage and timing ranges are illustrative of a common CMOS family, not universal limits; exact ratings require the specific manufacturer's datasheet.", "Standard names are recalled without source consultation; applicable editions and status need verification." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of logic gate 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": [ "AND gates", "OR gates", "NOT gates (inverters)", "NAND gates", "NOR gates", "Exclusive-OR and exclusive-NOR gates" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of logic gate this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "74-series integrated-circuit part numbering", "value_or_pattern": "74HC00", "note": "An example identifying a quad two-input NAND integrated circuit in the HC CMOS family; the identifier describes a packaged circuit type, not an individual gate." }, { "scheme": "4000-series CMOS integrated-circuit part numbering", "value_or_pattern": "CD4011B", "note": "A quad two-input NAND integrated-circuit designation; manufacturer prefixes and package suffixes vary." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of logic gate 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": [ "IEC 60617, issued by the International Electrotechnical Commission, provides graphical symbols for diagrams, including binary logic elements.", "IEEE Std 91, issued by IEEE, specifies graphic symbols for logic functions." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of logic gate 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": [ "Implementing arithmetic circuits such as adders and comparators.", "Decoding addresses and selecting data paths in digital systems.", "Combining sensor or control signals into enable and inhibit conditions.", "Building latches and other storage circuits through feedback connections.", "Implementing digital functions within processors, programmable logic and application-specific integrated circuits." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of logic gate 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": "Supply voltage", "typical_range": "2-6 for many 74HC-family devices; other families differ", "unit": "V" }, { "quantity": "Propagation delay", "typical_range": "Approximately 5-30 for many packaged 74HC-family gates, depending on supply voltage, load and temperature", "unit": "ns" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of logic gate 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": [ "Electrostatic discharge can damage semiconductor inputs and cause immediate or latent failure.", "Excessive supply voltage, input voltage or output current can damage a device.", "Floating inputs, noise or incompatible logic levels can produce unintended switching; floating CMOS inputs can also increase power consumption.", "Unequal signal propagation delays can produce transient output glitches.", "CMOS latch-up can create excessive current and damage susceptible devices." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of logic gate 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": "Boolean function", "difference": "A Boolean function is an abstract mapping; a logic gate physically implements such a mapping with electrical or other physical constraints." }, { "name": "Transistor", "difference": "A transistor is a switching or amplifying component; a logic gate usually combines transistors to implement a specified Boolean function." }, { "name": "Logic integrated circuit", "difference": "An integrated circuit is a fabricated chip that may contain several gates or a much more complex logic system." }, { "name": "Flip-flop", "difference": "A flip-flop stores state, whereas an ordinary combinational gate's settled output depends on its current inputs." }, { "name": "Logic buffer", "difference": "A logic buffer preserves the input's Boolean value while providing drive or isolation; broad classifications include it as an identity-function gate." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of logic gate this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend this physical entry to cover optical, mechanical and fluidic gates as well as electronic gates, and which characteristics need modality-specific extensions?", "Should controlled buffers and three-state drivers sit within this entry or be linked neighbouring kinds?", "Which representative manufacturer documents should establish researched examples without treating family-specific limits as universal gate properties?", "Which standards and issuing bodies apply to the selected implementations, and which concern only their containing components or end-use systems?", "How should Schmitt-trigger input behaviour be represented so that threshold hysteresis remains distinct from intentional sequential storage?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 29 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "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 logic gate, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a physical logic gate, record its logical and electrical behaviour, assess whether it can operate reliably, and judge compatible connections and uses.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Transcriptor, molecular logic gate, scan cell, XNOR gate, XOR gate, IMPLY gate, Toffoli gate, YES gate, Fredkin gate, coincidence circuit, AND gate, OR gate.", "18 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 72 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 logic gate, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "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": [ "Transcriptor", "molecular logic gate", "scan cell", "XNOR gate", "XOR gate", "IMPLY gate", "Toffoli gate", "YES gate", "Fredkin gate", "coincidence circuit", "AND gate", "OR gate" ] } ], "standing": "Described in 72 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 18 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 logic gate from another, and a logic gate 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 logic gate, 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 logic gate, 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 logic gate 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 logic gate, 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 logic gate, 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 logic gate 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 logic gate 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 logic gate, 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 logic gate, 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 logic gate 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 logic gate from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a logic gate, 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 logic gate, 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 logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a logic gate is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a logic gate, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a logic gate, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a logic gate is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a logic gate, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a logic gate, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a logic gate is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a logic gate, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a logic gate, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a logic gate is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a logic gate is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a logic gate, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a logic gate, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a logic gate is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a logic gate, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a logic gate, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a logic gate 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 logic gate 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 logic gate between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a logic gate, 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 logic gate, 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 logic gate 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 logic gate, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a logic gate 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 logic gate, 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 logic gate, 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 logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What logic gate is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does logic gate perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise logic gate, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How logic gate is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does logic gate have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does logic gate need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about logic gate is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about logic gate hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern logic gate, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a logic gate 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 logic gate and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a logic gate, 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 logic gate, 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 logic gate 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 logic gate is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a logic gate, 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 logic gate, 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 logic gate is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }