{ "model": { "rank": 5783, "code": "thing-q201898", "model_id": "vr.tr.tuning-fork", "name": "tuning fork", "purpose": "Enable an AI agent to recognise a tuning fork, assess whether its mechanical and acoustic state supports an intended use, and determine appropriate excitation, coupling, checking and care 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/q201898/", "tier": 2, "score": 65, "payload": { "layer": "wikidata", "aliases": [ "Sonorous forks" ], "aliasCount": 1, "merged": 1, "knownIn": 65, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.tuning-fork", "source": { "dataset": "wikidata", "item": "Q201898", "url": "https://www.wikidata.org/wiki/Q201898", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T09:17:42Z", "providers": [ "Codex" ], "missingProviders": [ "Grok" ], "pass": 2, "cost": { "grok": { "usd": null, "turns": null, "seconds": 14.2, "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": 76.7, "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: 01a07b27-93b8-7c73-b53e-4ad998e0a649\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: tuning fork\nRegistry id: vr.tr.tuning-fork\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA" } } }, "metaModel": { "id": "THING-Q201898", "registryId": "vr.tr.tuning-fork", "name": "tuning fork", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q201898/", "model": { "registry_id": "vr.tr.tuning-fork", "name": "tuning fork", "purpose": "Enable an AI agent to recognise a tuning fork, assess whether its mechanical and acoustic state supports an intended use, and determine appropriate excitation, coupling, checking and care actions.", "definition": "", "scope_statement": "This model owns the physical tuning fork as a mechanically excited resonator, including its paired tines, joined base, stem, fitted weights, frequency behaviour, condition and interfaces to users or resonating supports.", "in_scope": [ "Identification through paired-tine construction and observed vibration", "Nominal frequency, measured response and conditions of measurement", "Tine geometry, material, fitted weights and physical condition", "Excitation, holding, damping and coupling through the stem", "Suitability and restrictions for a declared musical, laboratory or clinical use" ], "out_of_scope": [ "The instrument being tuned and its tuning procedure", "Clinical examination protocols, patient findings and diagnoses", "Standalone resonator boxes, microphones and measuring instruments", "Electronic tone generators and software pitch references", "Quartz resonators incorporated into electronic circuits", "Claims about therapeutic effects of tuning-fork use" ], "distinguishing_features": [ "Inspect for two free tines joined at a common base, usually with a stem; distinguish this construction from a single vibrating rod, reed or struck bar.", "Under suitable excitation, look for the paired bending response associated with the fork's intended mode; verify rather than assuming that any two-pronged object is a tuning fork.", "Check whether free vibration provides a repeatable frequency reference or vibration stimulus without continued powered excitation.", "Distinguish nominal pitch markings and tuning-related construction from utensils or tools whose prongs are designed primarily to grip, pierce or strike." ], "characteristics": [ { "name": "Nominal frequency", "kind": "measurement", "unit_or_values": "Hz; marked, documented or unknown", "why_it_matters": "Identifies the intended reference frequency without treating a label as a measurement." }, { "name": "Measured operating frequency", "kind": "measurement", "unit_or_values": "Hz, with uncertainty and measurement conditions", "why_it_matters": "Supports comparison with the nominal frequency and the tolerance required by the intended task." }, { "name": "Tine geometry", "kind": "measurement", "unit_or_values": "Tine length, width, thickness and separation in mm", "why_it_matters": "Helps identify the fork and detect bending, asymmetry or changes that may affect response." }, { "name": "Body material", "kind": "category", "unit_or_values": "Documented material or alloy; unknown if unverified", "why_it_matters": "Informs interpretation of corrosion, temperature sensitivity and permitted cleaning methods." }, { "name": "Weight configuration", "kind": "category", "unit_or_values": "Unweighted, fixed weights, adjustable weights or undetermined", "why_it_matters": "Distinguishes configurations whose vibration behaviour and adjustment requirements may differ." }, { "name": "Decay duration", "kind": "measurement", "unit_or_values": "s, between defined amplitude thresholds under a stated setup", "why_it_matters": "Indicates whether usable vibration persists long enough for the intended task." }, { "name": "Mechanical condition", "kind": "state", "unit_or_values": "Observed cracks, bending, corrosion, surface damage and attachment security; inspected or uninspected", "why_it_matters": "Determines whether excitation or contact is appropriate and whether frequency checks are warranted." }, { "name": "Support and contact configuration", "kind": "relation", "unit_or_values": "Held stem, mounted stem, coupled stem, free tines or unintended tine contact", "why_it_matters": "Makes the physical setup explicit when interpreting loudness, decay and measured response." }, { "name": "Declared application", "kind": "category", "unit_or_values": "Musical reference, laboratory demonstration, clinical stimulus, other documented use or unknown", "why_it_matters": "Selects the relevant performance requirements and handling instructions." } ], "affordances": [ "Excite the fork using a method suitable for its construction and intended use.", "Hold or mount the stem while allowing the tines to vibrate freely.", "Couple the stem to an appropriate resonating support or permitted contact surface.", "Measure frequency and decay, then compare them with documented requirements.", "Inspect and clean the fork using material-compatible methods.", "Adjust designated movable weights when supported by the design, followed by verification." ] }, "sources": [], "structure": { "bundles": [ { "id": "fork-identity-and-construction", "name": "Fork identity and construction", "description": "Establishes what the object is and which tuning-fork configuration it embodies.", "rationale": "A fork-like outline alone does not establish a usable tuning fork or its intended response.", "layers": [ { "id": "paired-tine-body", "name": "Paired-tine body", "description": "Records the construction that supports the intended mechanical resonance.", "findings": [ { "id": "tines-base-and-stem", "name": "Tines, base and stem", "description": "Establish the relationship between the free tines, their common base and the holding or coupling interface.", "questions": [ { "text": "Does the object have two free tines joined through a common base, and where is it intended to be held?", "kind": "definition", "id": "tines-base-and-stem-q01" }, { "text": "What evidence distinguishes this object from a two-pronged tool or a component of another resonator?", "kind": "boundary", "id": "tines-base-and-stem-q02" } ] } ] }, { "id": "fork-variant", "name": "Fork variant", "description": "Identifies markings, weights and design-specific features.", "findings": [ { "id": "marked-and-fitted-configuration", "name": "Marked and fitted configuration", "description": "Separate observed configuration from manufacturer claims and inferred application.", "questions": [ { "text": "What maker, model, frequency, note or application markings are present, and which documentation explains them?", "kind": "provenance", "id": "marked-and-fitted-configuration-q01" }, { "text": "Are tine weights absent, fixed or adjustable, and is their current arrangement documented?", "kind": "definition", "id": "marked-and-fitted-configuration-q02" } ] } ] } ] }, { "id": "frequency-reference", "name": "Frequency reference", "description": "Connects the fork's declared frequency to its measured behaviour.", "rationale": "An agent must distinguish an intended frequency from evidence that the fork currently supplies it.", "layers": [ { "id": "declared-reference", "name": "Declared reference", "description": "Records the meaning and conditions of the stated pitch or frequency.", "findings": [ { "id": "nominal-frequency-basis", "name": "Nominal frequency basis", "description": "Identify the declared reference and any conditions attached to it.", "questions": [ { "text": "What nominal frequency is specified, and does any note marking identify a tuning convention?", "kind": "definition", "id": "nominal-frequency-basis-q01" }, { "text": "What source specifies reference temperature, tolerance or calibration conditions for this fork?", "kind": "provenance", "id": "nominal-frequency-basis-q02" } ] } ] }, { "id": "verified-response", "name": "Verified response", "description": "Records a frequency check with enough context to interpret it.", "findings": [ { "id": "measured-frequency-and-deviation", "name": "Measured frequency and deviation", "description": "Assess the intended resonance without confusing it with an attack transient or another mode.", "questions": [ { "text": "What frequency is measured after the initial attack, with what uncertainty, temperature and holding configuration?", "kind": "measurement", "id": "measured-frequency-and-deviation-q01" }, { "text": "How was the intended mode identified, and does its deviation meet the requirement of the declared task?", "kind": "measurement", "id": "measured-frequency-and-deviation-q02" } ] } ] } ] }, { "id": "excitation-and-vibration", "name": "Excitation and vibration", "description": "Describes how usable vibration is started, sustained and stopped.", "rationale": "The excitation method and unintended damping can make the same fork behave differently during use.", "layers": [ { "id": "starting-vibration", "name": "Starting vibration", "description": "Establishes suitable excitation points, tools and intensity.", "findings": [ { "id": "permitted-excitation", "name": "Permitted excitation", "description": "Identify a repeatable excitation method compatible with the particular fork.", "questions": [ { "text": "Which striking surface, striker or other excitation method is specified for this fork?", "kind": "action", "id": "permitted-excitation-q01" }, { "text": "Where and how may it be excited without tine collision, attachment displacement or surface damage?", "kind": "action", "id": "permitted-excitation-q02" } ] } ] }, { "id": "vibration-persistence", "name": "Vibration persistence", "description": "Assesses the usable part of the response and sources of premature damping.", "findings": [ { "id": "decay-and-unwanted-response", "name": "Decay and unwanted response", "description": "Record persistence, rattling, beating or other response features requiring interpretation.", "questions": [ { "text": "How long does vibration remain above a defined usable threshold under a repeatable excitation and support setup?", "kind": "measurement", "id": "decay-and-unwanted-response-q01" }, { "text": "Do unusual response features persist when unintended tine contact and external rattling are removed?", "kind": "measurement", "id": "decay-and-unwanted-response-q02" } ] } ] } ] }, { "id": "holding-and-coupling", "name": "Holding and coupling", "description": "Defines how the fork interfaces with a holder, resonator or intended recipient of vibration.", "rationale": "A tuning fork's usefulness depends on how its vibration is supported and transferred.", "layers": [ { "id": "stem-support", "name": "Stem support", "description": "Records holding and mounting arrangements that leave the intended vibrating regions free.", "findings": [ { "id": "grip-and-clearance", "name": "Grip and clearance", "description": "Identify the permitted grip or mount and the clearance needed around both tines.", "questions": [ { "text": "Which part of the stem is intended for gripping or mounting, and what restrictions are documented?", "kind": "action", "id": "grip-and-clearance-q01" }, { "text": "Are both tines clear of fingers, fixtures and neighbouring surfaces throughout their motion?", "kind": "boundary", "id": "grip-and-clearance-q02" } ] } ] }, { "id": "vibration-transfer", "name": "Vibration transfer", "description": "Records the interface through which the fork's output is made useful.", "findings": [ { "id": "stem-contact-interface", "name": "Stem contact interface", "description": "Distinguish airborne output from vibration transmitted through stem contact.", "questions": [ { "text": "Does the intended task use airborne sound, stem-transmitted vibration or both?", "kind": "definition", "id": "stem-contact-interface-q01" }, { "text": "What receiving surface, contact orientation and applied force are specified for this use?", "kind": "action", "id": "stem-contact-interface-q02" } ] } ] } ] }, { "id": "condition-and-use-readiness", "name": "Condition and use readiness", "description": "Connects physical integrity and maintenance history to permitted use.", "rationale": "Damage or modification can undermine the fork's reference behaviour even when it still produces sound.", "layers": [ { "id": "resonator-integrity", "name": "Resonator integrity", "description": "Inspects the vibrating body and any fitted masses for consequential defects.", "findings": [ { "id": "tine-and-weight-condition", "name": "Tine and weight condition", "description": "Record deformation, cracking, corrosion and loose or displaced weights.", "questions": [ { "text": "What defects or asymmetries are visible on the tines, their roots, the common base and the stem?", "kind": "measurement", "id": "tine-and-weight-condition-q01" }, { "text": "Are fitted weights secure and in their documented positions, and has the fork suffered an impact or alteration?", "kind": "provenance", "id": "tine-and-weight-condition-q02" } ] } ] }, { "id": "maintenance-and-release", "name": "Maintenance and release", "description": "Determines appropriate care and the evidence needed before further use.", "findings": [ { "id": "care-and-reverification", "name": "Care and reverification", "description": "Tie cleaning, adjustment and return to use to the fork's material, design and application.", "questions": [ { "text": "Which cleaning methods and storage arrangements are compatible with the body, markings and fitted weights?", "kind": "action", "id": "care-and-reverification-q01" }, { "text": "After damage, repair or weight adjustment, what inspection and frequency verification are required before the intended use?", "kind": "action", "id": "care-and-reverification-q02" } ] } ] } ] } ] }, "openQuestions": [ "Does the registry intend this entry to include electrically sustained metal tuning forks or only mechanically excited standalone forks?", "Which authoritative sources establish frequency tolerances and temperature conditions for the fork variants covered?", "Which excitation and decay measurement procedures allow meaningful comparisons across weighted and unweighted forks?", "Which clinical-use requirements belong in this object's readiness record, and which should be supplied exclusively by linked examination and hygiene models?", "Which designs permit adjustment or repair, and what evidence establishes acceptable performance afterward?" ], "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 tuning fork, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a tuning fork, assess whether its mechanical and acoustic state supports an intended use, and determine appropriate excitation, coupling, checking and care 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: Sonorous forks.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 65 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 tuning fork, 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": [ "Sonorous forks" ] } ], "standing": "Described in 65 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 tuning fork from another, and a tuning fork 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 tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a tuning fork 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 tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork 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 tuning fork, 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 tuning fork 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 tuning fork 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 tuning fork 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 tuning fork 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 tuning fork 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 tuning fork, 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 tuning fork 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 tuning fork and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a tuning fork, 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 tuning fork, 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 tuning fork 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 tuning fork is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a tuning fork, 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 tuning fork, 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 tuning fork 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 } } } }