Sangeetha-Grantha

Metadata Value
Status Active
Version 1.1.0
Last Updated 2026-09-10
Author Sangeetha Grantha Team
Document Type Evidence record

E2E Pipeline Validation & Lyric Section Consistency Fix


[!NOTE] Historical evidence: results, counts, commands, and observations below belong to the original work described here. The editorial update date is not a new test or corpus verification. For present behavior, use current feature map.

Purpose

Prove the CSV bulk import + PDF extraction pipeline end-to-end with real Dikshitar compositions, and fix the critical lyric section inconsistency affecting 92% of krithis.

Implementation Details

E2E Pipeline (Phase 3)

Section Fix (Phase 4A)

Code Changes

File Change
compose.yaml Dev backend source mount, extraction DATABASE_URL, frontend proxy
KrithiMatcherService.kt Route unmatched to imported_krithis instead of auto-creating
structure_parser.py MKS demotion, dual-format merge, bracket headers
LyricVariantPersistenceService.kt Type+queue section matching
KrithiLyricRepository.kt ORDER BY via JOIN for section order
38__fix_inconsistent_lyric_sections.sql Section cleanup migration
worker.py DB rollback after errors

Results

Trinity-import residue after the later 1,226-krithi corpus is closed in TRACK-133 (108 → 0).

Ref: application_documentation/10-implementations/track-079-e2e-pipeline-section-fix.md


Section index · Documentation home · Feature status