{ "model": { "rank": 5022, "code": "thing-q178048", "model_id": "vr.tr.bus-q178048", "name": "bus", "purpose": "Let an agent reason about a bus as a shared medium with arbitration, bandwidth and trust properties, rather than as a cable.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.KNW", "industry": "", "version": "", "url": "/models/thing/q178048/", "tier": 2, "score": 70, "payload": { "layer": "wikidata", "aliases": [ "V-Link", "VMEbus", "drive interface", "U.2", "fieldbus", "KBus", "Aries interconnect", "Low Pin Count", "Flexible Display Interface", "Q-Bus", "serial bus", "parallel bus", "control bus", "system bus", "Hypercube", "Avalon bus", "data bus", "Fireplane", "expansion bus", "GSC bus", "multi-lane serial bus", "local bus", "I²S", "interconnect", "Cray Gemini interconnect", "XT3 Internal Interconnect", "Bull BXI", "Quadrics", "XT4 Internal Interconnect", "HyperPlex", "SP Switch", "peripheral bus", "quantum bus", "From", "Audio/modem riser", "three-state bus", "torus interconnect", "vehicle bus", "address bus", "Wire Train Bus" ], "aliasCount": 40, "merged": 40, "knownIn": 70, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.bus", "source": { "dataset": "wikidata", "item": "Q178048", "url": "https://www.wikidata.org/wiki/Q178048", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T04:06:21Z", "providers": [ "Claude" ], "breadth": "written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify", "pass": 2, "wave": 1, "engine": "claude" }, "metaModel": { "id": "THING-Q178048", "registryId": "vr.tr.bus-q178048", "name": "bus", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.KNW" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q178048/", "model": { "registry_id": "vr.tr.bus-q178048", "name": "bus", "purpose": "Let an agent reason about a bus as a shared medium with arbitration, bandwidth and trust properties, rather than as a cable.", "definition": "A shared communication pathway inside or between computers that carries data, addresses and control signals among several attached components under a common protocol.", "what_it_is_for": "Connecting several components through one pathway so that they can exchange data without a dedicated link between every pair.", "affordances": [ "attach and detach components, within the rules of the bus", "measure its bandwidth and latency, which are shared by everything on it", "monitor traffic on it, which any attached component may be able to do", "saturate it, which degrades every component at once" ], "distinguishing_features": [ "Shared among several components, which separates it from a dedicated point-to-point link", "Requires arbitration, because only one sender can use the shared medium at a time", "Defined by its protocol, not its wires: the same connector can carry different buses", "Trust boundary: a component on the bus can often see or reach what other components exchange" ], "appearance": "Parallel traces on a circuit board, a connector with many pins, or a cable; the visible part says little, since the protocol defines the bus.", "visual_identification": [ "Connector shape identifies the physical standard but not the protocol version negotiated over it", "Parallel traces between chips on a board are often a bus, but can be point-to-point links", "Many modern \"buses\" are serial point-to-point links with switches, and look nothing like the shared lines the word implies" ], "physical_properties": [ { "quantity": "bandwidth", "typical_range": "0.001-128", "unit": "GB/s", "note": "from field buses to current PCI Express generations" }, { "quantity": "width", "typical_range": "1-512", "unit": "bits", "note": "serial buses are one lane per direction, parallel ones are wide" }, { "quantity": "clock frequency", "typical_range": "0.1-32000", "unit": "MHz", "note": "" } ], "families_and_kinds": [ "by scope: on-chip, system, peripheral, field", "by signalling: parallel, serial", "by topology: shared line, daisy chain, switched fabric", "by standard: PCI Express, USB, I2C, CAN, SPI, and many others" ], "related_models": [ { "relation": "is a kind of", "target": "communication channel", "why": "inherits bandwidth, latency and error handling" }, { "relation": "is confused with", "target": "bus the vehicle", "why": "a homonym; this entry is the computer bus and carries none of the transport questions" }, { "relation": "is confused with", "target": "network", "why": "the line has blurred as buses became switched serial links" }, { "relation": "connects", "target": "device", "why": "each attached component is a separate model with its own identity on the bus" } ], "identifiers": [ { "scheme": "bus address", "value_or_pattern": "standard-specific", "note": "identifies a component on the bus, not the component itself" }, { "scheme": "vendor and device ID", "value_or_pattern": "for example PCI vendor:device", "note": "self-reported by the device and therefore spoofable" } ], "standards_and_regulation": [ "PCI-SIG specifications for PCI Express", "USB-IF specifications for USB", "ISO 11898 for CAN", "Vendor specifications for I2C and SPI, which are de facto rather than formal standards" ], "failure_modes_and_hazards": [ "Contention and saturation, which slow every attached component", "A faulty component holding the bus, which stops all traffic on it", "Direct memory access from a hostile device over an exposed bus", "Signal integrity loss at length or speed, producing intermittent errors that are hard to attribute" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "topology-and-protocol", "name": "Topology and protocol", "description": "How it is wired and what rules govern it.", "rationale": "The protocol defines the bus, and the topology decides how failures and contention propagate.", "layers": [ { "id": "protocol", "name": "Protocol and version", "description": "The standard and the version actually negotiated.", "findings": [ { "id": "protocol-finding", "name": "Protocol in use", "description": "The standard, its version and the negotiated mode.", "questions": [ { "text": "Which bus protocol and version is in use, and what was negotiated?", "kind": "definition" }, { "text": "What happens when an attached component supports an older version?", "kind": "boundary" } ] } ] }, { "id": "topology", "name": "Topology", "description": "Shared, chained or switched.", "findings": [ { "id": "topology-finding", "name": "Topology and its consequences", "description": "How components are connected and what that implies.", "questions": [ { "text": "What is the topology of this bus, and where are its single points of failure?", "kind": "definition" }, { "text": "How does a failure of one component affect the others?", "kind": "boundary" } ] } ] } ] }, { "id": "capacity-and-performance", "name": "Capacity and performance", "description": "How much it carries and how fast.", "rationale": "Bandwidth on a bus is shared, so the question is never how fast one component is but what everything together needs.", "layers": [ { "id": "bandwidth", "name": "Bandwidth and latency", "description": "Rated and achieved throughput.", "findings": [ { "id": "bandwidth-finding", "name": "Throughput figures", "description": "The rated figure and what is actually achieved under load.", "questions": [ { "text": "What bandwidth and latency does this bus provide, rated and measured?", "kind": "measurement" }, { "text": "What load from all attached components does it have to carry?", "kind": "measurement" } ] } ] }, { "id": "arbitration", "name": "Arbitration", "description": "How access to the medium is shared.", "findings": [ { "id": "arbitration-finding", "name": "Arbitration scheme", "description": "How senders take turns and who gets priority.", "questions": [ { "text": "How is access arbitrated, and which component has priority?", "kind": "definition" }, { "text": "What happens to a low-priority component under sustained load?", "kind": "boundary" } ] } ] } ] }, { "id": "attached-components", "name": "Attached components", "description": "What is on the bus and how it is identified.", "rationale": "Each component is identified by what it reports about itself, which is convenient and untrustworthy at once.", "layers": [ { "id": "enumeration", "name": "Enumeration", "description": "Discovering what is attached.", "findings": [ { "id": "enumeration-finding", "name": "Discovered components", "description": "The components found and how they were identified.", "questions": [ { "text": "What components are attached, and how were they discovered?", "kind": "provenance" }, { "text": "What does a component self-reported identity actually establish?", "kind": "boundary" } ] } ] }, { "id": "compatibility", "name": "Compatibility", "description": "Whether a component can work on this bus.", "findings": [ { "id": "compatibility-finding", "name": "Compatibility check", "description": "Electrical, protocol and driver compatibility.", "questions": [ { "text": "Is this component compatible electrically, by protocol and by driver?", "kind": "definition" }, { "text": "What should happen when an incompatible component is attached?", "kind": "action" } ] } ] } ] }, { "id": "integrity-and-security", "name": "Integrity and security", "description": "Errors, isolation and hostile components.", "rationale": "A bus is a trust boundary that is usually treated as if it were not one.", "layers": [ { "id": "errors", "name": "Error handling", "description": "Detection and recovery of transmission errors.", "findings": [ { "id": "errors-finding", "name": "Error behaviour", "description": "How errors are detected, counted and recovered.", "questions": [ { "text": "How are transmission errors detected and recovered on this bus?", "kind": "definition" }, { "text": "What error rate should prompt investigation, and of what?", "kind": "measurement" } ] } ] }, { "id": "isolation", "name": "Isolation", "description": "What an attached component may reach.", "findings": [ { "id": "isolation-finding", "name": "Isolation controls", "description": "The controls that limit what a component can see or write.", "questions": [ { "text": "What memory or traffic can an attached component reach, and what limits it?", "kind": "boundary" }, { "text": "What should an agent do with a component it cannot identify?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should shared buses and switched serial interconnects be separate models, given that their failure and trust properties differ?", "How should a model record the negotiated version as distinct from the physical connector?", "What trust assumptions should an agent make about devices it discovers on a bus?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "discipline or field of knowledge", "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 bus, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent reason about a bus as a shared medium with arbitration, bandwidth and trust properties, rather than as a cable.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: V-Link, VMEbus, drive interface, U.2, fieldbus, KBus, Aries interconnect, Low Pin Count, Flexible Display Interface, Q-Bus, serial bus, parallel bus.", "40 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 70 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 bus, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "read it and act on what it says" ], "howItIsRecognised": [], "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": [ "V-Link", "VMEbus", "drive interface", "U.2", "fieldbus", "KBus", "Aries interconnect", "Low Pin Count", "Flexible Display Interface", "Q-Bus", "serial bus", "parallel bus" ] } ], "standing": "Described in 70 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 40 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 bus from another, and a bus 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 bus, 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 bus, 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 bus 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 bus, 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 bus, 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 bus 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 bus 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 bus, 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 bus, 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 bus 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 bus from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a bus, 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 bus, 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 bus 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 bus 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 bus between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a bus, 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 bus, 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 bus 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 bus, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a bus 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 bus, 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 bus, 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 bus is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a bus says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a bus contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a bus, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a bus, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a bus is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a bus and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a bus, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a bus, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a bus is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "subject-and-method", "name": "Subject matter and method", "description": "What bus studies and how it establishes anything.", "rationale": "A field is identified by its questions and its methods, and those are what distinguish it from the fields next to it.", "layers": [ { "id": "subject", "name": "Subject matter", "description": "The questions it takes as its own.", "findings": [ { "id": "subject-record", "name": "Questions and objects of study", "description": "What it is about, stated so a neighbouring field can be told apart.", "questions": [ { "id": "subject-record-q01", "text": "What questions and objects does bus take as its own?", "kind": "definition" }, { "id": "subject-record-q02", "text": "Which questions does it share with a neighbouring field, and who claims them?", "kind": "boundary" } ] } ] }, { "id": "method", "name": "Method and evidence", "description": "How claims are established and what counts as evidence.", "findings": [ { "id": "method-record", "name": "Methods and standards of evidence", "description": "The methods used and what they are taken to establish.", "questions": [ { "id": "method-record-q01", "text": "By what methods does bus establish claims, and what counts as sufficient evidence?", "kind": "provenance" }, { "id": "method-record-q02", "text": "What kind of claim can this field not settle, and where should an agent look instead?", "kind": "action" } ] } ] } ] }, { "id": "institutions-and-classification", "name": "Institutions and classification", "description": "Where bus is practised and how catalogues place it.", "rationale": "The institutional footprint is the evidence that a field exists as a field rather than as a topic.", "layers": [ { "id": "institutions", "name": "Institutional markers", "description": "Societies, journals, degrees and departments.", "findings": [ { "id": "institution-record", "name": "Bodies and venues", "description": "Where the field organises itself.", "questions": [ { "id": "institution-record-q01", "text": "Which societies, journals or degrees mark bus as an established field?", "kind": "provenance" }, { "id": "institution-record-q02", "text": "What would show that it is emerging or dissolving rather than established?", "kind": "boundary" } ] } ] }, { "id": "classification", "name": "Classification schemes", "description": "Where library and research classifications put it.", "findings": [ { "id": "classification-record", "name": "Codes and their disagreements", "description": "The classification codes that place it, and where they differ.", "questions": [ { "id": "classification-record-q01", "text": "Which classification schemes place bus, under what codes?", "kind": "definition" }, { "id": "classification-record-q02", "text": "Where do those schemes disagree about its scope?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a bus 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 bus and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a bus, 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 bus, 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 bus 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 bus is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a bus, 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 bus, 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 bus 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 } } } }