Back to corpus
experimentexperiment writeup candidatescore 24
Ankatta Capture V0
Ankatta fits the N'Ko/Malinke speech stack as a lexicon-assisted intent capture surface. It is not the recognizer and it is not the translator. Its job is to make human evidence collection easy when the speaker does not know exact N'Ko spelling.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
Ankatta fits the N'Ko/Malinke speech stack as a lexicon-assisted intent capture surface. It is not the recognizer and it is not the translator. Its job is to make human evidence collection easy when the speaker does not know exact N'Ko spelling.
The page records short audio, lets the speaker enter what they meant in English or rough Malinke/Bambara/Jula, and uses the scraped Ankataa dictionary as a quiet vocabulary aid. Dictionary matches appear automatically from the meaning or rough phrase field. Checked matches are saved only as candidate lexicon context. They do not prove that the audio contained those words.
The original simple capture flow is still preserved in code as `html_app_simple_capture()`, but the served app is the family trainer.
Advanced fields such as phrase identity, optional N'Ko, notes, local export, and raw status remain available behind the advanced drawer. They are useful for review, but they are not the main user journey.
Prompted kid and baby captures do not require typed meaning. The prompt itself becomes the expected meaning and rough Latin/Malinke phrase. This is stronger than open-ended capture because the intended label is known before recording, but it is still not training truth until governed review admits it.
Promotion decision
What has to happen next
Attach run IDs, datasets, metrics, and reproduction commands.
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.