cjm-transcription-tui
No purpose recorded on-graph yet — author it with assert 169694cd-2118-5390-a8b8-de26fb77c930 purpose "…" (or by the repo's entity key).
Modules
cjm_transcription_tui.__init__cjm_transcription_tui.app— The transcription-workflow TUI: run setup as three keyboard stages, then acjm_transcription_tui.candidates— Candidate (capability, MODEL)-instance enumeration for the comparison screen.cjm_transcription_tui.cli— The console-script driver: run the setup TUI, then hand the confirmed plan tocjm_transcription_tui.probe— Per-segment comparison probe: transcribe ONE VAD-cut segment across everycjm_transcription_tui.results— Past-run results for the setup TUI: the core's own runs/*.json manifests readcjm_transcription_tui.sources— Source-selection state for the picker stage: a keyboard file browser plus thecjm_transcription_tui.state— Sidecar TUI state: last-used run settings persisted across sessions (the
API
cjm_transcription_tui.app
TranscriptionAppclass — Transcription-run setup, v0 thinnest slice: three keyboard stages over one
cjm_transcription_tui.candidates
candidate_directivesfunction — Expand every installed transcription capability into its candidate space.discover_capabilityfunction — Pick a DEFAULT capability for a role by surface match.instance_id_forfunction — Derive an addressable instance id for a non-default (capability, MODEL) pick.manifests_with_methodfunction — Enumerate installed capabilities whose structural surface listsmethod.model_axisfunction — Find a capability's MODEL config axis in its config_schema.spec_stringfunction — Render a load directive back to the core CLI's --transcriber grammar.transcription_manifestsfunction — Enumerate installed transcription capabilities from their manifest files.
cjm_transcription_tui.cli
build_parserfunction — The TUI driver's argument surface (setup options + core-run passthrough).mainfunction — Resolve settings (flags > persisted state > manifest discovery), run theplan_argvfunction — Render a confirmed plan as headless core-CLI argv.
cjm_transcription_tui.probe
SegmentProbeclass — One source's cut segments + cached per-segment comparison results.
cjm_transcription_tui.results
RunIndexclass — runs/*.json manifests loaded newest-first + the lookups the TUI paints from.
cjm_transcription_tui.sources
CollectionFieldclass — Pre-run collection state for the sources stage (ae3464fc: the actorSourceBrowserclass — Keyboard file-browser + ordered selection state for the sources stage.
cjm_transcription_tui.state
load_statefunction — Read this project's persisted TUI state.save_statefunction — Merge updates into the persisted state and write it back (best-effort:state_pathfunction — Where this project's TUI state lives.
Dependencies
Depends on: cjm-substrate-tui-kit, cjm-transcription-core, textual
Metadata
Release files for cjm-transcription-tui 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cjm_transcription_tui-0.0.4.tar.gz | 38.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cjm_transcription_tui-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.0 kB
Release files / cjm_transcription_tui-0.0.4.tar.gz
| Download URL | cjm_transcription_tui-0.0.4.tar.gz |
|---|---|
| Size | 38.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
55fbf66a8c4bbad6696771aaeb1bbd4771e5d63ffc2407a3b8be0f3f479bb756
|
|
BLAKE2b-256 checksum How to use checksums |
3397d6a4e6973547bf7a4eed3f2fe0befe5a8014e04f5326f4448ce4e9727356
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Release files / cjm_transcription_tui-0.0.4-py3-none-any.whl
| Download URL | cjm_transcription_tui-0.0.4-py3-none-any.whl |
|---|---|
| Size | 36.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24e9c36e11e1c44a0530ffff094e9971f70c2a5022a50329bbc1617ad453c764
|
|
BLAKE2b-256 checksum How to use checksums |
ca713bea31c725f5f2c250e2dc625de5eab2f41f523df0234dca03e23746f986
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.12
|
Security for cjm-transcription-tui 0.0.4
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.