============================================================ OPERA LITTERA — STANDARD CHARACTER ANALYSIS PROTOCOL AGLA / LINGUISTIC STACK — MULTISCRIPT LITTERA EXTENSION Version: 0.2.0-OPERA-LITTERA-PHOENICIAN-CONNECTED-MULTISCRIPT Status: PROVISIONAL — MULTIPURPOSE LINGUISTIC STACK CANDIDATE Authority: CODEX / LOCAL ARTIFACT PARSING NODE Class: AGLA / OPERA / LITTERA / LINGUISTICA / PALEOGRAPHIA Scope: • define standard analysis protocol for one written sign / letter • fill missing character-analysis layer in the general linguistic stack • preserve RADIX-first discipline • support Hebrew, Greek, Latin, and other Phoenician-connected scripts • admit Old Italic, Etruscan, Gothic, and Runic when Unicode locus is reliable • support later OPERA LITTERAE IMAGO ROTATA • prevent symbolic, theological, gematric, and traditional collapse Mutation Policy: VERSION-CONTROLLED ONLY ============================================================ I. Purpose OPERA LITTERA defines the standard linguistic, paleographic, phonemic, morphemic, material, and media-historical analysis for one written sign, letter, grapheme, or script unit at a time. This protocol fills the missing character-analysis protocol inside the linguistic stack. The current normalized linguistic stack is not Hebrew-bound; Hebrew is a supported profile inside a broader Phoenician-connected script field. The required direction is: FORM / LETTER → LITTERA → RADIX → MORPHOLOGIA → PHILOLOGIA → EXPANSIO The letter protocol does not replace RADIX. It supplies the missing EX LITTERA layer required before letter-based structural claims can be stabilized. The interlanguage protocol also requires future mappings to operate EX LITTERA, grounded in letter structure rather than mere dictionary equivalence. Compressed: OPERA LITTERA = one-sign linguistic + graphemic + phonemic + morphemic + paleographic + media-historical investigation. II. Position in the stack RADIX STACK: WORD → RADIX → MORPHOLOGIA → PHILOLOGIA → EXPANSIO SEMANTICA LITTERA STACK: LETTER → GRAPHEME → HISTORICAL GRAPHEME → PHONEME → MORPHEME → MEDIA-GRAPHEME → ROTATA when authorized OPERA LITTERA is not yet a Sephirotic projection. It is a linguistic and paleographic operation. LETTER → LITTERA ANALYSIS → possible RADIX support not: LETTER → SYMBOLIC MEANING → SEPHIROT This also respects the Yetziratic restriction that letter analysis remains separate from Sephirot constitution unless explicitly authorized. Any Hebrew / Kabbalah / Sephirot use remains a downstream profile or interface, not universal LITTERA law. III. Core law ============================================================ OPERA LITTERA — CORE LAW ============================================================ A written sign must be analyzed first as: grapheme phoneme morpheme historical form material inscription unit media-specific writing/reading operator Unicode-located script unit where applicable not as: symbol doctrine gematric number mystical essence later Kabbalistic path theological sign ============================================================ The active hierarchy is: form → sound → grammatical function → historical development → material behavior → media behavior → controlled comparison Not: tradition → symbolic essence → letter meaning This aligns with the stack’s tradition discipline: tradition is analyzable material, but it is neither authority nor anti-authority. AREPO TRADITIO explicitly fixes the unilateral direction: AGLA operators may interpret traditional material, but traditional material may not define AGLA operators. IV. Standard letter format Every OPERA LITTERA begins with: [AGLA VALUE] — [SCRIPT GLYPH] — [Letter / Sign Name] — [Phonetic / Transliteration] Hebrew example: O — ע — AYIN — ayin / ʿayin Project mapping when declared: ע = O Greek example: A — Α / α — ALPHA — alpha Latin example: A — A / a — A — a For each letter, include: 1. script glyph 2. AGLA transliteration value 3. letter-name variants 4. phonetic approximation 5. scholarly transliteration if relevant 6. Unicode designation and code point 7. script profile 8. Phoenician-connection relation type where relevant V. Source discipline Primary source: Wiktionary Secondary source: Wikipedia Allowed secondary support: Unicode charts Wikimedia Commons script-history tables epigraphic charts uploaded image references Forbidden default sources: Sefer Yetzirah Kabbalah books gematria tables theological databases later symbolic correspondences Exception: Sefer Yetzirah or traditional material may be used only if the operation is explicitly reclassified as COMPARATIO, TRADITIO, or SEPHIROT YETZIRATICA interface work. All source classes must be marked: LINGUISTIC SOURCE PALEOGRAPHIC SOURCE COMPARATIVE SCRIPT SOURCE MEDIA-HISTORICAL SOURCE COMPARATIO MATERIAL FORBIDDEN AUTHORITY V.A Script scope and Unicode locus Mandatory first-class profiles: PHOENICIAN HEBREW GREEK LATIN Admissible extended profiles when evidence and Unicode locus are reliable: OLD_ITALIC ETRUSCAN GOTHIC RUNIC Relation types: DIRECT_DESCENT INDIRECT_DESCENT SCRIPT_CONTACT STRUCTURAL_ANALOGY UNCERTAIN_RELATION Control rule: A Phoenician connection records lineage, adaptation, or contact. It does not create one-to-one letter equivalence. Minimum Unicode loci: PHOENICIAN: U+10900..U+1091F right-to-left HEBREW: U+0590..U+05FF right-to-left includes niqqud, cantillation, final forms, matres lectionis GREEK: U+0370..U+03FF U+1F00..U+1FFF left-to-right includes accents, breathings, archaic letters where attested LATIN: U+0000..U+007F U+0080..U+00FF U+0100..U+017F U+0180..U+024F U+1E00..U+1EFF left-to-right includes case, diacritics, historical and epigraphic variants OLD_ITALIC: U+10300..U+1032F direction profile-dependent; often right-to-left or boustrophedon ETRUSCAN: Unicode locus: OLD_ITALIC, U+10300..U+1032F treat as language / orthographic profile inside the Old Italic block GOTHIC: U+10330..U+1034F left-to-right Greek derivation primary unless Latin / Runic contact is specifically evidenced RUNIC: U+16A0..U+16FF direction inscription-dependent identify futhark / corpus profile when possible If the signs cannot be reliably located in Unicode or a declared encoding, OPERA LITTERA may describe the limitation but must not emit a fully normalized LITTERA object. VI. Mandatory sections per letter ============================================================ STANDARD OUTPUT STRUCTURE — OPERA LITTERA ============================================================ I. Standard Format II. Current Grapheme III. Historical Grapheme IV. Directional / Ergonomic Grapheme Function V. Glyph-Name Functional Intersection VI. Material / Historiographic Grapheme Function VII. Media / Reading-Writing Function VIII. Phoneme IX. Morpheme — Language / Script Profile Domain X. Comparative Script / Language Notes XI. Structural Summary XII. Uncertainty Register XIII. Prohibited Import Check XIV. Final Formula ============================================================ VII. Section definitions VII.1 Standard Format Purpose: identify the sign under the declared script profile and project transliteration standard. Required fields: AGLA LETTER: SCRIPT GLYPH: LETTER NAME: PHONETIC: SCHOLARLY TRANSLITERATION: ALPHABETIC POSITION: SCRIPT PROFILE: UNICODE LOCUS: PROJECT MAPPING: Example: A — Α / α — ALPHA — alpha Script profile: GREEK Unicode locus: U+0391 / U+03B1 Project mapping: Α / α = A Hebrew example: I — י — YOD — yod / yodh / yōḏ י = I VII.2 Current Grapheme Purpose: analyze the current attested form under the declared script profile. Required fields: CURRENT FORM: FINAL FORM: POSITIONAL FORMS: UNICODE: ORTHOGRAPHIC ROLE: SCRIPT DIRECTION: CASE BEHAVIOR: VOWEL REPRESENTATION: For Hebrew final-form letters: כ → ך מ → ם נ → ן פ → ף צ → ץ Sofit law: Sofit forms are square-script positional forms. They must not be projected backward into Proto-Sinaitic, Phoenician, or Paleo-Hebrew unless evidence is supplied. VII.3 Historical Grapheme Purpose: trace the letter across earlier script stages. Mandatory stages when available: 1. Proto-Sinaitic / Proto-Canaanite 2. Phoenician 3. Paleo-Hebrew 4. Aramaic 5. Square Hebrew 6. Nabataean / Arabic branch where relevant 7. Greek / Coptic branch where relevant 8. Old Italic / Etruscan branch where relevant 9. Latin branch where relevant 10. Gothic branch where relevant 11. Runic branch where relevant Required fields: SCRIPT STAGE: GLYPH: NAME: PHONEMIC VALUE: SOURCE-FIELD: STATUS: NOTES: Status classes: ADMISSIBLE SOURCE-SUPPORTED RECONSTRUCTED PROVISIONAL SOURCE-SPLIT DEFERRED FORBIDDEN VII.4 Directional / Ergonomic Grapheme Function Purpose: test whether the letter-form participates in direction, reading orientation, line movement, facing, or ergonomic use. Questions: Does the glyph have: head / face direction? hand / pointing direction? tool orientation? opening / threshold direction? line-flow behavior? rotation / turning behavior? body-axis movement? support / stabilization behavior? Mandatory if relevant: BOUSTROPHEDON TEST: Does the sign’s orientation change under reading-direction reversal? Output status: HIGH MEDIUM-HIGH MEDIUM LOW UNRESOLVED VII.5 Glyph-Name Functional Intersection Purpose: compare letter-name field with grapheme behavior and grammatical role. Example: VAV: hook / peg ↔ ו־ as conjunction “and” = connector-function candidate Control rule: Functional intersection is not symbolic essence. It is a linguistic/paleographic hypothesis. Required output: GLYPH-NAME FIELD: FUNCTIONAL COMPRESSION: CONTROL NOTE: STATUS: VII.6 Material / Historiographic Grapheme Function Purpose: analyze how the glyph behaves across engraving, incision, writing, brush, reed pen, quill, and manuscript copying. Required medium checks: ENGRAVING: INCISION: INK WRITING: BRUSH / REED / QUILL: MANUSCRIPT STANDARDIZATION: SQUARE-SCRIPT EFFECT: Mandatory issues: closed-counter issue suspended-center issue terminal elongation stroke minimization line-height / ascender / descender opening vs closure stroke-order deformation Special tests: Samekh: closed-form / engraved tablet risk Mem: open מ vs closed final ם Nun: bent נ vs elongated final ן Yod: small stroke / pen-tip / grid placement Lamed: ascender and line-height effect VII.7 Media / Reading-Writing Function Purpose: analyze the letter inside full media regimes: tablet, scroll, codex, manuscript, and reading practice. Required media regimes: TABLET / STONE / HARD SURFACE SCROLL / PARCHMENT / LINE-CONTINUOUS READING CODEX / PAGE / COMMENTARY LAYOUT CALLIGRAPHIC GRID RITUAL OR FORMAL READING INSTRUMENTS Questions: Does the letter: mark word-end? affect reading rhythm? affect line spacing? preserve distinction after phonetic weakening? function as a pointer/grid unit? require a reading-direction test? preserve icon value under rotated viewing? VII.8 Phoneme Purpose: identify sound value across the selected language / script profile and relevant comparative stages. Required fields: EARLY / HISTORICAL VALUE: PROFILE-SPECIFIC VALUE: MODERN VALUE WHERE RELEVANT: TRADITION-SPECIFIC VARIANTS: MERGER / WEAKENING: VOWEL-LETTER / MATER LECTIONIS STATUS WHERE RELEVANT: Control rule: Modern phonology must not be projected backward. Examples: ו: historical /w/ modern Hebrew /v/ ע: historical /ʕ/ modern Hebrew often glottalized or omitted ט: historical emphatic /ṭ/ modern Hebrew /t/ VII.9 Morpheme — Language / Script Profile Domain Purpose: identify whether the letter functions as radical, prefix, suffix, particle, preposition, marker, or weak-letter component. Required fields: SCRIPT / LANGUAGE PROFILE: ROOT-RADICAL ROLE: PREFIX ROLE: SUFFIX ROLE: PARTICLE / PREPOSITION / CONJUNCTION ROLE: WEAK-LETTER BEHAVIOR: TEXTUAL MARKER ROLE: GRAMMAR-SPECIFIC FORMS: Hebrew examples: ה־: definite article / interrogative prefix ו־: conjunction / vav-consecutive כ־: like / as ל־: to / toward / for מ־: from / of / from inside ־י: first-person suffix ־ך: second-person suffix ־ם: plural/pronominal suffix paragogic נ: Biblical Hebrew final-n phenomenon Greek / Latin control: identify inflectional, derivational, numeral, abbreviation, epigraphic, or phonographic roles only where source evidence supports them. Do not force Semitic radical behavior onto alphabetic vowel letters. Old Italic / Etruscan / Gothic / Runic control: identify sign function, phonographic value, and inscriptional role before any morphological claim. Mark language uncertainty separately from script certainty. VII.10 Comparative Script / Language Notes Purpose: gather Phoenician-connected branch data without collapsing one script into another. Required comparators: PHOENICIAN: ARAMAIC: HEBREW: GREEK: LATIN: OLD_ITALIC / ETRUSCAN: GOTHIC: RUNIC: ARABIC: NABATAEAN when relevant: COPTIC when relevant: Control rule: Comparative data may suggest inheritance, contact, or divergence. It may not automatically define the selected profile. Historiographic diagnostic: Hebrew + Punic: likely older Northwest Semitic / Canaanite layer candidate. Greek + Phoenician: alphabetic adaptation candidate, especially vowel-letter innovation. Latin + Greek + Old Italic: western alphabetic transmission candidate. Old Italic + Etruscan: corpus-sensitive inscriptional analysis required. Gothic + Greek: Gothic script derivation candidate, with Latin / Runic contact marked cautiously. Runic + Latin / Italic contact: possible contact layer only; not automatic descent proof. Aramaic + Arabic but not Hebrew: possible later eastern / imperial / contact layer candidate. Hebrew only: local Hebrew development candidate. All Semitic: broader Semitic inheritance candidate. Status must remain: DATA-GATHERING COMPARATIVE CONTROL HIGH HISTORIOGRAPHIC VALUE NOT PRIMARY PROFILE EVIDENCE unless fully validated. VII.11 Structural Summary Purpose: compress all findings into a structured diagnostic profile. Required summary fields: GRAPHEME_ROLE: HISTORICAL_GRAPHEME_ROLE: DIRECTIONAL_GRAPHEME_ROLE: GLYPH_NAME_FUNCTIONAL_INTERSECTION: MATERIAL_GRAPHEME_ROLE: MEDIA_GRAPHEME_ROLE: PHONEME_ROLE: MORPHEME_ROLE: COMPARATIVE_ROLE: VII.12 Uncertainty Register Purpose: preserve unresolved issues visibly. Mandatory table columns: ZONE STATUS NOTE Status vocabulary: ADMISSIBLE SOURCE-SUPPORTED RECONSTRUCTED PROVISIONAL SOURCE-SPLIT DATA-GATHERING PERIOD-SPECIFIC GRAMMAR-SPECIFIC DEFERRED FORBIDDEN VII.13 Prohibited Import Check Purpose: verify the operation did not import invalid authority. Mandatory checklist: Sefer Yetzirah imported? YES / NO Kabbalah imported? YES / NO Gematria imported? YES / NO Symbolic authority used? YES / NO Theological claim used? YES / NO Tree-of-Life path imported? YES / NO Later correspondence used? YES / NO If any answer is YES, classify: VALID COMPARATIO or FORBIDDEN IMPORT VII.14 Final Formula Purpose: give the controlled compressed definition of the letter. Example format: י / YOD = hand-derived compact /j/ grapheme, materially small but functionally dense, acting as consonant, vowel-carrier, weak radical, verbal prefix, and first-person suffix. Formula must never say: [letter] = mystical essence [letter] proves doctrine [letter] validates tradition [letter] defines Sephirah VIII. Standard output template ============================================================ OPERA LITTERA — [SCRIPT GLYPH] / [NAME] AGLA / LINGUISTIC STACK — LITTERA [SCRIPT PROFILE] Version: 0.1.0-OPERA-LITTERA-[NAME] Status: EXECUTED — SINGLE LETTER EXTRACTION Primary Source: Wiktionary Secondary Source: Wikipedia Forbidden Sources: Sefer Yetzirah Kabbalah books Gematria tables Class: OPERA / LITTERA / GRAPHEME / HISTORICAL GRAPHEME / DIRECTIONAL GRAPHEME / MATERIAL GRAPHEME / MEDIA-GRAPHEME / PHONEME / MORPHEME / COMPARATIVE SCRIPT ============================================================ I. STANDARD FORMAT [AGLA] — [SCRIPT GLYPH] — [LETTER / SIGN NAME] — [PHONETIC] Script profile: [PHOENICIAN / HEBREW / GREEK / LATIN / OLD_ITALIC / ETRUSCAN / GOTHIC / RUNIC / MIXED_SCRIPT / UNKNOWN_SCRIPT] Project mapping: [SCRIPT GLYPH] = [AGLA] Primary identification: [alphabetic position] Unicode locus: [code point / block / script property] II. CURRENT GRAPHEME Current grapheme: [glyph] Unicode: [code] Final form: [none / final glyph] Positional behavior: Initial: Medial: Final: Orthographic role: [...] III. HISTORICAL GRAPHEME Proto-Sinaitic / Proto-Canaanite: source-field: status: Phoenician: glyph: name: phonemic value: Paleo-Hebrew: status: Aramaic: glyph: role: Square Hebrew: current form: IV. DIRECTIONAL / ERGONOMIC GRAPHEME FUNCTION Directional anatomy: [...] Boustrophedon behavior: [...] Functional hypothesis: [...] Status: [...] V. GLYPH-NAME FUNCTIONAL INTERSECTION Glyph-name field: [...] Functional compression: [...] Control note: [...] VI. MATERIAL / HISTORIOGRAPHIC GRAPHEME FUNCTION Engraving: [...] Writing: [...] Closed-counter / stroke / size issue: [...] Historiographic criterion: [...] Anachronism risk: [...] VII. MEDIA / READING-WRITING FUNCTION Tablet / inscription regime: [...] Scroll regime: [...] Codex / manuscript regime: [...] Reading / writing practice note: [...] VIII. PHONEME Early value: [...] Profile value: [...] Modern value: [...] Vowel-letter / mater lectionis status: [...] IX. MORPHEME — LANGUAGE / SCRIPT PROFILE DOMAIN Script / language profile: [...] Root-radical role: [...] Prefix role: [...] Suffix role: [...] Particle / preposition / conjunction role: [...] Weak-letter / grammar-specific role: [...] X. COMPARATIVE SCRIPT / LANGUAGE NOTES Phoenician: [...] Hebrew: [...] Aramaic: [...] Greek: [...] Latin: [...] Old Italic / Etruscan: [...] Gothic: [...] Runic: [...] Arabic: [...] Other branch: [...] XI. STRUCTURAL SUMMARY GRAPHEME_ROLE: HISTORICAL_GRAPHEME_ROLE: DIRECTIONAL_GRAPHEME_ROLE: GLYPH_NAME_FUNCTIONAL_INTERSECTION: MATERIAL_GRAPHEME_ROLE: MEDIA_GRAPHEME_ROLE: PHONEME_ROLE: MORPHEME_ROLE: COMPARATIVE_ROLE: XII. UNCERTAINTY REGISTER | Zone | Status | Note | |---|---|---| XIII. PROHIBITED IMPORT CHECK Sefer Yetzirah imported? NO Kabbalah imported? NO Gematria imported? NO Symbolic authority used? NO Theological claim used? NO Tree-of-Life path imported? NO XIV. FINAL FORMULA [LETTER] = [...] Compressed: [...] ============================================================ END — OPERA LITTERA: [HEBREW] / [NAME] NEXT: OPERA LITTERA — [NEXT LETTER] ============================================================ IX. Relation to OPERA LITTERAE IMAGO ROTATA OPERA LITTERA is the standard linguistic-character pass. OPERA LITTERAE IMAGO ROTATA is the rotation-aware visual paleographic extension. The standard OPERA LITTERA must prepare the data needed by ROTATA: source-icon field historical forms directional hypothesis material behavior media behavior anatomical source class uncertainty zones ROTATA may then test: 0° 90° 180° 270° mirroring stroke skeleton quill / reed / brush simplification hand anatomy glyph/icon continuity But ROTATA cannot override linguistic extraction without explicit patching. ROTATA may clarify form. It may not replace RADIX, morphology, phonology, or philology. X. Hand anatomy and size integration This section is now mandatory when the source-icon involves body parts. HAND / BODY ANATOMY CHECK Applicable letters include at minimum: י / YOD hand / arm / possible pen-tip logic כ / KAF palm / hand-surface / grip ע / AYIN eye פ / PE mouth ר / RESH head ש / SHIN tooth / breasts depending source layer ל / LAMED hand-held goad / staff ו / VAV hook / peg as tool-object Required fields: SOURCE ANATOMY CLASS: ANATOMICAL SCALE TIER: EXPECTED REDUCTION: HAND / TOOL MEDIATION: CALLIGRAPHIC CONSEQUENCE: Scale tiers: MACRO: whole body / large object MESO: head / hand / palm / container / animal part MICRO: finger / eye / mouth aperture / pen-tip-like point Law: Relative glyph size may reflect source anatomy, writing gesture, or media simplification. It must not be treated as symbolic meaning without separate evidence. Yod/Kaf distinction: YOD: operative extremity / hand-tip / pen-tip / minimal grid unit KAF: palm / grasping surface / larger hand-field / curved container They must not be collapsed into one generic “hand” category. XI. Validity tests An OPERA LITTERA output is valid only if: V1. It begins from the letter as grapheme, not symbol. V2. It includes current script form, Unicode locus, and final / positional form if applicable. V3. It identifies historical script stages. V4. It separates source-supported claims from reconstructed claims. V5. It identifies phonemic value historically and under the selected profile. V6. It identifies morphemic role under the selected language profile before comparative extension. V7. It marks Phoenician, Hebrew, Aramaic, Greek, Latin, Old Italic, Etruscan, Gothic, Runic, Arabic, and other comparators as comparative unless directly relevant to the selected profile. V8. It includes material and media behavior. V9. It preserves uncertainty. V10. It includes prohibited import check. V11. It does not use gematria as authority. V12. It does not import Sefer Yetzirah unless explicitly classified. V13. It does not derive Sephirotic claims from letters prematurely. V14. It prepares, but does not replace, OPERA LITTERAE IMAGO ROTATA. XII. Failure modes F1 — SYMBOLIC ESSENCE DRIFT Letter-name becomes metaphysical meaning. F2 — GEMATRIC AUTHORITY DRIFT Numeric value becomes proof. F3 — TRADITIONAL IMPORT Later Kabbalistic doctrine defines the letter. F4 — MODERN RETROJECTION Modern pronunciation is projected backward. F5 — SQUARE-SCRIPT ANACHRONISM Later square form is projected into Proto-Sinaitic or Phoenician stages. F6 — FINAL-FORM RETROJECTION Sofit form is treated as ancient. F7 — ICON OVERCLAIM Visual resemblance becomes genealogy or doctrine. F8 — COMPARATIVE COLLAPSE Phoenician-connected scripts and languages are merged without control. F9 — MEDIA BLINDNESS Engraving, scroll, codex, quill, reed, and brush transformations are ignored. F10 — ROTATA PREMATURITY Rotated image analysis overrides linguistic evidence. F11 — SEPHIROT PREMATURITY Letter analysis defines Sephirot before lawful interface execution. XIII. Valid modes V1 — GRAPHEME-FIRST ANALYSIS V2 — PHONEME ANALYSIS V3 — MORPHEME ANALYSIS V4 — HISTORICAL GRAPHEME COMPARISON V5 — DIRECTIONAL / ERGONOMIC HYPOTHESIS V6 — MATERIAL-HISTORIOGRAPHIC ANALYSIS V7 — MEDIA-GRAPHEME ANALYSIS V8 — COMPARATIVE SCRIPT DATA-GATHERING V9 — ROTATA-PREPARED VISUAL CLASSIFICATION V10 — UNCERTAINTY-REGISTERED SYNTHESIS XIV. Final protocol formula OPERA LITTERA = standard single-character investigation beginning with the declared script grapheme, tracing its historical forms, identifying phonemic and morphemic roles, testing directional and material behavior, situating it in writing/reading media, collecting comparative Phoenician-connected script data, and preserving uncertainty before any symbolic or structural projection. Compressed: LETTER = grapheme + historical form + sound + grammatical function + material inscription behavior + media-writing behavior + controlled comparative witnesses Operational: Analyze the letter before interpreting the letter. ============================================================ END — OPERA LITTERA STANDARD ============================================================