{ "model": { "rank": 6546, "code": "thing-q213100", "model_id": "vr.tr.tabla", "name": "tabla", "purpose": "Enable an AI agent to recognise a physical tabla, assess its completeness and playing condition, and decide whether it can be played, tuned, paired, transported or referred for repair.", "family": "Thing Registry", "category": "Physical world and living systems", "status": "research-draft", "kind": "thing", "plane": "PHY", "domain": "PHY.OBJ", "industry": "", "version": "", "url": "/models/thing/q213100/", "tier": 2, "score": 60, "payload": { "layer": "wikidata", "aliases": [ "tabla tarang" ], "aliasCount": 1, "merged": 1, "knownIn": 60, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q213100", "url": "https://www.wikidata.org/wiki/Q213100", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T15:12:56Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.0080988, "turns": 1, "seconds": 65.1, "error": null }, "codex": { "seconds": 93.4, "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: 01a07c6c-8b06-7a70-ad57-d12acabbfb1d\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: tabla\nRegistry id: vr.tr.tabla\nPlane / domain: PHY / PHY.OBJ\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Vercy model" } } }, "metaModel": { "id": "THING-Q213100", "registryId": "vr.tr.tabla", "name": "tabla", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "PHY.OBJ" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q213100/", "model": { "registry_id": "vr.tr.tabla", "name": "tabla", "purpose": "Enable an AI agent to recognise a physical tabla, assess its completeness and playing condition, and decide whether it can be played, tuned, paired, transported or referred for repair.", "definition": "A pair of tuned hand drums (bayan/duggi and dayan/tabla) used as the principal percussion of Hindustani classical and related North Indian, Pakistani, and Bangladeshi music, played with the fingers and palms to produce a closed set of named strokes (bols).", "scope_statement": "Own the physical instrument registered as vr.tr.tabla, provisionally interpreting tabla as the South Asian drum pair or an identified member of that pair, with component-level observations kept within this model pending clarification of registry intent.", "in_scope": [ "Identification of the represented object as a pair, dayan, bayan or unresolved component", "Shells, heads, syahi, head attachment and tensioning mechanisms", "Observed pitch, stroke response and compatibility between paired drums", "Physical condition and evidence supporting playing or maintenance decisions", "Fit and suitability of supports, protective covers and replacement components" ], "out_of_scope": [ "Tala structures, compositions and musical notation", "Performer proficiency, teaching curricula and stylistic lineage", "Maker biographies and workshop operations beyond attribution links", "Performance events, ensemble organisation and recording production", "Electronic tabla synthesisers, sample libraries and playback applications" ], "distinguishing_features": [ "Check whether the object comprises separate treble and bass drums, or an identifiable member of that arrangement; a pair alone does not establish tabla identity. The British Museum identifies these roles as dayan and bayan. [British Museum collection](https://www.britishmuseum.org/collection/object/A_2019-3043-1-2)", "Inspect for a cylindrical wooden treble shell and a kettle-shaped bass shell, allowing documented material variants; compare the complete construction rather than treating material alone as decisive. [Metropolitan Museum collection](https://www.metmuseum.org/art/collection/search/504453)", "Inspect the separate single-headed bodies, layered head construction and applied tuning-paste area; this construction helps distinguish a tabla component from an otherwise similar small drum. [University of Washington collection via DPLA](https://dp.la/item/5038f69d4094de904917a8279ac92105)", "Distinguish two separate drum bodies from a single body carrying heads at opposite ends; record damaged or missing components before rejecting an identification.", "Establish that sound comes from the physical drumhead and resonating body; a controller or playback device labelled tabla belongs to a neighbouring electronic-instrument model." ], "characteristics": [ { "name": "Represented instrument extent", "kind": "category", "unit_or_values": "pair | dayan only | bayan only | unresolved", "why_it_matters": "Prevents a single component from being judged as a complete pair or assigned the wrong acoustic expectations." }, { "name": "Component pairing", "kind": "relation", "unit_or_values": "Component identities, associated counterpart and evidence for the association", "why_it_matters": "Separates an established pair from drums temporarily assembled together." }, { "name": "Shell form and material", "kind": "category", "unit_or_values": "Observed form and material per drum; unknown permitted", "why_it_matters": "Supports identification, damage interpretation and appropriate handling." }, { "name": "Head and seating dimensions", "kind": "measurement", "unit_or_values": "mm, with measurement location and distinction between playing surface, shell opening and outer head diameter", "why_it_matters": "Supports replacement-head and accessory fit without conflating different diameters." }, { "name": "Head and syahi condition", "kind": "state", "unit_or_values": "Observed wear, tears, separation, cracking, missing material or unassessed areas, located per drum", "why_it_matters": "Supports decisions about playing, tuning and specialist inspection." }, { "name": "Tensioning arrangement", "kind": "category", "unit_or_values": "Observed straps, tuning blocks, threaded hardware or other documented mechanism", "why_it_matters": "Determines which adjustments are physically applicable." }, { "name": "Reference-stroke pitch", "kind": "measurement", "unit_or_values": "Hz and optionally note plus cents, with drum, stroke, pitch reference and test conditions", "why_it_matters": "Makes tuning observations comparable while preserving which sound was measured." }, { "name": "Stroke response", "kind": "state", "unit_or_values": "Observed ringing, damping, buzzing, rattling, weak response or untested, tied to a specified stroke", "why_it_matters": "Distinguishes functional evidence from appearance and unexplained sound judgements." }, { "name": "Bayan pressure response", "kind": "measurement", "unit_or_values": "Observed pitch excursion in Hz or cents under a described player test; untested permitted", "why_it_matters": "Records whether the bass drum supports the intended expressive response." }, { "name": "Use readiness", "kind": "state", "unit_or_values": "ready for stated use | adjustment needed | specialist assessment needed | unassessed", "why_it_matters": "Connects physical and acoustic observations to a specific proposed action." } ], "affordances": [ "Identify the drum roles and establish whether a usable pair is present.", "Select a pair for a stated pitch and playing context using observed response.", "Set the drums on fitting supports and assess playing stability.", "Tune through the observed mechanism within limits supported for the particular instrument.", "Route head, syahi, shell or tensioning faults to an appropriate repair assessment.", "Fit protective covers and packing that avoid pressure on vulnerable playing surfaces." ] }, "sources": [ { "id": "Grove", "title": "Tabla", "url": "https://doi.org/10.1093/gmo/9781561592630.article.27337", "what_it_supports": "Organological definition, pair construction, Hindustani role, bols and gharana practice.", "url_status": "unverified" }, { "id": "Met", "title": "Tabla", "url": "https://www.metmuseum.org/art/collection/search/500612", "what_it_supports": "Physical construction: wooden dayan, metal bayan, goatskin heads, syahi paste, straps and gatta tuning.", "url_status": "blocked" }, { "id": "Wikidata", "title": "tabla (Q271596)", "url": "https://www.wikidata.org/wiki/Q271596", "what_it_supports": "Stable identifier and aliases for the instrument as a pair of drums.", "url_status": "live" }, { "id": "HornbostelSachs", "title": "Revision of the Hornbostel-Sachs Classification of Musical Instruments by the MIMO Consortium", "url": "https://www.mimo-international.com/MIMO/l-revision-of-the-hornborstel-sachs-classification-1116.aspx", "what_it_supports": "Classification of kettledrums with laced skins (HS 211.31) used for cataloguing tabla.", "url_status": "unverified" } ], "structure": { "bundles": [ { "id": "tabla-identity-and-pairing", "name": "Tabla identity and pairing", "description": "Establish what the registry-linked physical object includes and how its drums are identified.", "rationale": "Tabla terminology can refer to different instrument extents, so recognition and completeness require explicit component roles.", "layers": [ { "id": "name-and-object-boundary", "name": "Name and object boundary", "description": "Resolve the relationship between the recorded name and the physical instrument.", "findings": [ { "id": "represented-tabla-extent", "name": "Represented tabla extent", "description": "Record whether this instance represents a pair or one drum without creating an additional registry concept.", "questions": [ { "text": "Does this instance denote the complete pair, the dayan, the bayan or an unresolved object?", "kind": "boundary", "id": "represented-tabla-extent-q01" }, { "text": "Which label, owner statement or collection record supports that interpretation?", "kind": "provenance", "id": "represented-tabla-extent-q02" } ] } ] }, { "id": "component-role-and-association", "name": "Component role and association", "description": "Identify each drum independently and establish the basis of its pairing.", "findings": [ { "id": "dayan-bayan-association", "name": "Dayan-bayan association", "description": "Keep drum role separate from physical placement and distinguish documented pairing from current proximity.", "questions": [ { "text": "Which construction and acoustic observations identify each drum as dayan or bayan?", "kind": "definition", "id": "dayan-bayan-association-q01" }, { "text": "Were these drums supplied or used together, or assembled as a pair later?", "kind": "provenance", "id": "dayan-bayan-association-q02" }, { "text": "Is a counterpart missing, substituted or represented by a separate physical-object record?", "kind": "boundary", "id": "dayan-bayan-association-q03" } ] } ] } ] }, { "id": "shell-head-and-syahi", "name": "Shell, head and syahi", "description": "Describe the sound-producing assembly sufficiently to identify construction and assess component fit.", "rationale": "Shell geometry, head construction and syahi observations determine what can be compared, replaced or investigated.", "layers": [ { "id": "shell-and-head-seat", "name": "Shell and head seat", "description": "Record the supporting body and the dimensions relevant to head seating.", "findings": [ { "id": "shell-form-and-fit", "name": "Shell form and fit", "description": "Identify shell construction and measure fit at explicitly named locations.", "questions": [ { "text": "What shell form and material are observed for each drum, and which material identifications remain uncertain?", "kind": "definition", "id": "shell-form-and-fit-q01" }, { "text": "What are the shell opening and head-seat dimensions, and where exactly were they measured?", "kind": "measurement", "id": "shell-form-and-fit-q02" } ] } ] }, { "id": "playing-head-assembly", "name": "Playing-head assembly", "description": "Locate the membrane regions, applied syahi and their attachment to the drum.", "findings": [ { "id": "head-regions-and-loading", "name": "Head regions and loading", "description": "Record visible construction without inferring membrane species or syahi composition from appearance alone.", "questions": [ { "text": "What membrane layers, outer-ring features and syahi position are visible on each head?", "kind": "definition", "id": "head-regions-and-loading-q01" }, { "text": "What evidence identifies the head materials, maker or replacement history?", "kind": "provenance", "id": "head-regions-and-loading-q02" }, { "text": "Which dimensions and construction details must a replacement head match?", "kind": "action", "id": "head-regions-and-loading-q03" } ] } ] } ] }, { "id": "tension-and-pitch-control", "name": "Tension and pitch control", "description": "Connect the installed adjustment mechanism to measured tuning and supported operating limits.", "rationale": "A desired pitch does not establish that this particular shell and head can safely or effectively reach it.", "layers": [ { "id": "installed-tensioning", "name": "Installed tensioning", "description": "Identify how the head is tensioned and whether the mechanism is serviceable.", "findings": [ { "id": "adjustment-mechanism-and-condition", "name": "Adjustment mechanism and condition", "description": "Record the actual straps, blocks or hardware and evidence of compromised adjustment.", "questions": [ { "text": "Which straps, tuning blocks or threaded parts control tension on this drum?", "kind": "definition", "id": "adjustment-mechanism-and-condition-q01" }, { "text": "Are any tensioning parts loose, displaced, damaged or unable to hold their position?", "kind": "measurement", "id": "adjustment-mechanism-and-condition-q02" }, { "text": "Which adjustment procedure is supported by the maker or a qualified repairer for this construction?", "kind": "action", "id": "adjustment-mechanism-and-condition-q03" } ] } ] }, { "id": "pitch-target-and-retention", "name": "Pitch target and retention", "description": "Separate current pitch, requested pitch and evidence of stable tuning.", "findings": [ { "id": "attainable-and-stable-tuning", "name": "Attainable and stable tuning", "description": "Record pitch under a repeatable stroke and preserve uncertainty about the usable tuning range.", "questions": [ { "text": "What pitch does the specified reference stroke produce, using which reference frequency and measurement method?", "kind": "measurement", "id": "attainable-and-stable-tuning-q01" }, { "text": "What evidence supports reaching the requested pitch with this head and shell?", "kind": "action", "id": "attainable-and-stable-tuning-q02" }, { "text": "How much does the measured pitch change after the stated playing interval and environmental exposure?", "kind": "measurement", "id": "attainable-and-stable-tuning-q03" } ] } ] } ] }, { "id": "stroke-response-and-pair-suitability", "name": "Stroke response and pair suitability", "description": "Assess the sounds the instrument can produce under identified player tests.", "rationale": "A tabla may appear intact yet fail to produce the response needed for its intended use.", "layers": [ { "id": "dayan-articulation", "name": "Dayan articulation", "description": "Assess repeatable differences between requested ringing and damped sounds.", "findings": [ { "id": "dayan-stroke-separation", "name": "Dayan stroke separation", "description": "Associate sound observations with demonstrated strokes, accounting for player technique.", "questions": [ { "text": "Which demonstrated strokes were tested, and what local bol names did the player use?", "kind": "definition", "id": "dayan-stroke-separation-q01" }, { "text": "Do the tested ringing and damped strokes produce the expected contrast, or show weak response, buzzing or rattling?", "kind": "measurement", "id": "dayan-stroke-separation-q02" }, { "text": "Has a competent player repeated the test before the response is attributed to an instrument fault?", "kind": "provenance", "id": "dayan-stroke-separation-q03" } ] } ] }, { "id": "bayan-response-and-pair-balance", "name": "Bayan response and pair balance", "description": "Assess bass response and whether the two drums work together for the stated use.", "findings": [ { "id": "bass-modulation-and-balance", "name": "Bass modulation and balance", "description": "Record observed pressure-dependent response and pair balance without imposing a universal tuning relationship.", "questions": [ { "text": "What bass pitch change and return are observed during a described pressure-modulation test?", "kind": "measurement", "id": "bass-modulation-and-balance-q01" }, { "text": "With the same player and setup, does either drum mask the other in the intended passage?", "kind": "measurement", "id": "bass-modulation-and-balance-q02" }, { "text": "Does the pair meet the player's stated pitch, articulation and balance requirements for this use?", "kind": "action", "id": "bass-modulation-and-balance-q03" } ] } ] } ] }, { "id": "condition-and-intervention", "name": "Condition and intervention", "description": "Turn located defects and repair history into evidence-based use and maintenance decisions.", "rationale": "Changes to the head, syahi or tension system can alter both sound and structural condition.", "layers": [ { "id": "located-damage", "name": "Located damage", "description": "Distinguish observed deterioration from an unexplained acoustic symptom.", "findings": [ { "id": "head-syahi-and-shell-defects", "name": "Head, syahi and shell defects", "description": "Record defect location, extent and change over time for the affected drum.", "questions": [ { "text": "Where are tears, head separation, syahi loss, shell cracks or tensioning damage visible?", "kind": "measurement", "id": "head-syahi-and-shell-defects-q01" }, { "text": "Are these observations new or changing relative to dated photographs or earlier inspections?", "kind": "provenance", "id": "head-syahi-and-shell-defects-q02" }, { "text": "Which observed defect warrants pausing playing or tuning pending specialist assessment?", "kind": "action", "id": "head-syahi-and-shell-defects-q03" } ] } ] }, { "id": "repair-decision-and-verification", "name": "Repair decision and verification", "description": "Define justified intervention and the evidence needed to judge its result.", "findings": [ { "id": "supported-tabla-intervention", "name": "Supported tabla intervention", "description": "Distinguish routine tuning from head replacement, syahi work and structural repair.", "questions": [ { "text": "Does the evidence support tuning, head replacement, syahi work, shell repair or further diagnosis?", "kind": "action", "id": "supported-tabla-intervention-q01" }, { "text": "Who performed previous work, on which drum and components, and what materials were documented?", "kind": "provenance", "id": "supported-tabla-intervention-q02" }, { "text": "Which pitch-retention and stroke-response checks must pass before the repaired drum returns to its intended use?", "kind": "action", "id": "supported-tabla-intervention-q03" } ] } ] } ] }, { "id": "playing-support-and-protection", "name": "Playing support and protection", "description": "Assess the support and protective interfaces that affect the pair during use and movement.", "rationale": "Each drum needs an appropriate physical seat and protection that accommodates its shell and exposed head.", "layers": [ { "id": "supported-playing-position", "name": "Supported playing position", "description": "Check how each drum sits and whether the arrangement permits the intended hand movements.", "findings": [ { "id": "drum-seat-and-hand-clearance", "name": "Drum seat and hand clearance", "description": "Relate support fit and drum placement to stability and access to the playing surfaces.", "questions": [ { "text": "Does each support fit its drum without rocking or obstructing the tensioning parts?", "kind": "measurement", "id": "drum-seat-and-hand-clearance-q01" }, { "text": "Can the intended player reach the required head regions and execute bayan pressure movements without destabilising the drum?", "kind": "action", "id": "drum-seat-and-hand-clearance-q02" } ] } ] }, { "id": "head-protection-and-storage", "name": "Head protection and storage", "description": "Evaluate covers, case fit and environmental evidence relevant to the physical instrument.", "findings": [ { "id": "protected-tabla-packing", "name": "Protected tabla packing", "description": "Record whether packing secures both drums while protecting their heads and tensioning assemblies.", "questions": [ { "text": "Do the covers and case fit without concentrated pressure on the syahi, head edges or tuning parts?", "kind": "measurement", "id": "protected-tabla-packing-q01" }, { "text": "What temperature or humidity changes accompanied any observed pitch drift or head-condition change?", "kind": "provenance", "id": "protected-tabla-packing-q02" }, { "text": "What packing and storage conditions are supported for this instrument by its maker or conservator?", "kind": "action", "id": "protected-tabla-packing-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": [ "Dayan (right-hand wooden treble drum, typically sheesham or teak, with syahi)", "Bayan / duggi (left-hand metal bass drum, typically copper, brass, or aluminum)", "Concert / classical tabla pair (full-size, professionally tuned)", "Student / practice tabla (smaller or lighter shells, often aluminum bayan)", "Folk and qawwali tabla (heavier playing, often with dholak-influenced technique)", "Electronic / MIDI tabla and tabla machines (sampled or synthesized substitutes)", "Tabla tarang (set of several dayan-type drums tuned to a scale)", "Children's / toy tabla (miniature skins, not concert-pitch)" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of tabla 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": "Q271596", "note": "Item for the Hindustani tabla pair." }, { "scheme": "Hornbostel-Sachs (MIMO revision)", "value_or_pattern": "211.31", "note": "Kettledrums with membrane laced to the body; individual drums of the pair." }, { "scheme": "MIMO / MIMO-DB instrument keyword", "value_or_pattern": "tabla", "note": "Museum catalogue term for the pair or the dayan." }, { "scheme": "HS/MIMO more specific", "value_or_pattern": "211.211.1-922 / related 211.31 variants", "note": "Some catalogues class the wooden dayan as a single-skin goblet/kettledrum with tuning paste; numbering varies by museum." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of tabla 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 and national wildlife law: raw skins (commonly goat, historically other mammals) are subject to export/import and product-of-animal rules; finished musical instruments generally travel as personal or commercial goods, not as a named instrument standard.", "Airline / IATA musical-instrument carriage: tabla pairs are typically cabin or special-baggage items; no instrument-specific ISO.", "No ISO pitch or construction standard for tabla; tuning is by gatta (wooden blocks) and strap tension to a chosen tonic (sa), not to A440 as a factory spec.", "India: Bureau of Indian Standards does not publish a dedicated tabla construction standard comparable to some Western orchestral instruments." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of tabla 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": [ "Principal accompanying percussion in Hindustani vocal (khayal, thumri) and instrumental (sitar, sarod, bansuri, violin) recitals, typically seated on the floor with the dayan on the right and bayan on the left for a right-handed player.", "Solo tabla recitals (tabla solo / very) built from qaida, rela, tukra, chakradar and tihai compositions in a chosen tala.", "Devotional and popular settings: kirtan, qawwali, ghazal, film and fusion bands; also teaching studios and graded exam boards (e.g. Prayag Sangeet Samiti, Gandharva Mahavidyalaya, Trinity/ABRSM-adjacent world-music syllabi).", "Dance accompaniment for kathak, where theka and bols lock to footwork (tatkar).", "Museum and ethnomusicology collections as a named pair of kettledrums with syahi.", "Sample libraries, electronic pads and 'tabla machines' in studio production when an acoustic pair is unavailable." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of tabla 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": "Dayan shell height (bearing edge to base)", "typical_range": "25-30", "unit": "cm" }, { "quantity": "Dayan head (puri) diameter", "typical_range": "12-16", "unit": "cm" }, { "quantity": "Bayan head diameter", "typical_range": "22-26", "unit": "cm" }, { "quantity": "Pair mass (concert set with cases excluded)", "typical_range": "8-14", "unit": "kg" }, { "quantity": "Playing pitch of dayan (tuned to sa of the soloist)", "typical_range": "C3-G4 depending on size; adult male vocal often C#3-E3; instrumental often D3-F#3", "unit": "note name / Hz" }, { "quantity": "Tala cycle length in common thekas", "typical_range": "6 (dadra), 7 (rupak), 8 (keherwa), 10 (jhaptal), 12 (ektal), 16 (teental)", "unit": "matra (beats)" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of tabla 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": [ "Puri (skin) tearing or syahi cracking from overtightening, impact, or dry heat; the drum then will not speak na/tin/tun cleanly.", "Strap (tasma) stretch or breakage and gatta slip, causing pitch collapse mid-performance.", "Shell crack in wooden dayan (especially cheap laminated shells) from climate cycling.", "Copper bayan denting; aluminum bayans go dull and are harder to keep in pitch.", "Mold and insect damage to skins and leather straps in humid storage.", "Hearing risk for the player in prolonged close-mic or high-volume fusion settings; not an intrinsically loud orchestral hazard compared with Western snare/cymbals.", "CITES/customs seizure if skins are of restricted species or undocumented; goat is usual and generally unrestricted as a finished product, but substitution is a documented commercial risk.", "Wrist, finger and lumbar strain from long sitting play (gharana-specific technique modulates load)." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of tabla 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": [ "Name: in Hindustani practice 'tabla' is the pair, or specifically the right-hand dayan; in some colloquial North Indian and Pakistani usage 'tabla' is the pair and 'dagga/duggi' the bass.", "South India: the analogous concert drum is the mridangam (double-headed barrel), not tabla; tabla appears in film, fusion and some bhajan settings, not as Carnatic concert default.", "Pakistan and Bangladesh: same instrument family; qawwali and folk gharanas use heavier bayan work and different theka vocabulary.", "Gharana differences (Delhi, Ajrada, Lucknow, Farrukhabad, Benares, Punjab) are schools of bol, composition and hand position, not different physical instruments, though Benares players often prefer a larger, heavier dayan.", "Diaspora (UK, US, Canada): student aluminum bayans and synthetic or 'fiber' shells are common; concert players still prefer copper bayan and sheesham dayan.", "West Bengal / Bangladesh: 'tabla' in some folk contexts sits beside khol and dholak; pairing and sitting posture may follow kirtan rather than court-recital convention." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of tabla 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": "Mridangam", "difference": "Double-headed barrel drum of Carnatic music, played horizontally with both hands on opposite heads; tabla is a pair of single-headed kettledrums played with both hands on separate drums. Mridangam has no independent bayan pitch-bend." }, { "name": "Pakhawaj (pakhavaj)", "difference": "Older North Indian barrel drum, ancestor of much tabla repertoire; one body, two heads, played horizontally. Tabla split the roles onto two drums and added the bayan wrist-modulated bass." }, { "name": "Dholak", "difference": "Folk barrel drum, two heads, rope or nut-bolt tension, no syahi-centered treble vocabulary of na/tin/tun; much louder, less pitch-definite treble." }, { "name": "Nagara / naqqara", "difference": "Pair of kettledrums played with sticks, outdoor/ceremonial; tabla is finger-played, indoor/art-music, with syahi." }, { "name": "Bongo pair", "difference": "Afro-Cuban attached pair, open-bottom shells, no syahi, no tala/bol system; technique and tuning logic are unrelated despite both being a 'pair of hand drums'." }, { "name": "Khol (mridanga of Bengal Vaishnava kirtan)", "difference": "Terracotta or fiberglass barrel with two heads, played for kirtan; not a tabla pair even when used in overlapping religious settings." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of tabla this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.tabla intend the South Asian pair, the treble drum specifically, or another regional use of the name? Museum terminology differs: [Metropolitan Museum](https://www.metmuseum.org/art/collection/search/504453) and [British Museum](https://www.britishmuseum.org/collection/object/A_2019-3043-1-2).", "Which construction variants, including alternative head materials and tensioning systems, should count as tabla within this registry entry?", "Which demonstrated stroke tests and terminology provide reliable comparisons across players and traditions?", "What maker- or repairer-supported tuning limits and environmental guidance apply to particular shell, head and syahi combinations?", "Which visible head or syahi changes indicate acceptable wear, impaired response or a need to stop playing, and what specialist evidence supports those distinctions?" ], "statistics": { "bundles": 7, "layers": 13, "findings": 20, "questions": 41 } }, "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 tabla, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise a physical tabla, assess its completeness and playing condition, and decide whether it can be played, tuned, paired, transported or referred for repair.", "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: tabla tarang.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 60 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 tabla, 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": [ "tabla tarang" ] } ], "standing": "Described in 60 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 tabla from another, and a tabla 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 tabla, 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 tabla, 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 tabla 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 tabla, 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 tabla, 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 tabla 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 tabla 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 tabla, 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 tabla, 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 tabla 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 tabla from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a tabla, 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 tabla, 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 tabla 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 tabla 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 tabla, 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 tabla, 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 tabla 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 tabla is built from and which parts are replaceable.", "questions": [ { "id": "parts-and-materials-q01", "text": "What identifies and describes the composition of a tabla, 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 tabla, 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 tabla 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 tabla is judged and by whom.", "questions": [ { "id": "condition-assessment-q01", "text": "What identifies and describes the condition of a tabla, 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 tabla, 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 tabla 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 tabla 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 tabla is, and what that position is measured against.", "questions": [ { "id": "position-and-frame-q01", "text": "What identifies and describes the location of a tabla, 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 tabla, 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 tabla 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 tabla 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 tabla, 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 tabla, 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 tabla 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 tabla 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 tabla between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a tabla, 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 tabla, 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 tabla 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 tabla, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a tabla 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 tabla, 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 tabla, 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 tabla 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 tabla 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 tabla 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 tabla, 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 tabla 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 tabla 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 tabla 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 tabla 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 tabla 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 tabla, 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 tabla 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 tabla and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a tabla, 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 tabla, 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 tabla 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 tabla is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a tabla, 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 tabla, 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 tabla 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 } } } }