{ "model": { "rank": 2448, "code": "thing-q8371", "model_id": "vr.tr.cello", "name": "cello", "purpose": "Enable an AI agent to recognise a cello, assess its playing readiness and preservation needs, and decide which playing, handling, setup or maintenance actions are appropriate.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q8371/", "tier": 2, "score": 105, "payload": { "layer": "wikidata", "aliases": [ "violoncello piccolo" ], "aliasCount": 1, "merged": 1, "knownIn": 105, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.cello", "source": { "dataset": "wikidata", "item": "Q8371", "url": "https://www.wikidata.org/wiki/Q8371", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:19:49Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 14.1, "error": "Error: Internal error: {\n \"message\": \"API error (status 402 Payment Required): Grok Build usage balance exhausted\",\n \"http_status\": 402\n}", "retried": true }, "codex": { "seconds": 94, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.3\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: 01a07b29-4164-7e00-9c92-1813925208ac\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: cello\nRegistry id: vr.tr.cello\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model" } } }, "metaModel": { "id": "THING-Q8371", "registryId": "vr.tr.cello", "name": "cello", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q8371/", "model": { "registry_id": "vr.tr.cello", "name": "cello", "purpose": "Enable an AI agent to recognise a cello, assess its playing readiness and preservation needs, and decide which playing, handling, setup or maintenance actions are appropriate.", "definition": "", "scope_statement": "This model owns an individual cello as a playable physical instrument, including its configuration, sounding system, structural condition, setup and instrument-specific constraints on use.", "in_scope": [ "Recognition of acoustic, electric and modified cello configurations", "Body, neck, fingerboard, strings, bridge and supporting components", "Tuning, string response and observed playing behaviour", "Structural condition, setup and readiness for a stated playing task", "Instrument-specific handling, storage and maintenance constraints" ], "out_of_scope": [ "The bow as a separately maintained object, including its hair and tensioning mechanism", "The player's technique, anatomy, proficiency and learning plan", "Compositions, notation, performances and repertoire requirements", "Cases, stands, amplifiers and other accessories as independent objects", "Ownership contracts, insurance policies, appraisals and sale transactions" ], "distinguishing_features": [ "Check the intended playing position: a cello is normally supported below the player with its neck extending upward and its body held between the legs, unlike a violin or viola held at the shoulder; record adaptations.", "Check nominal open-string pitches: the usual four-string cello configuration is C2-G2-D3-A3, which distinguishes it from standard violin, viola and double-bass tuning; alternative tuning requires additional identification evidence.", "Check string count, fret presence, body form and maker designation together when distinguishing a cello from a bass viol; no single feature is sufficient for every historical or modified instrument.", "Distinguish a fractional-size cello from another bowed instrument using intended tuning, playing position and model identification rather than body size alone.", "For a solid-body or skeletal electric instrument, check documented cello designation, intended tuning, string geometry and playing position rather than requiring an acoustic cello body." ], "characteristics": [ { "name": "Instrument configuration", "kind": "category", "unit_or_values": "acoustic, acoustic with pickup, electric, modified, unresolved", "why_it_matters": "Determines which body, acoustic and signal-path checks apply." }, { "name": "Nominal size designation", "kind": "category", "unit_or_values": "maker-stated full or fractional size; unknown", "why_it_matters": "Supports identification and fit assessment without treating a size label as an exact dimension." }, { "name": "Vibrating string length", "kind": "measurement", "unit_or_values": "mm, measured between nut and bridge contact points", "why_it_matters": "Informs string compatibility and playing geometry." }, { "name": "Installed string configuration", "kind": "relation", "unit_or_values": "ordered strings linked to intended pitch, product identity and observed condition", "why_it_matters": "Makes tuning and replacement decisions specific to the installed strings." }, { "name": "Observed tuning", "kind": "measurement", "unit_or_values": "pitch or frequency in Hz for each open string, with reference pitch and observation time", "why_it_matters": "Separates nominal tuning from the instrument's current state." }, { "name": "String clearance", "kind": "measurement", "unit_or_values": "mm for each string at a stated fingerboard location", "why_it_matters": "Helps assess playability and investigate buzzing or excessive stopping effort." }, { "name": "Bridge condition and position", "kind": "state", "unit_or_values": "observed alignment, foot contact, deformation and movement; unassessed", "why_it_matters": "Affects string geometry and whether tuning or playing should continue." }, { "name": "Body and neck integrity", "kind": "state", "unit_or_values": "location-specific observations of cracks, seam openings, deformation or looseness; unassessed", "why_it_matters": "Identifies conditions requiring restricted use or specialist assessment." }, { "name": "Support configuration", "kind": "category", "unit_or_values": "adjustable endpin, fixed support, no endpin, adapted support, unresolved", "why_it_matters": "Determines how the cello can be positioned securely for playing." }, { "name": "Playing response", "kind": "state", "unit_or_values": "string- and register-specific observations of response, sustain, buzz, rattle or unstable resonance under stated test conditions", "why_it_matters": "Connects reported sound problems to reproducible observations." }, { "name": "Use readiness", "kind": "state", "unit_or_values": "ready for stated task, usable with restrictions, assessment required, do not play, unknown", "why_it_matters": "Turns condition evidence into a bounded action decision." } ], "affordances": [ "Identify the cello's configuration and determine which assessment steps apply.", "Assess suitability for a stated playing task using size, setup, support and response observations.", "Tune compatible installed strings to an established target when condition permits.", "Position and support the instrument using its verified endpin or adapted support.", "Document sound or structural symptoms and refer appropriate work to a qualified repairer.", "Prepare the cello for storage or transport using its condition and support constraints." ] }, "sources": [], "structure": { "bundles": [ { "id": "cello-identity-and-configuration", "name": "Cello identity and configuration", "description": "Establishes why this instrument is treated as a cello and which physical variant is present.", "rationale": "Electric bodies, fractional sizes and modified string configurations make silhouette alone an unreliable basis for recognition.", "layers": [ { "id": "instrument-family-evidence", "name": "Instrument family evidence", "description": "Records evidence separating a cello from neighbouring bowed-string instruments.", "findings": [ { "id": "cello-identification-basis", "name": "Cello identification basis", "description": "Record intended tuning, playing position, construction cues and documented designation, including conflicting evidence.", "questions": [ { "text": "Which observed features and documented designation establish that this instrument is a cello?", "kind": "definition", "id": "cello-identification-basis-q01" }, { "text": "Could this instead be a viola, double bass or bass viol, and what evidence resolves that boundary?", "kind": "boundary", "id": "cello-identification-basis-q02" } ] } ] }, { "id": "variant-and-attribution", "name": "Variant and attribution", "description": "Separates physical configuration from claims about maker, age and model.", "findings": [ { "id": "documented-and-observed-configuration", "name": "Documented and observed configuration", "description": "Record acoustic or electric construction, size designation and modifications while distinguishing labels from verified attribution.", "questions": [ { "text": "What size, body type and string configuration are observed, and do they agree with the stated model?", "kind": "definition", "id": "documented-and-observed-configuration-q01" }, { "text": "What evidence supports the maker, date and modification history beyond any internal label?", "kind": "provenance", "id": "documented-and-observed-configuration-q02" } ] } ] } ] }, { "id": "strings-and-playing-geometry", "name": "Strings and playing geometry", "description": "Describes the installed strings and the geometry through which the player stops and bows them.", "rationale": "A cello may be recognisable and intact yet unsuitable to play because its strings or setup do not fit the intended use.", "layers": [ { "id": "stringing-and-tuning", "name": "Stringing and tuning", "description": "Records string identity, tuning targets and tuning-system behaviour.", "findings": [ { "id": "installed-strings-and-pitch-state", "name": "Installed strings and pitch state", "description": "Distinguish intended open-string pitches from measured pitches and establish whether the strings and tuning hardware support the target.", "questions": [ { "text": "Which strings are installed, what pitches are intended, and what pitches are currently measured?", "kind": "measurement", "id": "installed-strings-and-pitch-state-q01" }, { "text": "Do string condition, compatibility, peg behaviour or fine-tuner travel constrain tuning to those targets?", "kind": "action", "id": "installed-strings-and-pitch-state-q02" } ] } ] }, { "id": "fingerboard-and-bridge-geometry", "name": "Fingerboard and bridge geometry", "description": "Captures the measurable setup affecting stopping effort and access to individual strings.", "findings": [ { "id": "usable-string-path", "name": "Usable string path", "description": "Record vibrating length, string spacing, clearances and bridge or fingerboard irregularities without assuming one universal acceptable setup.", "questions": [ { "text": "What are the vibrating string length, string spacing and clearances at explicitly identified measurement points?", "kind": "measurement", "id": "usable-string-path-q01" }, { "text": "Which observed geometry limits clean stopping or bowing, and does correction require a cello setup specialist?", "kind": "action", "id": "usable-string-path-q02" } ] } ] } ] }, { "id": "structure-and-tension-bearing-condition", "name": "Structure and tension-bearing condition", "description": "Assesses components that maintain the cello's shape and carry string forces.", "rationale": "Cracks, unstable joints or displaced supporting parts can change whether continued tuning, playing or transport is appropriate.", "layers": [ { "id": "body-and-neck-integrity", "name": "Body and neck integrity", "description": "Records condition evidence in the body, seams, neck and fingerboard attachment.", "findings": [ { "id": "structural-symptoms-and-change", "name": "Structural symptoms and change", "description": "Locate visible damage and movement, distinguish observations from diagnoses, and record whether symptoms are changing.", "questions": [ { "text": "Where are cracks, open seams, deformation or loose attachments observed, and how have they changed since the last assessment?", "kind": "measurement", "id": "structural-symptoms-and-change-q01" }, { "text": "Which observations require stopping use or obtaining specialist assessment before further tuning?", "kind": "action", "id": "structural-symptoms-and-change-q02" } ] } ] }, { "id": "bridge-and-internal-support", "name": "Bridge and internal support", "description": "Assesses bridge seating, tailpiece attachment and applicable internal acoustic supports.", "findings": [ { "id": "support-condition-and-inspection-limits", "name": "Support condition and inspection limits", "description": "Record bridge and tailgut observations and, for applicable construction, evidence about the soundpost and bass bar without treating inaccessible parts as inspected.", "questions": [ { "text": "What can actually be established about bridge seating, tailgut condition and internal supports, and which parts remain uninspected?", "kind": "boundary", "id": "support-condition-and-inspection-limits-q01" }, { "text": "Does the evidence permit continued use, or require a repairer to assess the tension-bearing system?", "kind": "action", "id": "support-condition-and-inspection-limits-q02" } ] } ] } ] }, { "id": "sound-production-and-response", "name": "Sound production and response", "description": "Records how this cello responds during playing and, where applicable, through its electrical output.", "rationale": "Readiness depends on reproducible musical response as well as visible condition, and symptoms may arise outside the instrument.", "layers": [ { "id": "acoustic-playing-response", "name": "Acoustic playing response", "description": "Captures string- and register-specific sound observations under stated playing conditions.", "findings": [ { "id": "repeatable-response-symptoms", "name": "Repeatable response symptoms", "description": "Record response, sustain, buzzes, rattles and suspected wolf-note behaviour with enough context to repeat the observation.", "questions": [ { "text": "On which strings and pitches, at what dynamics and with which bowing or plucking conditions, does the symptom recur?", "kind": "measurement", "id": "repeatable-response-symptoms-q01" }, { "text": "What comparison distinguishes an instrument symptom from bow, player, room or accessory effects?", "kind": "boundary", "id": "repeatable-response-symptoms-q02" } ] } ] }, { "id": "pickup-and-output-path", "name": "Pickup and output path", "description": "Records installed sound capture and output components when present.", "findings": [ { "id": "electrical-output-readiness", "name": "Electrical output readiness", "description": "Identify pickup, onboard controls, power requirements and output behaviour; mark this layer inapplicable when absent.", "questions": [ { "text": "Which pickup and onboard electronics are installed, and what documented power and connection requirements apply?", "kind": "provenance", "id": "electrical-output-readiness-q01" }, { "text": "What test isolates an onboard output fault from the cable, amplifier or other external equipment?", "kind": "action", "id": "electrical-output-readiness-q02" } ] } ] } ] }, { "id": "playing-support-and-care-decisions", "name": "Playing support and care decisions", "description": "Connects cello-specific support, handling and care evidence to permitted actions.", "rationale": "An otherwise playable cello still needs secure positioning and condition-appropriate care to be usable for a particular task.", "layers": [ { "id": "support-and-task-fit", "name": "Support and task fit", "description": "Assesses endpin or adapted support security and compatibility with the intended playing arrangement.", "findings": [ { "id": "secure-playing-position", "name": "Secure playing position", "description": "Record support extension, locking behaviour, floor contact and instrument dimensions relevant to the proposed arrangement.", "questions": [ { "text": "Does the endpin or alternative support hold its intended position without slipping under the proposed playing conditions?", "kind": "measurement", "id": "secure-playing-position-q01" }, { "text": "What support or positioning adjustment is needed before this cello can be used for the stated task?", "kind": "action", "id": "secure-playing-position-q02" } ] } ] }, { "id": "care-history-and-use-restrictions", "name": "Care history and use restrictions", "description": "Connects repairs, environmental exposure and current symptoms to care and use decisions.", "findings": [ { "id": "condition-based-care-plan", "name": "Condition-based care plan", "description": "Record relevant repair history, recent exposure, finish-sensitive care instructions and explicit limits on playing, tuning or handling.", "questions": [ { "text": "Which repair records, maker instructions or recent temperature and humidity exposures affect the care decision for this cello?", "kind": "provenance", "id": "condition-based-care-plan-q01" }, { "text": "Which playing, cleaning, string-changing, storage or transport actions are appropriate now, and which require specialist guidance?", "kind": "action", "id": "condition-based-care-plan-q02" } ] } ] } ] } ] }, "openQuestions": [ "What registry boundary should apply to historical, extended-range and hybrid instruments described as cellos when their tuning or construction differs substantially?", "Which measurement conventions and acceptable setup ranges should be adopted for different cello sizes, string types and playing requirements?", "Which observable structural symptoms justify immediate suspension of playing or tuning, and which require specialist assessment before assigning urgency?", "What repeatable assessment protocol can separate cello response problems from player, bow, room and amplification effects?", "Which maker- or repairer-supported environmental and care limits apply to different materials, finishes, repairs and electric cello constructions?" ], "statistics": { "bundles": 5, "layers": 10, "findings": 10, "questions": 20 } }, "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 cello, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a cello, assess its playing readiness and preservation needs, and decide which playing, handling, setup or maintenance actions are appropriate.", "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: violoncello piccolo.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 105 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 cello, 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": [ "violoncello piccolo" ] } ], "standing": "Described in 105 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 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 cello from another, and a cello 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 cello, 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 cello, 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 cello 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 cello, 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 cello, 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 cello 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 cello 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 cello, 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 cello, 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 cello 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 cello from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a cello, 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 cello, 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 cello 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 cello 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 cello, 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 cello, 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 cello 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 cello is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a cello, 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 cello, 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 cello 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 cello is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a cello, 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 cello, 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 cello 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 cello 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 cello is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a cello, 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 cello, 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 cello 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 cello 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 cello, 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 cello, 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 cello 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 cello 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 cello between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a cello, 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 cello, 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 cello 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 cello, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a cello 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 cello, 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 cello, 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 cello 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 cello 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 cello 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 cello, 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 cello 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 cello 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 cello 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 cello 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 cello 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 cello, 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 cello 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 cello and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a cello, 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 cello, 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 cello 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 cello is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a cello, 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 cello, 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 cello 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 } } } }