{ "model": { "rank": 5911, "code": "thing-q229205", "model_id": "vr.tr.sitar", "name": "sitar", "purpose": "Enable an agent to recognise a sitar, assess its configuration and playing condition, and decide which tuning, performance, maintenance or conservation 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/q229205/", "tier": 2, "score": 64, "payload": { "layer": "wikidata", "aliases": [ "kachva sitar" ], "aliasCount": 1, "merged": 1, "knownIn": 64, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.sitar", "source": { "dataset": "wikidata", "item": "Q229205", "url": "https://www.wikidata.org/wiki/Q229205", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T10:03:11Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00506532, "turns": 1, "seconds": 76, "error": null }, "codex": { "seconds": 94.3, "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: 01a07b4f-5ed7-7dd1-bf44-e42cd2190bf3\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: sitar\nRegistry id: vr.tr.sitar\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model" } } }, "metaModel": { "id": "THING-Q229205", "registryId": "vr.tr.sitar", "name": "sitar", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q229205/", "model": { "registry_id": "vr.tr.sitar", "name": "sitar", "purpose": "Enable an agent to recognise a sitar, assess its configuration and playing condition, and decide which tuning, performance, maintenance or conservation actions are appropriate.", "definition": "A sitar is a long-necked, gourd-bodied plucked lute of Hindustani (North Indian) classical music, typically with a gourd resonator, a flat wooden soundboard, a hollow neck carrying movable curved metal frets, a set of playing (melody) strings plus drone strings, and a bank of sympathetic strings that resonate with the played notes.", "scope_statement": "This model owns the physical instrument registered as vr.tr.sitar in PHY / PHY.OBJ, including its identifying construction, installed string and fret configuration, acoustic response, condition and intervention constraints; historical and modified examples require evidence rather than conformity to one modern specification.", "in_scope": [ "Evidence identifying the instrument as a sitar and supporting any maker, period or style attribution", "Neck, resonators, bridges, movable frets, pegs and installed string paths", "Playing, drone and sympathetic string roles, where present", "Current tuning, fret placement and compatibility with an intended playing setup", "Jawari response, sympathetic resonance, intonation and string-pulling behaviour", "Structural condition and limits on playing, adjustment, repair and handling" ], "out_of_scope": [ "Raga definitions, compositions and performance traditions as independent musical knowledge", "The player's biography, proficiency and training programme", "Makers, workshops and ownership organisations as independent entities", "Cases, microphones, amplifiers and recording systems as separately managed equipment", "Persian setar, surbahar, tanpura and other neighbouring instrument types as independent models", "Recordings and performances as creative works or events" ], "distinguishing_features": [ "Inspect the combination of a long neck, raised curved movable frets and plucked string layout; neither a sitar-like sound nor a seller's label alone establishes identity. These construction features are documented in the [National Music Museum sitar record](https://emuseum.nmmusd.org/objects/5827/sitar).", "Check whether the fret and string geometry supports sideways melody-string pulls while maintaining fret contact, rather than assuming that any fretted lute has the same playing interface.", "Trace separately the strings above the frets and any sympathetic strings below them; use their paths and roles as evidence rather than treating a particular total string count as decisive.", "For a possible tanpura or bowed sitar-like instrument, establish whether the instrument is configured for fretted melody playing by plucking, using its construction and documented use together.", "For a possible surbahar, Persian setar or guitar marketed as an electric sitar, compare documented instrument identity, scale, fret construction and string layout; escalate uncertain cases instead of classifying by name, size or buzzing timbre alone." ], "characteristics": [ { "name": "Identity attribution", "kind": "category", "unit_or_values": "confirmed sitar | probable sitar | disputed | unidentified; supporting evidence", "why_it_matters": "Controls whether sitar-specific assessments and interventions apply." }, { "name": "Construction and style attribution", "kind": "relation", "unit_or_values": "Links to documented maker, period, construction tradition or playing style, with confidence", "why_it_matters": "Explains variation without forcing every instrument into a single modern pattern." }, { "name": "Effective vibrating string length", "kind": "measurement", "unit_or_values": "mm, identified string and measured endpoints", "why_it_matters": "Informs evaluation of replacement strings, pitch targets and fret placement." }, { "name": "Installed string arrangement", "kind": "category", "unit_or_values": "Per-string role, route, material, diameter in mm if known, and installed or missing status", "why_it_matters": "Distinguishes intended configuration from incomplete stringing and prevents inappropriate substitutions." }, { "name": "Tuning reference and targets", "kind": "measurement", "unit_or_values": "Sa frequency in Hz; per-string target and observed frequency or interval", "why_it_matters": "Makes tuning assessable relative to the intended setup." }, { "name": "Fret configuration", "kind": "measurement", "unit_or_values": "Fret count and positions in mm from a declared reference, with intended pitch assignments", "why_it_matters": "Allows misplaced frets to be distinguished from deliberate musical configuration." }, { "name": "Jawari response", "kind": "state", "unit_or_values": "acceptable for declared target | uneven | changed | unassessed; observations by string", "why_it_matters": "Separates the intended bridge-related sound from unwanted response changes." }, { "name": "Sympathetic response", "kind": "state", "unit_or_values": "not fitted | responsive | weak | obstructed | unassessed, by string or target note", "why_it_matters": "Identifies tuning or clearance problems without treating absent sympathetic strings as automatically defective." }, { "name": "Melody-string pulling capability", "kind": "measurement", "unit_or_values": "Observed pitch excursion in cents at identified frets and tuning, within an approved test limit", "why_it_matters": "Tests suitability for intended meend passages without assuming a universal bending range." }, { "name": "Readiness for intended use", "kind": "state", "unit_or_values": "ready | adjustment required | specialist assessment required | conservation-only | unknown", "why_it_matters": "Connects structural and acoustic evidence to permitted next actions." } ], "affordances": [ "Identify and document the sitar's construction and configuration against supported reference examples.", "Specify and check a string, tuning and fret setup for a declared playing requirement.", "Evaluate intonation, jawari response and sympathetic resonance through controlled playing tests.", "Determine whether intended melody-string pulls and drone articulation are achievable in the current setup.", "Recommend bounded adjustments or refer bridge, fret and structural work to a suitable specialist.", "Select handling, support and transport arrangements that protect the resonator, neck, bridges and projecting pegs." ] }, "sources": [ { "id": "met-sitar", "title": "Sitar", "url": "https://www.metmuseum.org/art/collection/search/503156", "what_it_supports": "Museum description of the instrument as a long-necked lute with gourd resonator, movable frets, and sympathetic strings, used in Hindustani classical music.", "url_status": "blocked" }, { "id": "grove-sitar", "title": "Sitar", "url": "https://doi.org/10.1093/gmo/9781561592630.article.25891", "what_it_supports": "Standard musicological account of construction, kharaj-pancham vs gandhar-pancham schools, and relation to surbahar.", "url_status": "unverified" }, { "id": "wikidata-q191821", "title": "sitar (Q191821)", "url": "", "what_it_supports": "Stable identifier and classification as a plucked string instrument of the Indian subcontinent.", "url_status": "dead" }, { "id": "horniman-sitar", "title": "Sitar", "url": "https://www.horniman.ac.uk/object/24.11.56/3", "what_it_supports": "Physical specimen notes on gourd body, wooden neck, movable frets, and string counts typical of concert instruments.", "url_status": "live" } ], "structure": { "bundles": [ { "id": "identity-and-variant", "name": "Identity and variant", "description": "Establish what makes this particular instrument a sitar and which variations its evidence supports.", "rationale": "Names and familiar modern features cannot by themselves resolve historical, modified or neighbouring instruments.", "layers": [ { "id": "identification-evidence", "name": "Identification evidence", "description": "Combine observed construction with traceable documentary attribution.", "findings": [ { "id": "sitar-attribution", "name": "Sitar attribution", "description": "Record the evidence for identity and the strongest competing identification.", "questions": [ { "text": "Which observed neck, fret, bridge and string-path features support identification as a sitar?", "kind": "definition", "id": "sitar-attribution-q01" }, { "text": "Which maker record, collection record or specialist assessment supports that identification?", "kind": "provenance", "id": "sitar-attribution-q02" }, { "text": "What evidence distinguishes this example from its closest plausible neighbouring instrument?", "kind": "boundary", "id": "sitar-attribution-q03" } ] } ] }, { "id": "variant-and-alteration", "name": "Variant and alteration", "description": "Distinguish intentional construction differences from later changes or missing parts.", "findings": [ { "id": "configuration-history", "name": "Configuration history", "description": "Treat unusual features as questions of attribution and history before declaring them defects; the [Metropolitan Museum's compound instrument record](https://www.metmuseum.org/art/collection/search/501879) documents a sitar component without sympathetic strings.", "questions": [ { "text": "Which features are documented as original, replaced, added or removed?", "kind": "provenance", "id": "configuration-history-q01" }, { "text": "Does an unusual string arrangement represent an intentional variant, an incomplete instrument or an unresolved alteration?", "kind": "boundary", "id": "configuration-history-q02" } ] } ] } ] }, { "id": "string-and-fret-configuration", "name": "String and fret configuration", "description": "Describe the installed playing system and its relationship to the intended pitch setup.", "rationale": "String roles and movable fret positions determine what the instrument can play and which adjustments make sense.", "layers": [ { "id": "string-paths-and-roles", "name": "String paths and roles", "description": "Account for each string's function, attachment and clearance.", "findings": [ { "id": "installed-string-map", "name": "Installed string map", "description": "Record melody, supporting, drone or chikari, and sympathetic roles as observed rather than inferred from a fixed count.", "questions": [ { "text": "What role does each installed string serve, and which peg, bridge path and attachment does it use?", "kind": "definition", "id": "installed-string-map-q01" }, { "text": "Which strings are missing, substituted or contacting a fret, another string or an unintended surface?", "kind": "measurement", "id": "installed-string-map-q02" } ] } ] }, { "id": "pitch-and-fret-setup", "name": "Pitch and fret setup", "description": "Relate the tuning reference and fret positions to a declared musical requirement.", "findings": [ { "id": "setup-consistency", "name": "Setup consistency", "description": "Assess the actual setup against explicit targets instead of assuming one universal sitar tuning.", "questions": [ { "text": "What Sa reference and per-string pitch targets have been specified, and by whom?", "kind": "provenance", "id": "setup-consistency-q01" }, { "text": "How far do open-string and selected fretted pitches deviate from those targets under a stated playing technique?", "kind": "measurement", "id": "setup-consistency-q02" }, { "text": "Which discrepancies call for tuning, fret repositioning or specialist diagnosis?", "kind": "action", "id": "setup-consistency-q03" } ] } ] } ] }, { "id": "bridge-and-resonance", "name": "Bridge and resonance", "description": "Assess bridge-mediated tone and the response of any sympathetic string system.", "rationale": "The sitar's characteristic bridge response makes a simple buzzing-versus-clean judgement inadequate.", "layers": [ { "id": "jawari-response", "name": "Jawari response", "description": "Evaluate the sound produced at the string-to-bridge contact against an agreed tonal target.", "findings": [ { "id": "bridge-contact-and-tone", "name": "Bridge contact and tone", "description": "Separate desired jawari character from uneven response, rattling or deterioration, retaining recordings and test conditions where available.", "questions": [ { "text": "What tonal reference has the player or specialist accepted for this instrument's jawari?", "kind": "definition", "id": "bridge-contact-and-tone-q01" }, { "text": "On which strings and pitches does the observed response differ from that reference?", "kind": "measurement", "id": "bridge-contact-and-tone-q02" }, { "text": "Can the discrepancy be assessed through tuning and clearance checks, or does bridge work require a specialist?", "kind": "action", "id": "bridge-contact-and-tone-q03" } ] } ] }, { "id": "sympathetic-coupling", "name": "Sympathetic coupling", "description": "Determine whether fitted sympathetic strings respond as intended.", "findings": [ { "id": "sympathetic-string-response", "name": "Sympathetic string response", "description": "Compare resonance under controlled excitation and damping; sympathetic strings responding to played strings are described in the [Grinnell College instrument record](https://omeka-s.grinnell.edu/s/MusicalInstruments/item/631).", "questions": [ { "text": "Which sympathetic strings respond when their intended corresponding pitches are sounded?", "kind": "measurement", "id": "sympathetic-string-response-q01" }, { "text": "Does a weak response track mistuning, unintended contact, damping or an unresolved cause?", "kind": "boundary", "id": "sympathetic-string-response-q02" } ] } ] } ] }, { "id": "playing-interface-and-readiness", "name": "Playing interface and readiness", "description": "Assess whether the current setup supports the intended sitar techniques.", "rationale": "An instrument that produces open-string pitches may still be unsuitable for fretted melody, string pulls or chikari articulation.", "layers": [ { "id": "fretting-and-meend", "name": "Fretting and meend", "description": "Evaluate melody-string contact and sideways pulling under bounded playing conditions.", "findings": [ { "id": "usable-melody-response", "name": "Usable melody response", "description": "Record achievable pitch movement and interfering behaviour at selected frets without imposing a universal range.", "questions": [ { "text": "What pitch excursion is required at the selected frets for the intended playing task?", "kind": "definition", "id": "usable-melody-response-q01" }, { "text": "Within an approved test range, do pulls produce choking, slippage, fret movement or interference with adjacent strings?", "kind": "measurement", "id": "usable-melody-response-q02" } ] } ] }, { "id": "plucking-and-tuning-retention", "name": "Plucking and tuning retention", "description": "Check articulation and stability during representative playing.", "findings": [ { "id": "performance-readiness", "name": "Performance readiness", "description": "Connect access to the intended strings and tuning retention to a specific use decision.", "questions": [ { "text": "Can the intended player articulate melody and chikari strings with the chosen mizrab without unintended contact?", "kind": "measurement", "id": "performance-readiness-q01" }, { "text": "How much do checked pitches change after a documented period of representative playing?", "kind": "measurement", "id": "performance-readiness-q02" }, { "text": "Is the instrument ready for the intended session, or which adjustment must precede it?", "kind": "action", "id": "performance-readiness-q03" } ] } ] } ] }, { "id": "structural-condition-and-intervention", "name": "Structural condition and intervention", "description": "Assess the sitar's load-bearing assembly and constrain changes to its setup or fabric.", "rationale": "String tension, projecting fittings and resonator construction make structural evidence essential before tuning or playing.", "layers": [ { "id": "loaded-assembly", "name": "Loaded assembly", "description": "Inspect the neck, resonator, soundboard, joints, bridges and string attachments as a connected assembly.", "findings": [ { "id": "tension-bearing-condition", "name": "Tension-bearing condition", "description": "Record cracks, movement, deformation and insecure fittings with their locations and assessment history.", "questions": [ { "text": "Where are cracks, joint openings, deformation or movement visible around the neck, resonator, soundboard and string attachments?", "kind": "measurement", "id": "tension-bearing-condition-q01" }, { "text": "What evidence supports retaining or changing the current string tension?", "kind": "action", "id": "tension-bearing-condition-q02" } ] } ] }, { "id": "adjustment-and-care-limits", "name": "Adjustment and care limits", "description": "Separate documented setup changes from interventions requiring specialist or conservation judgement.", "findings": [ { "id": "permitted-interventions", "name": "Permitted interventions", "description": "Record instrument-specific limits on restringing, fret movement, jawari work and physical support.", "questions": [ { "text": "Which string replacements, tuning limits and fret adjustments are supported by this instrument's maker or specialist assessment?", "kind": "provenance", "id": "permitted-interventions-q01" }, { "text": "Which proposed changes would alter historic material, bridge geometry or an undocumented configuration?", "kind": "boundary", "id": "permitted-interventions-q02" }, { "text": "What handling and case-support arrangement avoids loading the bridges, projecting pegs and any secondary resonator?", "kind": "action", "id": "permitted-interventions-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-kinds", "name": "Kinds and varieties", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Kharaj-pancham (standard concert / Ravi Shankar-style sitar, with bass strings and a second resonator gourd on the pegbox)", "Gandhar-pancham (Vilayat Khan / Imdadkhani-style sitar, no bass strings, typically no second gourd, more vocal-like baj)", "Surbahar (bass sitar, larger body and longer scale, used for alap in the dhrupad-influenced style)", "Sitar-banjo / electric sitar (Western/studio instrument with a sitar-like buzzing bridge on a guitar or solid-body, not a Hindustani concert sitar)", "Student / beginner sitar (fewer sympathetic strings, simpler decoration, often without a second gourd)", "Seni / older court sitar (historical form with fewer strings and a less standardised sympathetic-string bank)", "Punjabi / folk sitar (regional, often simpler construction and repertoire outside the khyal concert tradition)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "scheme": "Wikidata", "value_or_pattern": "Q191821", "note": "Item for the Hindustani sitar as a type of musical instrument." }, { "scheme": "Hornbostel-Sachs", "value_or_pattern": "321.321-6", "note": "Necked bowl lute, sounded by plectrum; the trailing -6 marks plectrum playing. Some catalogues place sitars under 321.321 more broadly." }, { "scheme": "MIMO / MIMO-DB", "value_or_pattern": "sitar (instrument type)", "note": "Used in European museum instrument catalogues; exact local type IDs vary by collection." }, { "scheme": "HS code (Harmonized System)", "value_or_pattern": "9202.90", "note": "Other string musical instruments (not pianos, not bowed instruments of 9202.10); sitars are commonly entered here in trade, not a sitar-specific code." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "CITES: tun wood (Cedrela spp.) and some other tonewoods used in necks or bridges may be listed; export of instruments containing listed timber needs the relevant CITES permit from the exporting authority.", "Airline / IATA passenger rules: sitars are oversized fragile instruments; carriage is by cabin, extra-seat, or specialised cargo, not a sitar-specific standard.", "India: no dedicated national product standard (BIS) for sitars as musical instruments; workshop practice is guild/maker-based rather than a published dimensional standard." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Solo and accompanying instrument in Hindustani classical concerts (alap, jor, jhala, gat in teental and other tala), typically paired with tabla and a tanpura drone.", "Teaching instrument in gharana lineages (especially Maihar and Imdadkhani) and in music schools in India, Pakistan, Bangladesh, and the diaspora.", "Studio and film music in South Asia; also used in 1960s-70s Western popular music as a timbral colour (distinct from the electric sitar).", "Museum and private collections as a named object type with documented stringing, decoration, and maker marks (e.g. Calcutta / Miraj workshops).", "Worship and courtly/light-classical contexts historically; today mainly concert, recording, and pedagogy." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "quantity": "Overall length", "typical_range": "120-140 (concert); surbahar longer, often ~140-160", "unit": "cm" }, { "quantity": "Scale length (nut to bridge / playing string speaking length)", "typical_range": "85-95", "unit": "cm" }, { "quantity": "Playing (melody + drone) strings", "typical_range": "6-7 (kharaj-pancham often 7; gandhar-pancham often 6)", "unit": "count" }, { "quantity": "Sympathetic (taraf) strings", "typical_range": "11-13 typical; some instruments 9-20", "unit": "count" }, { "quantity": "Movable frets (pardā)", "typical_range": "19-23", "unit": "count" }, { "quantity": "Main resonator (tumba) diameter", "typical_range": "30-40", "unit": "cm" }, { "quantity": "Concert pitch of the main melody string (baaj, often tuned to ma or sa depending on school)", "typical_range": "C#3-D3 region for the tonic reference in many modern concert setups, with the instrument tuned to the player's chosen sa", "unit": "nominal pitch / Hz set per performance" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "Gourd (tumba) cracking from impact, dryness, or humidity swing; a cracked resonator kills sustain and can split further under string tension.", "Neck warp or joint failure at the gourd-neck junction under the high tension of steel/bronze strings.", "Fret (pardā) ligatures (thread/gut/nylon) slipping or breaking, so intonation collapses.", "Jawari (bridge) wear: the flattened, buzz-producing contact surface files down, losing the characteristic sustain/buzz; re-cutting jawari is a specialist job.", "Sympathetic-string breakage and peg slip, especially with seasonal humidity change.", "CITES/customs seizure when an instrument contains listed timber or when documentation is missing on export.", "Hearing and playing strain: long practice at high jhala volume; plectrum (mizrab) can cut the finger if poorly fitted.", "Airline damage: the long neck and gourd are easily crushed in holds." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ "North India (Hindustani): the concert sitar as described; two living bajs, Maihar/kharaj-pancham and Imdadkhani/gandhar-pancham.", "Bengal / Kolkata workshops: a major 19th-20th century making centre; many extant concert instruments.", "Maharashtra (Miraj): another historic making centre, associated with specialised jawari work.", "Pakistan: same Hindustani instrument type in classical practice; folk relatives exist under local names.", "Iran / Central Asia: the word sitar/setar names a different, smaller long-necked lute (Persian setar); not the Hindustani instrument.", "West: 'sitar' in shops may mean an electric sitar or a cheap tourist instrument with incorrect stringing and a non-functional jawari." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Reported by the breadth pass; each item needs checking against its source before it becomes normative.", "evidence": [ { "name": "Persian setar / Iranian sehtar", "difference": "Smaller, typically four strings, no sympathetic bank, no large gourd tumba, different tuning and repertoire (radif); shared name etymology (seh/si + tar, 'three/thirty strings') does not make them the same instrument." }, { "name": "Surbahar", "difference": "Bass member of the same family: larger gourd, longer scale, thicker strings, lower pitch, used mainly for alap; a sitar is the higher concert instrument." }, { "name": "Tanpura (tambura)", "difference": "Fretless drone lute with four or five strings and no melody frets or sympathetic bank; a sitar is fretted and played melodically with a mizrab." }, { "name": "Veena / rudra veena / Saraswati veena", "difference": "Different body architecture (tube stick-zither for rudra veena; carved wooden resonator for Saraswati veena of Carnatic music), different technique and repertoire; not a sitar even when both have gourds and sympathetic or drone strings." }, { "name": "Santoor", "difference": "Hammered trapezoidal zither; struck with mallets, not plucked with a mizrab on a necked lute." }, { "name": "Electric sitar / Coral sitar", "difference": "Solid-body or guitar-shaped instrument with a buzzing bridge to imitate jawari timbre; no gourd resonator, usually no true taraf bank, used in pop/rock - not a Hindustani concert sitar." }, { "name": "Saz / bağlama", "difference": "Turkish/Anatolian long-necked lute with tied frets and a carved or staved bowl, no sympathetic strings, different tuning and plectrum technique." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of sitar this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.sitar encompass historical regional instruments called sitar and guitar-form electric sitars, or should those be linked to neighbouring registry entries?", "Which construction and string-layout criteria reliably distinguish the relevant sitar variants from surbahar and other closely related instruments?", "What instrument-specific evidence establishes suitable string materials, gauges and pitch limits when maker documentation is absent?", "How should jawari targets and acceptable intonation be recorded reproducibly across players and playing traditions without imposing one preferred sound?", "Which structural observations require suspension of playing, and which can be monitored, for each documented construction type?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 33 } }, "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 sitar, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise a sitar, assess its configuration and playing condition, and decide which tuning, performance, maintenance or conservation 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: kachva sitar.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 64 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 sitar, 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": [ "kachva sitar" ] } ], "standing": "Described in 64 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 sitar from another, and a sitar 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 sitar, 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 sitar, 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 sitar 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 sitar, 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 sitar, 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 sitar 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 sitar 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 sitar, 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 sitar, 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 sitar 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 sitar from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a sitar, 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 sitar, 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 sitar 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 sitar 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 sitar, 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 sitar, 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 sitar 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 sitar is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a sitar, 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 sitar, 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 sitar 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 sitar is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a sitar, 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 sitar, 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 sitar 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 sitar 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 sitar is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a sitar, 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 sitar, 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 sitar 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 sitar 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 sitar, 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 sitar, 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 sitar 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 sitar 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 sitar between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a sitar, 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 sitar, 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 sitar 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 sitar, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a sitar 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 sitar, 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 sitar, 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 sitar 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 sitar 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 sitar 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 sitar, 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 sitar 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 sitar 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 sitar 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 sitar 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 sitar 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 sitar, 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 sitar 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 sitar and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a sitar, 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 sitar, 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 sitar 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 sitar is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a sitar, 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 sitar, 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 sitar 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 } } } }