cjm-transcription-adapter-interface
Typed transcription task-adapter interface — TranscriptionAdapter ABC, the generic cache/persist adapter, the REMOVE-AFTER-OVERHAUL core shim, and transcription persistence helpers.
Modules
cjm_transcription_adapter_interface.__init__cjm_transcription_adapter_interface.adapter— The typed transcription task contract — TranscriptionAdapter ABC + the REAL structural tool protocol (capability-unit Option C, pass-2 Thread 3; protocol born real at stage 8).cjm_transcription_adapter_interface.core— REMOVE-AFTER-OVERHAUL(option-c-cascade): class-identical legacy import surface; TranscriptionResult relocated to cjm_capability_primitives.transcription at execution stage 8 (Option C / PILLAR 1c — pure-compute tool capabilities depend on the data noun, never the adapter machinery).cjm_transcription_adapter_interface.generic— The generic (tool-agnostic) transcription adapter — cache-check, invoke the bound tool's pure-compute transcribe, persist. Reused across every tool capability satisfying TranscriptionToolProtocol (whisper, voxtral, ...), exactly as GenericGraphStorageAdapter is reused across graph backends.cjm_transcription_adapter_interface.storage— Standardized SQLite storage for transcription results with content hashing.
API
cjm_transcription_adapter_interface.adapter
TranscriptionAdapterclass — Typed transcription task adapter: model-ready audio in,TranscriptionToolProtocolclass — Structural contract for transcription tool capabilities (BORN REAL at
cjm_transcription_adapter_interface.generic
GenericTranscriptionAdapterclass — Generic transcription adapter: cache-check -> pure-compute tool -> persist.
cjm_transcription_adapter_interface.storage
TranscriptionRowclass — A single row from the transcriptions table.TranscriptionStorageclass — Standardized SQLite storage for transcription results.
Dependencies
Depends on: cjm-capability-primitives, cjm-substrate
Used by: cjm-transcription-core
Metadata
Release files for cjm-transcription-adapter-interface 0.0.17
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 | Actions |
|---|---|---|---|---|
| cjm_transcription_adapter_interface-0.0.17.tar.gz | 16.3 kB | Without provenance | Details for cjm_transcription_adapter_interface-0.0.17.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cjm_transcription_adapter_interface-0.0.17-py3-none-any.whl | Python 3 | none | any | Details for cjm_transcription_adapter_interface-0.0.17-py3-none-any.whl |
Total release size: 30.8 kB
Release files / cjm_transcription_adapter_interface-0.0.17.tar.gz
| Download URL | cjm_transcription_adapter_interface-0.0.17.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c622a77f2063b050b82d4b825cb0109bf2434b1ff91a7433fe321be7ba6b540f
|
|
BLAKE2b-256 checksum How to use checksums |
2595fc8d26e094f1511b71beeae7f5d1fca3897bb043b6348f2a53d751df364d
|
| 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_adapter_interface-0.0.17-py3-none-any.whl
| Download URL | cjm_transcription_adapter_interface-0.0.17-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b691c912d4540d67767fa5ba50d93af335c4640087f926962debdb5e96b6ce35
|
|
BLAKE2b-256 checksum How to use checksums |
f32fb090ac7e8c7372e0f6761ec3146bf2cff0c2872b9be77d0c8b876648294c
|
| 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-adapter-interface 0.0.17
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.