Back to corpus
technical noteexperiment writeup candidatescore 32

N'Ko ASR Row Contract

This is the concrete row-level contract that the Vast ASR exporter should emit so the local uncertainty-packet pipeline can consume it without ad hoc parsing.

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

This is the concrete row-level contract that the Vast ASR exporter should emit so the local uncertainty-packet pipeline can consume it without ad hoc parsing. - `audio_path` - `split` - `script` - `mode` - `asr_text` - `ctc_confidence` - `partition` - `reference_text` - one stable join key: - `audio_path`, preferred - or `segment_id` - or `feat_id` - `feat_id` - `audio_id` - `segment_id` - `cer_edits` - `trajectory_scalars` - `top_confusable_spans` - `n_best_hypotheses` - `char_posteriors_summary` - legacy row upgrader: - `asr/upgrade_asr_row_contract.py` - corpus schema now includes: - `feat_id` - `audio_id` - `split` - `script` - `mode` - `reference_text` - `cer_edits` - `partition` - `trajectory_features` - `top_confusable_spans` - `n_best_hypotheses` - `char_posteriors_summary` - `uncertainty_score`

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.