{ "model": { "rank": 5322, "code": "thing-q156424", "model_id": "vr.tr.metronome", "name": "metronome", "purpose": "Enable an agent to recognise a metronome, assess whether it provides a usable timing reference, and select appropriate settings and maintenance actions.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q156424/", "tier": 2, "score": 68, "payload": { "layer": "wikidata", "aliases": [ "electric metronome", "Metronome of Maelzel", "traditional metronome" ], "aliasCount": 3, "merged": 3, "knownIn": 68, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q156424", "url": "https://www.wikidata.org/wiki/Q156424", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-09T22:07:57Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 16.9, "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: 01a08835-b0ba-7cd2-8024-9d6f87dee0b4\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: metronome\nSense to describe: (none recorded)\nDomain code: PHY.OBJ\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 005: 1001 regis", "usd": 0, "recall": true }, "codex": { "seconds": 62.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: 01a08835-b0c7-7560-816c-834fb6eb97e9\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: metronome\nRegistry id: vr.tr.metronome\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nCont" } } }, "metaModel": { "id": "THING-Q156424", "registryId": "vr.tr.metronome", "name": "metronome", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q156424/", "model": { "registry_id": "vr.tr.metronome", "name": "metronome", "purpose": "Enable an agent to recognise a metronome, assess whether it provides a usable timing reference, and select appropriate settings and maintenance actions.", "definition": "A metronome is a timing device that produces regularly recurring audible, visible or tactile signals at an adjustable rate to provide a reference for musical tempo and rhythmic practice.", "scope_statement": "This model owns the metronome as a kind of physical device that produces recurring perceptible timing cues at a selected tempo, including mechanical and electronic implementations and their operating condition.", "in_scope": [ "Adjustable tempo generation and the relationship between settings and emitted cues", "Mechanical and electronic timing mechanisms, power sources and controls", "Audible, visible and tactile beat cues where provided", "Beat grouping, accents and subdivisions where supported", "Timing performance, operating readiness and maintenance needs" ], "out_of_scope": [ "Musical tempo, meter and rhythm as abstract concepts", "Practice routines, teaching methods and assessments of a musician's performance", "Standalone metronome software and the general-purpose devices hosting it", "Clocks, stopwatches and timers whose primary function is measuring elapsed or civil time", "Product-line catalogues and individual device ownership or service histories" ], "distinguishing_features": [ "Provides recurring cues intended to guide the timing of an external activity, rather than primarily displaying elapsed time.", "Allows a user to select the reference tempo; the available settings and adjustment method depend on the implementation.", "Can continue producing a timing reference without requiring a fresh human input for every beat, unlike a tap-tempo input alone.", "Treats beat timing as its central function; producing musical patterns or accompaniment is not required.", "For this PHY entry, includes a physical timing-and-cue device; software-only implementations require an explicit boundary decision." ], "characteristics": [ { "name": "Timing mechanism", "kind": "category", "unit_or_values": "mechanical oscillator; electronic timing circuit; other documented mechanism", "why_it_matters": "Determines how tempo is generated and which operating conditions or faults may affect it." }, { "name": "Selectable tempo range", "kind": "measurement", "unit_or_values": "minimum and maximum beats per minute (BPM), with the meaning of one beat recorded", "why_it_matters": "Establishes whether the device can support the required reference rate." }, { "name": "Tempo adjustment", "kind": "category", "unit_or_values": "continuous or discrete; control method; selectable BPM values or step size", "why_it_matters": "Shows whether a requested tempo can be selected and reproduced." }, { "name": "Measured reference tempo", "kind": "measurement", "unit_or_values": "BPM, with observation duration, operating conditions and measurement uncertainty", "why_it_matters": "Allows comparison between the selected tempo and the timing actually delivered." }, { "name": "Interval variability", "kind": "measurement", "unit_or_values": "milliseconds or percent variation between equivalent reference-beat intervals, with method stated", "why_it_matters": "Distinguishes a stable tempo offset from irregular beat timing." }, { "name": "Cue modalities", "kind": "category", "unit_or_values": "audible; visible; tactile; supported combinations", "why_it_matters": "Determines whether the timing reference is perceptible in the intended setting." }, { "name": "Beat grouping and subdivisions", "kind": "category", "unit_or_values": "supported beats per group, accent positions and subdivision patterns; absent if unsupported", "why_it_matters": "Prevents extra clicks or accents from being mistaken for a change in reference tempo." }, { "name": "Power source", "kind": "category", "unit_or_values": "wound spring; replaceable battery; rechargeable battery; external electrical supply; other documented source", "why_it_matters": "Determines preparation, replenishment and interruption risks." }, { "name": "Operating state", "kind": "state", "unit_or_values": "stopped; running; depleted; obstructed; faulted; unknown", "why_it_matters": "Supports a decision to start, replenish, inspect or stop using the device." }, { "name": "Placement requirements", "kind": "relation", "unit_or_values": "documented relationship to support surface, orientation, clearance or body attachment", "why_it_matters": "Identifies whether the current setup permits reliable operation and cue perception." } ], "affordances": [ "Select a supported tempo and verify the resulting reference-beat rate.", "Start and stop the timing reference using the controls appropriate to the mechanism.", "Choose supported accents, subdivisions and cue modalities for the intended activity.", "Position or attach the device so its mechanism operates freely and its cues remain perceptible.", "Wind, recharge or replace the power source according to the device instructions.", "Compare timing against an independent reference and flag inconsistent operation for inspection." ] }, "sources": [], "structure": { "bundles": [ { "id": "metronome-identity", "name": "Metronome identity", "description": "Establishes the device's timing-reference function and the boundary of this physical-device model.", "rationale": "A metronome may resemble a clock, rhythm generator or software feature while requiring a different assessment of useful operation.", "layers": [ { "id": "reference-function", "name": "Reference function", "description": "Identifies what the recurring cues are intended to regulate.", "findings": [ { "id": "selectable-recurring-reference", "name": "Selectable recurring reference", "description": "Record whether the device independently emits recurring cues at a selectable tempo to guide another activity.", "questions": [ { "text": "Which behaviour establishes that this device supplies a tempo reference?", "kind": "definition", "id": "selectable-recurring-reference-q01" }, { "text": "Does it sustain cues after tempo selection, or merely measure or display timing supplied by a user?", "kind": "boundary", "id": "selectable-recurring-reference-q02" } ] } ] }, { "id": "implementation-boundary", "name": "Implementation boundary", "description": "Separates the physical metronome kind from software and multifunction equipment.", "findings": [ { "id": "physical-function-ownership", "name": "Physical function ownership", "description": "Record whether the metronome is a dedicated device or a function of equipment whose other capabilities belong elsewhere.", "questions": [ { "text": "Is the timing reference implemented by a dedicated physical device, an embedded function or standalone software?", "kind": "boundary", "id": "physical-function-ownership-q01" }, { "text": "For a combined tuner or rhythm device, which controls and outputs belong specifically to its metronome function?", "kind": "boundary", "id": "physical-function-ownership-q02" } ] } ] } ] }, { "id": "tempo-and-timing-fidelity", "name": "Tempo and timing fidelity", "description": "Connects selected tempo to the rate and regularity of the reference beats actually delivered.", "rationale": "A plausible setting or display is insufficient evidence that a metronome supplies the required timing reference.", "layers": [ { "id": "tempo-selection", "name": "Tempo selection", "description": "Captures tempo limits, adjustment resolution and the interpretation of the selected rate.", "findings": [ { "id": "setting-to-beat-mapping", "name": "Setting-to-beat mapping", "description": "Record the supported tempo settings and which emitted events count as reference beats.", "questions": [ { "text": "What minimum, maximum and intermediate BPM settings can actually be selected?", "kind": "measurement", "id": "setting-to-beat-mapping-q01" }, { "text": "With the current subdivision or accent mode, which cues correspond to the BPM setting?", "kind": "definition", "id": "setting-to-beat-mapping-q02" } ] } ] }, { "id": "delivered-timing", "name": "Delivered timing", "description": "Assesses actual tempo, interval consistency and changes during operation.", "findings": [ { "id": "rate-and-regularity-check", "name": "Rate and regularity check", "description": "Record measured beat intervals under stated conditions, distinguishing average tempo error, alternating intervals and longer-term drift.", "questions": [ { "text": "How does measured reference tempo differ from the selected BPM over a stated observation period?", "kind": "measurement", "id": "rate-and-regularity-check-q01" }, { "text": "Do equivalent beat intervals vary, alternate or drift as the device continues running?", "kind": "measurement", "id": "rate-and-regularity-check-q02" }, { "text": "What documented tolerance or task requirement determines whether the observed timing is acceptable?", "kind": "provenance", "id": "rate-and-regularity-check-q03" } ] } ] } ] }, { "id": "beat-cues-and-patterns", "name": "Beat cues and patterns", "description": "Describes how reference timing becomes perceptible and how additional cues express grouping.", "rationale": "Correct internal timing is useful only when the user can perceive and interpret the intended beat.", "layers": [ { "id": "cue-perception", "name": "Cue perception", "description": "Examines available sound, light, motion or vibration cues in their intended setting.", "findings": [ { "id": "usable-cue-output", "name": "Usable cue output", "description": "Record supported cue modalities, adjustable output and whether simultaneous outputs communicate the same beat coherently.", "questions": [ { "text": "Which audible, visible or tactile outputs mark the beat, and which can be adjusted or disabled?", "kind": "definition", "id": "usable-cue-output-q01" }, { "text": "Can the intended user perceive the chosen cue at the expected noise level, viewing position or attachment location?", "kind": "measurement", "id": "usable-cue-output-q02" }, { "text": "If multiple cue modalities run together, what offset between their corresponding beat events is observable?", "kind": "measurement", "id": "usable-cue-output-q03" } ] } ] }, { "id": "accent-and-subdivision-logic", "name": "Accent and subdivision logic", "description": "Separates the reference pulse from downbeat emphasis and additional within-beat cues.", "findings": [ { "id": "pattern-interpretation", "name": "Pattern interpretation", "description": "Record supported grouping and subdivision behaviour without assuming that every metronome provides programmable patterns.", "questions": [ { "text": "Which beat-group lengths, accent positions and subdivisions are supported, if any?", "kind": "definition", "id": "pattern-interpretation-q01" }, { "text": "How can an agent distinguish a group-start accent from an ordinary beat and a subdivision cue?", "kind": "measurement", "id": "pattern-interpretation-q02" } ] } ] } ] }, { "id": "mechanism-and-operation", "name": "Mechanism and operation", "description": "Relates the timing mechanism to power, controls and the physical conditions needed for operation.", "rationale": "Winding and positioning a mechanical metronome require different actions from powering and configuring an electronic one.", "layers": [ { "id": "timing-drive", "name": "Timing drive", "description": "Identifies the timing mechanism and how energy sustains its operation.", "findings": [ { "id": "mechanism-power-dependency", "name": "Mechanism and power dependency", "description": "Record the documented timing mechanism, its energy source and the observable signs of depleted or interrupted power.", "questions": [ { "text": "What mechanism establishes the beat interval, and what source supplies its operating energy?", "kind": "definition", "id": "mechanism-power-dependency-q01" }, { "text": "Which indicators or behaviours reveal insufficient spring winding, low battery charge or loss of external supply?", "kind": "measurement", "id": "mechanism-power-dependency-q02" }, { "text": "What replenishment procedure and power-source specifications do the device instructions require?", "kind": "action", "id": "mechanism-power-dependency-q03" } ] } ] }, { "id": "setup-and-state-transitions", "name": "Setup and state transitions", "description": "Captures placement and control actions needed to move between stopped and usable running states.", "findings": [ { "id": "safe-start-and-stop", "name": "Supported start and stop", "description": "Record mechanism-specific setup, movement clearance, start and stop controls, and any fitted transport restraint or protective feature.", "questions": [ { "text": "What orientation, support, movement clearance or attachment does this implementation require?", "kind": "action", "id": "safe-start-and-stop-q01" }, { "text": "How should the device be started, stopped and secured for transport, including any pendulum restraint where fitted?", "kind": "action", "id": "safe-start-and-stop-q02" } ] } ] } ] }, { "id": "readiness-and-care", "name": "Readiness and care", "description": "Supports decisions about continued use, troubleshooting and maintenance based on metronome-specific symptoms and documented requirements.", "rationale": "Missing cues, unstable tempo and mechanical interference can invalidate the reference even when the device appears to run.", "layers": [ { "id": "fault-recognition", "name": "Fault recognition", "description": "Distinguishes timing faults from output, configuration and setup problems.", "findings": [ { "id": "symptom-to-check", "name": "Symptom to check", "description": "Record missed or duplicate cues, uneven intervals, unexpected stopping and loss of cue perception together with the checks needed to investigate them.", "questions": [ { "text": "Is an apparently missing beat caused by timing failure, an output setting, an accent pattern or an imperceptible cue?", "kind": "measurement", "id": "symptom-to-check-q01" }, { "text": "Which documented checks of power, placement, obstruction and settings are appropriate before servicing the device?", "kind": "action", "id": "symptom-to-check-q02" } ] } ] }, { "id": "maintenance-and-requirements", "name": "Maintenance and requirements", "description": "Connects care and suitability decisions to instructions and evidence applicable to the implementation.", "findings": [ { "id": "documented-care-and-conformity", "name": "Documented care and conformity", "description": "Record permitted cleaning, power-source replacement, service restrictions and applicable conformity evidence without assuming a universal metronome certification.", "questions": [ { "text": "Which maintenance actions are permitted for the user, and which require qualified service according to the instructions?", "kind": "action", "id": "documented-care-and-conformity-q01" }, { "text": "Which standards, issuing bodies or certification marks are documented for this implementation and intended market, and what do they cover?", "kind": "provenance", "id": "documented-care-and-conformity-q02" }, { "text": "What timing and cue checks should confirm usable operation after maintenance or a significant impact?", "kind": "action", "id": "documented-care-and-conformity-q03" } ] } ] } ] }, { "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 device kind, including software implementations, rather than a particular product or physical unit.", "The stated tempo range is common for traditional mechanical models, not a universal specification; electronic and software ranges vary.", "Beats per minute requires an assigned musical note value to determine musical tempo unambiguously; no metronome-specific standard or identifier is confidently recalled." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of metronome 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": [ "Wind-up mechanical metronome", "Electronic audible metronome", "Visual metronome", "Tactile or vibrating metronome", "Software metronome" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of metronome 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": [ "Maintaining a target tempo during instrumental or vocal practice.", "Practising rhythmic subdivisions, accents and changes of tempo.", "Providing a shared timing reference during rehearsal.", "Generating a click reference for music recording." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of metronome 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": "Adjustable pulse rate on many traditional mechanical models", "typical_range": "40-208", "unit": "beats per minute" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of metronome 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": [ "An unlevel support can cause uneven tick intervals in a mechanical metronome.", "Wear, contamination or damage in a mechanical escapement can impair timing or stop operation.", "A depleted battery or interrupted electrical supply can stop an electronic metronome.", "Software scheduling or audio buffering can introduce timing jitter; uncompensated output latency can misalign clicks with other signals.", "Excessive click volume through headphones can contribute to hearing damage." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of metronome 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": "Clock", "difference": "A clock indicates time; a metronome primarily supplies recurring signals at a selected tempo." }, { "name": "Timer", "difference": "A timer measures or signals a specified duration; a metronome supplies a continuing sequence of tempo pulses." }, { "name": "Drum machine", "difference": "A drum machine generates percussion patterns; a metronome primarily provides a timing reference, although their functions can overlap." }, { "name": "Click track", "difference": "A click track is a recorded or sequenced timing reference; a metronome is the device or software function generating recurring timing signals." }, { "name": "Tuner", "difference": "A tuner measures or supplies a pitch reference; a metronome supplies a tempo reference, though one product may contain both." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of metronome this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does an existing Vercy world model already own the metronome concept, and how should this registry entry link to it if so?", "Should embedded metronome functions in tuners, instruments and wearable devices be applications of this physical-device model or relations to a separate functional model?", "What tempo ranges, adjustment increments, dimensions and operating durations are supported by representative mechanical and electronic devices?", "What timing-error and interval-variability tolerances are documented by manufacturers or justified for particular uses, and how should they be measured?", "Which standards and certification requirements apply by mechanism, power source and market, and does any specifically assess metronome timing performance?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 16, "questions": 30 } }, "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 metronome, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a metronome, assess whether it provides a usable timing reference, and select appropriate settings and maintenance actions.", "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: electric metronome, Metronome of Maelzel, traditional metronome.", "3 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 68 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 metronome, 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": [ "electric metronome", "Metronome of Maelzel", "traditional metronome" ] } ], "standing": "Described in 68 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 3 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 metronome from another, and a metronome 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 metronome, 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 metronome, 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 metronome 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 metronome, 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 metronome, 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 metronome 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 metronome 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 metronome, 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 metronome, 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 metronome 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 metronome from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a metronome, 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 metronome, 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 metronome 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 metronome 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 metronome, 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 metronome, 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 metronome 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 metronome is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a metronome, 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 metronome, 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 metronome 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 metronome is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a metronome, 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 metronome, 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 metronome 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 metronome 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 metronome is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a metronome, 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 metronome, 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 metronome 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 metronome 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 metronome, 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 metronome, 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 metronome 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 metronome 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 metronome between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a metronome, 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 metronome, 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 metronome 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 metronome, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a metronome 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 metronome, 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 metronome, 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 metronome 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 metronome 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 metronome 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 metronome, 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 metronome 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 metronome 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 metronome 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 metronome 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 metronome 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 metronome, 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 metronome 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 metronome and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a metronome, 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 metronome, 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 metronome 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 metronome is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a metronome, 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 metronome, 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 metronome 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 } } } }