{ "model": { "rank": 4917, "code": "thing-q2493", "model_id": "vr.tr.data-compression", "name": "data compression", "purpose": "Let an agent explain data compression and its methods, relay theory, algorithms and applications from computer science sources, describe the techniques the registry aliases name, and distinguish compression from encryption, deduplication, archiving and probabilistic data structures.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q2493/", "tier": 2, "score": 71, "payload": { "layer": "wikidata", "aliases": [ "Approximate Membership Query Filter", "executable compression", "model compression", "dataset compression", "entropy coding", "solid compression", "video compression", "token-based compression", "source coding", "speech coding", "image compression", "lossless compression", "lossy compression", "dictionary coder", "minification", "audio compression", "model quantization", "Fibonacci coding", "Asymmetric Numeral Systems", "adaptive coding", "Tunstall coding", "Algebraic code-excited linear prediction", "Continuously variable slope delta modulation", "PDC-EFR", "fractal compression", "texture compression", "LZ77 and LZ78", "Pumping", "Luminance-Alpha Texture Compression" ], "aliasCount": 29, "merged": 29, "knownIn": 71, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q2493", "url": "https://www.wikidata.org/wiki/Q2493", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-13T18:38:43Z", "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": 4, "engine": "claude" }, "metaModel": { "id": "THING-Q2493", "registryId": "vr.tr.data-compression", "name": "data compression", "version": "0.2.0-wave.4", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2493/", "model": { "registry_id": "vr.tr.data-compression", "name": "data compression", "purpose": "Let an agent explain data compression and its methods, relay theory, algorithms and applications from computer science sources, describe the techniques the registry aliases name, and distinguish compression from encryption, deduplication, archiving and probabilistic data structures.", "definition": "The process of encoding information using fewer bits than the original representation, either lossless, allowing exact reconstruction through entropy coding and dictionary methods, or lossy, discarding less important information as in JPEG and MP3, including executable compression, solid compression of many files as one stream in archivers, dataset compression and model compression of neural networks by pruning and quantisation; approximate membership query filters such as Bloom filters are related space-efficient data structures rather than compression per se.", "what_it_is_for": "Reducing data size for storage and transmission.", "affordances": [ "explain lossless and lossy compression", "relay algorithms and theory", "describe named techniques", "distinguish related concepts" ], "distinguishing_features": [ "Fewer bits", "Lossless or lossy", "Entropy bounds", "Ubiquitous" ], "appearance": "Not a visible object; smaller encoded files.", "visual_identification": [ "Encoding data in fewer bits", "Entropy coding, executable compression, solid compression, dataset and model compression; AMQ filters as related", "Encryption hides content; deduplication removes copies; archiving bundles files; Bloom filters answer membership queries" ], "physical_properties": [ { "quantity": "Shannon source coding theorem", "typical_range": "1948", "unit": "year", "note": "" }, { "quantity": "Huffman coding", "typical_range": "1952", "unit": "year", "note": "" }, { "quantity": "LZ77", "typical_range": "1977", "unit": "year", "note": "Lempel and Ziv" }, { "quantity": "JPEG standard", "typical_range": "1992", "unit": "year", "note": "" } ], "families_and_kinds": [ "entropy coding such as Huffman and arithmetic coding", "dictionary methods such as LZ77 and LZW", "lossy media codecs", "executable compression", "solid archive compression", "model compression for neural networks" ], "related_models": [ { "relation": "is a kind of", "target": "data processing", "why": "in registry terms" }, { "relation": "is bounded by", "target": "entropy (information theory)", "why": "" }, { "relation": "includes", "target": "Huffman coding", "why": "" }, { "relation": "is contrasted with", "target": "encryption", "why": "" } ], "identifiers": [], "standards_and_regulation": [ "Codec standards such as JPEG, MPEG and zlib RFC 1950", "Patent and licensing regimes for codecs" ], "failure_modes_and_hazards": [ "Quality loss in lossy compression", "Compression bombs", "Registry aliases mixing compression and filters" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "understand", "name": "Understand", "description": "What data compression is.", "rationale": "Science.", "layers": [ { "id": "definition", "name": "Definition", "description": "Definition.", "findings": [ { "id": "definition-finding", "name": "Definition", "description": "Definition.", "questions": [ { "text": "What is data compression, and how does it differ from encryption, deduplication, archiving and probabilistic filters?", "kind": "definition" }, { "text": "Is the question about theory, an algorithm, a format or a specific application?", "kind": "boundary" } ] } ] }, { "id": "techniques", "name": "Techniques", "description": "Named techniques.", "findings": [ { "id": "techniques-finding", "name": "Techniques", "description": "Techniques.", "questions": [ { "text": "What are entropy coding, executable, solid, dataset and model compression, and AMQ filters?", "kind": "definition" }, { "text": "Which entry fits the specific technique?", "kind": "action" } ] } ] } ] }, { "id": "theory", "name": "Theory", "description": "Theory.", "rationale": "Science.", "layers": [ { "id": "entropy", "name": "Entropy", "description": "Information theory.", "findings": [ { "id": "entropy-finding", "name": "Entropy", "description": "Entropy.", "questions": [ { "text": "How does Shannon entropy bound lossless compression?", "kind": "provenance" }, { "text": "Which references are standard?", "kind": "provenance" } ] } ] }, { "id": "algorithms", "name": "Algorithms", "description": "Algorithms.", "findings": [ { "id": "algorithms-finding", "name": "Algorithms", "description": "Algorithms.", "questions": [ { "text": "How do Huffman, arithmetic, LZ and transform coding work?", "kind": "provenance" }, { "text": "Which sources are cited?", "kind": "provenance" } ] } ] } ] }, { "id": "applications", "name": "Applications", "description": "Applications.", "rationale": "Application.", "layers": [ { "id": "media", "name": "Media", "description": "Media codecs.", "findings": [ { "id": "media-finding", "name": "Media", "description": "Media.", "questions": [ { "text": "How do lossy codecs for images, audio and video work?", "kind": "provenance" }, { "text": "Which entry fits JPEG?", "kind": "action" } ] } ] }, { "id": "ml", "name": "ML", "description": "Model compression.", "findings": [ { "id": "ml-finding", "name": "ML", "description": "ML.", "questions": [ { "text": "How are neural networks compressed by pruning, quantisation and distillation?", "kind": "provenance" }, { "text": "Which entry fits quantization (machine learning)?", "kind": "action" } ] } ] } ] }, { "id": "context", "name": "Context", "description": "History and security.", "rationale": "Context.", "layers": [ { "id": "history", "name": "History", "description": "History.", "findings": [ { "id": "history-finding", "name": "History", "description": "History.", "questions": [ { "text": "How did compression develop from Morse code to modern codecs?", "kind": "provenance" }, { "text": "Which entry fits the history of data compression?", "kind": "action" } ] } ] }, { "id": "security", "name": "Security", "description": "Security issues.", "findings": [ { "id": "security-finding", "name": "Security", "description": "Security.", "questions": [ { "text": "What risks such as compression bombs and side channels exist, at a general level?", "kind": "provenance" }, { "text": "Which entry fits zip bomb?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should model compression and solid compression be separate primary entries?", "How should computer science sources be linked?", "The registry alias approximate membership query filter is a data structure rather than compression; should it 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 data compression, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent explain data compression and its methods, relay theory, algorithms and applications from computer science sources, describe the techniques the registry aliases name, and distinguish compression from encryption, deduplication, archiving and probabilistic data structures.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Approximate Membership Query Filter, executable compression, model compression, dataset compression, entropy coding, solid compression, video compression, token-based compression, source coding, speech coding, image compression, lossless compression.", "29 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 71 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 data compression, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "physicalCharacter": [ "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Approximate Membership Query Filter", "executable compression", "model compression", "dataset compression", "entropy coding", "solid compression", "video compression", "token-based compression", "source coding", "speech coding", "image compression", "lossless compression" ] } ], "standing": "Described in 71 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 29 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 data compression from another, and a data compression 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 data compression, 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 data compression, 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 data compression 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 data compression, 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 data compression, 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 data compression 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 data compression 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 data compression, 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 data compression, 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 data compression 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 data compression from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a data compression, 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 data compression, 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 data compression 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 data compression 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 data compression between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a data compression, 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 data compression, 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 data compression 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 data compression, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a data compression 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 data compression, 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 data compression, 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 data compression is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a data compression proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a data compression, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a data compression and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a data compression, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a data compression, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a data compression is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a data compression consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a data compression takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a data compression, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a data compression, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a data compression 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 data compression 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 data compression 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 data compression 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 data compression 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 data compression?", "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 data compression?", "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 data compression 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 data compression and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a data compression, 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 data compression, 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 data compression 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 data compression is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a data compression, 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 data compression, 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 data compression 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 } } } }