Back to corpus
technical noteexperiment writeup candidatescore 32
Codex Handoff: N'Ko ASR Vast.ai Pipeline Monitor
**Created:** 2026-04-04 14:50 UTC **Author:** Claude (Mac1 bottom-right pane) **For:** Codex agent taking over monitoring duties
Full HTML reader
Read the full artifact
Extracted abstract or opening context
**Created:** 2026-04-04 14:50 UTC **Author:** Claude (Mac1 bottom-right pane) **For:** Codex agent taking over monitoring duties
Two CTC inference jobs are transcribing 32,826 Djoko soap opera audio segments on a Vast.ai RTX 4090 GPU. A watchdog monitors both jobs and will auto-launch a 3-step chain when they finish.
**Instance:** 34097422 (label: `djoko-batch-v3`) **Machine:** RTX 4090, 16 vCPUs, 127GB RAM, 100GB disk (53GB used) **Cost:** $0.3337/hr **SSH:** `[ssh command redacted]`
### Progress at handoff time - N'Ko: 16,128 / 32,826 (49.1%) - Latin: 16,129 / 32,826 (49.1%) - Rate: ~1.4 segments/second per job - ETA: ~3.2 hours from handoff (~6pm local)
| Session | Process | Purpose | |---------|---------|---------| | `nko_infer` | `vastai_transcribe.py --script nko --resume` | N'Ko CTC inference on 32,826 Djoko WAV segments | | `latin_infer` | `vastai_transcribe.py --script latin --resume` | Latin CTC inference on same 32,826 segments | | `watchdog` | `watchdog.sh` | Checks every 60s. Restarts dead jobs. Launches chain when both done. |
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.