{ "model": { "rank": 1249, "code": "thing-q8366", "model_id": "vr.tr.algorithm", "name": "algorithm", "purpose": "Let an agent handle algorithms by problem, steps, correctness, complexity and responsible use.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q8366/", "tier": 2, "score": 163, "payload": { "layer": "wikidata", "aliases": [ "facial recognition payment system", "parser", "packrat parser", "recursive-descent parser", "GLL parser", "LL(*) parser", "XSLT processor", "chart parser", "bottom-up parser", "recursive ascent parser", "Simple precedence parser", "text parser", "LL parser", "Fitness proportionate selection", "generative adversarial network", "tail-recursive parser", "Left corner parser", "Wasserstein GAN", "Deep Convolutional GAN", "abstraction layer", "Microcontroller Abstraction Layer", "OSI model layer", "machine learning model", "classification algorithm", "decompression algorithm", "uncritical thinking", "Bayes classifier", "hierarchical classifier", "Automated Pain Recognition", "nearest neighbor classifier", "constructive proof", "deductive-nomological model", "method of analytic tableaux", "adaptive algorithm", "natural language generation", "data conversion", "construction of the real numbers", "zero-sum thinking", "knowledge graph-to-text generation", "paraphrasing" ], "aliasCount": 404, "merged": 405, "knownIn": 163, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q8366", "url": "https://www.wikidata.org/wiki/Q8366", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-11T06:51:08Z", "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-Q8366", "registryId": "vr.tr.algorithm", "name": "algorithm", "version": "0.2.0-wave.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q8366/", "model": { "registry_id": "vr.tr.algorithm", "name": "algorithm", "purpose": "Let an agent handle algorithms by problem, steps, correctness, complexity and responsible use.", "definition": "A finite, well-defined sequence of instructions for solving a problem or performing a computation, such as sorting, searching, parsing or encryption.", "what_it_is_for": "Solving problems systematically, especially in computing.", "affordances": [ "design and describe it", "prove it correct", "analyse its complexity", "implement and test it" ], "distinguishing_features": [ "Finite and well-defined", "Correctness and complexity can be analysed", "Independent of programming language", "Automated decision systems raise fairness issues" ], "appearance": "Pseudocode, flowcharts or code.", "visual_identification": [ "Input, steps and output", "Named families such as parsers or sorts", "Programs implement algorithms" ], "physical_properties": [], "families_and_kinds": [ "sorting and searching", "graph algorithms", "parsing algorithms", "cryptographic algorithms", "machine learning algorithms" ], "related_models": [ { "relation": "is a kind of", "target": "procedure", "why": "category" }, { "relation": "is implemented by", "target": "computer program", "why": "code" }, { "relation": "is studied by", "target": "computer science", "why": "field" }, { "relation": "is used in", "target": "automated decision systems", "why": "applications" } ], "identifiers": [], "standards_and_regulation": [ "EU AI Act for high-risk automated systems", "GDPR Article 22 on automated decisions", "Cryptographic standards such as FIPS" ], "failure_modes_and_hazards": [ "Incorrect edge cases", "Poor complexity on large inputs", "Biased outcomes in decisions about people" ], "in_scope": [], "out_of_scope": [], "characteristics": [] }, "sources": [], "structure": { "bundles": [ { "id": "problem", "name": "Problem", "description": "What it solves.", "rationale": "The problem defines the algorithm.", "layers": [ { "id": "task", "name": "Task", "description": "Input and output.", "findings": [ { "id": "task-finding", "name": "Task", "description": "Problem specification.", "questions": [ { "text": "What problem does the algorithm solve, with what input and output?", "kind": "definition" }, { "text": "What assumptions does it make?", "kind": "boundary" } ] } ] }, { "id": "family", "name": "Family", "description": "Kind.", "findings": [ { "id": "family-finding", "name": "Family", "description": "Algorithm family.", "questions": [ { "text": "Which family does it belong to?", "kind": "definition" }, { "text": "Is there a known better alternative?", "kind": "action" } ] } ] } ] }, { "id": "analysis", "name": "Analysis", "description": "Correctness and cost.", "rationale": "Analysis proves quality.", "layers": [ { "id": "correctness", "name": "Correctness", "description": "Proof.", "findings": [ { "id": "correctness-finding", "name": "Correctness", "description": "Correctness.", "questions": [ { "text": "How is it shown to be correct?", "kind": "provenance" }, { "text": "What edge cases matter?", "kind": "boundary" } ] } ] }, { "id": "complexity", "name": "Complexity", "description": "Time and space.", "findings": [ { "id": "complexity-finding", "name": "Complexity", "description": "Complexity.", "questions": [ { "text": "What are its time and space complexity?", "kind": "measurement" }, { "text": "How does it behave in practice?", "kind": "measurement" } ] } ] } ] }, { "id": "implementation", "name": "Implementation", "description": "Code.", "rationale": "Implementation can differ from design.", "layers": [ { "id": "code", "name": "Code", "description": "Program.", "findings": [ { "id": "code-finding", "name": "Code", "description": "Implementation.", "questions": [ { "text": "Where is a reference implementation?", "kind": "provenance" }, { "text": "How is it tested?", "kind": "provenance" } ] } ] }, { "id": "performance", "name": "Performance", "description": "Benchmarks.", "findings": [ { "id": "performance-finding", "name": "Performance", "description": "Benchmarks.", "questions": [ { "text": "How does it perform on real data?", "kind": "measurement" }, { "text": "On which benchmark?", "kind": "provenance" } ] } ] } ] }, { "id": "impact", "name": "Impact", "description": "Use on people.", "rationale": "Algorithms can affect people.", "layers": [ { "id": "decisions", "name": "Decisions", "description": "Automated decisions.", "findings": [ { "id": "decisions-finding", "name": "Decisions", "description": "Automated decisions.", "questions": [ { "text": "Does it make or support decisions about people?", "kind": "boundary" }, { "text": "Is there human review?", "kind": "boundary" } ] } ] }, { "id": "fairness", "name": "Fairness", "description": "Bias.", "findings": [ { "id": "fairness-finding", "name": "Fairness", "description": "Fairness.", "questions": [ { "text": "Has it been tested for bias?", "kind": "provenance" }, { "text": "How can affected people contest outcomes?", "kind": "action" } ] } ] } ] } ] }, "openQuestions": [ "Should named algorithms be separate entries?", "How should complexity be recorded?", "How should algorithmic accountability be represented?" ], "statistics": { "bundles": 4, "layers": 8, "findings": 8, "questions": 16 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "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 algorithm, record what state it is in, and decide what may be done with it.", "whatItIs": "Let an agent handle algorithms by problem, steps, correctness, complexity and responsible use.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: facial recognition payment system, parser, packrat parser, recursive-descent parser, GLL parser, LL(*) parser, XSLT processor, chart parser, bottom-up parser, recursive ascent parser, Simple precedence parser, text parser.", "405 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 163 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 algorithm, 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", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "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": [ "facial recognition payment system", "parser", "packrat parser", "recursive-descent parser", "GLL parser", "LL(*) parser", "XSLT processor", "chart parser", "bottom-up parser", "recursive ascent parser", "Simple precedence parser", "text parser" ] } ], "standing": "Described in 163 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 405 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 algorithm from another, and a algorithm 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 algorithm, 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 algorithm, 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 algorithm 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 algorithm, 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 algorithm, 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 algorithm 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 algorithm 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 algorithm, 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 algorithm, 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 algorithm 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 algorithm from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a algorithm, 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 algorithm, 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 algorithm 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 algorithm 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 algorithm between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a algorithm, 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 algorithm, 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 algorithm 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 algorithm, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a algorithm 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 algorithm, 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 algorithm, 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 algorithm 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 algorithm 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 algorithm contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a algorithm, 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 algorithm, 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 algorithm 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 algorithm and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a algorithm, 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 algorithm, 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 algorithm is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of algorithm a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For algorithm, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of algorithm exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made algorithm and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to algorithm, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in algorithm, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a algorithm 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 algorithm and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a algorithm, 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 algorithm, 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 algorithm 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 algorithm is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a algorithm, 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 algorithm, 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 algorithm 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 } } } }