{ "model": { "rank": 15882, "code": "thing-q1771903", "model_id": "vr.tr.latency", "name": "latency", "purpose": "Let an agent explain latency as a concept across fields, relay its components and measurement from engineering references, describe how it is reduced, and distinguish latency from throughput, bandwidth, jitter and the medical and psychological senses of latency.", "family": "Thing Registry", "category": "Cross-cutting context", "status": "research-draft", "kind": "thing", "plane": "XCT", "domain": "XCT.TME", "industry": "", "version": "", "url": "/models/thing/q1771903/", "tier": 2, "score": 33, "payload": { "layer": "wikidata", "aliases": [ "signal propagation delay", "lag", "Skew", "shutter lag", "turbo lag", "network delay", "queuing delay", "nuclear latency", "display lag" ], "aliasCount": 9, "merged": 9, "knownIn": 33, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.latency-time", "source": { "dataset": "wikidata", "item": "Q1771903", "url": "https://www.wikidata.org/wiki/Q1771903", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T04:55:41Z", "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": 3, "engine": "claude" }, "metaModel": { "id": "THING-Q1771903", "registryId": "vr.tr.latency", "name": "latency", "version": "0.2.0-wave.3", "entryKind": "thing", "family": "Thing Registry", "domain": [ "XCT.TME" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q1771903/", "model": { "registry_id": "vr.tr.latency", "name": "latency", "purpose": "Let an agent explain latency as a concept across fields, relay its components and measurement from engineering references, describe how it is reduced, and distinguish latency from throughput, bandwidth, jitter and the medical and psychological senses of latency.", "definition": "The time delay between a cause and its observable effect in a system, measured as a duration, including signal propagation delay in circuits and networks, network delay and lag in online systems, timing skew between signals that should arrive together, shutter lag in cameras between pressing the button and capturing the image, and turbo lag in engines between throttle input and boost; latency is distinguished from throughput and bandwidth and is critical in real-time and interactive systems.", "what_it_is_for": "Not applicable; a performance quantity.", "affordances": [ "explain the concept", "relay components and measurement", "describe reduction techniques", "distinguish related terms" ], "distinguishing_features": [ "Time delay", "Cause to effect", "Composed of stages", "Field-specific forms" ], "appearance": "Not a visible object; a delay.", "visual_identification": [ "Delay between cause and effect", "Network delay, propagation delay, lag, skew, shutter lag, turbo lag", "Throughput is amount per time; bandwidth is capacity; jitter is variation in latency" ], "physical_properties": [ { "quantity": "light propagation in fibre", "typical_range": "about 5", "unit": "microseconds per km", "note": "" }, { "quantity": "typical broadband round trip", "typical_range": "about 10-50", "unit": "ms", "note": "" }, { "quantity": "human perceptible audio delay", "typical_range": "about 10-20", "unit": "ms", "note": "" } ], "families_and_kinds": [ "network latency and round-trip time", "signal propagation delay in circuits", "clock and signal skew", "input and display lag in computing and gaming", "shutter lag in cameras", "turbo lag in engines", "audio latency" ], "related_models": [ { "relation": "is a kind of", "target": "duration", "why": "in registry terms" }, { "relation": "is a kind of", "target": "quality", "why": "in registry terms, as a performance attribute" }, { "relation": "is contrasted with", "target": "throughput", "why": "amount per time" }, { "relation": "is bounded by", "target": "speed of light", "why": "in propagation" } ], "identifiers": [], "standards_and_regulation": [ "ITU-T recommendations on network delay", "Broadcast and telecom quality of service standards", "No general regulation" ], "failure_modes_and_hazards": [ "Confusing latency with bandwidth", "Ignoring jitter", "Mixing medical and engineering senses" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What latency is.", "rationale": "Science.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is latency, and how does it differ from throughput, bandwidth and jitter?", "kind": "definition" }, { "text": "Is the question about engineering latency, a specific form or a medical or psychological sense?", "kind": "boundary" } ] } ] }, { "id": "forms", "name": "Forms", "description": "Forms.", "findings": [ { "id": "forms-finding", "name": "Forms", "description": "Forms.", "questions": [ { "text": "What are propagation delay, network delay, skew, shutter lag and turbo lag?", "kind": "definition" }, { "text": "Which entry fits the specific form?", "kind": "action" } ] } ] } ] }, { "id": "measure", "name": "Measure", "description": "Measurement.", "rationale": "Practice.", "layers": [ { "id": "components", "name": "Components", "description": "Components.", "findings": [ { "id": "components-finding", "name": "Components", "description": "Components.", "questions": [ { "text": "What components make up end-to-end latency, from propagation and transmission to queuing and processing?", "kind": "measurement" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "tools", "name": "Tools", "description": "Tools.", "findings": [ { "id": "tools-finding", "name": "Tools", "description": "Tools.", "questions": [ { "text": "How is latency measured with ping, traceroute, oscilloscopes and profiling tools?", "kind": "action" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] } ] }, { "id": "reduce", "name": "Reduce", "description": "Reducing latency.", "rationale": "Practice.", "layers": [ { "id": "networks", "name": "Networks", "description": "Networks and computing.", "findings": [ { "id": "networks-finding", "name": "Networks", "description": "Networks.", "questions": [ { "text": "How do edge computing, caching, protocol design and hardware reduce latency?", "kind": "provenance" }, { "text": "Which entry fits edge computing?", "kind": "action" } ] } ] }, { "id": "devices", "name": "Devices", "description": "Devices and engines.", "findings": [ { "id": "devices-finding", "name": "Devices", "description": "Devices.", "questions": [ { "text": "How are shutter lag and turbo lag reduced in cameras and engines?", "kind": "provenance" }, { "text": "Which entry fits the specific device?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "Impact and other senses.", "rationale": "Context.", "layers": [ { "id": "impact", "name": "Impact", "description": "Impact.", "findings": [ { "id": "impact-finding", "name": "Impact", "description": "Impact.", "questions": [ { "text": "Why does latency matter in gaming, trading, telemedicine and real-time control?", "kind": "provenance" }, { "text": "Which entry fits real-time computing?", "kind": "action" } ] } ] }, { "id": "senses", "name": "Senses", "description": "Other senses.", "findings": [ { "id": "senses-finding", "name": "Senses", "description": "Senses.", "questions": [ { "text": "What are latency in medicine, virology and psychology?", "kind": "provenance" }, { "text": "Which entry fits latent period?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should network latency and shutter lag be separate entries?", "How should engineering references be linked?", "The registry entry has merged aliases from unrelated fields; should they be split off?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "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 latency, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain latency as a concept across fields, relay its components and measurement from engineering references, describe how it is reduced, and distinguish latency from throughput, bandwidth, jitter and the medical and psychological senses of latency.", "characteristics": { "substance": "abstract", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: signal propagation delay, lag, Skew, shutter lag, turbo lag, network delay, queuing delay, nuclear latency, display lag.", "9 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 33 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 latency, and on what evidence are they told apart?" ], "whatItIsMadeOf": "an abstraction with no physical instance", "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": [ "signal propagation delay", "lag", "Skew", "shutter lag", "turbo lag", "network delay", "queuing delay", "nuclear latency", "display lag" ] } ], "standing": "Described in 33 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 9 finer distinctions are held inside this entry as names rather than as separate models.", "structure": { "bundles": [ { "id": "identity-and-classification", "name": "Identity, naming and classification", "description": "How an agent tells one latency from another, and a latency 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 latency, 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 latency, 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 latency 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 latency, 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 latency, 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 latency 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 latency 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 latency, 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 latency, 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 latency 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 latency from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a latency, 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 latency, 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 latency 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 latency 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 latency between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a latency, 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 latency, 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 latency 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 latency, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a latency 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 latency, 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 latency, 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 latency 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 latency 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 latency 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 latency 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 latency 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 latency?", "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 latency?", "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 latency 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 latency and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a latency, 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 latency, 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 latency 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 latency is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a latency, 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 latency, 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 latency is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 5, "layers": 10, "findings": 12, "questions": 32 } } } }