Skip to main content

M06: Interlinear & Lexicon

Phase: P2: Scholar Features Target: Weeks 17–24 Sprints: S8 (tail), S9, S10, S11 (start) Release Tags: web/v0.6.0-alpha


Phase Context

Goal: The three paid pillars that justify $79.99/year — interlinear Hebrew/Greek + JST, constellation view, and constrained AI. Ref: MVP.md § Paid Tier.

Key constraint: Founding users enter during this phase (~Week 22). Ship incrementally; don't wait for "complete."


ZenHub Configuration

FieldValue
MilestoneM06: Interlinear & Lexicon
Due Date2026-08-23
Default PipelineProduct Backlog
Primary Epic(s)Interlinear & Lexicon

Prerequisites

PrerequisiteSource MilestoneWhat Must Be Complete
Word alignment + lexicon data ingestedM01: Data PipelineStage 2 (lexicon pipeline — :Word nodes, DERIVES_FROM, RELATED_TO) and Stage 3 (:WordAlignment nodes) must be complete
Reader with verse displayM03: Scripture ReaderScripture reader with chapter navigation — interlinear mode extends the existing reader

Epics

Epic: Interlinear & Lexicon

Story AreaScopeSpec Reference
Interlinear data verificationValidate word alignment data in corpus against schemasGOSPELIB-SCHEMAS.md § WordAlignment
Interlinear APIPassage response enriched with word alignment + Strong's dataTECH-SPEC.md § Content Service
WordToken componentTap target for each original-language wordDESIGN-SYSTEM.md § P1 Components
Lexicon bubbleTap word → pop-up with Strong's number, gloss, root, morphologyMVP.md § Priority #1
Word journeyTap word → occurrences highlighted across current chapterMVP.md § Priority #1
Interlinear display modeWord-by-word with transliteration + glossDESIGN-SYSTEM.md § Interlinear View
Hebrew RTL renderingGentium Plus / SBL Hebrew font, BiDi layoutDESIGN-SYSTEM.md § Original Language
Study modeActivate study mode from reader — verse long-press entry pointDESIGN-SYSTEM.md § Render Modes
P2 icon additionsinterlinear, witness, strong-number, word-journey, graph-node iconsDESIGN-SYSTEM.md § Bespoke GospeLib Icons

Document References

DocContainsUse When Writing Stories For
MVP.mdFeature scope, tier breakdown, success criteria, budgetAcceptance criteria, scope boundaries
TECH-SPEC.mdArchitecture, service boundaries, data stores, API catalogTechnical implementation details
GOSPELIB-SCHEMAS.mdAll 7 schema families, node/edge types, validation rulesData models, Pydantic models, graph schema
GOSPELIB-INGEST-SPEC.md7-stage pipeline, Cypher templates, batch strategy, CLIIngest pipeline stories
DESIGN-SYSTEM.mdVisual identity, component catalog, reader modes, tokensUI component stories
DESIGN-SYSTEM.md §§ 13, 21–23Footnotes (§13), subscription boundaries (§21), sharing (§22), onboarding (§23)UX flow stories
Deployment & OperationsEnvironments, K8s, CI/CD, migrations, secrets, DRInfrastructure and deployment stories
REPO-MAP.mdDirectory structure, naming conventions, dependency rulesAll stories (coding standards)
BusinessLEGAL.md, POLICY-TERMS.md, executive summary, market research, GTMLaunch readiness, legal/compliance stories

Additional Spec References for This Milestone

Doc SectionRelevance
GOSPELIB-SCHEMAS.md § WordAlignmentWord alignment data model for interlinear verification
DESIGN-SYSTEM.md § Interlinear ViewInterlinear display mode layout and typography
DESIGN-SYSTEM.md § Original LanguageHebrew RTL rendering, font selection, BiDi layout
DESIGN-SYSTEM.md § Render ModesStudy mode activation and mode switching
DESIGN-SYSTEM.md § Bespoke GospeLib IconsP2 icon additions for interlinear features

Sprint Mapping

SprintWeeksPrimary Focus for M06
S919–20Interlinear data verification, API enrichment, WordToken component
S1021–22Lexicon bubble, word journey, interlinear display mode, Hebrew RTL
S1123–24Founding users enter. Study mode polish, P2 icon additions

S8 (Weeks 17–18) is primarily M05 work but P2 infrastructure prep may start. S11 overlaps M07 start.

Sprint Load Warnings

