Skip to content

Epic 4 — Warsh implementation #34

Description

@Hetchy

Parent: #27 · Plan

Goal: Land Warsh by adding data and the minimal Warsh-specific rule code on top of the seam. First epic that introduces new behavior.

Tasks

  • Add the Warsh corpus from the Epic 0 script decision, through the Epic 1a validator.
  • Add Warsh data files, phonemes, rules as riwaya-scoped siblings.
  • Implement the genuine Warsh rule deltas from 1b (e.g. imala, differing madd measures, orthography-driven differences) via the adapter/fork pattern chosen in the 3a ADR.
  • Turn the Epic 2B Warsh expected-case suite green.

Acceptance

  • All Warsh expected-cases pass; Hafs characterization net still byte-identical.
  • Phonemizer(riwaya="warsh") (or equivalent) produces verified output for the research-covered cases.

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions