updating pipeline roadmap and status to match branch reality
Roadmap: phase 4 re-scoped to import only (migration already applied), phase 3 gains prompt templating, wordlist dedup, structured output, raw-response persistence, and validation tests; idempotency decision documented (skip already-staged words, one transaction per word). Stale paths, postgres setup, and file structure corrected. STATUS.md: refreshed from stale 2026-05-15 Kaikki state to current gemini-only pipeline work. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
parent
e534b98bc5
commit
303bb9388c
2 changed files with 242 additions and 213 deletions
|
|
@ -1,6 +1,6 @@
|
|||
# Status — 2026-05-15
|
||||
# Status — 2026-08-09
|
||||
|
||||
> Last updated: 2026-05-15. Update this file after every deploy or when switching tasks.
|
||||
> Last updated: 2026-08-09. Update this file after every deploy or when switching tasks.
|
||||
|
||||
## What Works Today ✅
|
||||
|
||||
|
|
@ -12,7 +12,7 @@
|
|||
|
||||
## What's Broken / Blocked 🚧
|
||||
|
||||
- **Data quality** — Production still uses OpenWordNet/OMW translations. Kaikki pipeline (sense-disambiguated) is in progress but not yet synced to production.
|
||||
- **Data quality** — Production still uses OpenWordNet/OMW translations. The replacement is the Gemini-only pipeline on branch `refactor/gemini-only-pipeline`: the sense-based schema (`words` → `senses` → `translations`) is migrated but empty, and the pipeline itself is not built yet. The earlier Kaikki/local-LLM pipeline was abandoned and removed (docs in `documentation/archive/`).
|
||||
- **Guest play** — Auth is required for all game routes. No try-before-signup flow.
|
||||
- **Game session store** — Still in-memory (`InMemoryGameSessionStore`). Valkey container exists in local dev but not wired up.
|
||||
- **Rate limiting** — Partially implemented on auth endpoints; game endpoints not yet covered.
|
||||
|
|
@ -21,26 +21,26 @@
|
|||
|
||||
## What I'm Working On Now 🔄
|
||||
|
||||
**Primary:** Rewriting the Kaikki data pipeline enrich script for sub-stage architecture (round1_gloss → round1_example → round1_translations → round1_cefr).
|
||||
**Primary:** Phase 3 of the Gemini-only data pipeline (see [pipeline/roadmap.md](pipeline/roadmap.md)): template the Gemini prompt, write the validation module + `pipeline.ts`, and run the first full staging pass (~1,600–1,800 deduped nouns × 5 languages into SQLite).
|
||||
|
||||
**Secondary:** Phase 7 hardening backlog items (see BACKLOG.md `next` section).
|
||||
|
||||
## Next 2-Week Goal 🎯
|
||||
|
||||
Finish Kaikki Stage 3 (enrich) sub-stage rewrite → run full sample → compare quality → decide on production sync timeline.
|
||||
Finish pipeline Phase 3 (full noun run staged in SQLite, reject rate < 10%, 50 entries spot-checked) → Phase 4 import script (pipeline Postgres :5433, then dev :5432) → start rewriting `getGameTerms`/`getDistractors` against the new schema.
|
||||
|
||||
## The Big Picture
|
||||
|
||||
Lila is a **deployed, working vocabulary quiz app**. The core loop (singleplayer + multiplayer) is solid. The next strategic milestone is **media-based practice** (learn vocab from a song/TV episode/book chapter), but that depends on:
|
||||
|
||||
1. Kaikki data pipeline reaching production (fixes translation quality)
|
||||
1. The Gemini data pipeline reaching production (fixes translation quality)
|
||||
2. A media ingestion prototype (subtitles/lyrics → text → vocab extraction → quiz)
|
||||
|
||||
Until then, the app is a generic vocabulary quiz — functional but not differentiated.
|
||||
|
||||
## Quick Links
|
||||
|
||||
- [BACKLOG.md](BACKLOG.md) — Prioritized tasks
|
||||
- [DATA_PIPELINE.md](DATA_PIPELINE.md) — Pipeline stages and current progress
|
||||
- [BACKLOG.md](BACKLOG.md) — `now` / `next` / `later`
|
||||
- [BACKLOG.md](BACKLOG.md) — Prioritized tasks (`now` / `next` / `later`)
|
||||
- [DATA_PIPELINE.md](DATA_PIPELINE.md) — Pipeline orientation and current progress
|
||||
- [pipeline/roadmap.md](pipeline/roadmap.md) — Phase-by-phase pipeline plan
|
||||
- [DEPLOYMENT.md](DEPLOYMENT.md) — Infrastructure ops
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue