{ "model": { "rank": 4266, "code": "thing-q19541", "model_id": "vr.tr.search-engine", "name": "search engine", "purpose": "Enable an AI agent to recognise a search engine, assess its coverage and retrieval behaviour, and decide how to query, evaluate or administer it within authorised limits.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q19541/", "tier": 2, "score": 77, "payload": { "layer": "wikidata", "aliases": [ "Search appliance", "blog search engine", "distributed search engine", "hotel booking website", "scholarly search service", "web search", "desktop search", "site-specific search engine", "semantic search", "vertical search", "hangul search engine", "human search engine", "Associatieve zoekmachine", "video search engine", "visual search engine", "audio search engine", "collaborative search engine", "database search engine", "BitTorrent search engine", "network search engine", "COVID-19 search engine", "metasearch engine", "People search site", "IP search engine", "slow search engine", "Symcio", "news search engine", "social search", "image meta search", "Zoombu" ], "aliasCount": 30, "merged": 32, "knownIn": 77, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q19541", "url": "https://www.wikidata.org/wiki/Q19541", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T19:50:28Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 20.3, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087b7-dfab-7c92-adf5-a19bb00b8fb1\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: search engine\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 695 things:\n# Batch 004: 1001 re", "usd": 0, "recall": true }, "codex": { "seconds": 59, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a087b7-dfb1-7bd0-8a5c-ec0261474a2c\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: search engine\nRegistry id: vr.tr.search-engine\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none" } } }, "metaModel": { "id": "THING-Q19541", "registryId": "vr.tr.search-engine", "name": "search engine", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q19541/", "model": { "registry_id": "vr.tr.search-engine", "name": "search engine", "purpose": "Enable an AI agent to recognise a search engine, assess its coverage and retrieval behaviour, and decide how to query, evaluate or administer it within authorised limits.", "definition": "A search engine is a software system that accepts a query and retrieves items from an information collection, usually using an index and ranking results by estimated relevance.", "scope_statement": "This model owns search engine as a kind of software system that accepts search requests and selects relevant items from a searchable corpus; it covers retrieval capabilities and operational state, while treating deployment hardware, individual products and operators as related entities.", "in_scope": [ "Searchable corpus, acquisition boundaries and coverage", "Indexing or equivalent searchable representations and their freshness", "Query interpretation, matching, ranking and result presentation", "Retrieval quality, service availability and observable limitations", "Access controls, result exclusions and authorised search operations" ], "out_of_scope": [ "Physical servers, storage devices and network infrastructure", "The full content and lifecycle of indexed documents", "Web browsers and general navigation interfaces", "General-purpose database management beyond search capabilities", "Advertising marketplaces and the operator's wider business", "Standalone answer generators that do not retrieve from a corpus" ], "distinguishing_features": [ "Accepts a query or equivalent search request and selects matching or relevant items from a corpus, rather than only presenting a fixed directory.", "Performs retrieval itself or orchestrates retrieval providers; a browser that merely submits requests to another service is a search client.", "Provides a reusable retrieval capability across a corpus, rather than only navigating to an already specified address.", "Identifies retrieved items or passages, potentially alongside generated answers; answer generation alone does not establish a search engine.", "May use lexical, semantic or other matching methods and need not crawl the public web." ], "characteristics": [ { "name": "Search domain", "kind": "category", "unit_or_values": "Public web, enterprise, site, collection, specialised domain, or mixed", "why_it_matters": "Determines which information needs the engine can plausibly satisfy." }, { "name": "Retrieval architecture", "kind": "category", "unit_or_values": "Own index, direct corpus search, federated retrieval, or hybrid", "why_it_matters": "Locates responsibility for coverage, freshness and retrieval failures." }, { "name": "Searchable corpus", "kind": "relation", "unit_or_values": "Collections, repositories, source systems or upstream search providers", "why_it_matters": "Defines the information boundary behind returned results." }, { "name": "Supported query capabilities", "kind": "category", "unit_or_values": "Keywords, phrases, Boolean operators, field filters, natural language, image, audio, or other documented inputs", "why_it_matters": "Allows an agent to formulate requests the engine can interpret." }, { "name": "Searchable item count", "kind": "measurement", "unit_or_values": "Items, with item definition, corpus boundary and observation time", "why_it_matters": "Indicates retrieval scale without treating item count as proof of completeness." }, { "name": "Source-to-searchable delay", "kind": "measurement", "unit_or_values": "Seconds, minutes, hours or days, with event definition and percentile", "why_it_matters": "Indicates how quickly source changes become discoverable." }, { "name": "Query latency", "kind": "measurement", "unit_or_values": "Milliseconds, with percentile, workload and measurement boundary", "why_it_matters": "Supports interactive use and timeout decisions." }, { "name": "Retrieval effectiveness", "kind": "measurement", "unit_or_values": "Precision@k, recall@k, nDCG@k or other declared metric, with evaluation set and judgement method", "why_it_matters": "Makes quality claims interpretable for a stated search task." }, { "name": "Service state", "kind": "state", "unit_or_values": "Available, degraded, unavailable, or unknown", "why_it_matters": "Guides retry, fallback and escalation decisions." }, { "name": "Visibility context", "kind": "relation", "unit_or_values": "User identity, tenant, permissions, locale and applicable search policies", "why_it_matters": "Explains why different users may legitimately receive different results." } ], "affordances": [ "Submit supported queries and inspect retrieved items, snippets and source links.", "Refine a search through documented filters, operators and sorting options.", "Compare results against a task-specific relevance evaluation set.", "Inspect coverage and freshness evidence where the engine exposes it.", "Request authorised ingestion, refresh, exclusion or removal operations.", "Detect degraded retrieval and use an approved fallback or report the limitation." ] }, "sources": [], "structure": { "bundles": [ { "id": "search-identity-and-boundaries", "name": "Search identity and boundaries", "description": "Establishes the retrieval system's role, search domain and relationship to adjacent systems.", "rationale": "An agent must distinguish the engine from its client interface, operator, hardware and optional answer-generation features.", "layers": [ { "id": "retrieval-role", "name": "Retrieval role", "description": "Identifies the capability that makes the system a search engine.", "findings": [ { "id": "engine-versus-client", "name": "Engine versus client", "description": "Record whether the system performs or orchestrates retrieval, and which interfaces only submit requests.", "questions": [ { "text": "Which component selects corpus items in response to a search request?", "kind": "definition", "id": "engine-versus-client-q01" }, { "text": "Which browser, search box or answer interface is a client of this engine?", "kind": "boundary", "id": "engine-versus-client-q02" } ] } ] }, { "id": "corpus-boundary", "name": "Corpus boundary", "description": "Defines what can be searched and the sources supplying that content.", "findings": [ { "id": "search-domain-and-dependencies", "name": "Search domain and dependencies", "description": "Record intended collections, supported content types and reliance on external retrieval providers.", "questions": [ { "text": "Which collections and content types are within the engine's intended search domain?", "kind": "boundary", "id": "search-domain-and-dependencies-q01" }, { "text": "Which results come from the engine's own retrieval resources and which come from upstream providers?", "kind": "provenance", "id": "search-domain-and-dependencies-q02" } ] } ] } ] }, { "id": "acquisition-and-searchable-state", "name": "Acquisition and searchable state", "description": "Tracks how content becomes searchable, remains current and leaves the searchable corpus.", "rationale": "A missing or stale result can originate before query processing, so acquisition and representation require separate evidence.", "layers": [ { "id": "content-acquisition", "name": "Content acquisition", "description": "Describes discovery, submission and source access mechanisms.", "findings": [ { "id": "ingestion-paths-and-gaps", "name": "Ingestion paths and gaps", "description": "Record crawlers, connectors, feeds or direct access paths and the content they cannot acquire.", "questions": [ { "text": "How are new and changed items discovered or supplied to the engine?", "kind": "provenance", "id": "ingestion-paths-and-gaps-q01" }, { "text": "Which source restrictions, unsupported formats or acquisition failures prevent intended content from becoming searchable?", "kind": "boundary", "id": "ingestion-paths-and-gaps-q02" } ] } ] }, { "id": "representation-lifecycle", "name": "Representation lifecycle", "description": "Tracks searchable units, updates, duplicates and deletion propagation.", "findings": [ { "id": "freshness-and-removal", "name": "Freshness and removal", "description": "Record how source items map to searchable units and how changes propagate to results.", "questions": [ { "text": "What is a searchable unit, and how are versions, duplicate items and canonical sources represented?", "kind": "definition", "id": "freshness-and-removal-q01" }, { "text": "How long do additions, updates and deletions take to appear in search, and how is completion verified?", "kind": "measurement", "id": "freshness-and-removal-q02" } ] } ] } ] }, { "id": "query-and-result-behaviour", "name": "Query and result behaviour", "description": "Describes how requests become candidate matches and how those matches are ordered and exposed.", "rationale": "An agent needs to predict query semantics and interpret results without assuming undocumented operators or ranking behaviour.", "layers": [ { "id": "query-interpretation", "name": "Query interpretation", "description": "Captures accepted input and transformations affecting retrieval.", "findings": [ { "id": "query-semantics", "name": "Query semantics", "description": "Record supported syntax, matching methods and query rewriting where known.", "questions": [ { "text": "Which query forms, operators and filters are supported, and what do they mean?", "kind": "definition", "id": "query-semantics-q01" }, { "text": "How can an agent detect or control spelling correction, expansion, translation or semantic interpretation?", "kind": "action", "id": "query-semantics-q02" } ] } ] }, { "id": "ranking-and-presentation", "name": "Ranking and presentation", "description": "Captures result ordering, grouping and evidence visible to the searcher.", "findings": [ { "id": "result-interpretation", "name": "Result interpretation", "description": "Record the meaning of result fields and distinctions among retrieved evidence, promotions and generated text.", "questions": [ { "text": "Which documented factors, filters or user context affect result order and inclusion?", "kind": "definition", "id": "result-interpretation-q01" }, { "text": "How are source items, extracted snippets, sponsored placements and generated answers distinguished and traced?", "kind": "provenance", "id": "result-interpretation-q02" } ] } ] } ] }, { "id": "retrieval-quality-and-operation", "name": "Retrieval quality and operation", "description": "Assesses search effectiveness and whether the retrieval service is usable under stated conditions.", "rationale": "Fast responses can still be irrelevant or incomplete, while service failures can resemble legitimate empty results.", "layers": [ { "id": "effectiveness-evidence", "name": "Effectiveness evidence", "description": "Defines task-specific evaluations and limits on coverage claims.", "findings": [ { "id": "relevance-and-coverage-evaluation", "name": "Relevance and coverage evaluation", "description": "Record evaluation queries, relevance judgements and the evidence supporting reported metrics.", "questions": [ { "text": "Which query set, user tasks and relevance judgements support the engine's quality measurements?", "kind": "provenance", "id": "relevance-and-coverage-evaluation-q01" }, { "text": "What precision, recall or ranking metric is measured, at what cutoff, and against which known reference set?", "kind": "measurement", "id": "relevance-and-coverage-evaluation-q02" } ] } ] }, { "id": "runtime-condition", "name": "Runtime condition", "description": "Captures latency, limits and partial failure behaviour.", "findings": [ { "id": "degradation-and-recovery", "name": "Degradation and recovery", "description": "Record observable distinctions between successful empty searches, partial retrieval and unavailable service.", "questions": [ { "text": "Which signals distinguish zero matches from timeouts, stale indexes, unavailable partitions or failed upstream providers?", "kind": "definition", "id": "degradation-and-recovery-q01" }, { "text": "Which retries, request reductions or fallback routes are permitted under the engine's limits?", "kind": "action", "id": "degradation-and-recovery-q02" } ] } ] } ] }, { "id": "visibility-and-search-governance", "name": "Visibility and search governance", "description": "Defines who may discover content and which controls govern search data and result exclusions.", "rationale": "Search can expose information through titles, snippets and aggregates even when opening the source is restricted.", "layers": [ { "id": "permission-aware-retrieval", "name": "Permission-aware retrieval", "description": "Examines enforcement of source and tenant access boundaries throughout retrieval.", "findings": [ { "id": "result-access-boundaries", "name": "Result access boundaries", "description": "Record how permissions apply to matches, snippets, suggestions, counts and cached representations.", "questions": [ { "text": "How are source permissions enforced for results, snippets, suggestions and result counts?", "kind": "boundary", "id": "result-access-boundaries-q01" }, { "text": "How are permission changes propagated and checked before restricted content remains discoverable?", "kind": "action", "id": "result-access-boundaries-q02" } ] } ] }, { "id": "search-data-and-exclusions", "name": "Search data and exclusions", "description": "Captures query-data handling and authorised controls over discoverability.", "findings": [ { "id": "logging-and-removal-controls", "name": "Logging and removal controls", "description": "Record query retention, personalisation inputs and the scope of exclusion or removal mechanisms.", "questions": [ { "text": "Which query, identity and interaction data are retained or used for personalisation, and under whose control?", "kind": "provenance", "id": "logging-and-removal-controls-q01" }, { "text": "Who may request exclusion or removal, and does each mechanism affect acquisition, indexed results, cached content or all three?", "kind": "action", "id": "logging-and-removal-controls-q02" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This describes the general software-system sense, including web search; the PHY.OBJ domain assignment should be checked because a search engine is not inherently a physical device.", "The kinds overlap: academic search is domain-specific, while metasearch describes an architecture that queries other search services.", "These statements are recalled knowledge, not source-verified research; no universal capacity, latency range or certification requirement is asserted." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Web search engine", "Enterprise search engine", "Desktop search engine", "Domain-specific search engine", "Metasearch engine", "Academic search engine" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "RFC 9309, Robots Exclusion Protocol, published by the IETF, standardizes robots.txt instructions for crawlers; these instructions are not access authorization.", "Unicode Standard, maintained by the Unicode Consortium, provides character encoding used in multilingual queries and indexed text." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Finding public web pages and other online resources", "Retrieving documents across an organization's information systems", "Locating files and their contents on a personal computer", "Discovering scholarly publications", "Finding products within a retail catalogue" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Precision at a specified result cutoff", "typical_range": "0-1 by definition; observed values depend on the query set and relevance judgments", "unit": "proportion" }, { "quantity": "Recall against a defined set of relevant items", "typical_range": "0-1 by definition; open-web recall is generally difficult to establish", "unit": "proportion" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Incomplete or stale indexes omit useful items or return outdated information.", "Ambiguous queries and inadequate language handling produce irrelevant results.", "Spam and ranking manipulation promote misleading or malicious content.", "Incorrect access-control enforcement exposes restricted documents or snippets.", "Query logging and personalization can expose sensitive interests or reinforce biased rankings." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Languages and writing systems require different tokenization, normalization and morphological processing.", "Ranking and available results can vary with location, language preferences and local content coverage.", "Privacy requirements and content-removal obligations vary by jurisdiction." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "Web browser", "difference": "A browser displays and interacts with web resources; a search engine retrieves resources matching a query." }, { "name": "Web crawler", "difference": "A crawler discovers and fetches resources; it may supply a search engine but does not itself provide the complete query-and-retrieval system." }, { "name": "Search index", "difference": "An index is a data structure supporting retrieval; a search engine includes query processing and result delivery." }, { "name": "Database management system", "difference": "A database management system manages stored data and structured operations; a search engine specializes in information retrieval, often with relevance ranking, although products can combine both." }, { "name": "Recommendation system", "difference": "A recommendation system suggests items from contextual or preference signals, often without an explicit query; search centers on a submitted information request." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of search engine this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend the ordinary software retrieval sense of search engine, and how should that sense relate to its assigned PHY / PHY.OBJ classification?", "Does an existing Vercy world model already own this concept or its core retrieval capabilities?", "Should metasearch services and retrieval systems that return only generated answers be included as variants or linked neighbouring kinds?", "Which authoritative sources establish the query semantics, quality measures and operational controls appropriate to this kind?", "Which deployment-specific interoperability, accessibility, privacy or other requirements should be recorded without implying a universal search-engine certification?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "device, machine or tool", "method": "Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.", "facetsInferred": true, "nextPass": "A researcher replaces this draft with a sourced specification. Treat every sentence below as a proposal to argue with.", "purpose": "Give an agent a durable, checkable way to recognise a search engine, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a search engine, assess its coverage and retrieval behaviour, and decide how to query, evaluate or administer it within authorised limits.", "characteristics": { "substance": "material", "origin": "manufactured", "agency": "inert", "mobility": "varies" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Search appliance, blog search engine, distributed search engine, hotel booking website, scholarly search service, web search, desktop search, site-specific search engine, semantic search, vertical search, hangul search engine, human search engine.", "32 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 77 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 search engine, and on what evidence are they told apart?" ], "whatItIsMadeOf": "matter you can touch", "physicalCharacter": [ "Mobility varies between examples.", "Does nothing on its own; everything it does, something else did to it.", "These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing." ], "whatCanBeDoneWithIt": [ "observe it, measure it, record its state" ], "howItIsRecognised": [ "Recognised by form, by the arrangement of its controls, and by markings - a plate, a model number, a certification mark. Form alone rarely separates two models that do very different things." ], "relatedModels": [ { "relation": "covers", "note": "Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.", "targets": [ "Search appliance", "blog search engine", "distributed search engine", "hotel booking website", "scholarly search service", "web search", "desktop search", "site-specific search engine", "semantic search", "vertical search", "hangul search engine", "human search engine" ] } ], "standing": "Described in 77 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 32 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 search engine from another, and a search engine 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 search engine, 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 search engine, 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 search engine 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 search engine, 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 search engine, 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 search engine 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 search engine 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 search engine, 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 search engine, 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 search engine 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 search engine from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a search engine, 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 search engine, 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 search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "form-and-composition", "name": "Form, composition and condition", "description": "What a search engine is made of, what shape and size it takes, and what state it is in.", "rationale": "A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.", "layers": [ { "id": "form-and-dimensions", "name": "Form and dimensions", "description": "Shape, size, mass and the ranges these take across examples.", "findings": [ { "id": "measurable-dimensions", "name": "Measurable dimensions and their units", "description": "The quantities worth recording and the units they are recorded in.", "questions": [ { "id": "measurable-dimensions-q01", "text": "What identifies and describes the dimensions of a search engine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "measurable-dimensions-q02", "text": "Who or what asserted this about the dimensions of a search engine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "measurable-dimensions-q03", "text": "What may an agent decide or do once the dimensions of a search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "material-and-composition", "name": "Material and composition", "description": "Materials, parts and how they are put together.", "findings": [ { "id": "parts-and-materials", "name": "Parts and materials", "description": "What a search engine is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a search engine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "parts-and-materials-q02", "text": "Who or what asserted this about the composition of a search engine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "parts-and-materials-q03", "text": "What may an agent decide or do once the composition of a search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "condition-and-integrity", "name": "Condition and integrity", "description": "Wear, damage, health and the difference between working and broken.", "findings": [ { "id": "condition-assessment", "name": "Condition, damage and health", "description": "How the condition of a search engine is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a search engine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "condition-assessment-q02", "text": "Who or what asserted this about the condition of a search engine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "condition-assessment-q03", "text": "What may an agent decide or do once the condition of a search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "place-and-movement", "name": "Place and movement", "description": "Where a search engine is, how it got there and where it may go (varies).", "rationale": "A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.", "layers": [ { "id": "location-and-placement", "name": "Location and placement", "description": "Position, containment and the reference frame the position is given in.", "findings": [ { "id": "position-and-frame", "name": "Position, container and reference frame", "description": "Where a search engine is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a search engine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "position-and-frame-q02", "text": "Who or what asserted this about the location of a search engine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "position-and-frame-q03", "text": "What may an agent decide or do once the location of a search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "movement-and-transfer", "name": "Movement and transfer", "description": "How a search engine is carried, installed or relocated.", "findings": [ { "id": "movement-events", "name": "Movement events and constraints", "description": "What counts as a movement, what records it and what limits it.", "questions": [ { "id": "movement-events-q01", "text": "What identifies and describes the movement of a search engine, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "movement-events-q02", "text": "Who or what asserted this about the movement of a search engine, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "movement-events-q03", "text": "What may an agent decide or do once the movement of a search engine 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 search engine 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 search engine between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a search engine, 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 search engine, 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 search engine 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 search engine, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a search engine 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 search engine, 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 search engine, 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 search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "function-and-principle", "name": "Function and operating principle", "description": "What search engine is for and how it achieves it.", "rationale": "Two devices with the same name can work on different principles, and the principle is what predicts failure and constrains use.", "layers": [ { "id": "intended-function", "name": "Intended function", "description": "The job it does, and the jobs it is used for anyway.", "findings": [ { "id": "function-record", "name": "Function, principle and variants", "description": "What it does, how, and which variants do it differently.", "questions": [ { "id": "function-record-q01", "text": "What function does search engine perform, on what operating principle, and which variants differ in that principle?", "kind": "definition" }, { "id": "function-record-q02", "text": "What use falls outside the intended function but happens in practice?", "kind": "boundary" } ] } ] }, { "id": "capacity-and-rating", "name": "Capacity and rating", "description": "The numbers that say what it can do and where it stops.", "findings": [ { "id": "ratings", "name": "Ratings and their conditions", "description": "Rated capacity, power, throughput and the conditions each assumes.", "questions": [ { "id": "ratings-q01", "text": "What ratings characterise search engine, in what units, and under what stated conditions?", "kind": "measurement" }, { "id": "ratings-q02", "text": "What happens beyond the rating - degradation, refusal, damage - and how is that detected?", "kind": "action" } ] } ] } ] }, { "id": "operation-and-state", "name": "Operation, controls and state", "description": "How search engine is operated and what state it is in right now.", "rationale": "An agent acting on a device needs its current state and the controls that change it, not just its specification.", "layers": [ { "id": "controls-and-modes", "name": "Controls and modes", "description": "What can be set, what that changes, and what is interlocked.", "findings": [ { "id": "control-surface", "name": "Control surface and interlocks", "description": "The settings available and the conditions that block them.", "questions": [ { "id": "control-surface-q01", "text": "What controls and modes does search engine have, and what does each change?", "kind": "definition" }, { "id": "control-surface-q02", "text": "Which actions are interlocked or forbidden in which state, and what must be true before acting?", "kind": "action" } ] } ] }, { "id": "condition-and-maintenance", "name": "Condition and maintenance", "description": "Wear, service intervals, consumables and the line between working and broken.", "findings": [ { "id": "service-record", "name": "Condition, service and consumables", "description": "What is consumed, what is serviced, and how condition is judged.", "questions": [ { "id": "service-record-q01", "text": "What consumables and service does search engine need, at what interval, and on whose authority?", "kind": "measurement" }, { "id": "service-record-q02", "text": "What evidence separates a unit that is working from one that is out of service?", "kind": "boundary" } ] } ] } ] }, { "id": "kind-model-unit", "name": "Kind, model and unit", "description": "Whether a claim about search engine is about the kind, a product line, or one physical unit.", "rationale": "This is the boundary most often got wrong for made things, and getting it wrong mixes a catalogue entry with the machine in the yard.", "layers": [ { "id": "level-of-reference", "name": "Level of reference", "description": "The three levels and what belongs at each.", "findings": [ { "id": "level-rules", "name": "What belongs to kind, model and unit", "description": "Which properties are shared by all of them and which are not.", "questions": [ { "id": "level-rules-q01", "text": "Which facts about search engine hold for every one of them, which for a model, and which only for one unit?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifies an individual unit, and what should an agent do when it has only the kind?", "kind": "action" } ] } ] }, { "id": "standards-and-conformity", "name": "Standards and conformity", "description": "The standards a working example must meet and who attests it.", "findings": [ { "id": "conformity", "name": "Standards, marks and attestation", "description": "Which standard applies, who certifies, and what the mark means.", "questions": [ { "id": "conformity-q01", "text": "Which standards govern search engine, issued by whom, and what does conformity actually assert?", "kind": "provenance" }, { "id": "conformity-q02", "text": "What may an agent conclude from a certification mark, and what may it not?", "kind": "boundary" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a search engine 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 search engine and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a search engine, 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 search engine, 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 search engine 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 search engine is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a search engine, 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 search engine, 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 search engine is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 8, "layers": 17, "findings": 19, "questions": 51 } } } }