No specific load warnings apply to M06 sprints. However, note that founding users enter at ~Week 22 (S11) — prioritize stability and a functional interlinear experience over feature completeness.


Release Info

ReleaseTagContains
v0.6.0-alphaweb/v0.6.0-alphaInterlinear + lexicon (Scholar)

Tags follow <component>/v<semver> per release-please-config.json.


Relevant Risks

RiskImpactMitigation
Interlinear Hebrew RTL renderingCore differentiator broken or uglyPrototype RTL layout early in P2; test with real corpus data
Ingest pipeline data quality issuesWord alignment data may have gaps or errorsCorpus validation epic in P0; data verification story in this milestone
Custom icon set scope creepDelays P2 deliveryShip P1 with minimum viable icon set; P2 icons are additive. Consider temporary placeholder icons
Solo founder velocity38-week plan too aggressiveFounding users at Week 22 provide feedback before full scope; cut P3 scope if needed

Cross-Cutting Concerns

Testing

LayerFrameworkWhenSpec Reference
Python unit/integration (interlinear API)pytest + testcontainersEvery PRTECH-SPEC.md § Testing
TypeScript unit (WordToken, lexicon bubble)VitestEvery PRTECH-SPEC.md § Testing
Component visualStorybook or playgroundP1+DESIGN-SYSTEM.md § Governance
Visual regressionPlaywright + pixelmatchP1+ (any packages/ui/ or apps/*/src/ change)DESIGN-SYSTEM.md § Visual Regression CI

Documentation

DocUpdate Trigger
API OpenAPI specsContent service interlinear enrichment
ADRsRTL rendering approach, interlinear data model decisions

CI/CD

AdditionPhaseDetail
Visual regression screenshotsP1+Interlinear components added to playground; pixelmatch diff baseline updated

Dependencies

Upstream (what M06 needs)

DependencySourceStatus
Lexicon pipeline (Stage 2) — :Word nodesM01: Data PipelineMust be complete
Word alignment data (Stage 3) — :WordAlignment nodesM01: Data PipelineMust be complete
Scripture reader shellM03: Scripture ReaderMust be complete (interlinear mode extends reader)
Content API (passage routes)M02: Content APIMust be complete (interlinear API enriches passage response)
Staging environmentM05: Search & StagingShould be live for founding-user testing

Downstream (what depends on M06)

DependentMilestoneWhat It Needs From M06
JST InterlinearM07Interlinear display mode, WordToken component, study mode, lexicon infrastructure
Constellation viewM08: Knowledge GraphStudy mode and interlinear as entry points to graph exploration
AI study assistantM09: AI Study AssistantLexicon data for AI citation linking

Issues

IssueTitleStatusNotes
M06-001Interlinear Data Verification — Validate Word Alignment Data Against Schemas❌ To Donot implemented
M06-002Interlinear API — Passage Response Enriched with Word Alignment and Strong's Data🔶 Partialinclude_words param and Cypher query exist but no interlinear corpus data
M06-003WordToken Component — Tappable Original-Language Word Target❌ To Donot implemented
M06-004Lexicon Bubble — Tap Word to Show Strong's Entry Popup❌ To Donot implemented
M06-005Word Journey — Highlight Same-Root Occurrences Across Current Chapter❌ To Donot implemented
M06-006Interlinear Display Mode — Word-by-Word Layout with Transliteration and Gloss❌ To Donot implemented
M06-007Hebrew RTL Rendering — Gentium Plus / SBL Hebrew Font and BiDi Layout❌ To Donot implemented
M06-008Study Mode — Activate from Reader with Verse Long-Press Entry Point❌ To Donot implemented
M06-009P2 Icon Additions — Interlinear, Witness, Strong's, Word Journey, and Graph Node Icons❌ To Donot implemented

Progress: 0 Done · 1 Partial · 8 To Do (6%)

Epic: Interlinear & Lexicon


Issue Dependency Graph

M06-001 ──► M06-002 ──► M06-003 ──► M06-004 ──► M06-005
M06-002 ──► M06-005
M06-002 ──► M06-006 ──► M06-007
M06-003 ──► M06-005
M06-003 ──► M06-006
M06-009 ──► M06-003
M06-009 ──► M06-004
M06-009 ──► M06-008

Legend: A ──► B means A blocks B (B is blocked by A)


Summary

MetricCount
Total Issues9
Sub-Issues0
Total Estimate (pts)52
SprintsS9–S11
Dependencies (blocking)13
Dependencies (blocked by)15