Eve library

Nisaba Domain Feature Inventory

Guide

Revision 1

On this page

Generated on May 8, 2026. This document captures domain feature scope from the Oshun repository and the phase checklist in TODOS.md.

Overview#

Nisaba owns scholarly text analysis, manuscript workflows, ancient-language processing, collation, annotation, critical-edition production, and cross-tradition research tooling in the Oshun platform.

Coverage Summary#

  • Domain slug: nisaba
  • TODO phase coverage: 65
  • Checklist-derived feature items: 243
  • Repository status: Repository implementation exists under apps/libs/services.
  • Oshun integration status: Dedicated Oshun domain adapter library present.
  • Source confidence: Implementation-backed and documentation-backed

Source Hierarchy#

  1. Actual implementation footprints in apps/, libs/, services/, and openapi/
  2. TODO-derived capability scope from the mapped phase sections
  3. Existing standalone domain docs in docs/domains/nisaba/

Capability Pillars#

Capability Pillar Primary Source Status
Directory Structure & Nx Configuration TODOS.md phase 65 implemented
Database & Infrastructure TODOS.md phase 65 implemented
Core Domain Types & Utilities TODOS.md phase 65 implemented
Zod Schemas TODOS.md phase 65 implemented
Writing System Support — Semitic Scripts TODOS.md phase 65 implemented
Writing System Support — Cuneiform Scripts TODOS.md phase 65 implemented
Writing System Support — Egyptian Scripts TODOS.md phase 65 implemented
Writing System Support — South Asian Scripts TODOS.md phase 65 implemented
Writing System Support — East Asian & Other Scripts TODOS.md phase 65 implemented
Morphological Parsers TODOS.md phase 65 implemented
Tokenization TODOS.md phase 65 implemented
Transliteration Engine TODOS.md phase 65 implemented
Lexicon Integration TODOS.md phase 65 implemented
Display Modes TODOS.md phase 65 implemented
Alignment Algorithms TODOS.md phase 65 implemented
Divergence Detection TODOS.md phase 65 implemented
Manuscript Witness Registry TODOS.md phase 65 implemented
Collation Engine TODOS.md phase 65 implemented
Variant Classification TODOS.md phase 65 implemented
Stemmatic Analysis TODOS.md phase 65 implemented
Critical Apparatus Generation TODOS.md phase 65 implemented
Lacuna Tracking TODOS.md phase 65 implemented
Biblical Canon Systems TODOS.md phase 65 implemented
Non-Biblical Canon Systems TODOS.md phase 65 implemented
Cross-System Reference Resolution TODOS.md phase 65 implemented
Script & Period Classification TODOS.md phase 65 implemented
Letterform Analysis & Scribal Identification TODOS.md phase 65 implemented
Damaged Text & Dating TODOS.md phase 65 implemented
Etymology & Semantic Analysis TODOS.md phase 65 implemented
Hapax Legomena & Statistical Linguistics TODOS.md phase 65 implemented
Discourse Analysis TODOS.md phase 65 implemented
Intertextuality Detection TODOS.md phase 65 implemented
Cross-Tradition Concept Mapping TODOS.md phase 65 implemented
Parallel Passage Detection TODOS.md phase 65 implemented
Motif & Theme Tracking TODOS.md phase 65 implemented
Influence Network & Synoptic Views TODOS.md phase 65 implemented
Format Parsers TODOS.md phase 65 implemented
Corpus Connectors TODOS.md phase 65 implemented
Ingestion Pipeline TODOS.md phase 65 implemented
Standoff Annotation Architecture TODOS.md phase 65 implemented
Collaborative Annotation TODOS.md phase 65 implemented
Annotation Export TODOS.md phase 65 implemented
Edition Project Management TODOS.md phase 65 implemented
Edition Export & Publishing TODOS.md phase 65 implemented
Provenance & Diffusion TODOS.md phase 65 implemented
Geographic & Timeline Integration TODOS.md phase 65 implemented
Spatial Search TODOS.md phase 65 implemented
Translation & Commentary Assistance TODOS.md phase 65 implemented
Variant Evaluation & Research TODOS.md phase 65 implemented
Text Encoding Standards TODOS.md phase 65 implemented
Reference, Citation & Linked Data Standards TODOS.md phase 65 implemented
Image & Annotation Standards TODOS.md phase 65 implemented
Research Environment TODOS.md phase 65 implemented
Personal Library & Export TODOS.md phase 65 implemented

Implementation-Derived Capability Surfaces#

Category Path Inferred Capability Surface
Library libs/nisaba/annotations/ Annotations
Library libs/nisaba/api-client/ Api Client
Library libs/nisaba/assistant/ Assistant
Library libs/nisaba/canon/ Canon
Library libs/nisaba/client/ Client
Library libs/nisaba/comparative/ Comparative
Library libs/nisaba/core/ Core
Library libs/nisaba/corpora/ Corpora
Library libs/nisaba/criticism/ Criticism
Library libs/nisaba/database/ Database
Library libs/nisaba/editions/ Editions
Library libs/nisaba/geotemporal/ Geotemporal
Library libs/nisaba/languages/ Languages
Library libs/nisaba/paleography/ Paleography
Library libs/nisaba/philology/ Philology
Library libs/nisaba/schemas/ Schemas
Library libs/nisaba/standards/ Standards
Library libs/nisaba/translations/ Translations
Library libs/nisaba/workspace/ Workspace

Canonical Standalone Feature Coverage#

No standalone features.md headings discovered for this domain.

Detailed TODO Phase Coverage#

Phase 65: Nisaba - Ancient Text Analysis & Cross-Tradition Scholarly Research Platform#

  • Checklist items captured: 243
  • Source: TODOS.md

Named for Nisaba (𒀭𒉀) — the Sumerian goddess of writing, learning, grain, and reeds. She is the divine scribe who kept the accounts of the gods, the inventor of cuneiform script, and the patron of the world's first libraries. Her temple, É-zagin ("House of Lapis Lazuli"), was the prototype of every library and archive that followed. She predates every other deity associated with writing — older than Thoth, older than Seshat, older than Saraswati. She belongs to the civilization that invented writing itself. Her dual patronage of grain (agriculture) and writing (knowledge) reflects how civilization and literacy co-evolved. As daughter of An (the supreme sky god), she bridges heaven and earth — divine wisdom made accessible through the written word.

Domain Vision: Nisaba is the world's first comprehensive, AI-powered scholarly platform for ancient text analysis and cross-tradition research. The platform provides state-of-the-art tools for analyzing ancient texts across all world traditions (Sumerian, Egyptian, Hebrew, Greek, Sanskrit, Chinese, Arabic, Pali, and beyond) in their original languages, comparing translations with precision, performing textual criticism from manuscript collation to critical edition publishing, and discovering the deep connections between philosophical and religious traditions throughout human history. Inspired by the insight that ancient traditions across cultures independently arrived at the same ineffable truths — from the Tao Te Ching's "The Tao that can be spoken is not the eternal Tao" to Jesus's use of parables, from the Buddhist "finger pointing at the moon" to the Hindu concept of Brahman as neti neti — Nisaba provides the tools to trace these connections through rigorous scholarship, not speculation. Every claim of parallel or influence must be grounded in textual evidence, philological analysis, chronological plausibility, and verifiable citation.

