============================================================ OPERA LITTERAE IMAGO ROTATA AGLA / LINGUISTIC STACK — MULTISCRIPT ROTATION-AWARE PALEOGRAPHIC PROTOCOL Version: 0.2.1-OPERA-LITTERAE-IMAGO-ROTATA-MULTISCRIPT-DUCTUS Status: PROVISIONAL — MULTIPURPOSE LINGUISTIC STACK CANDIDATE WITH DUCTUS / CURSIVE / STROKE-WEIGHT PATCH Authority: CODEX / LOCAL ARTIFACT PARSING NODE Class: AGLA / OPERA / LITTERAE / IMAGO / ROTATA / PALEOGRAPHY Scope: • define the rotation-aware image protocol for written signs / letters • support Hebrew, Greek, Latin, and other Phoenician-connected scripts • admit Old Italic, Etruscan, Gothic, and Runic when Unicode locus is reliable • compare glyphs across relevant script stages without Hebrew-first collapse • require image-recognition pass when visual form cannot be read reliably • integrate handwritten / cursive variation when relevant • distinguish mechanical rotation from human rewriting • model pen-tip position and stroke-thickness transformation • preserve distinction between lineage and icon/glyph value • integrate media-history and calligraphic simplification • integrate hand-anatomy and source-object scale constraints • standardize textual output for rotated forms Mutation Policy: VERSION-CONTROLLED ONLY ============================================================ ============================================================ I. PURPOSE ============================================================ OPERA LITTERAE IMAGO ROTATA defines a controlled visual protocol for studying each written sign / letter as: • grapheme • phonemic carrier • morphemic carrier • historical glyph • rotated image-object • media-transformed writing form • image-recognition object when visual evidence is required The protocol exists because letter history cannot be reconstructed adequately if the glyph is treated only as: a fixed upright modern square character. The protocol therefore requires that each relevant letter-form be tested as an oriented visual object under rotation, and where needed mirroring, while keeping separate: A. lineage continuity B. icon/glyph continuity C. media transformation D. anatomical scale logic E. image-recognition confidence F. handwriting / cursive variation G. pen-tip / stroke-weight effects ============================================================ II. CORE LAW ============================================================ ============================================================ ROTATA CORE LAW ============================================================ A historical letter-form must be treated as an oriented image-object. Therefore, whenever a glyph appears visually discontinuous from an earlier form or source-icon, the analysis must test whether: • rotation • mirroring • stroke simplification • tool-medium transformation • size reduction • anatomical abstraction restore intelligible continuity. But: visual continuity ≠ proof of descent pictorial resemblance ≠ symbolic authority rotated fit ≠ final historical conclusion ============================================================ ============================================================ III. PRIMARY OBJECTS ============================================================ Mandatory first-class script profiles: PHOENICIAN HEBREW GREEK LATIN Admissible extended profiles when Unicode locus and visual evidence are reliable: OLD_ITALIC ETRUSCAN GOTHIC RUNIC The Hebrew primary units remain: א ב ג ד ה ו ז ח ט י כ ל מ נ ס ע פ צ ק ר ש ת and, where useful for media-history and positional development: ך ם ן ף ץ Greek and Latin primary units include their standard uppercase and lowercase Unicode forms, plus archaic, epigraphic, diacritic, and case-specific variants where evidence supports them. Old Italic / Etruscan, Gothic, and Runic units are admissible only when the submitted sign has a reliable Unicode locus or a user-provided image. Each letter is to be studied across available relevant script stages: 1. Egyptian exemplar field, when relevant 2. Proto-Sinaitic / Proto-Canaanite 3. Phoenician 4. Paleo-Hebrew 5. Imperial Aramaic 6. Square Hebrew 7. Greek, when relevant 8. Old Italic / Etruscan, when relevant 9. Latin, when relevant 10. Gothic, when relevant 11. Runic, when relevant 12. Nabataean, when relevant 13. Arabic, when relevant Control rule: Hebrew is one profile. It is not the universal visual form, direction, or rotation law. ============================================================ III.A UNICODE AND IMAGE-RECOGNITION ADMISSIBILITY ============================================================ ROTATA requires visual evidence. The assistant may internally generate or read simple Unicode glyph forms for: square Hebrew standard Greek standard Latin stable Phoenician, Gothic, and Runic Unicode characters Old Italic signs when font/rendering support is visibly reliable Internal glyph handling is sufficient only for: clear Unicode character analysis schematic rotation tags generic stroke-orientation tests non-damaged printed glyphs profile-level comparison without manuscript or inscription claims The assistant must ask the user for image input before proceeding when: the target is an inscription, manuscript, seal, coin, tablet, drawing, rubbing, photograph, scan, facsimile, epigraphic chart, paleographic plate, generated visual asset, damaged sign, ligature, uncertain glyph, archaic variant, ornamental form, or font-dependent historical form The assistant must also ask for image input when: Unicode rendering is unavailable or visually unreliable the sign belongs to Old Italic / Etruscan and the exact corpus form matters the sign belongs to Runic and futhark/corpus distinction matters visually the sign belongs to Gothic and manuscript form matters the analysis depends on stroke order, ductus, line thickness, angle, curvature, incision, medium damage, or actual rotation display the user asks for image recognition, visual comparison, or icon recovery the assistant cannot confidently see the character shape Allowed request formula: "Please provide an image of the sign or inscription before ROTATA proceeds; Unicode text alone is not reliable for this visual claim." If no image is provided: STATUS := SUSPENDED_IMAGE_REQUIRED The assistant may then provide only: admissibility notes Unicode locus notes likely script-profile candidates questions needed to obtain visual evidence It must not provide: final rotation classification icon recovery lineage match medium transformation conclusion stroke-skeleton conclusion ============================================================ III.B KABBALAH STACK COMPATIBILITY CLAUSE ============================================================ When ROTATA is executed inside KABBALAH STACK: Hebrew remains the root-resolution domain for RADIX. But: Hebrew does not govern visual glyph comparison across scripts. Therefore: RADIX discipline remains Hebrew-bound. ROTATA visual comparison may be multiscript. The two layers must not collapse. Operational distinction: HEBREW RADIX: governs root-resolution and semantic grounding inside KABBALAH STACK. MULTISCRIPT ROTATA: governs visual, paleographic, ductus, rotation, and glyph/icon comparison across script profiles. Forbidden collapse: ✘ using Greek / Latin / Runic visual form as Hebrew RADIX evidence ✘ using Hebrew square script as universal paleographic baseline ✘ treating multiscript visual similarity as semantic equivalence ✘ treating ROTATA as replacement for RADIX Allowed: ✓ using Phoenician / Greek / Latin / Runic / other script witnesses as visual comparatio ✓ using multiscript forms to detect lineage, ductus, and icon continuity ✓ preserving Hebrew RADIX as root-resolution domain while allowing multiscript visual comparison ============================================================ IV. ANALYTIC LAYERS ============================================================ Every letter-pass must distinguish these layers. ------------------------------------------------------------ LAYER A — LINEAGE ------------------------------------------------------------ Question: How does the form develop from one script stage into another? ------------------------------------------------------------ LAYER B — GLYPH / ICON VALUE ------------------------------------------------------------ Question: What pictorial or quasi-pictorial value remains recoverable? ------------------------------------------------------------ LAYER C — MEDIA TRANSFORMATION ------------------------------------------------------------ Question: How do incision, brush, reed pen, quill, and manuscript habits transform the form? ------------------------------------------------------------ LAYER D — ANATOMICAL SCALE ------------------------------------------------------------ Question: If the source-icon is bodily or manually derived, how does source-part size influence glyph reduction, simplification, and relative visual importance? ------------------------------------------------------------ LAYER E — IMAGE-RECOGNITION CONFIDENCE ------------------------------------------------------------ Question: Is the actual visible form available and reliable enough for rotation, mirroring, stroke, and icon/glyph comparison? Possible states: INTERNAL_UNICODE_SUFFICIENT IMAGE_PROVIDED IMAGE_REQUIRED IMAGE_LOW_CONFIDENCE RENDERING_UNRELIABLE SUSPENDED_IMAGE_REQUIRED Rule: If Layer E is IMAGE_REQUIRED, IMAGE_LOW_CONFIDENCE, RENDERING_UNRELIABLE, or SUSPENDED_IMAGE_REQUIRED, all claims from Layers A-D, F, and G must remain provisional or suspended. ------------------------------------------------------------ LAYER F — HANDWRITING / CURSIVE VARIATION ------------------------------------------------------------ Question: Does a handwritten, cursive, documentary, book-hand, or semi-formal variant preserve ductus continuity that the formal glyph conceals? Rule: If the claim depends on ductus and no handwriting evidence is available, the handwriting layer must be marked required or deferred. ------------------------------------------------------------ LAYER G — PEN-TIP / STROKE-WEIGHT EFFECTS ------------------------------------------------------------ Question: Does pen-tip position, nib angle, stroke pressure, or thick/thin distribution change the visual result under rotation or rewriting? Rule: If stroke-weight behavior is central and no image or ductus data is available, final ROTATA classification must be suspended. ============================================================ V. MANDATORY ROTATION SET ============================================================ Each form must be tested in all four cardinal orientations. Required orientations: R0 = 0° R90 = 90° R180 = 180° R270 = 270° (or -90°) Default notation: [glyph]@R0 [glyph]@R90 [glyph]@R180 [glyph]@R270 Examples of textual annotation: ע@R270 א@R90 י@R0 פ@R180 If the environment permits actual rotated inline characters or rotated image-snippets, they must be included in the textual output. If not, angle annotation remains mandatory. Compressed rule: actual rotated display when available angle-tag notation always ============================================================ VI. OPTIONAL MIRROR SET ============================================================ Mirroring is conditional, but strongly recommended when: • boustrophedon is relevant • facing direction matters • the source-icon is asymmetrical • the sign may have direction-of-reading behavior Optional transformations: MH = horizontal mirror MV = vertical mirror R90+MH R270+MH R90+MV R270+MV Default notation: [glyph]@R0+MH [glyph]@R270+MH Important: the four rotations are mandatory mirroring is conditional but often necessary ============================================================ VII. TEXTUAL OUTPUT LAW FOR ROTATED FORMS ============================================================ Every formal output must contain a visible rotation section. Minimum textual output format: LETTER: ע / AYIN ROTATION DISPLAY: ע@R0 ע@R90 ע@R180 ע@R270 If actual rotated symbols are renderable, use: ע@R0 [actual glyph] ע@R90 [actual rotated glyph] ע@R180 [actual rotated glyph] ע@R270 [actual rotated glyph] If actual rotation cannot be rendered in plain text, the angle-tag notation is sufficient. Rule: no rotation result may be described without explicit orientation tags. ============================================================ VIII. MEDIA-HISTORY LAW ============================================================ A glyph must not be compared only as outline-to-outline. It must also be compared as a product of writing medium. Required medium classes: M1. incised / engraved M2. carved / chiseled M3. brush-drawn M4. reed-pen drawn M5. quill-pen drawn M6. manuscript / scribal standardization M7. calligraphic grid regularization Each letter-pass must ask: • does the earlier form function as image-outline? • does it function as stroke skeleton? • does it function as writing gesture? • does it function as pen-entry / pen-exit schema? • does it function as grid-placement logic? Special consequence: a form that seems distant by contour may be close by gesture. ============================================================ IX. HANDWRITTEN / CURSIVE VARIATION LAW ============================================================ ROTATA must not privilege formal, monumental, printed, or typographic characters as the only valid witnesses of glyph value. When relevant, each sign must also be tested against: • handwritten forms • cursive forms • documentary hands • book hands • informal scribal hands • semi-formal inscriptional hands • ligature-prone hands • fast-written forms • educational / copybook forms • transitional ductus forms Rationale: Historical Latin, Greek, Hebrew, and related handwriting variations may sometimes preserve stroke-skeletons closer to Phoenician or earlier alphabetic characters than more formal or monumental forms. Therefore: formal glyph distance does not imply ductus distance. A later formal sign may appear far from an earlier form, while a handwritten or cursive variant may reveal continuity through: • stroke order • pen-entry point • pen-exit point • curvature • ligature tendency • angular simplification • speed deformation • hand economy • repeated scribal habit Required test: For any script profile where handwritten witnesses are relevant, ROTATA must compare: FORMAL_GLYPH CURSIVE_GLYPH DOCUMENTARY_HAND CALLIGRAPHIC_HAND INSCRIPTIONAL_FORM when evidence is available. If no handwritten evidence is available: STATUS := HANDWRITING_DATA_REQUIRED Allowed output: • note formal glyph comparison • mark cursive layer as deferred • request image/sample if the conclusion depends on handwriting Forbidden output: ✘ final glyph/icon classification based only on formal glyphs when the claim depends on ductus or handwritten transformation ✘ treating printed Unicode glyphs as sufficient evidence for historical handwriting behavior ✘ ignoring cursive variants where they are known to materially affect form Classification addition: HANDWRITING STATUS: NOT_RELEVANT FORMAL_ONLY HANDWRITING_AVAILABLE HANDWRITING_REQUIRED CURSIVE_REQUIRED DOCUMENTARY_HAND_REQUIRED UNRESOLVED ============================================================ X. PEN-TIP / STROKE-THICKNESS TRANSFORMATION LAW ============================================================ ROTATA must consider that glyph appearance is generated not only by outline geometry, but also by the position, angle, pressure, and motion of the writing instrument. Required variables: 1. PEN-TIP POSITION Where does the pen, reed, brush, stylus, or chisel enter the stroke? 2. PEN-TIP ANGLE At what angle is the nib, brush, reed, or tool held relative to the writing direction? 3. STROKE PRESSURE Is the stroke thickened by pressure, angle, repeated pass, or medium absorption? 4. DUCTUS PATH What is the actual motion path of the hand? 5. THICK / THIN DISTRIBUTION Which parts of the stroke become thick or thin due to tool orientation? 6. ROTATED RENDERING EFFECT If the sign is rotated, does a human writer preserve the same stroke-thickness pattern, or does the tool generate a different visual result? Core principle: A rotated glyph drawn by a human hand is not necessarily identical to a mechanically rotated printed glyph. Reason: The pen-tip position and writing gesture can regenerate the sign differently in each orientation. Therefore: ROTATA must distinguish: MECHANICAL ROTATION: same image rotated as an object HUMAN REWRITING AFTER ROTATION: sign redrawn by hand in a new orientation DUCTUS ROTATION: stroke order and tool angle transformed with the sign TOOL-STABLE ROTATION: sign orientation changes but pen angle remains stable TOOL-ROTATED EXECUTION: sign orientation and pen angle rotate together This distinction is mandatory when: • stroke thickness affects glyph recognition • calligraphy affects visual form • cursive variants are analyzed • handwritten evidence is used • rotated character rendering is compared • ductus or writing gesture is part of the claim Required output fields: PEN TOOL: brush / reed / quill / stylus / chisel / modern pen / unknown PEN ANGLE STATUS: known / inferred / unknown / image required THICKNESS MODEL: monolinear / contrastive / pressure-driven / brush-variable / chisel-incised / unknown ROTATION MODE: mechanical rotation / human rewriting / ductus rotation / tool-stable rotation / tool-rotated execution / unresolved STROKE-WEIGHT EFFECT: none / low / medium / high / decisive / unresolved Classification addition: STROKE-WEIGHT STATUS: STRONG MEDIUM LOW UNRESOLVED IMAGE_REQUIRED Control: If stroke-weight behavior is central and no image or ductus data is available, ROTATA must suspend final classification. Forbidden: ✘ treating a mechanically rotated Unicode glyph as equivalent to a human-written rotated sign when stroke contrast matters ✘ ignoring thick/thin distribution in calligraphic scripts ✘ treating pen-tip position as decorative only ✘ deriving icon continuity from a rotated printed glyph when a handwritten ductus comparison is required ============================================================ XI. HAND / TOOL TRANSFORMATION LAW ============================================================ This law is mandatory for letters connected to hands, palms, fingers, grips, hooks, or writing gesture. Relevant letters include at minimum: י / YOD כ / KAF ו / VAV ל / LAMED פ / PE and others where tool mediation becomes relevant Critical principle: the hand may persist in two ways: 1. as icon of a hand-part 2. as the act that writes the sign Therefore: a hand-derived glyph may shrink not only because of abstraction, but because the source-hand becomes reinterpreted as the writing-hand. Example status law for Yod: Proto / Phoenician Yod may preserve hand-icon value, while square י may preserve hand-action or pen-tip logic. So the analysis must distinguish: hand as depicted object hand as producing instrument hand-part as scale source pen-tip as reduced hand index ============================================================ XII. ANATOMICAL SCALE LAW ============================================================ This section is mandatory whenever the source-icon is bodily, especially for: hand palm finger eye mouth head breast foot arm hook-like bodily/tool analogues Core principle: source anatomy influences expected glyph size, internal detail, and simplification pathway. The protocol must register: ------------------------------------------------------------ A. SOURCE ANATOMY CLASS ------------------------------------------------------------ Possible classes: BODY-WHOLE HEAD FACE-PART EYE MOUTH HAND-WHOLE PALM FINGER / DIGIT LIMB / ARM TOOL-HELD-BY-HAND ABSTRACT OBJECT ------------------------------------------------------------ B. ANATOMICAL SCALE TIER ------------------------------------------------------------ Possible tiers: MACRO whole body / large object MESO head / hand / container / animal body part MICRO finger / eye / mouth opening / pen-tip-like feature ------------------------------------------------------------ C. EXPECTED GLYPH CONSEQUENCE ------------------------------------------------------------ Examples: MACRO source: more contour loss acceptable during reduction MESO source: core outline or axis tends to persist MICRO source: glyph may become minimal mark, hook, tick, angle, or placement unit ------------------------------------------------------------ D. HAND-ANATOMY APPLICATION ------------------------------------------------------------ Mandatory note for hand-derived letters: HAND-WHOLE and PALM-derived letters should not be expected to reduce in the same way as FINGER-derived letters. Implication: YOD and KAF must be distinguished anatomically. YOD: likely MICRO or sub-MESO logic if reduced to hand-tip, finger, or pen-point behavior. KAF: likely MESO logic if palm / cupped hand remains primary. Therefore: relative glyph size and density must be evaluated against source-anatomy class. ------------------------------------------------------------ E. SIZE-TO-STROKE RULE ------------------------------------------------------------ Smaller anatomical source units tend to yield: • fewer strokes • stronger reduction • higher gestural abstraction • greater potential to become diacritic-like or grid-like Larger source units tend to yield: • more contour persistence • stronger enclosure logic • larger visual span • slower reduction into minimal marks ============================================================ XIII. BOUSTROPHEDON LAW ============================================================ If a sign-family is attested in boustrophedon or mirror-facing conditions, the analysis must test whether orientation serves: • reading-direction signaling • ergonomic stroke economy • icon facing behavior • line-direction adaptation This is especially important for: א / Aleph and other asymmetrical source-icons. Question type: does the sign face the direction of reading? does reversal preserve icon value? does reversal improve glyph function? ============================================================ XIV. OUTPUT TEMPLATE PER LETTER ============================================================ Each letter-pass must follow this template. ------------------------------------------------------------ LETTER HEADER ------------------------------------------------------------ HEBREW: [letter, if Hebrew profile] SCRIPT PROFILE: [PHOENICIAN / HEBREW / GREEK / LATIN / OLD_ITALIC / ETRUSCAN / GOTHIC / RUNIC / MIXED_SCRIPT / UNKNOWN_SCRIPT] SCRIPT GLYPH: [letter / sign] UNICODE LOCUS: [code point / Unicode block / script property] NAME: [name] SCRIPT STAGES INCLUDED: [list] SOURCE-ICON FIELD: [ox-head / hand / palm / eye / etc.] SOURCE ANATOMY CLASS: [BODY-WHOLE / HAND-WHOLE / PALM / FINGER / EYE / etc.] ANATOMICAL SCALE TIER: [MACRO / MESO / MICRO] IMAGE EVIDENCE STATUS: INTERNAL_UNICODE_SUFFICIENT / IMAGE_PROVIDED / IMAGE_REQUIRED / IMAGE_LOW_CONFIDENCE / RENDERING_UNRELIABLE / SUSPENDED_IMAGE_REQUIRED IMAGE SOURCE: [internal Unicode rendering / user-provided image / uploaded plate / manuscript scan / inscription photo / generated image / none] HANDWRITING EVIDENCE STATUS: NOT_RELEVANT / FORMAL_ONLY / HANDWRITING_AVAILABLE / HANDWRITING_REQUIRED / CURSIVE_REQUIRED / DOCUMENTARY_HAND_REQUIRED / UNRESOLVED HANDWRITING SOURCE: internal formal Unicode / user-provided cursive image / manuscript sample / inscription sample / paleographic chart / none ------------------------------------------------------------ ROTATION DISPLAY ------------------------------------------------------------ SQUARE HEBREW: [glyph]@R0 [glyph]@R90 [glyph]@R180 [glyph]@R270 PHOENICIAN: [glyph]@R0 [glyph]@R90 [glyph]@R180 [glyph]@R270 PROTO-SINAITIC / EARLY FORM: [descriptor or image tag]@R0 [descriptor or image tag]@R90 [descriptor or image tag]@R180 [descriptor or image tag]@R270 GREEK / LATIN / OLD ITALIC / ETRUSCAN / GOTHIC / RUNIC WHEN RELEVANT: [glyph or image tag]@R0 [glyph or image tag]@R90 [glyph or image tag]@R180 [glyph or image tag]@R270 OPTIONAL MIRRORS: [glyph]@R0+MH [glyph]@R270+MH etc. ------------------------------------------------------------ LAYER A — LINEAGE ------------------------------------------------------------ Best lineage orientation: [R0 / R90 / R180 / R270 / mirrored form] Reason: [brief justification] ------------------------------------------------------------ LAYER B — GLYPH / ICON VALUE ------------------------------------------------------------ Best icon orientation: [R0 / R90 / R180 / R270 / mirrored form] Recovered icon value: [eye / hand / mouth / etc.] ------------------------------------------------------------ LAYER C — MEDIA TRANSFORMATION ------------------------------------------------------------ Relevant medium transitions: [incision → brush → reed pen → square script etc.] Stroke simplification note: [brief note] Handwritten / cursive variation: [whether cursive or handwritten variants clarify lineage or icon value] Ductus note: [stroke order / hand path / speed / simplification / ligature tendency] Pen-tip / stroke-weight note: [pen angle, thickness distribution, pressure, tool effects] Rotation mode: mechanical rotation / human rewriting / ductus rotation / tool-stable rotation / tool-rotated execution / unresolved ------------------------------------------------------------ LAYER D — ANATOMICAL SCALE ------------------------------------------------------------ Source-part size effect: [how source anatomy affects expected simplification] Hand-anatomy note: [mandatory if relevant] ------------------------------------------------------------ LAYER E — IMAGE-RECOGNITION CONFIDENCE ------------------------------------------------------------ Recognition status: [INTERNAL_UNICODE_SUFFICIENT / IMAGE_PROVIDED / IMAGE_REQUIRED / IMAGE_LOW_CONFIDENCE / RENDERING_UNRELIABLE / SUSPENDED_IMAGE_REQUIRED] Visual basis: [what image, glyph, font, scan, or inscription was actually inspected] Confidence note: [why rotation/icon/stroke claims are permitted or suspended] ------------------------------------------------------------ CLASSIFICATION ------------------------------------------------------------ LINEAGE STATUS: MATCH / PARTIAL MATCH / WEAK MATCH / FALSE FRIEND / UNRESOLVED ICON STATUS: MATCH / PARTIAL MATCH / WEAK MATCH / FALSE FRIEND / UNRESOLVED MEDIA STATUS: STRONG / MEDIUM / LOW / UNRESOLVED ANATOMICAL SCALE STATUS: STRONG / MEDIUM / LOW / UNRESOLVED IMAGE RECOGNITION STATUS: SUFFICIENT / IMAGE REQUIRED / LOW CONFIDENCE / SUSPENDED HANDWRITING STATUS: NOT_RELEVANT / FORMAL_ONLY / HANDWRITING_AVAILABLE / HANDWRITING_REQUIRED / CURSIVE_REQUIRED / DOCUMENTARY_HAND_REQUIRED / UNRESOLVED STROKE-WEIGHT STATUS: STRONG / MEDIUM / LOW / UNRESOLVED / IMAGE_REQUIRED ------------------------------------------------------------ RISK ------------------------------------------------------------ Possible risks: overfitting false friend late-shape contamination medium confusion image-recognition overconfidence font/rendering substitution Unicode/form mismatch handwriting-form overgeneralization cursive-form overfitting ductus speculation pen-angle reconstruction error mechanical-rotation error stroke-weight false continuity symbolic overread ------------------------------------------------------------ FINAL NOTE ------------------------------------------------------------ [compressed synthesis] ============================================================ XV. CLASSIFICATION GRID ============================================================ The following classifications are mandatory. ------------------------------------------------------------ LINEAGE CLASSIFICATION ------------------------------------------------------------ MATCH: strong continuity across script stages under limited transformation PARTIAL MATCH: continuity visible but dependent on rotation or medium interpretation WEAK MATCH: resemblance present but unstable FALSE FRIEND: visual similarity without adequate historical support UNRESOLVED: insufficient witness or conflicting evidence ------------------------------------------------------------ ICON CLASSIFICATION ------------------------------------------------------------ MATCH: pictorial value is strongly recoverable PARTIAL MATCH: pictorial value recoverable only after rotation or abstraction WEAK MATCH: pictorial value faint FALSE FRIEND: resemblance likely accidental UNRESOLVED: unclear icon source ------------------------------------------------------------ MEDIA CLASSIFICATION ------------------------------------------------------------ STRONG: writing medium clearly explains transformation MEDIUM: medium explanation plausible but not decisive LOW: medium explanation weak UNRESOLVED: insufficient evidence ------------------------------------------------------------ ANATOMICAL SCALE CLASSIFICATION ------------------------------------------------------------ STRONG: source-part size clearly explains glyph reduction MEDIUM: anatomical size helps but does not decide LOW: weak explanatory contribution UNRESOLVED: anatomy not decisive or source uncertain ------------------------------------------------------------ IMAGE-RECOGNITION CLASSIFICATION ------------------------------------------------------------ SUFFICIENT: actual visible form is available or internal Unicode rendering is adequate for the limited claim being made IMAGE REQUIRED: the analysis depends on visual evidence not present in the text input LOW CONFIDENCE: an image exists, but resolution, damage, angle, lighting, or crop prevents stable recognition RENDERING UNRELIABLE: font, platform, missing glyph, fallback rendering, or text encoding prevents trustworthy visual comparison SUSPENDED: ROTATA may not classify until image evidence improves ------------------------------------------------------------ HANDWRITING CLASSIFICATION ------------------------------------------------------------ NOT_RELEVANT: handwriting or cursive variation does not materially affect the claim FORMAL_ONLY: only formal glyph evidence is available and the limitation is marked HANDWRITING_AVAILABLE: handwriting evidence is present and may inform ductus comparison HANDWRITING_REQUIRED: the claim depends on handwriting evidence not yet supplied CURSIVE_REQUIRED: cursive variation is central and must be supplied or sourced DOCUMENTARY_HAND_REQUIRED: documentary or scribal hand evidence is required for classification UNRESOLVED: handwriting relevance cannot yet be determined ------------------------------------------------------------ STROKE-WEIGHT CLASSIFICATION ------------------------------------------------------------ STRONG: stroke-weight behavior materially supports the visual classification MEDIUM: stroke-weight behavior helps but does not decide the classification LOW: stroke-weight behavior has minor relevance UNRESOLVED: tool angle, pressure, or ductus data is insufficient IMAGE_REQUIRED: stroke-weight behavior is central and cannot be assessed from text alone ============================================================ XVI. PRIORITY LETTERS ============================================================ The Hebrew first priority tier is: א ט י כ ל נ ס ע פ ר Reason: they are especially sensitive to one or more of: • directionality • rotation • icon recovery • hand/tool transformation • enclosure • reduction by writing medium • anatomical scale logic Equivalent priority tiers may be declared for Greek, Latin, Old Italic, Etruscan, Gothic, and Runic only after their script profile and visual evidence are established. ============================================================ XVII. YOD-SPECIFIC SPECIAL LAW ============================================================ YOD receives a special protocol patch. ------------------------------------------------------------ YOD SPECIAL RULE ------------------------------------------------------------ For י / YOD the analysis must explicitly test whether: 1. the early form preserves hand or hand-part icon value 2. the later form preserves writing-gesture logic 3. Phoenician Yod functions as a pen-tip positioning schema 4. square י functions as a minimal calligraphic grid-unit Therefore Yod must always receive: • four-orientation rotation test • media transformation test • hand-anatomy scale test • grid-placement note ------------------------------------------------------------ ============================================================ XVIII. KAF-SPECIFIC SPECIAL LAW ============================================================ KAF must be distinguished from YOD anatomically. ------------------------------------------------------------ KAF SPECIAL RULE ------------------------------------------------------------ For כ / KAF the analysis must explicitly test whether: 1. the source remains palm-like, cupped, or grasp-like 2. the glyph reduction preserves enclosure or curvature 3. the form reflects larger hand-unit anatomy than YOD 4. the writing-medium compresses a palm-form into an open curved sign Therefore: KAF must not be treated as merely “another hand-form.” It must be anatomically separated from YOD. ------------------------------------------------------------ ============================================================ XIX. OUTPUT SERIALIZATION LAW ============================================================ The protocol should be executed one letter at a time unless a summary table is explicitly requested. Recommended serialization: Output 1: protocol artifact Subsequent outputs: one pass per letter / sign Optional batch mode: summary table first then detailed per-letter outputs ============================================================ XX. PROHIBITIONS ============================================================ This protocol prohibits: ✘ treating modern square Hebrew as the only valid orientation ✘ treating any one script profile as the universal visual law ✘ treating formal / monumental / printed forms as exhaustive glyph evidence ✘ ignoring rotation ✘ confusing icon recovery with proof of descent ✘ ignoring writing medium ✘ ignoring quill / brush simplification ✘ ignoring handwritten or cursive variants when glyph value depends on ductus ✘ ignoring hand anatomy when source-icon is bodily ✘ collapsing YOD and KAF into identical “hand” logic ✘ projecting symbolic meaning from visual resemblance alone ✘ treating rotated fit as doctrinal proof ✘ treating mechanically rotated printed glyphs as equivalent to human-redrawn rotated signs when stroke weight matters ✘ ignoring pen-tip position, nib angle, pressure, or stroke contrast when these affect the rotated rendering ✘ treating cursive similarity as lineage proof without historical support ✘ using one handwriting tradition as universal script law ✘ omitting orientation tags in textual output ✘ claiming image recognition without visible image evidence ✘ using unreliable font rendering as paleographic evidence ✘ issuing final ROTATA classification when image input is required ✘ smoothing Old Italic, Etruscan, Gothic, or Runic variants into Latin ============================================================ XXI. VALID MODES ============================================================ This protocol permits: ✓ four-orientation testing ✓ conditional mirroring ✓ image-based comparison ✓ handwritten-form comparison ✓ cursive-form comparison ✓ documentary-hand comparison ✓ ductus-aware comparison ✓ pen-tip-position analysis ✓ stroke-thickness analysis ✓ mechanical-rotation vs human-rewriting distinction ✓ asking for image input before proceeding ✓ suspending analysis when image evidence is missing ✓ suspension of classification when handwriting or ductus evidence is required but unavailable ✓ stroke-skeleton analysis ✓ medium-aware analysis ✓ hand-anatomy-aware analysis ✓ calligraphic grid interpretation ✓ boustrophedon-aware testing ✓ lineage / icon separation ✓ explicit uncertainty markers ✓ internal Unicode-glyph testing when visual form is stable and simple ============================================================ XXII. FINAL FORMULA ============================================================ OPERA LITTERAE IMAGO ROTATA = sign-by-sign rotation-aware and ductus-aware paleographic analysis across script stages, integrating four cardinal orientations, conditional mirroring, image-recognition admissibility, handwritten and cursive variation, media-history, pen-tip position, stroke-thickness transformation, calligraphic simplification, and anatomical-scale logic, while preserving the distinction between: lineage continuity icon/glyph continuity medium transformation handwriting / cursive variation pen-tip / stroke-weight effects source-part size effects image-recognition confidence Compressed: rotate verify image compare compare handwriting trace ductus model pen-tip classify stroke weight simplify anatomize classify without overclaiming ============================================================ XXIII. IMMEDIATE NEXT EXECUTION ============================================================ Next suggested operational use: OPERA LITTERA IMAGO ROTATA — א / ALEPH or, if preferred: OPERA LITTERA IMAGO ROTATA — י / YOD For non-Hebrew or visually uncertain cases: OPERA LITTERA IMAGO ROTATA — [SCRIPT] / [SIGN] If the sign is not a stable internally readable Unicode glyph: request image input before execution. ============================================================ END — OPERA LITTERAE IMAGO ROTATA ============================================================