{ "model": { "rank": 6382, "code": "thing-q186599", "model_id": "vr.tr.arabesque", "name": "arabesque", "purpose": "Enable an AI agent to recognise, assess and select appropriate next actions for an arabesque performed as a dance position or movement.", "family": "Thing Registry", "category": "Activities and processes", "status": "research-draft", "kind": "thing", "plane": "ACT", "domain": "ACT.ACT", "industry": "", "version": "", "url": "/models/thing/q186599/", "tier": 2, "score": 60, "payload": { "layer": "wikidata", "aliases": [ "Garrus", "moresque" ], "aliasCount": 2, "merged": 2, "knownIn": 60, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": "vr.tr.arabesque", "source": { "dataset": "wikidata", "item": "Q186599", "url": "https://www.wikidata.org/wiki/Q186599", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T14:07:26Z", "providers": [ "Codex", "Grok" ], "missingProviders": [], "pass": 2, "cost": { "grok": { "usd": 0.00333472, "turns": 1, "seconds": 41.3, "error": null }, "codex": { "seconds": 78.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: 01a07c30-cfef-7950-83bb-7d8f2eb7a27a\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: arabesque\nRegistry id: vr.tr.arabesque\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\nA Ver" } } }, "metaModel": { "id": "THING-Q186599", "registryId": "vr.tr.arabesque", "name": "arabesque", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q186599/", "model": { "registry_id": "vr.tr.arabesque", "name": "arabesque", "purpose": "Enable an AI agent to recognise, assess and select appropriate next actions for an arabesque performed as a dance position or movement.", "definition": "An arabesque is a classical ballet pose in which the dancer stands on one supporting leg, fully stretched, with the other leg extended behind the body and the arms arranged to continue that line through the torso.", "scope_statement": "Provisionally interprets arabesque in ACT / ACT.ACT as the dance action: owns the intended and observed configuration, execution, support conditions and transitions of an individual arabesque; the registry's intended sense remains unconfirmed.", "in_scope": [ "Identification of an arabesque within a named dance practice or teaching convention", "Relationships among the supporting leg, leg extended behind, pelvis, trunk, head and arms", "Entry, sustained position and exit, including their timing and continuity", "Support mode, assistance and environmental conditions affecting execution", "Assessment against the declared task and performer-specific constraints" ], "out_of_scope": [ "Arabesque ornament in visual art, architecture or decorative design", "Musical works or forms named arabesque", "Complete choreography, phrase composition and production staging", "The performer's medical diagnosis, treatment or general fitness profile", "Comprehensive models of adjacent dance actions such as attitude, turns or jumps", "The dance school's complete technique syllabus" ], "distinguishing_features": [ "For the provisional dance sense, recognition requires a leg extended behind the body; decorative repetition or a musical title does not satisfy this test.", "A substantially bent raised leg requires checking the boundary with attitude rather than automatically labelling the position arabesque.", "A leg extended principally forward or to the side requires another position label or identification as a transition through arabesque.", "A rear-leg extension alone is insufficient: the agent must establish the intended dance position through the declared task, body relationships and movement context.", "An arabesque shape occurring within a turn or jump can be identified locally without treating the entire turn or jump as an arabesque action." ], "characteristics": [ { "name": "Technique convention and variant", "kind": "category", "unit_or_values": "Named practice, school or syllabus; variant label; unspecified", "why_it_matters": "Arm arrangements and variant names need an explicit convention before they can support assessment." }, { "name": "Supporting side and contact mode", "kind": "category", "unit_or_values": "Left or right; flat foot, demi-pointe, pointe, assisted, other declared mode or unknown", "why_it_matters": "Determines the support task and which executions are meaningfully comparable." }, { "name": "Rear-leg elevation", "kind": "measurement", "unit_or_values": "Degrees relative to a declared reference, with movement phase and observation uncertainty", "why_it_matters": "Describes the extension without assuming a universal target height." }, { "name": "Raised-knee configuration", "kind": "measurement", "unit_or_values": "Knee flexion in degrees or a qualified observation when measurement is unavailable", "why_it_matters": "Helps distinguish the intended extended-leg shape from neighbouring positions and execution deviations." }, { "name": "Trunk and pelvis relationship", "kind": "relation", "unit_or_values": "Observed trunk inclination and pelvic orientation relative to the supporting leg, rear leg and travel direction", "why_it_matters": "Makes changes in leg height interpretable alongside the rest of the body." }, { "name": "Arm, head and gaze arrangement", "kind": "relation", "unit_or_values": "Positions relative to the trunk, rear leg and declared facing", "why_it_matters": "Supports variant recognition and comparison with the intended line." }, { "name": "Execution phase", "kind": "state", "unit_or_values": "Entering, sustaining, transitioning out, completed, interrupted or uncertain", "why_it_matters": "Prevents a transitional frame from being judged as a completed position." }, { "name": "Support stability", "kind": "state", "unit_or_values": "Task maintained, corrective movement, unintended step, additional support, loss of balance or unobservable", "why_it_matters": "Shows whether the performer can sustain or leave the position as intended." }, { "name": "Sustained duration", "kind": "measurement", "unit_or_values": "Seconds or musical counts within explicitly stated position criteria", "why_it_matters": "Separates briefly passing through the shape from maintaining the requested balance." }, { "name": "Reported execution constraint", "kind": "state", "unit_or_values": "No constraint reported, discomfort reported, fatigue reported, performer-declared limit, instructor restriction or unknown", "why_it_matters": "Constrains proposed repetitions and modifications without inferring a diagnosis from appearance." } ], "affordances": [ "Identify candidate arabesque moments and state recognition confidence.", "Compare an execution with a named variant and declared task.", "Annotate rear-leg extension, body relationships, support changes and phase boundaries.", "Compare repeated attempts under equivalent support and observation conditions.", "Select a task-appropriate modification, such as reducing the requested elevation or adding authorised support.", "Recommend continuing, exiting, pausing or requesting qualified review using observed control and reported constraints." ] }, "sources": [ { "id": "abt-ballet-dictionary", "title": "Ballet Dictionary: Arabesque", "url": "", "what_it_supports": "ABT's working definition of the pose, the à terre / en l'air distinction, and the Cecchetti numbering of first through fifth arabesque.", "url_status": "dead" }, { "id": "abt-ballet-dictionary-penche", "title": "Ballet Dictionary: Arabesque penchée", "url": "", "what_it_supports": "Defines arabesque penchée as a tipped-forward arabesque with the raised leg near 180°, and notes the French-school first-arabesque arm as the typical accompanying port de bras.", "url_status": "dead" }, { "id": "rad-specifications-2024", "title": "Specifications 2024 (Grades, Vocational, Presentation Classes and Discovering Repertoire)", "url": "https://www.royalacademyofdance.org/media/2024/09/05150727/2024-Specifications-AUGUST-2024-FINAL-with-hyperlinks.pdf", "what_it_supports": "RAD's published grade and vocational syllabus: named arabesque types (1st-4th, à terre, en l'air, allongé, fondu, in attitude), required heights (45° / 90°), and the 2-second hold as an examined measurement.", "url_status": "blocked" }, { "id": "wikidata-q624449", "title": "arabesque (Q624449)", "url": "https://www.wikidata.org/wiki/Q624449", "what_it_supports": "Wikidata identity for the ballet pose (not the ornament), with the Library of Congress subject heading Ballet dancing - Arabesque.", "url_status": "live" } ], "structure": { "bundles": [ { "id": "arabesque-identity", "name": "Arabesque identity", "description": "Establishes which dance sense and positional convention the occurrence is intended to instantiate.", "rationale": "The registry provides no definition, and recognition must not silently collapse different senses or technique conventions.", "layers": [ { "id": "sense-and-convention", "name": "Sense and convention", "description": "Anchors the action to its declared dance practice.", "findings": [ { "id": "declared-arabesque-reference", "name": "Declared arabesque reference", "description": "Records the intended meaning and the authority used to interpret its variant name.", "questions": [ { "text": "Does this occurrence mean a dance arabesque, and which practice or syllabus defines the requested form?", "kind": "definition", "id": "declared-arabesque-reference-q01" }, { "text": "Which instruction, demonstration or published reference establishes the intended variant?", "kind": "provenance", "id": "declared-arabesque-reference-q02" } ] } ] }, { "id": "neighbouring-position-boundaries", "name": "Neighbouring position boundaries", "description": "Tests whether the observed shape belongs to arabesque or a related position.", "findings": [ { "id": "rear-extension-recognition", "name": "Rear extension recognition", "description": "Evaluates rear-leg direction and knee configuration without treating every rearward leg movement as arabesque.", "questions": [ { "text": "Does the leg extend behind the body in the relationship required by the declared arabesque convention?", "kind": "definition", "id": "rear-extension-recognition-q01" }, { "text": "Does knee flexion or leg direction warrant identifying attitude, another extension, a transition or an uncertain case?", "kind": "boundary", "id": "rear-extension-recognition-q02" } ] } ] } ] }, { "id": "arabesque-body-configuration", "name": "Arabesque body configuration", "description": "Describes the relationships that produce the intended arabesque shape.", "rationale": "Rear-leg height alone cannot establish the configuration or explain departures from the requested form.", "layers": [ { "id": "rear-leg-and-body-axis", "name": "Rear leg and body axis", "description": "Relates the extended leg to the pelvis, trunk and supporting leg.", "findings": [ { "id": "extension-geometry", "name": "Extension geometry", "description": "Records rear-leg elevation and associated body orientation using explicit measurement references.", "questions": [ { "text": "What are the rear-leg elevation and knee configuration at the assessed phase, and which references define those measurements?", "kind": "measurement", "id": "extension-geometry-q01" }, { "text": "How are trunk inclination and pelvic orientation related to that extension, and which relationships does the declared task require?", "kind": "measurement", "id": "extension-geometry-q02" } ] } ] }, { "id": "arms-head-and-facing", "name": "Arms, head and facing", "description": "Captures the upper-body arrangement that completes the requested variant.", "findings": [ { "id": "variant-specific-line", "name": "Variant-specific line", "description": "Interprets arms, head and gaze relative to the body and intended presentation.", "questions": [ { "text": "Where are the arms, head and gaze relative to the rear leg, trunk and declared facing?", "kind": "measurement", "id": "variant-specific-line-q01" }, { "text": "Which observed differences change the variant identity, and which are permitted expressive choices under the selected convention?", "kind": "boundary", "id": "variant-specific-line-q02" } ] } ] } ] }, { "id": "arabesque-support-and-control", "name": "Arabesque support and control", "description": "Establishes how the position is supported and whether its balance demand is being met.", "rationale": "The same apparent shape can represent materially different tasks when foot contact, assistance or balance control changes.", "layers": [ { "id": "support-conditions", "name": "Support conditions", "description": "Identifies the supporting side, foot contact and external assistance.", "findings": [ { "id": "actual-support-task", "name": "Actual support task", "description": "Separates the requested support mode from the support actually used.", "questions": [ { "text": "Which leg supports the position, in what foot-contact mode, and with what barre, partner or other assistance?", "kind": "measurement", "id": "actual-support-task-q01" }, { "text": "Does the observed assistance satisfy the task, or does it change a requested unsupported arabesque into a different support condition?", "kind": "boundary", "id": "actual-support-task-q02" } ] } ] }, { "id": "balance-maintenance", "name": "Balance maintenance", "description": "Tracks whether the intended configuration remains controlled for the requested interval.", "findings": [ { "id": "hold-and-corrections", "name": "Hold and corrections", "description": "Records sustained duration, corrections and unintended support changes.", "questions": [ { "text": "For how many seconds or counts are the declared arabesque criteria maintained, and what corrections or unintended contacts occur?", "kind": "measurement", "id": "hold-and-corrections-q01" }, { "text": "Given observed control and reported constraints, should the current attempt continue, use permitted assistance or exit?", "kind": "action", "id": "hold-and-corrections-q02" } ] } ] } ] }, { "id": "arabesque-execution-and-next-action", "name": "Arabesque execution and next action", "description": "Places the position within its movement sequence and connects assessment to a justified next step.", "rationale": "An arabesque must be assessed through its entry and exit as well as its visible peak, and modifications need a stated basis.", "layers": [ { "id": "entry-and-exit", "name": "Entry and exit", "description": "Identifies how the performer reaches and leaves the arabesque.", "findings": [ { "id": "phase-and-continuity", "name": "Phase and continuity", "description": "Distinguishes an intended hold from a passing shape and records control through transitions.", "questions": [ { "text": "Which preceding and following actions frame this arabesque, and is it intended to be held or passed through?", "kind": "definition", "id": "phase-and-continuity-q01" }, { "text": "At what counts or times does the performer enter, establish and leave the shape, and where does unintended interruption occur?", "kind": "measurement", "id": "phase-and-continuity-q02" } ] } ] }, { "id": "assessment-led-adjustment", "name": "Assessment-led adjustment", "description": "Connects specific observed departures to bounded changes in the next attempt.", "findings": [ { "id": "justified-next-attempt", "name": "Justified next attempt", "description": "Records an actionable adjustment while preserving uncertainty about causes that observation cannot establish.", "questions": [ { "text": "Which observed departure and declared task justify changing elevation, duration, support or transition complexity in the next attempt?", "kind": "action", "id": "justified-next-attempt-q01" }, { "text": "What performer report or qualified instruction supports that adjustment, and what uncertainty requires review before proceeding?", "kind": "provenance", "id": "justified-next-attempt-q02" } ] } ] } ] }, { "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": [ "first arabesque", "second arabesque", "third arabesque", "fourth arabesque", "arabesque penchée", "arabesque à terre", "arabesque allongée", "arabesque croisée / ouverte" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of arabesque 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": "Q624449", "note": "Item labelled 'arabesque'; described as a ballet position. Distinct from Q624480 (ornamental pattern) and Q259171 (musical form)." }, { "scheme": "Library of Congress Subject Headings", "value_or_pattern": "sh85011290 (Ballet dancing - Arabesque)", "note": "LCSH used for the dance pose; mapped from Wikidata Q624449." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of arabesque 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": [ "Royal Academy of Dance, Specifications 2024 - Grades, Vocational Graded Examinations, Presentation Classes and Discovering Repertoire: names 1st-4th arabesque, à terre / en l'air / allongé / fondu variants, and sets examined heights and a 2-second hold.", "Cecchetti method (as used by American Ballet Theatre and other schools): numbers arabesques first through fifth by port de bras and épaulement; ABT's public dictionary follows this numbering.", "Vaganova / Russian school: numbers arabesques first through fourth; the count and which arm is 'first' do not match Cecchetti, so a numbered arabesque is school-relative, not a universal code." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of arabesque 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": [ "Taught from junior grades as a line-making pose: supporting leg stretched, working leg extended behind, arms continuing the torso line (ABT dictionary).", "Set as an examined step in RAD Grades 1-8 and Intermediate Foundation, both à terre and en l'air, sometimes held two seconds, sometimes arriving via développé, fouetté, or tombé (RAD Specifications 2024).", "Used on stage as a still picture (held arabesque), a travelling step (arabesque travelling, pas de bourrée to arabesque), and a tipping line (penchée) in classical variations and pas de deux.", "Recorded in notation, coaching notes, and exam reports by school (RAD / Cecchetti / Vaganova / French) because the same number does not mean the same arms." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of arabesque 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": "working-leg height en l'air (examined)", "typical_range": "45 (Grade 1-2) to 90 (from Grade 3); penchée approaches 180", "unit": "degree" }, { "quantity": "hold duration (examined)", "typical_range": "about 2", "unit": "second" }, { "quantity": "Cecchetti numbered types", "typical_range": "1-5", "unit": "school-specific index" }, { "quantity": "Vaganova / RAD numbered types", "typical_range": "1-4", "unit": "school-specific index" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of arabesque 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": [ "Sinking or unlocking the supporting knee, which collapses the line the pose is meant to show.", "Sickling or winging the working foot, or letting the hip of the raised leg hike, so the arabesque reads as a lift rather than a long back line.", "Lumbar compression and posterior-chain strain in high arabesque and especially penchée, when height is forced without turnout and core support.", "School-mismatch in numbered arabesques (calling 'first' when the arms are another method's second or third), which fails examinations and rehearsal notes." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of arabesque 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": [ "Cecchetti (Italian, followed by ABT's public dictionary): five numbered arabesques.", "Vaganova (Russian) and RAD (British examination syllabus): four numbered arabesques; RAD also writes à terre, en l'air, allongé, and fondu as examined states of the same pose.", "French school: tends to describe arabesque by openness (croisée / ouverte / éffacée) and which arm is forward, rather than a single 1-4/5 table; ABT notes that a penchée is often shown with French-school first-arabesque arms.", "The word 'arabesque' is also an ornament and a musical form in other domains; those are different things (Wikidata Q624480, Q259171), not this pose." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of arabesque 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": "attitude", "difference": "In attitude the working leg is bent at the knee; in arabesque it is fully stretched behind. RAD lists both as distinct syllabus steps." }, { "name": "arabesque (ornament) / Mooresque", "difference": "A surface pattern of interlaced foliage, not a body pose; Wikidata Q624480 versus Q624449." }, { "name": "arabesque (music)", "difference": "A character piece or ornamental melody (Wikidata Q259171), not a stance." }, { "name": "penché as a generic tilt", "difference": "Arabesque penchée is a specific tipped arabesque with the working leg high behind; a cambré or hinge forward without that stretched back leg is not an arabesque." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of arabesque this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does vr.tr.arabesque specifically denote the dance action, or does its intended ACT meaning include another practice?", "Which authoritative dance references should define recognition criteria and variant terminology for the first publication?", "How should the model distinguish accepted stylistic variation from execution error, particularly for pelvic orientation, trunk inclination and arm placement?", "Should airborne, turning, penchée and partnered occurrences be owned here as variants or linked to neighbouring action models?", "Which observation methods and uncertainty limits are sufficient for assessing rear-leg elevation, knee configuration and balance without overinterpreting a camera view?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 16, "questions": 24 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "abstract concept", "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 arabesque, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an AI agent to recognise, assess and select appropriate next actions for an arabesque performed as a dance position or movement.", "characteristics": { "substance": "activity", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Garrus, moresque.", "2 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 arabesque, and on what evidence are they told apart?" ], "whatItIsMadeOf": "something that happens over time", "physicalCharacter": [ "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": [ "Nothing to see. What is recognised is an instance of it, and which instances count is exactly what is argued about." ], "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": [ "Garrus", "moresque" ] } ], "standing": "Described in 60 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 2 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 arabesque from another, and a arabesque 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 arabesque, 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 arabesque, 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 arabesque 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 arabesque, 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 arabesque, 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 arabesque 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 arabesque 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 arabesque, 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 arabesque, 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 arabesque 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 arabesque from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a arabesque, 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 arabesque, 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 arabesque 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 arabesque 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 arabesque between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a arabesque, 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 arabesque, 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 arabesque 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 arabesque, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a arabesque 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 arabesque, 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 arabesque, 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 arabesque is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "process-and-outcome", "name": "Process, inputs and outcome", "description": "How a arabesque proceeds, what it needs and what it leaves behind.", "rationale": "An activity is known by its steps and its results, and both have to be recordable while it is still running.", "layers": [ { "id": "steps-and-sequence", "name": "Steps and sequence", "description": "The steps of a arabesque, their order and what may run in parallel.", "findings": [ { "id": "steps-and-preconditions", "name": "Steps, preconditions and completion", "description": "What has to be true before each step of a arabesque and what marks it done.", "questions": [ { "id": "steps-and-preconditions-q01", "text": "What identifies and describes a step of a arabesque, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "steps-and-preconditions-q02", "text": "Who or what asserted this about a step of a arabesque, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "steps-and-preconditions-q03", "text": "What may an agent decide or do once a step of a arabesque is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "inputs-and-results", "name": "Inputs, resources and results", "description": "What a arabesque consumes and what it produces.", "findings": [ { "id": "inputs-and-outputs", "name": "Inputs, outputs and side effects", "description": "The resources a arabesque takes and the results it leaves, wanted or not.", "questions": [ { "id": "inputs-and-outputs-q01", "text": "What identifies and describes the inputs and results of a arabesque, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "inputs-and-outputs-q02", "text": "Who or what asserted this about the inputs and results of a arabesque, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "inputs-and-outputs-q03", "text": "What may an agent decide or do once the inputs and results of a arabesque is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "definitions-in-contest", "name": "Definitions and who holds them", "description": "What arabesque is taken to mean, and by whom.", "rationale": "When a field disagrees about a concept, the disagreement is the content. A model that picks one definition silently destroys the information.", "layers": [ { "id": "competing-definitions", "name": "Competing definitions", "description": "The main readings and the traditions behind them.", "findings": [ { "id": "definition-map", "name": "Definitions and their holders", "description": "Each definition with the school or body that holds it.", "questions": [ { "id": "definition-map-q01", "text": "Which definitions of arabesque are in use, and which tradition or body holds each?", "kind": "definition" }, { "id": "definition-map-q02", "text": "What turns on the difference between them in practice?", "kind": "boundary" } ] } ] }, { "id": "operationalisation", "name": "Operationalisation", "description": "How it is measured or applied when it has to be.", "findings": [ { "id": "operational-record", "name": "Measures and proxies", "description": "Instruments and indicators used to stand in for it.", "questions": [ { "id": "operational-record-q01", "text": "How is arabesque operationalised or measured in practice, and by what instrument?", "kind": "measurement" }, { "id": "operational-record-q02", "text": "What does that operationalisation leave out, and when does that matter?", "kind": "boundary" } ] } ] } ] }, { "id": "instances-and-use", "name": "Instances, use and consequence", "description": "What counts as an instance of arabesque and what follows from calling something that.", "rationale": "Applying a concept is an act with consequences, so a model must say what the label licenses and what it does not.", "layers": [ { "id": "instances", "name": "What counts as an instance", "description": "Clear cases, borderline cases and non-cases.", "findings": [ { "id": "instance-tests", "name": "Tests for an instance", "description": "What would settle whether something falls under it.", "questions": [ { "id": "instance-tests-q01", "text": "What would settle whether something is an instance of arabesque?", "kind": "boundary" }, { "id": "instance-tests-q02", "text": "Which borderline cases are argued about, and on what grounds?", "kind": "definition" } ] } ] }, { "id": "consequence", "name": "Consequence of application", "description": "Rights, duties or decisions that follow from the label.", "findings": [ { "id": "consequence-record", "name": "What the label licenses", "description": "What an agent may do once something is classified this way.", "questions": [ { "id": "consequence-record-q01", "text": "What follows practically once something is treated as arabesque?", "kind": "action" }, { "id": "consequence-record-q02", "text": "What must an agent not infer from the label alone?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a arabesque 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 arabesque and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a arabesque, 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 arabesque, 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 arabesque 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 arabesque is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a arabesque, 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 arabesque, 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 arabesque is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] } ] }, "statistics": { "bundles": 6, "layers": 12, "findings": 14, "questions": 38 } } } }