Skip to main content

cjm-transcript-decomp-tui

Decomp-batch TUI driver for the transcript-decomposition workflow: browse the transcription core's run manifests, queue an ordered multi-run batch with per-run authoritative-text (text-from) picks, preview how the batch folds into headless invocations, then hand off to cjm-transcript-decomp-core's batch runner — one loaded capability stack per text-from group, every run byte-identical to a hand-launched one. Includes a read-only decomp-results view over the decomp core's own manifests.

Modules

  • cjm_transcript_decomp_tui.__init__
  • cjm_transcript_decomp_tui.app — The decomp-batch TUI: pick transcription runs into an ordered batch, then a
  • cjm_transcript_decomp_tui.cli — The console-script driver: run the batch-selection TUI, then hand each
  • cjm_transcript_decomp_tui.discovery — Capability-role discovery by manifest surface match — the journaling-by-
  • cjm_transcript_decomp_tui.runs — Run-manifest indexes for the decomp-batch TUI (work item 0ff6bf0f): the
  • cjm_transcript_decomp_tui.segments — Fine-segment inspection for the decomp TUI (work item 166dd2b8, half a):
  • cjm_transcript_decomp_tui.state — Sidecar TUI state: last-used batch settings persisted across sessions (the

API

cjm_transcript_decomp_tui.app

  • DecompApp class — Decomp-batch setup, v0 thinnest slice: one selection stage over the

cjm_transcript_decomp_tui.cli

  • batch_argv function — Render one hand-off group as headless decomp-core argv.
  • build_parser function — The TUI driver's argument surface (batch-setup options + core passthrough).
  • event_split_batch_error function — One propset carves ONE source: the core applies --event-propset to every
  • hand_off function — The shared driver tail: persist the confirmed choices, adopt the in-app
  • main function — Resolve the shared setup surface, run the batch app, hand off — the
  • resolve_settings function — Resolve the batch-setup settings every shell shares (flags > persisted
  • resolve_split_flags function — Resolve the post-parse split-flag contract (pure; main() calls it

cjm_transcript_decomp_tui.discovery

  • discover_capability function — Pick a DEFAULT capability for a role by surface match.
  • manifests_with_method function — Enumerate installed capabilities whose structural surface lists method.

cjm_transcript_decomp_tui.runs

  • DecompIndex class — Decomp-core run manifests read back: coverage chips for the batch stage
  • PropsetIndex class — Proposal-set manifests under the workspace proposals/ dir — the model's
  • SourceRunIndex class — Transcription-core run manifests — the decomp workflow's SOURCES — plus
  • TrainingRunIndex class — Training-run manifests under the workspace training-runs/ dir — the
  • group_batches function — Fold an ordered batch selection into headless hand-off groups.

cjm_transcript_decomp_tui.segments

  • SegmentStack class — One lazily-opened READ-ONLY graph seat, keyed by db path.
  • aseg_index_for function — Which coarse AudioSegment a source-coordinate time falls in (pure;
  • build_display function — Interleave gap markers into the paintable entry list (pure).
  • capability_config_schema function — A capability's config_schema off its installed manifest (json read, pure).
  • find_gaps function — Uncovered timestamp spans between committed segments (pure).
  • fmt_ts function — Source-coordinate timestamp for listing rows (pure).
  • locate_span function — Resolve a source-coordinate span onto its owning coarse WAV (pure).
  • ordered_rows function — Re-impose the manifest's spine order on fetched rows (pure).
  • predicted_rows function — Synthesize segment-shaped rows for a probe's predicted skeleton (pure).
  • probe_compare function — Compare a VAD probe against the committed skeleton (pure).
  • realign_rows function — Re-run the decomp pipeline's own text fold over a PROBE skeleton (pure).
  • split_predicted function — Run the decomp pipeline's own SENTENCE-SPLIT stage over a probe skeleton
  • vad_summary function — The decomp run's recorded VAD config, one status line (pure).

cjm_transcript_decomp_tui.state

  • load_state function — Read this project's persisted TUI state.
  • save_state function — Merge updates into the persisted state and write it back (best-effort:
  • state_path function — Where this project's TUI state lives.

Dependencies

Depends on: cjm-substrate-tui-kit, cjm-transcript-decomp-core, textual Used by: cjm-transcript-decomp-qt

Metadata

Release files for cjm-transcript-decomp-tui 0.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cjm-transcript-decomp-tui 0.0.3
File Size Uploaded Provenance
cjm_transcript_decomp_tui-0.0.3.tar.gz 47.1 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for cjm-transcript-decomp-tui 0.0.3
File Interpreter ABI Platform
cjm_transcript_decomp_tui-0.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 89.7 kB

Release files / cjm_transcript_decomp_tui-0.0.3.tar.gz

Download URL cjm_transcript_decomp_tui-0.0.3.tar.gz
Size 47.1 kB
Tags Source
SHA-256 checksum
How to use checksums
0231a396275254699d017d7cbbc746fa966390442534ddaa58bd40af87cd2006
BLAKE2b-256 checksum
How to use checksums
1b08bd5eedfc851dd825c17d8594fdbb76acff5b969b3c582323660589bb1886
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.12

Release files / cjm_transcript_decomp_tui-0.0.3-py3-none-any.whl

Download URL cjm_transcript_decomp_tui-0.0.3-py3-none-any.whl
Size 42.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e612ba536af357aae49a2bd63730947c76dd9534547849a48ac659db887a01da
BLAKE2b-256 checksum
How to use checksums
89c4f870eb17edf530ed0754672b688d8ad33a2770daf8d614cb940cef93bf6b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.12

Security for cjm-transcript-decomp-tui 0.0.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page