Developer tooling / In progress
An SDK is taking shape.
The first Python prototype makes the file format easier to inspect and test. A public release is still ahead.
Implemented in the prototype
Inspect. Validate. Write.
- Bounded bundle inspection
- MAIN structural and semantic checks
- Landmark record encoding and decoding
- Exact frame-to-time conversion
- Basic single-MAIN bundle writing
Still to come
Generate. Match. Interoperate.
- Acoustic fingerprint generation
- Acoustic matching and timing evidence
- Edit-layer resolution
- Cross-language interoperability testing
- Public packaging and license selection
A clear first step
The prototype is version 0.1.0.dev0, declares Python 3.10 or newer and was tested with Python 3.12.3 in its initial review. Thirty SDK tests passed at that review. Those checks cover the inspection implementation and synthetic vectors; they are not proof of compatibility with every native reader.
Encoding landmark records means packing already-created hash/frame pairs into the file’s representation. It does not mean generating acoustic fingerprints from a recording. The same distinction applies to validation: reading a file successfully does not make it eligible for playback reuse.
The path to a public SDK
Make the current format visible
Document the file family, publish review examples and identify where readers differ.
Agree on the shared behavior
Resolve the seven compatibility decisions, then test actual reader and writer implementations against the same vectors.
Package the agreed contract
Select licenses and qualify the public API. Generation and matching need their own implementation and interoperability evidence.