Domain Assignment: Nisaba Library Prefix: @nisaba/* Goddess: Nisaba — Sumerian goddess of writing, learning, grain, and reeds; inventor of cuneiform; divine scribe of the gods

Key Capabilities:

  • Ancient language engine with 20+ writing systems, morphological parsing, transliteration, and lexicon integration (BDB, LSJ, Monier-Williams, CAD, PSD, Lewis & Short, Lane, PTS Pali dictionary)
  • Translation comparison engine with side-by-side, synoptic, and interlinear views, alignment algorithms (Gale-Church, neural), and divergence detection
  • Full textual criticism workflow: manuscript witness registry, CollateX- compatible collation, variant classification, stemmatic analysis (phylogenetic methods), critical apparatus generation, lacuna tracking
  • Canonical text management for Bible (all canons), Quran, Buddhist Canon (Pali, Chinese, Tibetan), Hindu scriptures, Jewish texts, and classical Greco-Roman references with cross-system resolution
  • Paleographic analysis with ML-based script classification, scribal hand identification, damaged text enhancement, and dating estimation
  • Philological analysis with etymology tracking, semantic field analysis, hapax legomena detection, discourse analysis, and intertextuality detection
  • Cross-tradition concept mapping (Nirvana ~ Moksha ~ Theosis ~ Fana), parallel passage detection, motif/theme tracking, and influence network mapping
  • Open-source corpora integration (Perseus, ETCSL, CDLI, SuttaCentral, CBETA, Sefaria, OpenITI, SARIT, and 7+ more)
  • Annotation and commentary system (W3C Web Annotation, Talmudic-style layered commentary, CRDT-based collaborative annotation)
  • Digital critical edition tools (apparatus composition, TEI-XML/EpiDoc export, print-ready PDF, collaborative editing workflows)
  • Temporal-geographic mapping (Pleiades gazetteer, PeriodO, multi-calendar timeline, spatial search)
  • AI scholarly assistant (grounded commentary generation, variant evaluation, research gap identification, linguistic dating analysis)
  • Comprehensive standards support (TEI-XML, OSIS, USFM, CTS/CITE, IIIF, W3C Web Annotation, RDF/SPARQL, BibTeX/RIS/CSL)
  • Scholarly workspace with configurable reading environment, unified multi- corpus search, personal library, and export pipeline

Technology Stack:

  • TypeScript (~80%): Core infrastructure, search, workspace, API, corpora connectors, annotation system, edition tools, standards, comparisons
  • Rust/WASM (~15%): High-performance morphological parsers, collation algorithms, sandhi decomposition, transliteration engines
  • Python (~5%): ML model training for paleographic classification, alignment models, scribal hand identification
  • PostgreSQL with nisaba schema, Redis caching, Qdrant (via Sophia) for vector search
  • fast-xml-parser for TEI-XML processing, custom CollateX-compatible collation
  • Sophia integration for document ingestion, vector search, knowledge graph, citation management, and embeddings
  • Vitest for testing, Nx with esbuild/swc for builds

65.1 Nisaba Domain Infrastructure Setup#

65.1.1 Directory Structure & Nx Configuration#
  • 65.1.1.1 Create Nisaba domain directory structure with all 18 top-level library directories under libs/nisaba/: core/, schemas/, database/, languages/, translations/, criticism/, canon/, paleography/, philology/, comparative/, corpora/, annotations/, editions/, geotemporal/, assistant/, standards/, workspace/, client/ — each containing src/, package.json, project.json, tsconfig.json, tsconfig.lib.json, tsconfig.spec.json, and vitest.config.ts

  • 65.1.1.2 Configure all 18 project.json files with proper Nx targets (build, test, lint, typecheck) and inter-library dependency declarations: core first, then schemas, then database, then languages and canon (parallel), then translations/criticism/corpora/standards (parallel), then philology/comparative/annotations/paleography/ geotemporal (parallel), then editions/assistant (parallel), then workspace and client last — with proper implicitDependencies and tags for scope:nisaba enforcement

  • 65.1.1.3 Add all TypeScript path mappings to tsconfig.base.json following the pattern @nisaba/core, @nisaba/schemas, @nisaba/database, @nisaba/languages, @nisaba/translations, @nisaba/criticism, @nisaba/canon, @nisaba/paleography, @nisaba/philology, @nisaba/comparative, @nisaba/corpora, @nisaba/annotations, @nisaba/editions, @nisaba/geotemporal, @nisaba/assistant, @nisaba/standards, @nisaba/workspace, @nisaba/client for all 18 library paths

  • 65.1.1.4 Add scope:nisaba to ESLint module boundaries configuration in eslint.config.js, defining allowed dependency rules: Nisaba libraries can depend on @sophia/schemas, @sophia/database, @sophia/search, @oshun/ai, @oshun/database, @oshun/events; cannot depend on @iris/*, @hathor/*, @kuanyin/*, @themis/*

  • 65.1.1.5 Configure Rust/WASM build integration for libs/nisaba/languages/rust/ with Cargo workspace, wasm-pack build targets, and Nx executor wrapping cargo build --release and wasm-pack build --target web

65.1.2 Database & Infrastructure#
  • 65.1.2.1 Create Nisaba database schema in Prisma (libs/nisaba/database/prisma/schema.prisma) with models for: Manuscript (witness metadata, siglum, date, provenance, script type, material, dimensions, repository, catalog number, IIIF manifest URL), CollationProject (base text, witness set, normalization rules), VariantUnit (locus, variant readings, witness attestations, classification), CriticalEdition (project metadata, base text, apparatus entries, version), Annotation (standoff offsets, type, layer, body, creator, status), AnnotationLayer (name, type, permissions), ConceptMapping (source concept, target concept, similarity type, evidence grade), MotifAttestation (motif ID, tradition, text reference, date), InfluenceEdge (source tradition, target tradition, evidence grade, scholarly citations), CanonicalReference (tradition, work, reference string, normalized URI), PaleographicAnalysis (manuscript ID, features JSON, date estimate, confidence), ScribalHand (identifier, manuscripts, habits JSON, date range), ResearchProject (name, type, members, status), PersonalLibraryItem (user, document, collection, tags), Bookmark (user, document, offset, note)

  • 65.1.2.2 Create database seed script (libs/nisaba/database/prisma/seed.ts) with reference data: canonical reference system definitions for Bible (Protestant 66 books, Catholic 73 books, Orthodox extended canon, Hebrew Bible Tanakh ordering), Quran (114 surahs with names), Pali Canon (PTS structure), Bhagavad Gita (18 chapters), Stephanus pages for Plato, Bekker pages for Aristotle, Diels-Kranz for Pre-Socratics; initial cuneiform sign list entries; tradition definitions for all major world traditions

  • 65.1.2.3 Create database migration configuration, Prisma client factory (libs/nisaba/database/src/client.ts), and index exports (libs/nisaba/database/src/index.ts) following Sophia's database library patterns

  • 65.1.2.4 Add Nisaba database to Docker Compose development environment: add nisaba to POSTGRES_MULTIPLE_DATABASES in docker/docker-compose.dev.yml, create docker/init-scripts/nisaba-init.sql with pgvector extension and initial schema

  • 65.1.2.5 Add Nisaba environment variables to root .env: NISABA_DATABASE_URL, NISABA_REDIS_PREFIX, embedding model configuration for ancient language vocabularies, corpus API keys (Sefaria API, CDLI API), and IIIF server configuration

65.1.3 Core Domain Types & Utilities#
  • 65.1.3.1 Implement core type definitions (@nisaba/core/types) including: WritingSystem enum (cuneiform-sumerian, cuneiform-akkadian, cuneiform-hittite, cuneiform-elamite, cuneiform-ugaritic, hieroglyphic-egyptian, hieratic, demotic, coptic, hebrew-square, paleo-hebrew, aramaic-imperial, aramaic-syriac, arabic-classical, geez, phoenician, greek-ancient, latin-classical, devanagari, sinhala, thai-pali, burmese-pali, khmer-pali, tibetan, chinese-classical, linear-b, etruscan, old-persian, avestan, old-church-slavonic, runic-elder-futhark, runic-younger-futhark, kharoshthi, sogdian, tocharian), Tradition enum, CanonicalReferenceSystem type, MorphologicalParse type (root, stem, pattern, person, gender, number, state, tense, aspect, mood, voice, case, suffixes), LexiconEntry type, TransliterationScheme enum, ManuscriptMaterial enum, VariantClassification enum, ApparatusFormat enum, AnnotationType enum, SimilarityTaxonomy enum, EvidenceGrade enum

  • 65.1.3.2 Implement script metadata constants (@nisaba/core/constants): Unicode block ranges for each writing system, script direction (LTR, RTL, TTB), diacritical marks and combining characters per script, ISO 15924 script codes, ISO 639-3 language codes for all supported ancient languages, tradition identifiers with chronological and geographic metadata

  • 65.1.3.3 Implement domain-specific error types (@nisaba/core/errors): MorphologyParseError, TransliterationError, LexiconLookupError, CollationError, ReferenceResolutionError, CorpusConnectionError, TEIParseError, AlignmentError, ApparatusGenerationError, PaleographicAnalysisError, DateEstimationError, ConceptMappingError, IIIFError — each with contextual data (language, script, source text, position)

  • 65.1.3.4 Implement utility functions (@nisaba/core/utils): Unicode normalization for ancient scripts (NFC/NFD with script-specific rules), byte offset calculation for standoff annotations across multi-byte Unicode text, canonical reference string normalization, confidence score aggregation, fuzzy date comparison utilities, scholarly citation formatting helpers

65.1.4 Zod Schemas#
  • 65.1.4.1 Implement manuscript/witness schemas (@nisaba/schemas/manuscript): ManuscriptSchema with fields for siglum, date (fuzzy), provenance chain, script type, material, dimensions, current repository, catalog number, digitization status, IIIF manifest URL, text family classification, witness hierarchy (parent groups), language, tradition; WitnessClassificationSchema for majuscule/minuscule, scroll/codex, text family assignment; CreateManuscriptSchema, UpdateManuscriptSchema, ManuscriptQuerySchema with filtering by date range, provenance, script type, tradition, repository

  • 65.1.4.2 Implement variant/collation schemas (@nisaba/schemas/variant, @nisaba/schemas/collation): VariantReadingSchema with text, witness sigla, classification (orthographic, morphological, lexical, syntactic, semantic, substantial, nonsense), probable cause (haplography, dittography, homoioteleuton, homoioarcton, metathesis, itacism, harmonization, theological alteration); CollationResultSchema with variant graph representation, alignment table, variant units; CollationConfigSchema with normalization rules, fuzzy match threshold, transposition detection toggle

  • 65.1.4.3 Implement critical apparatus schemas (@nisaba/schemas/apparatus): ApparatusEntrySchema with lemma, variant readings, witness attestations, scholarly judgment, format (positive, negative, mixed, Leiden), cross-references; ApparatusConfigSchema with format preference, siglum style, grouping rules; CriticalEditionSchema with base text, apparatus entries, introduction metadata, version, collaborators, status

  • 65.1.4.4 Implement annotation schemas (@nisaba/schemas/annotation): AnnotationSchema conforming to W3C Web Annotation Data Model with id, type, body (textual, linguistic, translation, critical, comparative, structural, pedagogical), target (standoff selector with start/end offsets), creator, created, modified, layer, status (draft, review, published), permissions; AnnotationLayerSchema, AnnotationExportSchema (WADM JSON-LD, TEI-XML, Hypothesis format)

  • 65.1.4.5 Implement canonical reference schemas (@nisaba/schemas/reference): CanonicalReferenceSchema with tradition, work, book/chapter/verse/line/folio/page decomposition, normalized URI (nisaba://tradition/work/ref), display string; VersificationMappingSchema for cross-system mappings (MT ↔ LXX ↔ English, Buddhist PTS ↔ Thai ↔ Burmese); ReferenceRangeSchema for passage ranges

  • 65.1.4.6 Implement tradition/concept mapping schemas (@nisaba/schemas/tradition): ConceptMappingSchema with source concept (name, tradition, definition, primary sources), target concept, similarity type (genetic, typological, analogical, contested), evidence grade (documented, strong, probable, possible, speculative), scholarly citations, scholarly consensus level; MotifSchema with name, description, attestations across traditions; InfluenceEdgeSchema with source tradition, target tradition, evidence grade, date range, scholarly citations

  • 65.1.4.7 Implement corpus and paleography schemas (@nisaba/schemas/corpus, @nisaba/schemas/paleography): CorpusMetadataSchema with name, URL, API type, languages covered, traditions covered, license, last sync timestamp; PaleographicFeatureSchema with stroke angle measurements, aspect ratios, serif presence, ligature patterns, ductus analysis; DateEstimationSchema with probability distribution (earliest, latest, peak, confidence percentage), calibration data references; ScribalHandSchema with identifier, manuscripts, spelling preferences, abbreviation patterns, error tendencies

  • 65.1.4.8 Implement geotemporal schemas (@nisaba/schemas/geotemporal): FuzzyDateSchema with earliest, latest, era (BCE/CE), display string, calendar system, confidence; ProvenanceChainSchema with ordered location/date/owner entries; HistoricalLocationSchema with Pleiades ID, coordinates, PeriodO period, modern name, ancient name(s); TimelineEventSchema with multi-calendar date representation, tradition, significance


65.2 Ancient Language Engine (@nisaba/languages)#

65.2.1 Writing System Support — Semitic Scripts#
  • 65.2.1.1 Implement Biblical Hebrew script handler with full Unicode support for consonants, Tiberian vowel points (qamets, patach, tsere, segol, hiriq, holem, qibbuts, shureq, qamets hatuf), cantillation marks (all te'amim), dagesh (lene and forte distinction), shin/sin dot, maqqef, sof pasuq, maqaf, and ketiv/qere notation; support for Babylonian and Palestinian vocalization systems

  • 65.2.1.2 Implement Aramaic script handlers for Imperial Aramaic, Biblical Aramaic (using Hebrew square script with Aramaic-specific features), and Syriac in all three script variants: Estrangela, Serto (West Syriac), and Eastern (East Syriac/Madnhaya) with diacritical vowel marks (Jacobite and Nestorian systems)

  • 65.2.1.3 Implement Classical Arabic script handler with full Unicode support for consonants, short vowels (fatha, kasra, damma), tanwin (nunation), sukun, shadda, hamza positions (above/below alif, on waw, on ya, on line), Quranic orthographic conventions including tajweed markers (idgham, iqlab, ikhfa, ghunna), pause marks (mandatory, permissible, prohibited), and sajda indicators

  • 65.2.1.4 Implement Ge'ez/Ethiopic script handler with the full syllabary (base consonants × 7 vowel orders), Amharic extensions, numeral system, and punctuation marks (word divider, full stop, comma, colon, preface colon, question mark)

  • 65.2.1.5 Implement Phoenician, Paleo-Hebrew, Moabite (Mesha Stele conventions), and Samaritan script handlers with Unicode block mappings and transliteration support

65.2.2 Writing System Support — Cuneiform Scripts#
  • 65.2.2.1 Implement Sumerian cuneiform handler with support for logographic and syllabic readings, determinative classification (semantic classifiers: dingir/god, ki/place, lu2/person, giš/wood, etc.), sign list integration (Borger MZL, aBZL, CDLI sign values), sign variant tracking, and composite sign decomposition

  • 65.2.2.2 Implement ATF (ASCII Transliteration Format) parser and generator for cuneiform texts: support for sign names, sign values, determinatives, glosses, damage notation (broken, effaced, illegible), editorial marks, line numbering, composite text assembly, and round-trip fidelity between ATF and Unicode cuneiform

  • 65.2.2.3 Implement Akkadian cuneiform handler supporting Old Babylonian, Standard Babylonian, and Neo-Assyrian dialect conventions, with syllabic value disambiguation and logogram-to- Akkadian reading resolution using context-based heuristics

  • 65.2.2.4 Implement Hittite and Elamite cuneiform handlers with language-specific sign value tables and determinative conventions

  • 65.2.2.5 Implement Ugaritic cuneiform alphabetic handler with the 30-letter alphabet, word divider, and transliteration support

65.2.3 Writing System Support — Egyptian Scripts#
  • 65.2.3.1 Implement Egyptian hieroglyphic handler with Gardiner sign list integration (all categories A-Z, Aa), Manuel de Codage (MdC) encoding support for scholarly input, JSesh-compatible rendering output, cartouche boundaries, direction indicators (left-facing/right-facing), and support for Middle Egyptian, Late Egyptian, and Ptolemaic sign extensions

  • 65.2.3.2 Implement Hieratic script handler with period-specific paleographic conventions and hieratic-to-hieroglyphic conversion tables for scholarly use

  • 65.2.3.3 Implement Demotic script handler with Unicode support and transliteration following standard Demotic conventions

  • 65.2.3.4 Implement Coptic script handler with full support for all major dialects: Sahidic, Bohairic, Akhmimic, Fayyumic, and Lycopolitan, including dialect-specific letters and supralinear strokes

65.2.4 Writing System Support — South Asian Scripts#
  • 65.2.4.1 Implement Sanskrit/Devanagari handler with full Unicode support for consonants, vowels, conjunct consonants (ligatures), virama, anusvara, visarga, chandrabindu, avagraha, and Vedic accent marks (udatta, anudatta, svarita); support for multiple transliteration schemes: IAST (primary), Harvard-Kyoto, SLP1, Velthuis, ISO 15919

  • 65.2.4.2 Implement Pali multi-script handler supporting Devanagari, Roman (with PTS transliteration conventions), Sinhala, Thai, Burmese, and Khmer script representations with cross-script conversion maintaining semantic identity

  • 65.2.4.3 Implement Prakrit language handlers for Ardhamagadhi (Jain canonical language), Shauraseni, and Maharashtri with dialect-specific phonological rules

  • 65.2.4.4 Implement Tibetan script handler with Wylie transliteration support, proper stack construction for consonant clusters, tsheg (syllable separator), and shad (phrase/sentence delimiter)

  • 65.2.4.5 Implement Tamil Brahmi, Grantha, and Kharoshthi script handlers for early Indic inscriptional texts

65.2.5 Writing System Support — East Asian & Other Scripts#
  • 65.2.5.1 Implement Classical Chinese handler with support for traditional characters (not simplified), proper segmentation of Literary Chinese (文言文) without word boundaries, punctuation insertion heuristics for unpunctuated texts, and variant character tracking (異體字)

  • 65.2.5.2 Implement Ancient Greek handler with full polytonic accentuation support (acute, grave, circumflex, rough/smooth breathing, iota subscript/adscript, diaeresis, coronis), dialectal orthographic variants (Attic, Ionic, Doric, Aeolic), and numeral system (Attic, Ionic/Milesian)

  • 65.2.5.3 Implement Latin handler with Classical orthographic conventions (no distinction between U/V and I/J in inscriptions), Medieval Latin extensions, Ecclesiastical Latin conventions, and abbreviation expansion for common medieval abbreviations

  • 65.2.5.4 Implement Avestan script handler (Gathic Avestan and Younger Avestan) and Old Persian cuneiform script handler with proper syllabic sign representation

  • 65.2.5.5 Implement Old Church Slavonic handlers for both Glagolitic and Early Cyrillic alphabets, runic script handlers for Elder Futhark, Younger Futhark, and Anglo-Saxon Futhorc, and Linear B handler for Mycenaean Greek syllabic writing

65.2.6 Morphological Parsers#
  • 65.2.6.1 Implement Hebrew morphological parser with complete verb paradigm coverage: all 7 major stems (Qal, Niphal, Piel, Pual, Hiphil, Hophal, Hithpael), all conjugations (perfect, imperfect, imperative, infinitive construct, infinitive absolute, participle), weak root detection (I-Nun, I-Yod, I-Aleph, II-Waw/Yod, III-He, Geminate), pronominal suffix decomposition (subject and object suffixes), construct chain analysis, waw-consecutive identification, and definite article/preposition/conjunction prefix stripping

  • 65.2.6.2 Implement Greek morphological parser with full nominal paradigm (3 declensions, all cases including dual), verbal paradigm (all tenses: present, imperfect, future, aorist, perfect, pluperfect, future perfect; all moods: indicative, subjunctive, optative, imperative, infinitive, participle; all voices: active, middle, passive), augment detection (syllabic and temporal), contract verb resolution (alpha, epsilon, omicron contracts), middle/passive distinction in aorist and future, participle agreement tracking, and enclitic/proclitic handling

  • 65.2.6.3 Implement Latin morphological parser with all 5 declensions (including irregular nouns), 4 conjugations plus irregular verbs (sum, eo, fero, volo, possum, etc.), deponent and semi-deponent verb detection, ablative absolute identification, gerund/gerundive distinction, and supine recognition

  • 65.2.6.4 Implement Sanskrit morphological parser in Rust (WASM) for performance: external sandhi decomposition (vowel sandhi, consonant sandhi, visarga sandhi with all rules), internal sandhi, compound analysis with classification (tatpurusha, dvandva, bahuvrihi, avyayibhava, dvigu), vibhakti (case) parsing for 8 cases × 3 numbers, verb conjugation (10 present classes, all tenses/moods), and secondary derivation identification

  • 65.2.6.5 Implement Arabic morphological parser with root-pattern (trilateral and quadrilateral) extraction, Form I-X identification and semantic description, broken plural detection and classification, idafa (construct state) chain analysis, dual number support, and passive voice detection

  • 65.2.6.6 Implement Akkadian morphological parser with G-stem, D-stem, Š-stem, N-stem (and Gt, Dt, Št, Ntn iterative forms), stative conjugation, ventive suffix detection, and subordination marker handling

  • 65.2.6.7 Implement Sumerian morphological parser with verbal chain analysis (dimensional prefixes, modal prefixes, conjugation prefixes, pronominal elements, stem, pronominal suffixes), nominal chain parsing (noun + possessive + case marker), and finite/non-finite verb distinction

  • 65.2.6.8 Implement Pali morphological parser with sandhi decomposition (simpler than Sanskrit but still required), nominal declension (6 groups), verb conjugation (present, aorist, future, imperative, optative, conditional, gerund, infinitive, participle), and compound analysis

  • 65.2.6.9 Implement Coptic morphological parser with tripartite conjugation system (First Present, Second Present, Circumstantial, etc.), prenominal/prepronominal state handling, and bound group analysis

65.2.7 Tokenization#
  • 65.2.7.1 Implement base tokenizer interface with configurable granularity (morpheme, word, phrase, clause), position-preserving byte offset tracking for standoff annotation alignment, and Unicode normalization pre-processing

  • 65.2.7.2 Implement Hebrew tokenizer with clitic separation (inseparable prepositions, conjunctive waw, definite article, relative pronoun she-), maqqef-joined word handling, and ketiv/qere token distinction

  • 65.2.7.3 Implement Greek tokenizer with enclitic/proclitic handling, crasis resolution, elision detection, and movable-nu normalization

  • 65.2.7.4 Implement Sanskrit tokenizer using the Rust WASM sandhi decomposition module for automatic word boundary detection in continuous sandhi text

  • 65.2.7.5 Implement Arabic tokenizer with proclitic (wa-, fa-, bi-, li-, ka-, al-) and enclitic separation, and handling of orthographic variants (ta marbuta, alif maqsura, hamza seat)

  • 65.2.7.6 Implement Classical Chinese tokenizer with ML-assisted word segmentation for texts without explicit word boundaries, using character bigram/trigram models trained on annotated classical Chinese corpora

65.2.8 Transliteration Engine#
  • 65.2.8.1 Implement core transliteration engine with bidirectional native-script ↔ romanization conversion, support for multiple romanization schemes per language, round-trip fidelity validation, and scholarly convention compliance (SBL Handbook of Style, Chicago Manual of Style)

  • 65.2.8.2 Implement Hebrew transliteration schemes: SBL academic, simplified (no diacritics), general-purpose with full vowel representation, and Library of Congress (ALA-LC) romanization

  • 65.2.8.3 Implement Greek transliteration with proper handling of rough/smooth breathing, polytonic accents, and both scholarly (preserving accents) and simplified (ASCII-only) modes

  • 65.2.8.4 Implement Sanskrit transliteration with IAST (primary scholarly standard), Harvard-Kyoto (ASCII-only, widely used in databases), SLP1 (compact computational format), Velthuis (legacy TeX format), and ISO 15919 bidirectional conversion

  • 65.2.8.5 Implement Arabic transliteration with DIN 31635 (primary scholarly standard), ALA-LC (Library of Congress), and Buckwalter (computational) schemes

  • 65.2.8.6 Implement cuneiform transliteration supporting ATF conventions for sign values, determinatives (superscript notation), and damage notation

65.2.9 Lexicon Integration#
  • 65.2.9.1 Implement unified lexicon lookup API (LexiconService) with language-specific lexicon chain resolution, cross-language cognate linking, semantic domain grouping, and frequency data integration — providing a single lookup(word, language, options) interface that returns structured LexiconEntry results from all available lexica for that language

  • 65.2.9.2 Implement BDB (Brown-Driver-Briggs) Hebrew-Aramaic lexicon connector with root-based lookup, semantic domain cross- referencing, and scriptural reference linking (public domain)

  • 65.2.9.3 Implement LSJ (Liddell-Scott-Jones) Greek-English lexicon connector with full entry parsing, cross-references, and citation lookup (public domain via Perseus)

  • 65.2.9.4 Implement Lewis & Short Latin dictionary connector with lemma lookup, principal parts cross-referencing, and usage example extraction (public domain via Perseus)

  • 65.2.9.5 Implement Monier-Williams Sanskrit-English dictionary connector with Devanagari/IAST dual lookup, compound decomposition assistance, and Vedic/Classical usage distinction (public domain)

  • 65.2.9.6 Implement CAD (Chicago Assyrian Dictionary) and ePSD2 (electronic Pennsylvania Sumerian Dictionary) connectors for Akkadian and Sumerian lexicon lookup (public domain / open access)

  • 65.2.9.7 Implement PTS Pali-English Dictionary connector and Lane's Arabic-English Lexicon connector for Pali and Classical Arabic lookup (public domain)

  • 65.2.9.8 Implement lexicon extension API allowing users to connect their own licensed lexica (HALOT, BDAG) via a plugin interface, with standardized LexiconEntry output format


65.3 Translation Comparison Engine (@nisaba/translations)#

65.3.1 Display Modes#
  • 65.3.1.1 Implement side-by-side translation view with parallel columns synchronized by verse/line/paragraph anchors, configurable number of columns (2-6), independent scrolling with sync lock toggle, and visual alignment indicators for corresponding segments

  • 65.3.1.2 Implement synoptic view with horizontal layout showing all versions of a passage simultaneously, color-coded alignment markers, and expandable/collapsible segment groups

  • 65.3.1.3 Implement interlinear view with source language text, morphological parsing line (POS, stem, form), gloss line (word-by- word translation), and one or more smooth translation lines beneath — supporting right-to-left source texts with left-to-right glosses

  • 65.3.1.4 Implement reverse interlinear view with translation text as primary, source language words and morphological data displayed above each translated word/phrase, with clickable links to full lexicon entries

65.3.2 Alignment Algorithms#
  • 65.3.2.1 Implement Gale-Church sentence alignment algorithm (length-based) adapted for ancient text segments (verse, shloka, ayah, line) with configurable segment type and penalty parameters

  • 65.3.2.2 Implement word-level alignment using IBM Model 1 adaptation for ancient language pairs, with bilingual concordance bootstrapping for Hebrew-English, Greek-English, Latin-English, Sanskrit-English, and Arabic-English

  • 65.3.2.3 Implement neural alignment using multilingual transformer embeddings (e.g., XLM-R or mBERT fine-tuned on ancient language parallel corpora), with attention weight extraction for word alignment visualization

  • 65.3.2.4 Implement manual alignment interface allowing scholars to create, approve, or reject automatic alignments, with export capability as parallel corpus for model retraining

65.3.3 Divergence Detection#
  • 65.3.3.1 Implement semantic divergence scoring at word, phrase, clause, and sentence levels using embedding cosine distance calibrated against human divergence judgments

  • 65.3.3.2 Implement theological divergence flagging with a configurable rule engine for known translation controversy points: Isaiah 7:14 (almah), Romans 3:25 (hilasterion), Galatians 2:16 (pistis Christou), John 1:1 (theos/ho theos), Philippians 2:6 (harpagmon), Genesis 1:1-2 (creation ex nihilo vs. from chaos), and user-definable rules for other traditions

  • 65.3.3.3 Implement omission/addition detection identifying material present in one translation but absent in another, with classification of probable cause (textual basis difference, interpretive addition, dynamic equivalence expansion)

  • 65.3.3.4 Implement formal-dynamic equivalence scoring quantifying where each translation falls on Nida's spectrum, using structural preservation metrics (word order retention, syntactic mirroring) and semantic fidelity metrics

  • 65.3.3.5 Implement translation history timeline showing how specific passages have been translated across centuries, with influence mapping between translation traditions (e.g., Tyndale → KJV → RSV → NRSV lineage for English Bible)


65.4 Textual Criticism Engine (@nisaba/criticism)#

65.4.1 Manuscript Witness Registry#
  • 65.4.1.1 Implement manuscript witness CRUD with full metadata: siglum, date (fuzzy), provenance chain, script type, material (papyrus, parchment, paper, clay, stone, bone, metal), dimensions, current repository, catalog number, digitization status (none, partial, full, multispectral), condition assessment, and content description

  • 65.4.1.2 Implement witness classification system for multiple traditions: majuscule/minuscule for Greek, scroll/codex format, text family assignment (Alexandrian, Byzantine, Western, Caesarean for NT; Masoretic families for Hebrew Bible; recension families for LXX), and versional witness categories (translations used as textual witnesses: LXX, Vulgate, Peshitta, Coptic versions, Ethiopic, Armenian, Georgian, Old Latin, Old Syriac)

  • 65.4.1.3 Implement hierarchical witness organization with support for family groups (e.g., f1, f13 in NT criticism), versional witness grouping, patristic citation witnesses, and lectionary witnesses

  • 65.4.1.4 Implement IIIF manifest linking for each witness, enabling side-by-side text and facsimile image viewing using IIIF Presentation API v3 manifests, with canvas-to-text-position mapping

65.4.2 Collation Engine#
  • 65.4.2.1 Implement CollateX-compatible collation algorithm (Dekker's variant graph model) in TypeScript: token-based alignment with Needleman-Wunsch scoring, variant graph construction, and variant unit boundary detection

  • 65.4.2.2 Implement fuzzy matching for orthographic variants with language-specific normalization rules: itacism in Greek (ι/η/ει/οι interchange), matres lectionis variation in Hebrew (plene/defective spelling), gemination variation in Akkadian, and configurable normalization profiles per collation project

  • 65.4.2.3 Implement transposition detection for identifying word/phrase order changes between witnesses, distinguishing true transpositions from independent variation

  • 65.4.2.4 Implement block-level alignment for handling larger structural variants (missing/added paragraphs, displaced sections) beyond word-level collation

  • 65.4.2.5 Implement manual collation interface with accept/reject controls for automatic alignments, custom variant unit boundary adjustment, uncertain reading markers, and scholar notes per variant unit

  • 65.4.2.6 Implement collation output formats: variant graph (JSON, interactive SVG visualization), alignment table (HTML, CSV), TEI-XML apparatus entries (positive, negative, mixed), and JSON collation interchange format for interoperability

65.4.3 Variant Classification#
  • 65.4.3.1 Implement ML-assisted variant classification with categories: orthographic (spelling only), morphological (different grammatical form, same lexeme), lexical (synonym substitution), syntactic (word order), semantic (meaning-affecting), substantial (clause-level additions/omissions/transpositions), and nonsense (scribal errors producing non-words) — using a combination of morphological parser output, embedding similarity, and heuristic rules

  • 65.4.3.2 Implement scribal error taxonomy with classification by probable cause: haplography, dittography, homoioteleuton, homoioarcton, metathesis, letter confusion (similar letterforms), itacism (vowel interchange), harmonization (assimilation to parallel passages), and deliberate theological alteration detection with confidence scoring

65.4.4 Stemmatic Analysis#
  • 65.4.4.1 Implement maximum parsimony algorithm (Fitch algorithm) for manuscript stemma construction from collation data, with bootstrapping for confidence assessment on tree topology

  • 65.4.4.2 Implement NeighborNet algorithm for visualizing conflicting phylogenetic signals (reticulation/contamination) in manuscript traditions, producing split network graphs

  • 65.4.4.3 Implement contamination detection using consistency index analysis and split decomposition, identifying manuscript traditions that cross-pollinated

  • 65.4.4.4 Implement CBGM (Coherence-Based Genealogical Method) compatibility analysis for evaluating genealogical coherence of variant readings, following the methodology used in the Editio Critica Maior of the Greek New Testament

  • 65.4.4.5 Implement traditional Lachmannian stemmatic reconstruction support with conjunctive/separative error identification, archetype reconstruction, and stemma export to Newick/Nexus format for visualization in external tools

  • 65.4.4.6 Implement interactive stemma visualization with confidence indicators on branches, alternative stemma proposals, and click-through to supporting variant evidence

65.4.5 Critical Apparatus Generation#
  • 65.4.5.1 Implement apparatus generation from collation data with support for positive apparatus (all witnesses for each reading), negative apparatus (only divergent witnesses), and mixed apparatus (Nestle-Aland style with majority text abbreviation)

  • 65.4.5.2 Implement Leiden conventions for epigraphic apparatus with proper bracket notation for supplied text, uncertain readings, lacunae, erasures, and editorial corrections

  • 65.4.5.3 Implement siglum and abbreviation management with witness shorthand definition, family group notation (e.g., "𝔐" for Majority Text), and automatic siglum assignment for new witnesses

  • 65.4.5.4 Implement apparatus typography rendering with proper Unicode support for all scripts, superscript sigla, traditional apparatus layout conventions, and print-quality output suitable for LaTeX/PDF critical edition formatting

65.4.6 Lacuna Tracking#
  • 65.4.6.1 Implement physical lacuna registry documenting damage to manuscripts: extent (character/word/line/column count), probable cause (physical damage, fading, deliberate erasure), partial legibility assessment, and multispectral imaging availability

  • 65.4.6.2 Implement reconstruction proposal system with confidence levels per reconstructed character/word, supporting evidence from parallel witnesses or formulaic patterns, and multiple competing proposals with scholarly attribution


65.5 Canonical Text Management (@nisaba/canon)#

65.5.1 Biblical Canon Systems#
  • 65.5.1.1 Implement Protestant canon reference system (66 books, 39 OT + 27 NT) with chapter/verse numbering, book abbreviation tables (SBL, OSIS, Paratext standards), and verse range parsing

  • 65.5.1.2 Implement Catholic canon reference system (73 books) adding Tobit, Judith, 1-2 Maccabees, Wisdom, Sirach, Baruch, and additions to Daniel and Esther with proper chapter/verse numbering

  • 65.5.1.3 Implement Orthodox canon systems: Greek Orthodox (adding 1 Esdras, Prayer of Manasseh, Psalm 151, 3-4 Maccabees) and Ethiopian Orthodox (adding 1 Enoch, Jubilees, broader canon) with appropriate reference systems

  • 65.5.1.4 Implement Hebrew Bible (Tanakh) reference system with Torah/Nevi'im/Ketuvim ordering and verse numbering differences from Christian Old Testament

  • 65.5.1.5 Implement Septuagint (LXX) reference system with Rahlfs numbering and chapter/verse mapping to MT (Masoretic Text)

  • 65.5.1.6 Implement versification mapping engine for automated conversion between versification systems: MT ↔ LXX ↔ English, Psalm numbering differences (MT Psalm 10 = LXX Psalm 9b, etc.), and handling of divergent chapter/verse boundaries

65.5.2 Non-Biblical Canon Systems#
  • 65.5.2.1 Implement Quranic reference system with surah/ayah numbering (114 surahs), juz/hizb/rub divisions, and qira'at (variant reading) tracking for the 10 canonical readings (Hafs, Warsh, Qalun, al-Duri, etc.)

  • 65.5.2.2 Implement Pali Canon (Tipitaka) reference system with PTS (Pali Text Society) page numbering, sutta/nikaya reference format (DN 22, MN 10, SN 56.11, AN 3.65), Vinaya and Abhidhamma reference systems, and Thai/Burmese/Sinhalese edition numbering

  • 65.5.2.3 Implement Chinese Buddhist Canon reference system with Taishō Tripiṭaka numbering (T. volume/page/column/line), CBETA reference format, and Dunhuang manuscript numbering

  • 65.5.2.4 Implement Tibetan Buddhist Canon reference system with Kangyur/Tengyur classification, Derge edition numbering, and Tohoku catalog number cross-referencing with Peking, Narthang, and Cone editions

  • 65.5.2.5 Implement Hindu scripture reference systems: Rigveda (mandala/sukta/mantra), Mahabharata (parva/chapter/verse with both critical edition and Vulgate numbering), Ramayana (kanda/sarga/shloka), Bhagavad Gita (adhyaya/shloka), Yoga Sutras (pada/sutra), Brahma Sutras (adhyaya/pada/sutra), and major Upanishads

  • 65.5.2.6 Implement Jewish textual reference systems: Talmud (tractate/folio/amud), Mishnah (seder/tractate/chapter/mishnah), Tosefta, Midrash (collection/parasha/section), and Zohar

  • 65.5.2.7 Implement classical text reference systems: Stephanus pages for Plato, Bekker pages for Aristotle, Diels-Kranz for Pre-Socratics, standard line numbering for Homer/tragedy/comedy, and standard chapter/section for Cicero, Seneca, Livy, Tacitus; Avesta (yasna/ha), Confucian Analects (book/chapter), Daodejing (chapter), I Ching (hexagram/line)

65.5.3 Cross-System Reference Resolution#
  • 65.5.3.1 Implement canonical URI scheme with format nisaba://tradition/work/reference supporting all registered canon systems, with URI parsing, normalization, and display string generation

  • 65.5.3.2 Implement CTS/CITE protocol compliance layer for interoperability with Perseus Digital Library and other Canonical Text Services consumers/providers

  • 65.5.3.3 Implement bidirectional mapping service converting between reference systems (e.g., LXX Psalm 50 ↔ MT Psalm 51 ↔ English Psalm 51) with handling of ambiguous and one-to-many mappings


65.6 Paleographic Analysis (@nisaba/paleography)#

65.6.1 Script & Period Classification#
  • 65.6.1.1 Implement ML-based writing system classifier that identifies script type from manuscript images: cuneiform (Sumerian, Akkadian), hieroglyphic/hieratic/demotic Egyptian, Hebrew square script, Greek uncial/minuscule, Devanagari, Arabic, Syriac, Coptic, Latin, Tibetan, and other supported scripts — using a CNN-based classification model trained on labeled manuscript image datasets

  • 65.6.1.2 Implement period classification model estimating date range from script features: distinguishing Hasmonean from Herodian Hebrew hands (Dead Sea Scrolls dating), Greek majuscule periods (2nd-9th century CE), minuscule development stages, and similar period-diagnostic features for other scripts

  • 65.6.1.3 Implement regional classification for identifying scribal schools and geographic provenance by distinctive letterform features characteristic of specific writing centers

65.6.2 Letterform Analysis & Scribal Identification#
  • 65.6.2.1 Implement letterform feature extraction measuring quantitative features: stroke angle, aspect ratio, serif presence and style, ligature patterns, ductus (stroke order and direction), letter spacing, line height consistency, and baseline adherence

  • 65.6.2.2 Implement writer identification model for determining whether multiple manuscripts were written by the same scribe, using statistical comparison of extracted letterform features with confidence scoring

  • 65.6.2.3 Implement hand change detection within a single manuscript, identifying section boundaries where a different scribe took over, later additions, and corrections by second hands

  • 65.6.2.4 Implement scribal habit profiling cataloging spelling preferences, abbreviation patterns, error tendencies, and correction methods of identified scribes for cross-manuscript comparison

65.6.3 Damaged Text & Dating#
  • 65.6.3.1 Implement multispectral imaging integration for ingesting infrared, ultraviolet, and X-ray fluorescence image data to read faded, erased, or overwritten text (palimpsests), with image registration and layer separation

  • 65.6.3.2 Implement AI-assisted character reading model for suggesting probable letter readings for damaged or partially legible characters, with per-character confidence levels integrated into the textual criticism workflow

  • 65.6.3.3 Implement multi-factor dating model combining paleographic features, orthographic conventions, material analysis data (when available), and radiocarbon calibration curves to produce date estimates expressed as probability distributions (e.g., "70% probability between 150-50 BCE") rather than point estimates


65.7 Philological Analysis (@nisaba/philology)#

65.7.1 Etymology & Semantic Analysis#
  • 65.7.1.1 Implement cross-language cognate chain tracking for Proto-Semitic roots (→ Hebrew, Aramaic, Arabic, Akkadian, Ugaritic, Ge'ez), Proto-Indo-European roots (→ Sanskrit, Greek, Latin, Avestan, Old Persian), Sino-Tibetan root relationships, and Egyptian-Coptic etymological continuity

  • 65.7.1.2 Implement semantic drift visualization showing how word meanings shifted across languages and centuries (e.g., Hebrew ruach → "wind/breath/spirit" → Greek pneuma → Latin spiritus → English "spirit"), with attestation timeline and usage context examples

  • 65.7.1.3 Implement loanword detection algorithms identifying borrowed words across language boundaries: Sumerian loanwords in Akkadian, Persian loanwords in Biblical Hebrew, Greek loanwords in Rabbinic Hebrew, Sanskrit loanwords in Pali, and Arabic loanwords in Persian/Turkish/Urdu — using phonological correspondence rules and chronological filtering

  • 65.7.1.4 Implement semantic domain mapping following Louw-Nida framework (for NT Greek) and Semantic Dictionary of Biblical Hebrew approach, with cross-linguistic semantic field comparison (e.g., the range of Hebrew chesed vs. Greek agape/philia/eros vs. Sanskrit prema/bhakti/karuna)

  • 65.7.1.5 Implement collocational analysis identifying statistically significant word co-occurrences and fixed phrases within each corpus, and metaphor mapping following Lakoff-Johnson conceptual metaphor theory applied to ancient texts

65.7.2 Hapax Legomena & Statistical Linguistics#
  • 65.7.2.1 Implement hapax legomena detection with automatic flagging of words occurring only once (hapax) or twice (dis legomena) in a corpus, with cross-corpus checking to determine if a hapax in one corpus appears in related corpora (e.g., NT hapax in LXX or Pseudepigrapha)

  • 65.7.2.2 Implement word frequency analysis with type-token ratios, vocabulary richness metrics (Yule's K, Simpson's D, hapax percentage), and corpus comparison statistics

  • 65.7.2.3 Implement stylometric authorship attribution using function word frequencies, sentence length distributions, vocabulary overlap, and other statistical features — supporting disputed authorship questions (e.g., Pauline epistles, Isaianic unity, multiple authors of the Pentateuch)

  • 65.7.2.4 Implement register analysis distinguishing prose from poetry, narrative from discourse, legal from prophetic, based on statistical profiles of syntactic patterns, vocabulary, and discourse markers

65.7.3 Discourse Analysis#
  • 65.7.3.1 Implement chiastic structure detection algorithm for automatic identification of chiasmus (A-B-C-B'-A' patterns) in texts, with configurable detection parameters (minimum/maximum depth, element matching criteria) and confidence scoring

  • 65.7.3.2 Implement ring composition detection (Homeric ring structure and similar large-scale patterns) and inclusio detection (framing devices where a passage begins and ends with the same word/phrase)

  • 65.7.3.3 Implement discourse boundary detection using discourse markers, topic shifts, participant changes, temporal indicators, and formulaic expressions to automatically segment texts into discourse units

  • 65.7.3.4 Implement narrative analysis tools: character tracking across a narrative, speech/narration distinction, reported speech nesting analysis, and narrative perspective identification

65.7.4 Intertextuality Detection#
  • 65.7.4.1 Implement quotation detection identifying explicit quotations of earlier texts in later ones (e.g., OT quotations in NT, Vedic citations in Upanishads, Quranic references to Biblical narratives), with source identification and citation format analysis

  • 65.7.4.2 Implement allusion detection for identifying probable but inexact references using shared vocabulary clusters, thematic parallels, and structural similarities, with configurable sensitivity thresholds

  • 65.7.4.3 Implement echo detection for faint thematic or verbal resonances that may or may not represent conscious literary dependence, producing scored results with supporting evidence

  • 65.7.4.4 Implement influence scoring quantifying probability and strength of intertextual connections, with dependency direction analysis determining which text is source and which is dependent using chronological, linguistic, and contextual evidence


65.8 Comparative Traditions Framework (@nisaba/comparative)#

65.8.1 Cross-Tradition Concept Mapping#
  • 65.8.1.1 Implement concept equivalence registry with curated, scholar-reviewed mappings of analogous concepts across traditions: ineffability (Tao ~ Brahman ~ Sunyata ~ Ein Sof ~ Theologia Negativa ~ Fana), liberation (Moksha ~ Nirvana ~ Theosis ~ Salvation ~ Fana ~ Wu Wei), universal ethics (Golden Rule across Confucius, Hillel, Jesus, Muhammad, Buddhist precepts), cosmic order (Logos ~ Rta/Dharma ~ Ma'at ~ Tao ~ Torah), self-transcendence (Anatta ~ Fana ~ Kenosis ~ Bittul HaYesh ~ Wu Wei) — each with primary source citations, scholarly references, and nuanced similarity ratings

  • 65.8.1.2 Implement similarity taxonomy classification for each concept mapping: genetic (historical influence or common source), typological (independent parallel development), analogical (structural similarity without semantic identity), contested (scholars disagree on the relationship) — with evidence requirements enforcing that every mapping must cite primary sources, scholarly literature, and specify scholarly consensus level

  • 65.8.1.3 Implement concept mapping CRUD with search, filtering by tradition/concept/similarity-type/evidence-grade, and version history for tracking how mappings evolve as scholarship progresses

65.8.2 Parallel Passage Detection#
  • 65.8.2.1 Implement cross-tradition parallel passage finder using semantic similarity (multilingual embeddings), motif-based matching (Thompson Motif-Index compatible controlled vocabulary), and structural parallel detection (similar narrative arcs, argument patterns)

  • 65.8.2.2 Implement cultural context weighting adjusting similarity scores based on historical plausibility of influence: known trade routes and cultural contact, chronological ordering (earlier cannot borrow from later), geographic proximity, and linguistic relatedness

  • 65.8.2.3 Implement parallel quality classification: verbatim parallel (direct translation/quotation), close parallel (same content, different expression), thematic parallel (same theme, different treatment), structural parallel (same literary structure, different content), typological parallel (independent development)

65.8.3 Motif & Theme Tracking#
  • 65.8.3.1 Implement universal motif catalog database with comprehensive entries for: creation narratives (ex nihilo, cosmic egg, world parents, emergence), flood narratives (Gilgamesh/ Atrahasis, Genesis, Manu, Deucalion, Yu), descent to the underworld (Inanna, Orpheus, Aeneas, Izanagi), divine sacrifice (Purusha, Odin, Christ, Osiris), teacher's last words (Buddha's parinirvana, Socrates' Phaedo, Jesus's farewell discourse), ineffability of the divine, and 50+ additional cataloged motifs

  • 65.8.3.2 Implement motif attestation tracking recording every known attestation of each motif with date, tradition, text reference, relevant passage, and scholarly commentary

  • 65.8.3.3 Implement theme evolution timeline visualization showing how a theme (e.g., "the soul after death," "creation from chaos," "the golden age") developed across traditions and centuries

65.8.4 Influence Network & Synoptic Views#
  • 65.8.4.1 Implement historical influence graph as a directed graph showing documented and proposed channels of influence between traditions: Zoroastrian → Jewish → Christian → Islamic eschatology, Greek philosophy → Hellenistic Judaism → Christian theology, Upanishadic thought → Buddhist philosophy → East Asian Buddhism, Neoplatonism → Christian mysticism → Islamic falsafa, Silk Road exchanges — with evidence-graded edges (documented, strong, probable, possible, speculative)

  • 65.8.4.2 Implement interactive influence network visualization with filterable edges by evidence grade, temporal range, and tradition pair, and click-through to supporting scholarly evidence

  • 65.8.4.3 Implement synoptic cross-tradition reader displaying thematically parallel passages from multiple traditions side by side, with scholarly commentary on the parallels and configurable comparison sets (e.g., "creation accounts," "afterlife descriptions," "meditation instructions")


65.9 Open-Source Corpora Integration (@nisaba/corpora)#

65.9.1 Format Parsers#
  • 65.9.1.1 Implement TEI-XML parser with full TEI P5 support: header metadata extraction (teiHeader), structural parsing (div, p, l, lg, sp, stage), critical apparatus parsing (app, lem, rdg, wit), named entity extraction (persName, placeName, orgName), linguistic annotation parsing (w, pc, s with morphological attributes), manuscript description (msDesc), and bibliographic data (bibl, biblStruct) — using fast-xml-parser with streaming for large files

  • 65.9.1.2 Implement TEI-XML generator producing valid TEI P5 output from Nisaba's internal data structures, with configurable output profiles (minimal, standard, full apparatus) and EpiDoc variant for epigraphic/papyrological texts

  • 65.9.1.3 Implement ATF (ASCII Transliteration Format) parser for cuneiform texts: sign names, sign values, determinatives, glosses, damage notation, editorial marks, line numbering, and composite text handling

  • 65.9.1.4 Implement USFM/USX parser for United Bible Societies format Bible texts, OSIS XML parser for Open Scripture Information Standard, and SWORD module reader for CrossWire Bible Society module format (compressed text modules, dictionary modules, commentary modules)

  • 65.9.1.5 Implement OpenITI mARkdown parser for Arabic/Persian texts from the Open Islamicate Texts Initiative, handling the mARkdown annotation format (structural, semantic, and metadata annotations)

65.9.2 Corpus Connectors#
  • 65.9.2.1 Implement Perseus Digital Library connector for accessing Greek and Latin texts with morphological data, English translations, and commentary — via Perseus REST API and/or bulk TEI-XML download processing

  • 65.9.2.2 Implement ETCSL (Electronic Text Corpus of Sumerian Literature) connector for the complete Sumerian literary corpus with transliteration and translation, and CDLI (Cuneiform Digital Library Initiative) connector for cuneiform tablet catalog with ATF transliterations

  • 65.9.2.3 Implement ORACC (Open Richly Annotated Cuneiform Corpus) connector for annotated cuneiform texts across multiple projects, parsing ORACC JSON format

  • 65.9.2.4 Implement SuttaCentral connector for Pali, Chinese, Sanskrit, and Tibetan Buddhist texts with translations and parallel identifications — via SuttaCentral API

  • 65.9.2.5 Implement CBETA (Chinese Buddhist Electronic Text Association) connector for the complete Chinese Buddhist canon, with Taishō volume/page/column/line reference resolution

  • 65.9.2.6 Implement Sefaria connector for Jewish texts (Tanakh, Talmud, Midrash, Halakha, Kabbalah, Liturgy, Philosophy) via Sefaria REST API, with Hebrew/Aramaic original text and English translations

  • 65.9.2.7 Implement OpenITI connector for Arabic and Persian texts in mARkdown format, including metadata extraction and author/title resolution

  • 65.9.2.8 Implement SARIT (Search and Retrieval of Indic Texts) connector for Sanskrit and Prakrit texts in TEI-XML, and GRETIL connector for the Göttingen Register of Electronic Texts in Indian Languages

  • 65.9.2.9 Implement CTP (Chinese Text Project) connector for pre-modern Chinese texts (Confucian, Taoist, Legalist, Mohist, etc.) via CTP API

  • 65.9.2.10 Implement Dead Sea Scrolls Digital Library connector for transcriptions and image references, CAL (Comprehensive Aramaic Lexicon) connector for Aramaic texts, and ETCBC connector for the morphologically analyzed Hebrew Bible database

  • 65.9.2.11 Implement SWORD module connector reading CrossWire Bible Society modules for dozens of Bible translations, original language texts, lexica, and commentaries in the SWORD compressed format

65.9.3 Ingestion Pipeline#
  • 65.9.3.1 Implement Nisaba-specific chunking strategies that plug into Sophia's document ingestion pipeline: verse-aware chunking (for poetry and scripture, respecting verse boundaries), pericope- aware chunking (for narrative texts, using discourse boundary detection), section-aware chunking (for prose treatises, following author's structural divisions), and parallel-preserving chunking (keeping synoptic parallels aligned across chunk boundaries)

  • 65.9.3.2 Implement corpus metadata extraction and normalization pipeline converting source-specific metadata formats to Sophia's DocumentMetadataSchema, with tradition, language, and genre classification, author/editor normalization, and date normalization to fuzzy date format

  • 65.9.3.3 Implement corpus synchronization scheduler for periodic re-ingestion of updated corpora, with incremental update detection (content hash comparison), new document discovery, and synchronization conflict resolution


65.10 Annotation & Commentary System (@nisaba/annotations)#

65.10.1 Standoff Annotation Architecture#
  • 65.10.1.1 Implement W3C Web Annotation Data Model storage with standoff annotations stored separately from base text, referenced by character offset ranges (TextPositionSelector), enabling multiple overlapping annotation layers without markup conflict

  • 65.10.1.2 Implement annotation type system with extensible types: textual notes (commentary, explanation, cross-reference), linguistic annotations (morphological, syntactic, semantic), translation annotations (gloss, paraphrase, formal translation), critical annotations (variant readings, emendation proposals), comparative annotations (cross-tradition parallel markers), structural annotations (discourse markers, chiastic boundaries), pedagogical annotations (difficulty level, prerequisite knowledge)

  • 65.10.1.3 Implement Talmudic-style layered commentary model supporting: base text layer, first commentary layer (direct commentary), super-commentary layer (commentary on commentary), marginalia layer (informal notes), and modern scholarly layer — with historical layering display showing how commentary accumulated over centuries

65.10.2 Collaborative Annotation#
  • 65.10.2.1 Implement CRDT-based (Conflict-free Replicated Data Type) real-time collaborative annotation allowing multiple scholars to annotate simultaneously with automatic conflict resolution preserving all contributions

  • 65.10.2.2 Implement annotation review workflow with draft → review → published pipeline, peer review capabilities (request review, approve, reject, request changes), and audit trail

  • 65.10.2.3 Implement permission model for annotations: private (visible only to creator), team-shared (visible to project members), and published (publicly accessible), with granular per-layer and per-annotation permissions

  • 65.10.2.4 Implement threaded discussion system attached to specific annotations for scholarly debate, with @-mention notifications, quote-reply from annotation text, and resolution status tracking

65.10.3 Annotation Export#
  • 65.10.3.1 Implement W3C Web Annotation (WADM) JSON-LD export conforming to the full specification with TextPositionSelector, TextQuoteSelector, annotation motivation, and body types

  • 65.10.3.2 Implement TEI-XML annotation export embedding annotations as TEI note elements or linking via standoff reference, and Hypothesis-compatible export for integration with the Hypothesis open annotation platform

  • 65.10.3.3 Implement PDF annotation export generating PDF markup overlays for print review of annotated texts


65.11 Digital Critical Edition Tools (@nisaba/editions)#

65.11.1 Edition Project Management#
  • 65.11.1.1 Implement critical edition project lifecycle: create, configure (base text selection with justification, witness set definition, apparatus format choice, collaborator invitation), manage (milestone tracking, task assignment), and version (semantic versioning for published editions: major/minor/patch)

  • 65.11.1.2 Implement apparatus composition interface with visual tools for: lemma selection from base text, variant reading entry with witness sigla, scholarly judgment annotations (preferred reading, uncertainty markers), cross-reference linking between apparatus entries, and source apparatus (Quellenapparat) for identifying sources and parallels

  • 65.11.1.3 Implement collaborative edition editing with role- based access (editor-in-chief, section editors, apparatus editors, reviewers), version control for every element (base text, apparatus, introduction, notes), and review pipeline with approval gates

65.11.2 Edition Export & Publishing#
  • 65.11.2.1 Implement TEI-XML critical edition export with full TEI P5 encoding using <app>, <rdg>, <wit>, <lem> elements, <teiHeader> metadata, and EpiDoc variant for epigraphic/ papyrological editions

  • 65.11.2.2 Implement print-ready PDF generation using LaTeX backend (reledmac/reledpar packages) with critical edition conventions: apparatus at page bottom, line numbering, section headers, multi-script support (Hebrew, Greek, Arabic, Devanagari in the same page), proper apparatus typography, and configurable page layout (single/double column, facing pages)

  • 65.11.2.3 Implement interactive HTML digital edition with clickable apparatus entries revealing full variant information, IIIF manuscript image integration, dynamic filtering of apparatus by witness or variant type, and responsive layout for reading on various devices


65.12 Temporal-Geographic Mapping (@nisaba/geotemporal)#

65.12.1 Provenance & Diffusion#
  • 65.12.1.1 Implement manuscript provenance chain tracking recording ownership and location history from creation to current repository, scriptoria mapping locating known writing centers, and transmission route visualization showing how manuscripts traveled

  • 65.12.1.2 Implement tradition diffusion maps showing animated geographic spread of traditions over time: Buddhism from NE India through Central Asia to China/Korea/Japan, Christianity from Palestine through the Roman Empire, Islam from Arabia across the Middle East/North Africa/Central Asia/SE Asia, Greek philosophy from Ionia through Athens to Alexandria and the Islamic world

65.12.2 Geographic & Timeline Integration#
  • 65.12.2.1 Implement Pleiades ancient world gazetteer integration for precise place identification with stable URIs, and PeriodO integration for standardized historical period definitions

  • 65.12.2.2 Implement historical atlas with period-accurate boundaries (not projecting modern national boundaries onto the ancient world), linking texts and manuscripts to their geographical and archaeological context (findspot, repository, scriptoria)

  • 65.12.2.3 Implement multi-calendar timeline engine with simultaneous display in Gregorian/Julian, Hebrew, Islamic (Hijri), Buddhist, Hindu (Vikram Samvat, Shaka Samvat), Egyptian, Athenian, Chinese traditional, Seleucid era, and Olympiad dating systems

  • 65.12.2.4 Implement fuzzy dating support for imprecise dates: "ca. 500 BCE" (approximately), "6th-5th century BCE" (range), "Pre-exilic" (relative to event), "Ptolemaic period" (named period), terminus post quem / ante quem — with synchronized parallel timelines for contemporaneous events across traditions

  • 65.12.3.1 Implement geographic search queries: "Find all texts composed within 100km of Alexandria between 300 BCE and 200 CE," tradition overlay showing geographic extent at a given date, and route-based search along trade routes (Silk Road, Via Maris, King's Highway) for cultural contact evidence

65.13 AI Scholarly Assistant (@nisaba/assistant)#

65.13.1 Translation & Commentary Assistance#
  • 65.13.1.1 Implement AI translation assistance with morphological explanation: for any word in an ancient text, provide full morphological parsing with plain-language explanation, multiple translation possibilities with scholarly justification, and contextual disambiguation using surrounding context and parallel passages

  • 65.13.1.2 Implement AI translation drafting for unpublished or under-studied texts, producing first-draft translations with confidence markers, notes on uncertain readings, and explicit flagging of AI-generated vs. attested interpretations

  • 65.13.1.3 Implement grounded commentary generation using Sophia RAG pipeline: commentary drafts that cite specific scholarly sources (verified via Sophia's citation verification), reference parallel passages with precise citations, explain textual variants, discuss philological issues, and never fabricate citations — with style templates for exegetical, thematic, historical-critical, comparative, and philological commentary

65.13.2 Variant Evaluation & Research#
  • 65.13.2.1 Implement AI variant evaluation using internal evidence criteria (lectio difficilior, lectio brevior, scribal tendency analysis, conformity to author's style) and external evidence analysis (geographic distribution, chronological range, quality and independence of witnesses, versional and patristic support)

  • 65.13.2.2 Implement research gap identification analyzing existing scholarship to identify under-explored questions, bibliography discovery using Sophia's knowledge base and external bibliographic databases, and methodology suggestion for research questions

  • 65.13.2.3 Implement linguistic dating analysis assessing probable date of composition based on vocabulary, syntactic features, and orthographic conventions characteristic of specific periods, with probability distributions for estimated dates

  • 65.13.2.4 Implement domain-specific curated prompt library with expert-reviewed templates: "Parse this Hebrew/Greek/Sanskrit passage morphologically," "Compare these translations and identify divergences," "Evaluate textual variants at this passage," "Identify intertextual allusions," "Draft a philological note on this hapax," "Trace this concept across traditions," "Summarize the scholarly debate on this passage"


65.14 Import/Export Standards (@nisaba/standards)#

65.14.1 Text Encoding Standards#
  • 65.14.1.1 Implement comprehensive TEI-XML (P5) import/export with full support for: teiHeader metadata, structural encoding (div, p, l, lg, sp, stage), critical apparatus (app, lem, rdg, wit, witDetail), named entity markup, linguistic annotation, manuscript description (msDesc), and bibliographic data — with round-trip fidelity testing

  • 65.14.1.2 Implement EpiDoc TEI variant for ancient documents (inscriptions, papyri) with Leiden convention rendering, apparatus criticus, and physical description encoding

  • 65.14.1.3 Implement OSIS XML import/export for Bible texts, USFM/USX import/export for Bible translation data, and SWORD module reading for CrossWire Bible Society resources

65.14.2 Reference, Citation & Linked Data Standards#
  • 65.14.2.1 Implement CTS/CITE protocol client and server for Canonical Text Services interoperability with Perseus and other digital humanities infrastructure

  • 65.14.2.2 Implement BibTeX, RIS, and CSL-JSON import/export for bibliographic data, and Zotero API integration for direct import/export with Zotero libraries

  • 65.14.2.3 Implement RDF/SPARQL export of knowledge graph data as RDF triples, JSON-LD support for web integration, Pelagios/ Recogito interoperability for geo-historical annotation, and Wikidata entity alignment for disambiguation and enrichment

65.14.3 Image & Annotation Standards#
  • 65.14.3.1 Implement IIIF integration with Presentation API v3 (manifest generation for manuscript viewers), Image API v3 (deep zoom, region extraction), Content Search API (search within annotations on images), and compatibility with Mirador, Universal Viewer, and other IIIF clients

  • 65.14.3.2 Implement W3C Web Annotation Protocol compliance for annotation exchange, and Hypothesis platform compatibility for annotation import/export


65.15 Scholarly Workspace (@nisaba/workspace)#

65.15.1 Research Environment#
  • 65.15.1.1 Implement research project management with project containers (shared resources, team members, permissions), templates for common research types (critical edition, translation, comparative study, philological analysis, manuscript survey), and progress tracking with milestone management

  • 65.15.1.2 Implement configurable split-pane reading environment showing text, translation, apparatus, commentary, lexicon, and manuscript images simultaneously — with morphological popups (hover for parsing/gloss/lexicon), persistent lexicon side panel, keyboard navigation (vim-style keybindings option), and configurable fonts and themes for ancient script display

  • 65.15.1.3 Implement unified cross-corpora search supporting: lemma-aware search (find all inflected forms of a root), morphology-aware search (find all aorist passive participles), semantic search (find passages about "divine mercy" across languages), regex with script-aware character classes, Boolean operators (AND, OR, NOT, NEAR/n), and field-restricted search (author, title, tradition, date range) — with enriched results showing morphological parsing, context preview, and relevance scoring

65.15.2 Personal Library & Export#
  • 65.15.2.1 Implement personal library with document upload (TEI-XML, plain text, PDF, DOCX, EPUB), collection organization (folders, tags, smart collections), reading lists with progress tracking, and bookmarks/highlights on any text in any corpus

  • 65.15.2.2 Implement export pipeline: publication-quality PDF with critical apparatus and multi-script support, DOCX for journal submission, LaTeX with BibTeX bibliography and reledmac/reledpar critical edition macros, and standalone HTML — all with configurable citation style

  • 65.15.2.3 Implement citation manager integration with Sophia's citation infrastructure (@sophia/schemas citation schemas) for source management and bibliography generation, external citation manager import/export (Zotero, Mendeley, EndNote via BibTeX, RIS, CSL-JSON), and inline citation insertion into documents


65.16 Client SDK (@nisaba/client)#

  • 65.16.1 Implement Nisaba API client with typed methods for all domain operations: manuscript CRUD, collation management, annotation CRUD, edition management, canonical reference resolution, corpus search, concept mapping queries, and AI assistant invocations

  • 65.16.2 Implement React hooks for Nisaba workspace features: useManuscript, useCollation, useAnnotation, useEdition, useCanonicalReference, useCorpusSearch, useConceptMapping, useTranslationComparison, useMorphologicalPopup, useLexiconLookup, useTimeline, useInfluenceNetwork

  • 65.16.3 Implement real-time subscription hooks for collaborative features: useAnnotationSync (CRDT-based live annotation updates), useEditionSync (collaborative edition editing), and useDiscussionThread (live discussion updates)


65.17 Integration Testing & Cross-Domain Validation#

  • 65.17.1 Implement integration tests for Sophia dependency: document ingestion via Sophia pipeline with Nisaba chunking strategies, entity creation using Sophia's Custom entity type with manuscript metadata, citation creation and verification via Sophia's citation system, and vector search queries across Nisaba corpora via Sophia/Qdrant

  • 65.17.2 Implement end-to-end test for complete textual criticism workflow: create manuscripts → run collation → classify variants → build stemma → generate apparatus → export TEI-XML critical edition → verify round-trip fidelity

  • 65.17.3 Implement end-to-end test for comparative traditions workflow: create concept mapping → detect parallel passages → track motif attestations → build influence network → render synoptic view → verify evidence requirements met for all mappings

  • 65.17.4 Implement end-to-end test for translation comparison workflow: load source text + multiple translations → align sentences → align words → detect divergences → flag theological divergences → render interlinear view

  • 65.17.5 Implement end-to-end test for corpus ingestion workflow: download from Perseus/SuttaCentral/Sefaria → parse format (TEI-XML/JSON/mARkdown) → extract metadata → chunk with Nisaba strategies → ingest via Sophia pipeline → verify searchable via unified search

  • 65.17.6 Implement performance benchmarks: collation of 50 witnesses × 500 variant units in < 30s, cross-corpora lemma-aware search p95 < 500ms, morphological parsing throughput > 10,000 words/sec (TypeScript) and > 100,000 words/sec (Rust WASM), TEI-XML round-trip in < 5s for 10MB document, influence network rendering for 500 nodes × 2000 edges in < 2s


65.18 Documentation & Deployment#

  • 65.18.1 Create Nisaba API documentation with OpenAPI/Swagger specification for all REST endpoints, including request/response schemas, authentication requirements, and rate limiting policies

  • 65.18.2 Create scholar-facing user guide covering: workspace configuration, corpus browsing and search, translation comparison, collation workflow, annotation and commentary, critical edition creation, concept mapping, and export options — with screenshots and step-by-step tutorials

  • 65.18.3 Create developer documentation covering: library architecture, adding new language support, creating corpus connectors, extending the annotation type system, and contributing concept mappings

  • 65.18.4 Configure CI/CD pipeline for Nisaba libraries: Nx- affected build/test/lint on PR, automated TEI-XML round-trip validation, morphological parser accuracy regression tests, and performance benchmark gates


Phase 65 Summary Statistics#

Section Subsection Task Count
65.1 Infrastructure Setup 65.1.1-65.1.4 22
65.2 Ancient Language Engine 65.2.1-65.2.9 53
65.3 Translation Comparison 65.3.1-65.3.3 13
65.4 Textual Criticism 65.4.1-65.4.6 24
65.5 Canonical Text Management 65.5.1-65.5.3 16
65.6 Paleographic Analysis 65.6.1-65.6.3 10
65.7 Philological Analysis 65.7.1-65.7.4 17
65.8 Comparative Traditions 65.8.1-65.8.4 12
65.9 Corpora Integration 65.9.1-65.9.3 19
65.10 Annotation System 65.10.1-65.10.3 10
65.11 Critical Edition Tools 65.11.1-65.11.2 6
65.12 Geotemporal Mapping 65.12.1-65.12.3 7
65.13 AI Scholarly Assistant 65.13.1-65.13.2 7
65.14 Import/Export Standards 65.14.1-65.14.3 8
65.15 Scholarly Workspace 65.15.1-65.15.2 6
65.16 Client SDK 3
65.17 Integration Testing 6
65.18 Documentation & Deployment 4
TOTAL Phase 65 243

Phase 65 defines the complete Nisaba domain — the world's first comprehensive, AI-powered scholarly platform for ancient text analysis and cross-tradition research. Named for Nisaba (𒀭𒉀), the Sumerian goddess of writing, learning, and reeds, this platform provides 243 tasks across 18 libraries covering 20+ ancient writing systems with morphological parsing, translation comparison with divergence detection, a complete textual criticism pipeline from manuscript collation to critical edition publishing, canonical reference management for every major world tradition, paleographic analysis with ML-based dating and scribal identification, comprehensive philological tools (etymology, semantic fields, hapax legomena, discourse analysis, intertextuality), cross-tradition concept mapping with evidence-graded influence networks, integration with 15+ open-source digital text repositories, W3C-compliant collaborative annotation with Talmudic-style layered commentary, digital critical edition publishing with print-quality PDF output, temporal-geographic mapping with multi-calendar timelines and historical atlases, an AI scholarly assistant grounded in verifiable sources, comprehensive standards support (TEI-XML, CTS/CITE, IIIF, W3C Web Annotation, RDF/SPARQL), and a configurable scholarly workspace with unified cross-corpora search — all built on Sophia's research infrastructure and designed to enable scholars to trace the deep connections between humanity's oldest recorded thoughts through rigorous, evidence-based analysis.