Back to corpus
research notebacklog referencescore 22

ߒߞߏ N'Ko Unified Platform — Master Integration Plan

``` ┌─────────────────────────────────────────────────────────────────┐ │ N'KO UNIFIED PLATFORM │ │ ═══════════════════ │ │ │ │ ┌──────────────────────── APPS ────────────────────────────┐ │ │ │ │ │ │ │ 📱 iOS App 🖥 macOS MenuBar 🌐 PWA/Web │ │ │ │ (Keyboard + (SpeakFlow + (Bridge + │ │ │ │ Voice + Quick Translate) Demo) │ │ │ │ Bridge) │ │ │ │ │ │ │ │ 🤖 Telegram Bot 🔌 Chrome Ext ⌨️ Raycast │ │ │ │ (Translate + (Inline Bridge) (Quick Convert) │ │ │ │ Cultural) │ │ │ └───────────────────────────┬─────────────────

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

# ߒߞߏ N'Ko Unified Platform — Master Integration Plan ## From 13 Scattered Projects → 1 Unified System ### R1: Transliteration (3 implementations → 1) | Current | Location | Lines | Action | |---------|----------|-------|--------| | Python Bridge | cross-script-bridge/core/ | ~400 | **KEEP as canonical** | | Python Translation Bridge | nko-keyboard-ai/lib/translation_bridge.py | ~200 | **DELETE** — redirect imports to core bridge | | Swift Transliterator | ios-keyboard/Sources/NKoCore/ | ~150 | **REWRITE** — port canonical Python to Swift natively | ### R2: Phonetics/IPA (scattered across 13 files → 1 module) | Current | Action | |---------|--------| | Inline IPA maps in bridge.py, nko.py, arabic.py | **EXTRACT** into `core/phonetics/ipa.py` | | IPA references in 10 keyboard engines | **IMPORT** from shared phonetics module | | Tone handling in prosody_engine.py | **MERGE** into phonetics module | **Result:** `nko.phonetics` — single source of truth for IPA mappings, tone marks, diacritics. ### R3: Cultural Data (3 sources → 1) | Current | Location | Action | |---------|----------|--------| | cultural_engine.py | nko-keyboard-ai | **KEEP** — richest implementation | | proverbs.json | nko-code-comments | **MERGE** into unified `data/proverbs/` | | Manding Proverbs API | 28-days-of-code | **ABSORB** — data into proverbs/, API logic into core |

Promotion decision

What has to happen next

Keep in the searchable backlog until it intersects a live paper or system.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.