{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-07T11:27:14Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 17.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: 01a07b9e-62d2-73c1-b673-df91cc0b3f66\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: T/t\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 registered t", "usd": 0.0, "recall": true }, "codex": { "seconds": 62.1, "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: 01a07b9e-62d0-7c71-a69a-7a4dc8a308b8\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: T/t\nRegistry id: vr.tr.t-t\nPlane / domain: INF / INF.MED\nRegistry definition: (none recorded)\nNames folded into this entry: (none)\n\n\nContext for this" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T11:00:00Z", "ingestedAt": "2026-10-06T08:05:31+00:00", "fields": [ "agent_conduct", "ethics", "owners", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:33+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q9813", "registryId": "vr.tr.t-t", "name": "T/t", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "INF.MED" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q9813/", "model": { "registry_id": "vr.tr.t-t", "name": "T/t", "purpose": "Enable an AI agent to recognise, describe and handle T/t as a letter while distinguishing its identity from its glyphs, linguistic uses and context-dependent symbolic meanings.", "definition": "Interpreted as the Latin letter, T/t is the uppercase-lowercase pair occupying the twentieth position in the modern English alphabet.", "scope_statement": "Provisionally interprets T/t as the paired uppercase and lowercase forms of the Latin letter T, owning their identity, representation and contextual interpretation; the registry provides no definition confirming this sense.", "in_scope": [ "Identity of T and t as case forms of one Latin letter", "Distinction between the letter, its encoded representations and its visible glyphs", "Language-dependent uses of T/t in spelling", "Context-dependent use of T or t as a symbol or abbreviation", "Recognition and transformation of occurrences of T/t" ], "out_of_scope": [ "The Latin alphabet as a complete writing system", "Full spelling and pronunciation systems of individual languages", "Quantities, entities or concepts denoted by a contextual T or t", "Typeface designs and font licensing as independent resources", "Creative works whose title happens to be T/t" ], "distinguishing_features": [ "A qualifying occurrence functions as Latin T or t, rather than merely resembling either glyph.", "Uppercase T and lowercase t share letter identity, but substituting one for the other may change the meaning of a symbol or identifier.", "A mathematical or technical T/t occurrence needs a local definition before its referent can be identified.", "The slash in the registry label is provisionally treated as separating case forms, rather than as part of a literal three-character expression.", "A font-specific drawing of T or t is a glyph representing the letter, rather than a separate letter identity." ], "characteristics": [ { "name": "Registry sense resolution", "kind": "state", "unit_or_values": "unresolved | supported as Latin letter | alternative sense established", "why_it_matters": "The missing definition makes sense confirmation a prerequisite for accepting this model." }, { "name": "Case form", "kind": "category", "unit_or_values": "uppercase T | lowercase t | case pair | unresolved", "why_it_matters": "Case can be typographic, orthographic or semantically significant." }, { "name": "Encoded representation", "kind": "relation", "unit_or_values": "Link to the observed character sequence and its encoding", "why_it_matters": "Visual resemblance alone cannot establish character identity." }, { "name": "Usage role", "kind": "category", "unit_or_values": "letter in text | letter name | abbreviation | defined symbol | unresolved", "why_it_matters": "The role determines how an agent should read and manipulate an occurrence." }, { "name": "Language and orthographic context", "kind": "relation", "unit_or_values": "Language, writing convention and surrounding text", "why_it_matters": "Pronunciation and spelling behaviour cannot be assigned universally to T/t." }, { "name": "Transformation permission", "kind": "state", "unit_or_values": "case conversion permitted | exact form required | unresolved", "why_it_matters": "Changing case or substituting a visually similar character can alter meaning or break matching." } ], "affordances": [ "Classify an occurrence as uppercase T, lowercase t or an unresolved lookalike.", "Associate T and t for letter-level searches while preserving their observed forms.", "Link a linguistic occurrence to its language-specific spelling and pronunciation context.", "Resolve a symbolic occurrence against its surrounding definition or notation convention.", "Convert case when the context permits and retain the original representation.", "Flag ambiguous recognition or unsupported interpretation for review." ], "agent_conduct": { "may": [ "Identify the letter T in its upper and lower case forms.", "Explain its history and uses, citing sources." ], "must_not": [ "Confuse it with similar letters of other scripts where the difference matters.", "Use the letter in ways that impersonate a trademark.", "Present folk origins of the letter as history." ], "requires_human": [ "Choosing letter forms for official identifiers." ] }, "ethics": { "considerations": [ "Letters are shared by everyone and confusion causes errors in names and codes.", "Look-alike letters from other scripts are used to spoof web addresses and deceive people." ], "affected_parties": [ "Readers and writers", "Learners" ] }, "owners": { "steward": "Nobody: a letter held in common.", "master_systems": [] }, "visual_identification": [ "Upper case is a vertical stroke topped by a horizontal bar; lower case has a shorter crossbar." ], "what_it_is_for": [ "T and t are used in written languages that employ the Latin alphabet, including English.", "They also occur in identifiers, abbreviations and technical notation, where meaning depends on context and capitalization." ], "standards_and_regulation": [ "The Unicode Standard, issued by the Unicode Consortium, assigns U+0054 to LATIN CAPITAL LETTER T and U+0074 to LATIN SMALL LETTER T.", "ISO/IEC 10646, issued jointly by the International Organization for Standardization and the International Electrotechnical Commission, includes both letters in the Universal Coded Character Set." ], "failure_modes_and_hazards": [ "Confusion with similar glyphs from other scripts can cause identity mismatches or deceptive identifiers.", "Incorrect case conversion can alter identifiers or technical symbols in systems where uppercase and lowercase have different meanings.", "Treating a context-dependent use of T or t as an ordinary letter can corrupt interpretation of units, variables or abbreviations." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q9813: T/t", "url": "https://www.wikidata.org/wiki/Q9813", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: T", "url": "https://en.wikipedia.org/wiki/T", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "letter-identity", "name": "Letter identity", "description": "Establishes whether the registry entry denotes the Latin letter and how its case forms belong together.", "rationale": "The label T/t suggests a case pair, but the registry has not supplied a definition.", "layers": [ { "id": "registry-sense", "name": "Registry sense", "description": "Tests the provisional reading of the entry.", "findings": [ { "id": "case-pair-interpretation", "name": "Case-pair interpretation", "description": "Record evidence that T/t names a letter through its two case forms, rather than a title, abbreviation or literal expression.", "questions": [ { "text": "Does the originating registry record identify T/t as a Latin letter?", "kind": "definition", "id": "case-pair-interpretation-q01" }, { "text": "Does the slash separate case forms, or belong to the registered name itself?", "kind": "boundary", "id": "case-pair-interpretation-q02" } ] } ] }, { "id": "case-relationship", "name": "Case relationship", "description": "Separates shared letter identity from the significance of an observed case form.", "findings": [ { "id": "identity-versus-case", "name": "Identity versus case", "description": "Represent T and t as related forms without presuming that they are interchangeable in every occurrence.", "questions": [ { "text": "Is this occurrence being described at letter level or as an exact case-sensitive character?", "kind": "boundary", "id": "identity-versus-case-q01" }, { "text": "Would replacing T with t, or t with T, change the interpretation in this context?", "kind": "action", "id": "identity-versus-case-q02" } ] } ] } ] }, { "id": "characters-and-glyphs", "name": "Characters and glyphs", "description": "Connects the letter to digital characters and visible forms without conflating them.", "rationale": "An agent may encounter T/t as text, handwriting or an image, each providing different evidence of identity.", "layers": [ { "id": "encoded-identity", "name": "Encoded identity", "description": "Records what characters an observed digital sequence actually contains.", "findings": [ { "id": "character-sequence", "name": "Character sequence", "description": "Preserve the underlying sequence and distinguish ordinary Latin T/t from lookalikes, styled symbols and modified forms.", "questions": [ { "text": "Which encoded characters constitute the observed T-like or t-like form?", "kind": "measurement", "id": "character-sequence-q01" }, { "text": "Is the occurrence an ordinary Latin letter, a separately encoded symbol or a sequence with additional marks?", "kind": "boundary", "id": "character-sequence-q02" } ] } ] }, { "id": "visual-recognition", "name": "Visual recognition", "description": "Evaluates recognition where character identity must be inferred from appearance.", "findings": [ { "id": "glyph-evidence", "name": "Glyph evidence", "description": "Record the image or writing sample supporting recognition and any competing reading.", "questions": [ { "text": "What visible and contextual evidence supports reading this mark as T or t?", "kind": "provenance", "id": "glyph-evidence-q01" }, { "text": "Could this mark instead be a cross, another script's character or a different handwritten letter?", "kind": "boundary", "id": "glyph-evidence-q02" } ] } ] } ] }, { "id": "linguistic-and-symbolic-use", "name": "Linguistic and symbolic use", "description": "Determines what an occurrence of T/t does in its surrounding expression.", "rationale": "Letter identity alone does not supply pronunciation, abbreviation expansion or a technical referent.", "layers": [ { "id": "orthographic-use", "name": "Orthographic use", "description": "Places the letter within a particular language and spelling context.", "findings": [ { "id": "contextual-reading", "name": "Contextual reading", "description": "Distinguish the letter's name from its contribution to a written word, including combinations with neighbouring letters.", "questions": [ { "text": "Which language and orthographic convention govern this occurrence of T/t?", "kind": "definition", "id": "contextual-reading-q01" }, { "text": "Is the requested reading the letter name or its pronunciation within the surrounding word?", "kind": "boundary", "id": "contextual-reading-q02" } ] } ] }, { "id": "notation-use", "name": "Notation use", "description": "Links symbolic and abbreviated occurrences to their local meanings.", "findings": [ { "id": "locally-defined-meaning", "name": "Locally defined meaning", "description": "Attach a meaning to a particular use of T or t only where a definition or applicable convention supports it.", "questions": [ { "text": "What nearby definition or notation convention establishes what this T or t denotes?", "kind": "provenance", "id": "locally-defined-meaning-q01" }, { "text": "Does the notation distinguish T from t or assign meaning through styling, subscripts or surrounding syntax?", "kind": "boundary", "id": "locally-defined-meaning-q02" } ] } ] } ] }, { "id": "matching-and-transformation", "name": "Matching and transformation", "description": "Governs searches, case changes and transcription of T/t occurrences.", "rationale": "Useful letter-level operations must preserve distinctions required by exact text and symbolic notation.", "layers": [ { "id": "matching-policy", "name": "Matching policy", "description": "Defines which forms count as equivalent for a particular task.", "findings": [ { "id": "task-specific-equivalence", "name": "Task-specific equivalence", "description": "Make equivalence explicit when counting or retrieving T/t across case forms and visual variants.", "questions": [ { "text": "Should this search match T and t together or require the exact observed form?", "kind": "action", "id": "task-specific-equivalence-q01" }, { "text": "Should marked or styled forms be included, and what task-specific rule justifies their inclusion?", "kind": "boundary", "id": "task-specific-equivalence-q02" } ] } ] }, { "id": "editing-and-transcription", "name": "Editing and transcription", "description": "Controls changes to observed forms and the treatment of uncertain readings.", "findings": [ { "id": "meaning-preserving-change", "name": "Meaning-preserving change", "description": "Assess whether a case conversion or transcription correction preserves the intended text or notation.", "questions": [ { "text": "What evidence permits changing this occurrence's case or replacing a suspected lookalike with Latin T/t?", "kind": "action", "id": "meaning-preserving-change-q01" }, { "text": "How will the original form and any unresolved reading be retained for review?", "kind": "provenance", "id": "meaning-preserving-change-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": [ "No sense is recorded; the Latin-letter interpretation is provisional, and INF.MED alone does not establish it.", "Check whether the registry instead intends a titled work, abbreviation or specialised notation before adopting this description." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of T/t 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": "Unicode", "value_or_pattern": "U+0054", "note": "LATIN CAPITAL LETTER T." }, { "scheme": "Unicode", "value_or_pattern": "U+0074", "note": "LATIN SMALL LETTER T." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of T/t 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, encodes uppercase T and lowercase t as distinct characters.", "ISO/IEC 10646, issued by ISO and IEC, includes these characters in the Universal Coded Character Set." ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of T/t 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 words in languages that use the Latin script.", "Alphabetical ordering and indexing.", "Representing context-dependent abbreviations, variables and symbols." ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of T/t 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": [ "Confusing a letter with a technical symbol that uses the same written form.", "Losing meaningful distinctions between T and t through case conversion." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of T/t 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": [ "Letter names, pronunciation and sound correspondences vary across languages using the Latin script." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of T/t 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": "Glyph", "difference": "A glyph is a particular visual rendering; T and t are characters that can appear in many typefaces and handwriting styles." }, { "name": "Cyrillic letter Т/т", "difference": "It belongs to the Cyrillic script and has separate character encodings, despite possible visual similarity." }, { "name": "Greek letter Τ/τ", "difference": "Tau belongs to the Greek alphabet and has separate character encodings." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of T/t this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Does the originating registry identifier confirm the Latin-letter sense of T/t, or identify a specific work or another entity?", "Does the registry intentionally include modified and styled forms under T/t, or give them separate entries?", "Which authoritative character and case-mapping references should anchor the representation rules?", "Which languages and notation domains must the initial model support with researched contextual rules?", "Does an existing Vercy model already own Latin-letter identity or this specific letter, requiring a link instead of a separate publication?" ], "statistics": { "bundles": 5, "layers": 9, "findings": 15, "questions": 23 } }