{ "model": { "rank": 1389, "code": "thing-q8196", "model_id": "vr.tr.arabic-alphabet", "name": "Arabic alphabet", "purpose": "Enable an agent to recognise the Arabic alphabet, record its repertoire and writing conventions, assess a representation against an identified convention, and choose transformations that preserve intended distinctions.", "family": "Thing Registry", "category": "Information and virtual systems", "status": "research-draft", "kind": "thing", "plane": "INF", "domain": "INF.MED", "industry": "", "version": "", "url": "/models/thing/q8196/", "tier": 2, "score": 150, "payload": { "layer": "wikidata", "aliases": [ "Kurdish Arabic alphabet" ], "aliasCount": 1, "merged": 1, "knownIn": 150, "facets": null, "markers": [], "lexicalClass": "", "senseRank": null, "alsoRegisteredAs": null, "source": { "dataset": "wikidata", "item": "Q8196", "url": "https://www.wikidata.org/wiki/Q8196", "license": "CC0 1.0" } }, "research": { "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:26:12Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 29.2, "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: 01a07b9d-22b7-73e2-987d-849544e5a673\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Arabic alphabet\nSense to describe: (none recorded)\nDomain code: INF.MED\nAlso known as: (none)\n\n\nContext for this batch of 210 things:\n# Batch 001: 1001 ", "usd": 0, "recall": true }, "codex": { "seconds": 81.9, "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: 01a07b9d-22c6-71d0-ba61-caa21caabc3b\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Arabic alphabet\nRegistry id: vr.tr.arabic-alphabet\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (" } } }, "metaModel": { "id": "THING-Q8196", "registryId": "vr.tr.arabic-alphabet", "name": "Arabic alphabet", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q8196/", "model": { "registry_id": "vr.tr.arabic-alphabet", "name": "Arabic alphabet", "purpose": "Enable an agent to recognise the Arabic alphabet, record its repertoire and writing conventions, assess a representation against an identified convention, and choose transformations that preserve intended distinctions.", "definition": "The Arabic alphabet is the conventional set of 28 basic letters used to write Arabic in a predominantly right-to-left, joining script, structurally classified as an abjad because consonants and long vowels are normally represented while short vowels are usually omitted or indicated by optional marks.", "scope_statement": "This model owns the Arabic alphabet as a conventional writing system for Arabic, specialising the wider alphabet model with Arabic letter identity, joining behaviour, orthographic signs, ordering and representation constraints; it distinguishes this repertoire from the broader Arabic script and its adaptations for other languages.", "in_scope": [ "Arabic letter identities, names, repertoire membership and ordering conventions", "Relationships between letters, contextual forms, ligatures and distinguishing dots", "Arabic-specific use of vowel signs, hamza, shadda and other orthographic marks", "Right-to-left writing, joining constraints and interactions with mixed-direction text", "Digital representations and transformations that affect Arabic letter identity or orthographic distinctions", "Explicitly identified historical, regional and specialised orthographic profiles" ], "out_of_scope": [ "General properties of alphabets and writing systems owned by the wider alphabet model", "Arabic grammar, vocabulary, pronunciation and dialect systems beyond their relationship to written signs", "Additional repertoires for other languages using Arabic script", "Individual manuscripts, books, editions and inscriptions as authored or material objects", "Typeface design, calligraphic artworks and font licensing as independently managed things", "Translation and transliteration systems except where their mappings clarify alphabet boundaries" ], "distinguishing_features": [ "The subject is a conventional repertoire used to write Arabic, rather than every character belonging to the broader Arabic script.", "Consonantal letters and context-dependent vowel representation make the term abjad relevant; the registered name alphabet must not imply obligatory letters for every vowel.", "A letter can have contextual joining forms without those forms becoming separate alphabet members.", "Distinguishing dots can determine letter identity, whereas optional vocalisation marks serve a different orthographic role.", "Arabic text has a right-to-left base direction, but mixed text cannot be represented correctly by simply reversing a character sequence." ], "characteristics": [ { "name": "Orthographic profile", "kind": "category", "unit_or_values": "Named convention with language variety, period, region and specialised use where applicable", "why_it_matters": "Repertoire and acceptable spellings must be assessed against a stated convention." }, { "name": "Repertoire membership", "kind": "relation", "unit_or_values": "Sign related to profile as core letter, orthographic variant, auxiliary sign or excluded extension", "why_it_matters": "Prevents broader Arabic-script characters from being silently treated as Arabic alphabet members." }, { "name": "Letter count", "kind": "measurement", "unit_or_values": "Number of members under an explicit counting rule", "why_it_matters": "A count is interpretable only when treatment of hamza and other disputed or dependent forms is recorded." }, { "name": "Joining behaviour", "kind": "category", "unit_or_values": "Applicable joining class, named standard and exceptional context", "why_it_matters": "Supports recognition of valid connections and diagnosis of broken rendering." }, { "name": "Vocalisation coverage", "kind": "state", "unit_or_values": "Unvocalised, partially vocalised or fully vocalised relative to a declared profile", "why_it_matters": "Missing marks can be conventional rather than evidence of corruption." }, { "name": "Ordering convention", "kind": "category", "unit_or_values": "Named sequence, such as hijai or abjad, with its actual member order", "why_it_matters": "Alphabet teaching order, historical order and software collation need not be interchangeable." }, { "name": "Representation fidelity", "kind": "state", "unit_or_values": "Unchecked, verified for a stated purpose, lossy or ambiguous", "why_it_matters": "A visually plausible rendering may conceal character substitutions or lost distinctions." }, { "name": "Representational equivalence", "kind": "relation", "unit_or_values": "Two forms related as the same letter, encoding equivalent, orthographic alternative or distinct signs under a named rule", "why_it_matters": "Constrains normalisation, search expansion and transcription." } ], "affordances": [ "Classify a sign as an Arabic letter, orthographic mark, contextual form or neighbouring script extension.", "Validate a proposed repertoire and order against an identified Arabic orthographic profile.", "Explain contextual joining and distinguish a shaping failure from a different letter sequence.", "Assess whether removing dots, vowel marks or hamza-related distinctions would lose information.", "Compare encoded and displayed text while preserving logical order and letter identity.", "Choose a documented normalisation or search policy and identify transformations requiring human review." ] }, "sources": [], "structure": { "bundles": [ { "id": "repertoire-and-boundaries", "name": "Repertoire and boundaries", "description": "Establishes which signs belong to the Arabic alphabet under the selected convention.", "rationale": "Arabic alphabet membership must remain distinct from Arabic script coverage and from the generic alphabet concept.", "layers": [ { "id": "alphabet-specialisation", "name": "Alphabet specialisation", "description": "Locates this registered thing within writing-system concepts.", "findings": [ { "id": "arabic-alphabet-sense", "name": "Arabic alphabet sense", "description": "Record the Arabic-language repertoire intended by the entry and its relationship to alphabet, abjad and Arabic script.", "questions": [ { "text": "Which Arabic writing convention defines the repertoire being modelled?", "kind": "definition", "id": "arabic-alphabet-sense-q01" }, { "text": "Which properties are inherited from the wider alphabet model, and which require Arabic-specific treatment?", "kind": "boundary", "id": "arabic-alphabet-sense-q02" } ] } ] }, { "id": "membership-and-counting", "name": "Membership and counting", "description": "Separates alphabet members from related signs and extensions.", "findings": [ { "id": "explicit-repertoire-rule", "name": "Explicit repertoire rule", "description": "Record the member list and the rule used to classify hamza, alif variants, ta marbuta, alif maqsura and lam-alif.", "questions": [ { "text": "Which of these signs are counted as independent letters, variants, auxiliary signs or ligatures in the selected authority?", "kind": "definition", "id": "explicit-repertoire-rule-q01" }, { "text": "What letter count follows from that rule, and which Arabic-script extensions are excluded?", "kind": "measurement", "id": "explicit-repertoire-rule-q02" } ] } ] } ] }, { "id": "letter-identity-and-shaping", "name": "Letter identity and shaping", "description": "Connects abstract letters with visible forms without equating appearance with identity.", "rationale": "Arabic recognition depends on distinguishing identity-bearing features from contextual shaping and stylistic variation.", "layers": [ { "id": "dots-and-letter-identity", "name": "Dots and letter identity", "description": "Records how dots and base shapes distinguish letters.", "findings": [ { "id": "identity-bearing-features", "name": "Identity-bearing features", "description": "Identify the features needed to distinguish letters within a specified writing tradition.", "questions": [ { "text": "Which letters share similar base shapes, and which dot patterns distinguish them in this profile?", "kind": "definition", "id": "identity-bearing-features-q01" }, { "text": "When dots are absent or unclear, what contextual evidence is required before assigning a letter identity?", "kind": "action", "id": "identity-bearing-features-q02" } ] } ] }, { "id": "joining-and-ligatures", "name": "Joining and ligatures", "description": "Records contextual forms, connection constraints and multi-letter glyphs.", "findings": [ { "id": "contextual-form-resolution", "name": "Contextual form resolution", "description": "Relate visible forms to underlying letters, including letters that interrupt joining and ligatures such as lam-alif.", "questions": [ { "text": "Which joining contexts are available for each letter, and which apparent connections are stylistic?", "kind": "definition", "id": "contextual-form-resolution-q01" }, { "text": "How can an agent recover the underlying letter sequence from a ligature or contextual glyph without treating it as a new alphabet member?", "kind": "action", "id": "contextual-form-resolution-q02" } ] } ] } ] }, { "id": "orthographic-signs-and-vocalisation", "name": "Orthographic signs and vocalisation", "description": "Models the roles of written vowel information and supplementary orthographic signs.", "rationale": "The presence, absence and placement of Arabic marks affect interpretation, while their status differs from that of core letters.", "layers": [ { "id": "vowel-representation", "name": "Vowel representation", "description": "Distinguishes vowel-related letter uses from added vocalisation marks.", "findings": [ { "id": "vocalisation-policy", "name": "Vocalisation policy", "description": "Record how the profile uses alif, waw, ya and short-vowel signs, and what omission of signs permits.", "questions": [ { "text": "How does the profile distinguish consonantal and vowel-related uses of these letters?", "kind": "definition", "id": "vocalisation-policy-q01" }, { "text": "Which marks are expected for the intended use, and how is vocalisation completeness assessed?", "kind": "measurement", "id": "vocalisation-policy-q02" } ] } ] }, { "id": "hamza-and-additional-marks", "name": "Hamza and additional marks", "description": "Captures sign-specific distinctions that generic diacritic handling would obscure.", "findings": [ { "id": "mark-specific-interpretation", "name": "Mark-specific interpretation", "description": "Record the profile's treatment of hamza and its carriers, madda, shadda, sukun and specialised signs.", "questions": [ { "text": "Which distinctions involving hamza, its carriers and other marks are required by the selected orthography?", "kind": "definition", "id": "mark-specific-interpretation-q01" }, { "text": "Which marks can be omitted for a specified task, and which omissions change spelling or remove needed reading information?", "kind": "action", "id": "mark-specific-interpretation-q02" } ] } ] } ] }, { "id": "direction-and-digital-representation", "name": "Direction and digital representation", "description": "Preserves Arabic text identity across storage, shaping, display and comparison.", "rationale": "Arabic display order, joining and character sequences interact in ways that can produce plausible-looking but incorrect text.", "layers": [ { "id": "logical-and-visual-order", "name": "Logical and visual order", "description": "Distinguishes stored sequence from displayed arrangement.", "findings": [ { "id": "mixed-direction-integrity", "name": "Mixed-direction integrity", "description": "Record expected reading order and the effect of embedded numbers, Latin text, punctuation and directional controls.", "questions": [ { "text": "What logical sequence should the text preserve when Arabic appears beside numbers or left-to-right text?", "kind": "definition", "id": "mixed-direction-integrity-q01" }, { "text": "Which display and copy-paste checks would expose reordered characters or misplaced punctuation?", "kind": "action", "id": "mixed-direction-integrity-q02" } ] } ] }, { "id": "encoding-and-equivalence", "name": "Encoding and equivalence", "description": "Separates standard encoding equivalence from task-specific substitutions.", "findings": [ { "id": "controlled-text-transformation", "name": "Controlled text transformation", "description": "Record encoding, presentation forms, combining marks, tatweel and joining controls before choosing transformations.", "questions": [ { "text": "Which character sequences are equivalent under the identified encoding standard, and which merely look similar?", "kind": "boundary", "id": "controlled-text-transformation-q01" }, { "text": "For this task, may an agent fold alif variants, remove vocalisation or tatweel, or alter joining controls, and what information would each operation lose?", "kind": "action", "id": "controlled-text-transformation-q02" } ] } ] } ] }, { "id": "ordering-and-attested-variation", "name": "Ordering and attested variation", "description": "Makes order and convention-dependent differences explicit and traceable.", "rationale": "A single unqualified modern repertoire cannot adequately represent historical ordering or regional and specialised practice.", "layers": [ { "id": "alphabetic-order", "name": "Alphabetic order", "description": "Records named member sequences and their intended applications.", "findings": [ { "id": "order-versus-collation", "name": "Order versus collation", "description": "Distinguish hijai and abjad sequences from rules used to sort complete words.", "questions": [ { "text": "Which authority supplies the precise hijai or abjad sequence used by this profile?", "kind": "provenance", "id": "order-versus-collation-q01" }, { "text": "Which additional rules govern sorting words containing hamza forms, vowel marks or other orthographic variants?", "kind": "boundary", "id": "order-versus-collation-q02" } ] } ] }, { "id": "historical-and-specialised-profiles", "name": "Historical and specialised profiles", "description": "Bounds differences by period, region and use.", "findings": [ { "id": "attested-profile-differences", "name": "Attested profile differences", "description": "Record sourced differences in dotting, sign inventory and orthographic practice, including specialised Quranic usage where applicable.", "questions": [ { "text": "Which dated or institutionally identified sources establish each claimed regional, historical or specialised difference?", "kind": "provenance", "id": "attested-profile-differences-q01" }, { "text": "Does the difference change repertoire or orthography, or does it belong to calligraphic style or an individual document?", "kind": "boundary", "id": "attested-profile-differences-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-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is recalled knowledge, not source-verified research.", "The conventional count of 28 needs qualification when discussing hamza, derived forms and pedagogical counting practices.", "The sense assumed is the basic alphabet used for Arabic, not every character used by Arabic-script languages." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "ISO 15924", "value_or_pattern": "Arab; 160", "note": "Identifies the Arabic script, including its use beyond Arabic, rather than this alphabet alone." }, { "scheme": "Unicode", "value_or_pattern": "Arabic block: U+0600-U+06FF", "note": "Contains core Arabic letters, marks and other characters; additional blocks support the wider script. The block is not an alphabet inventory." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "The Unicode Standard, issued by the Unicode Consortium, specifies character encoding and properties for Arabic text.", "Unicode Standard Annex #9, Unicode Bidirectional Algorithm, issued by the Unicode Consortium, specifies bidirectional text ordering.", "ISO 15924, issued by ISO, provides codes for identifying scripts, including Arabic." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Writing Arabic in education, administration, publishing and everyday communication.", "Writing Qur'anic text with specialized orthographic and recitation marks.", "Representing Arabic in digital documents, messaging, search and typesetting.", "Providing the letter-system foundation for adaptations used to write languages such as Persian and Urdu." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Conventional basic-letter inventory", "typical_range": "28", "unit": "letters" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Omitted short-vowel marks can leave words ambiguous without linguistic context.", "Missing or misrecognized dots can change letter identity, particularly in handwriting and optical character recognition.", "Incorrect joining or contextual shaping can produce broken or misleading text.", "Mixed Arabic, Latin text and numerals can display in an unintended order when bidirectional processing is mishandled.", "Inappropriate normalization of hamza-bearing letters, alif variants or other distinctions can impair spelling fidelity and search." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Maghrebi manuscript and calligraphic traditions use some letter forms and dotting conventions that differ from common eastern practices, notably for fa and qaf.", "Qur'anic orthography and marking conventions differ in some respects from ordinary modern Arabic spelling and typography.", "Arabic-script alphabets for other languages add or modify letters; these are adaptations of the script rather than regional inventories of the Arabic alphabet." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "alphabet", "difference": "The broader registry concept concerns letter-based writing systems generally; this entry specifies the Arabic inventory and conventions, while noting its stricter classification as an abjad." }, { "name": "abjad", "difference": "An abjad is a type of writing system organized primarily around consonant letters; the Arabic alphabet is a particular instance." }, { "name": "Arabic script", "difference": "The script encompasses graphic conventions and characters used across multiple languages; the Arabic alphabet is the basic letter inventory for Arabic." }, { "name": "Arabic language", "difference": "Arabic is a language with spoken and written varieties; the alphabet is a means of representing it in writing." }, { "name": "Arabic calligraphy", "difference": "Calligraphy concerns the artistic formation and arrangement of writing; styles such as Naskh and Kufic do not constitute separate basic alphabets." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Arabic alphabet this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which authoritative orthographic profile should serve as the default when the registry supplies no definition?", "How should the publication count and classify hamza, alif variants, ta marbuta and alif maqsura while preserving alternative documented conventions?", "Which historical and regional practices need explicit profiles, and which should remain references to neighbouring models?", "How much specialised Quranic marking belongs in this alphabet model rather than a linked orthographic or recitation model?", "Which encoding-standard version and task-specific comparison policies should govern digital equivalence and permitted information loss?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 18, "questions": 28 } }, "draft": { "generator": "vr.draft.v3", "status": "draft-generated", "researched": false, "archetype": "work, medium or creative form", "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 Arabic alphabet, record what state it is in, and decide what may be done with it.", "whatItIs": "Enable an agent to recognise the Arabic alphabet, record its repertoire and writing conventions, assess a representation against an identified convention, and choose transformations that preserve intended distinctions.", "characteristics": { "substance": "information", "origin": "conceptual", "agency": "inert" }, "whatYouCanDoWithIt": [ "read and interpreted", "observed and measured" ], "distinguishingFeatures": [ "Names folded into this entry, which a task may need to split apart again: Kurdish Arabic alphabet.", "1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.", "Described in 150 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 Arabic alphabet, and on what evidence are they told apart?" ], "whatItIsMadeOf": "content that has to be carried by something else", "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": [ "read it and act on what it says", "observe it, measure it, record its state" ], "howItIsRecognised": [ "What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it." ], "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": [ "Kurdish Arabic alphabet" ] } ], "standing": "Described in 150 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 Arabic alphabet from another, and a Arabic alphabet 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 Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 Arabic alphabet 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 Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 Arabic alphabet from the things most often confused with it.", "questions": [ { "id": "distinguishing-features-q01", "text": "What identifies and describes what distinguishes a Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 Arabic alphabet 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 Arabic alphabet between them.", "questions": [ { "id": "stages-and-transitions-q01", "text": "What identifies and describes the lifecycle of a Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 Arabic alphabet, how often and by whom.", "findings": [ { "id": "observation-record", "name": "Observation record", "description": "How an observation of a Arabic alphabet 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 Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "content-and-access", "name": "Content, encoding and access", "description": "What a Arabic alphabet says, how it is encoded and who may read it.", "rationale": "An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.", "layers": [ { "id": "content-and-encoding", "name": "Content and encoding", "description": "The content itself, its format and its language.", "findings": [ { "id": "content-and-format", "name": "Content, format and language", "description": "What a Arabic alphabet contains and in what form it is held.", "questions": [ { "id": "content-and-format-q01", "text": "What identifies and describes the content of a Arabic alphabet, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "content-and-format-q02", "text": "Who or what asserted this about the content of a Arabic alphabet, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "content-and-format-q03", "text": "What may an agent decide or do once the content of a Arabic alphabet is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] }, { "id": "access-and-rights", "name": "Access, rights and retention", "description": "Who may read, copy or change it, and for how long it is kept.", "findings": [ { "id": "access-rules", "name": "Access rules and retention", "description": "The permissions attached to a Arabic alphabet and the period it survives.", "questions": [ { "id": "access-rules-q01", "text": "What identifies and describes access to a Arabic alphabet, and in what units or vocabulary?", "kind": "definition", "answer_data": [ "identifiers", "types and classes", "values with units", "explicit unknowns" ] }, { "id": "access-rules-q02", "text": "Who or what asserted this about access to a Arabic alphabet, by which method, and when was it true?", "kind": "provenance", "answer_data": [ "authority", "method", "evidence", "event time", "knowledge time" ] }, { "id": "access-rules-q03", "text": "What may an agent decide or do once access to a Arabic alphabet is known, and what must it refuse?", "kind": "action", "answer_data": [ "permitted actions", "preconditions", "refusals", "escalation" ] } ] } ] } ] }, { "id": "work-and-manifestation", "name": "Work, version and copy", "description": "Which level of Arabic alphabet a statement is about.", "rationale": "The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.", "layers": [ { "id": "levels", "name": "Levels of the thing", "description": "Work, expression, manifestation and item, in plain terms.", "findings": [ { "id": "level-rules", "name": "What belongs at each level", "description": "Which facts hold for the work and which only for one copy.", "questions": [ { "id": "level-rules-q01", "text": "For Arabic alphabet, which facts belong to the work itself, which to a version, and which to a single copy?", "kind": "boundary" }, { "id": "level-rules-q02", "text": "What identifier exists at each level, and which one is being cited?", "kind": "definition" } ] } ] }, { "id": "versions", "name": "Versions, editions and variants", "description": "How versions differ and which is canonical to whom.", "findings": [ { "id": "version-record", "name": "Versions and canonicity", "description": "Differences that matter and who calls one authoritative.", "questions": [ { "id": "version-record-q01", "text": "Which versions or editions of Arabic alphabet exist, and how do they differ substantively?", "kind": "definition" }, { "id": "version-record-q02", "text": "Who treats which version as authoritative, and for what purpose?", "kind": "provenance" } ] } ] } ] }, { "id": "authorship-and-rights", "name": "Authorship, rights and permitted use", "description": "Who made Arabic alphabet and what may be done with it.", "rationale": "Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.", "layers": [ { "id": "authorship", "name": "Authorship and contribution", "description": "Who contributed what, and in what capacity.", "findings": [ { "id": "contribution-record", "name": "Contributors and roles", "description": "The people and bodies behind it, with their roles.", "questions": [ { "id": "contribution-record-q01", "text": "Who authored or contributed to Arabic alphabet, in what roles, and how is that attested?", "kind": "provenance" }, { "id": "contribution-record-q02", "text": "Where authorship is disputed or anonymous, what is recorded instead?", "kind": "boundary" } ] } ] }, { "id": "rights", "name": "Rights and permissions", "description": "Which rights subsist, where, until when, and what they permit.", "findings": [ { "id": "rights-record", "name": "Rights, term and permitted acts", "description": "The regime in force and what it allows.", "questions": [ { "id": "rights-record-q01", "text": "What rights subsist in Arabic alphabet, in which jurisdictions, and until when?", "kind": "definition" }, { "id": "rights-record-q02", "text": "Which acts are permitted without further permission, and which must an agent refuse?", "kind": "action" } ] } ] } ] }, { "id": "provenance-and-evidence", "name": "Provenance, evidence and time", "description": "Where every claim about a Arabic alphabet 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 Arabic alphabet and how confident it is.", "questions": [ { "id": "claim-provenance-q01", "text": "What identifies and describes a claim about a Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 Arabic alphabet is retired without being erased.", "questions": [ { "id": "validity-and-supersession-q01", "text": "What identifies and describes the validity of a claim about a Arabic alphabet, 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 Arabic alphabet, 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 Arabic alphabet 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 } } } }