akousma (Python)
Reference implementation of the Sonic Field akousma sonic-memory protocol. Consumed by oída, germ (backend), and algophony (pipelines) so all three share one memory layer with one lineage model.
Spec: earworm/docs/akousma_spec_v1.md ·
Store: earworm/docs/akousmata-store.md
Install
cd packages/py-akousma
pip install -e .
Use
import akousma
# Build + validate a record
rec = akousma.new_akousma(
audio={"asset_id": "asset_1", "content_hash": "sha256:...", "duration_seconds": 10.0},
originating_app="oida", source_type="recorded", origin="live-input",
listening={"oida.signal": {"class": "music-like"}},
)
assert akousma.is_valid(rec)
# Optional v1.5 accountable-listening index. The full producer report remains
# namespaced in `listening`; the auditum keeps attribution and references.
rec["auditum"] = akousma.auditum(listenings=[{
"listening_id": "lst_1",
"listener_id": "oida",
"listener_type": "agent",
"created_at": rec["created_at"],
"report_namespace": "oida.signal",
"contract": "akouo/v0.9",
}], route_decisions=[akousma.route_decision(
"decision-listen-1",
gate="inference", outcome="proceed",
subject="accountable listening pass",
reason="The user requested an observe-only pass.",
actor="oida-router", listening_id="lst_1",
producer_contract="akouo/v0.9",
)])
# Shared store (platform application-data directory, or $AKOUSMATA_PATH)
with akousma.AkousmataStore() as store:
uri = store.put_audio(open("clip.wav", "rb").read()) # content-addressed
rec["audio"]["uri"] = uri
store.put(rec)
child = akousma.new_akousma(
audio={"asset_id": "asset_2"}, originating_app="germ",
source_type="generated", origin="generated",
parent_akousma_ids=[rec["akousma_id"]], operation="transform", prompt="make it metallic",
)
store.put(child)
store.ancestors(child["akousma_id"]) # -> [rec["akousma_id"]] (germ lineage explorer)
store.query(originating_app="oida") # -> [rec] (algophony batch)
store.query(has_auditum=True) # accountable records
store.query(has_route_decision=True) # auditum/v2 decisions
store.query(has_stop_decision=True) # refusal, withholding, forgetting, non-action...
store.query(has_disagreement=True) # plural hearings with preserved differences
A refusal before capture is also addressable without inventing audio:
refusal = akousma.new_akousma(
originating_app="oida",
source_type="unknown",
origin="live-input",
subject="quiet-hours capture request",
auditum=akousma.auditum(route_decisions=[akousma.route_decision(
"decision-capture-1",
gate="capture", outcome="refuse", subject="audio capture",
reason="The adopted covenant closes the ear.", actor="covenant-gate",
)]),
)
forget_with_receipt(...) removes a record and returns a content-free durable
receipt. forgotten(id) can later prove the operation occurred without
restoring summary, tags, location, hashes, URIs, or forgotten content.
The bundled akousma/akousma.schema.json is the canonical schema, kept in sync with
earworm/packages/core/schemas/akousma.schema.json.
Metadata
Release files for akousma 0.6.1
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 |
|---|---|---|---|---|
| akousma-0.6.1.tar.gz | 25.6 kB | With provenance | Details for akousma-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| akousma-0.6.1-py3-none-any.whl | Python 3 | none | any | Details for akousma-0.6.1-py3-none-any.whl |
Total release size: 46.6 kB
Release files / akousma-0.6.1.tar.gz
| Download URL | akousma-0.6.1.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1cb097574c84d291d95b11b8f290e5a2fcdbe728fc01ba8e3ff04e23ebe16356
|
|
BLAKE2b-256 checksum How to use checksums |
df546f9fce7fac1256b0df5f840d7fe58ddb99113c05f1db135a38e9e6d84a28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 3, 2026.
Transparency logRelease files / akousma-0.6.1-py3-none-any.whl
| Download URL | akousma-0.6.1-py3-none-any.whl |
|---|---|
| Size | 21.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
881cc76428d0a149f2c935aec6faaaef74027cb450d5fc237a13c0c5d7b5114c
|
|
BLAKE2b-256 checksum How to use checksums |
e8e48d0b8687469d2a4457a9ebc9f0f818a77844f49866e87f7dad089efb80cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 3, 2026.
Transparency logSecurity for akousma 0.6.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for akousma-0.6.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 3, 2026.
Transparency logA 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.