Expand description
Post-transcription text cleanup ( “flow”).
Two backends:
- rules (default): pure on-device regex/heuristics — no network, no model
- openrouter: LLM rewrite via chat completions (optional, explicit)
Cleanup is opt-in at the CLI/library boundary so raw ASR stays available.
Re-exports§
pub use openrouter::OpenRouterCleanup;pub use rules::RulesCleanup;
Modules§
- openrouter
- LLM-assisted cleanup via OpenRouter (JOE-1589 structured untrusted-data contract).
- rules
- On-device rule-based cleanup (JOE-1610).
Structs§
- Cleanup
Report - Structured report for a full-result cleanup transaction.
- Cleanup
Result - Result of a cleanup pass over bare text.
Enums§
- Cleanup
Provider Kind - Where cleanup runs.
- Cleanup
Style - How aggressively / in what shape to clean transcript text.
- Segment
Cleanup Policy - How to treat ASR segments after cleaning the full transcript text.
Constants§
- MAX_
PER_ SEGMENT_ CHARS - MAX_
PER_ SEGMENT_ COUNT - Hard bounds for per-segment cleanup (failure semantics live here; remote batching belongs to a follow-up issue).
Traits§
- Text
Cleanup - Pluggable cleanup backend.
Functions§
- apply_
cleanup - Apply cleanup to a full transcription result.
- apply_
cleanup_ with_ segments - Like
apply_cleanupwith explicit segment policy. - apply_
cleanup_ with_ segments_ op - Like
apply_cleanup_with_segmentswith an optionalOpContextfor cancel, deadline, and progress (JOE-1831). - cleanup_
text - Clean a bare string (stdin / text file path) without a full transcription result.