Skip to content

Releases: sonicfieldlabs/algophony

Algophony v0.5.2

Choose a tag to compare

@emeisazam emeisazam released this 03 Aug 03:39
0f68053

What's Changed

  • Align Listening Stack releases and Earworm install ref by @emeisazam in #7
  • Align GERM 0.3.2 compatibility reference by @emeisazam in #8
  • Keep automated listening claims attributable by @emeisazam in #9
  • Align Earworm install reference by @emeisazam in #10

Full Changelog: v0.5.1...v0.5.2

Algophony v0.5.1

Choose a tag to compare

@emeisazam emeisazam released this 02 Aug 23:53
62d8d2f

Aligns the portable listening contract with AKOÚŌ 0.9 and Oída gateway 0.5, restores the strict heard-evidence boundary, adds corpus listening, and updates Next.js plus vulnerable transitive dependencies. Both public apps build cleanly and the dependency audits report zero vulnerabilities.

Algophony v0.5.0 — the sovereignty layer, evaluated honestly

Choose a tag to compare

@emeisazam emeisazam released this 12 Jul 22:59

Algophony v0.5.0 — The Sovereignty Layer, Evaluated Honestly

2026-07-12. Contract-alignment release; the frozen corpus is untouched.

AKOÚŌ v0.7 (sovereign listening)

The AKOÚŌ contract pin moves to akouo/v0.7: the fifteenth mode
(sovereign-listening) and the eighteenth command (/covenant) enter the
mode and command enums (schemas/listening-report.schema.json, the TS
contract mirror, and the drift guards — all verified against the published
manifest).

Akousma spec v1.3 (the covenant block)

Records may carry a covenant block: under which ethics they were listened —
the listening covenant's identity and lineage plus honest absence (what was
withheld, counted and attributed to its rule, never described).
akousma_to_prompt_record(...) carries the block (and a covenant_id
convenience), so evaluation runs can group and audit by covenant.

Evaluation discipline: what a covenant withheld does not exist for the
evaluator. Algophony never scores, reconstructs, or guesses at withheld
material; coverage metrics treat attributed absence as out-of-universe, not
as a miss. Withheld-without-attribution remains indistinguishable from a bad
ear — which is precisely why the attribution requirement exists.

Compatibility

  • Oída gateway pin unchanged (oida/gateway/v0.2); Oída 0.4.0's covenant
    gates are additive.
  • Records without a covenant block read exactly as before.

Algophony v0.4.0 — spec v1.2: located, directed listening

Choose a tag to compare

@emeisazam emeisazam released this 12 Jul 03:50

Algophony v0.4.0 — Spec v1.2: located, directed listening

2026-07-11. Integration release; the frozen corpus is untouched.

Akousma spec v1.2 (Earworm v0.3)

The shared store's records may now carry two optional consent-scoped blocks,
and the record is open at the top level (unknown fields are preserved by
stores, never rejected):

  • location — where the sound was heard: lat/lon, accuracy_m,
    altitude_m, human label, source (gps/network/manual/config/inferred),
    captured_at. The akousmata navigator plots these on its new listening
    map and strips them from every open-research export.
  • capture — how the listening was triggered: direction (past =
    the ring-buffer seconds before the trigger; future = the window recorded
    after it; live = open-ended), window seconds, trigger surface,
    armed_at, triggered_at. Oída's floating listener and new remote ear
    write it on every capture.

workers/akousmata_source.py carries both blocks through
akousma_to_prompt_record(...) — as location, capture, and the
convenience capture_direction — so evaluation and organization runs can
group by place or temporal direction. A record without akousma_id now
raises a clear KeyError instead of an anonymous one.

CI

The worker unit tests (provider contracts, Oída gateway contract, the
AKOÚŌ drift guards, and the akousmata batch surface) now run in CI. The
cross-repo drift assertions self-skip where the sibling checkouts are
absent and run fully in local development.

Compatibility

  • The Oída gateway contract pin stays oida/gateway/v0.2; every gateway
    addition in Oída 0.3.0 is optional and additive.
  • The AKOÚŌ contract pin stays akouo/v0.6.
  • Records without location/capture (spec v1.0/v1.1) read exactly as
    before.

Algophony v0.3.1 — Akousmata Navigator Connection

Choose a tag to compare

@emeisazam emeisazam released this 10 Jul 17:10

Documentation subrelease connecting Algophony to the new akousmata listening navigator (github.com/sonicfieldlabs/akousmata) — the library app over the shared store this repo's batch surface reads and writes. Evaluation stamps (extensions["algophony.eval"]) render on each record's wiki page there, and the compares_with links written across evaluation batches are navigable as kinship edges.

No code changes; py-akousma >= 0.2.1 recommended (adds tags(), changed_since(), forget()).

Algophony v0.3 — Executed Listening Contract

Choose a tag to compare

@emeisazam emeisazam released this 10 Jul 14:30

Algophony v0.3 Release Notes

Date: 2026-07-10

v0.3 turns the listening contract from documentation into an executed layer,
aligned with AKOÚŌ v0.6 and Earworm v0.2 across the Listening Stack.

Listening-contract execution (new)

  • workers/listening_plan.py: deterministic AKOÚŌ routing plans without any
    LLM. Artifact availability derives the evidence level (prompt-only →
    prompt_only, generation metadata → metadata_only, analysis features →
    measured_signal, everything together → mixed); the evidence level plus
    command overrides derive claim permissions; missing inputs become stop
    conditions instead of imagined listening.
  • scripts/generate_reports.py attaches a routing plan and the
    akouo_contract_version pin to every new report and enforces claim
    permissions: blocked claims move to undetermined with an explicit marker,
    never silently dropped.
  • scripts/test_listening_plan.py covers evidence derivation, permissions,
    enforcement, schema conformance of built plans, and a drift check against
    the machine-readable AKOÚŌ manifest, so contract copies cannot silently
    diverge from the source of truth.

AKOÚŌ v0.6 contract sync

  • 14 listening modes (adds memory-lineage-listening, the sound-memory ear)
    and 17 commands (adds /remember).
  • Claims may carry source (audio, dsp, metadata, model, transcript,
    context, memory, human, other) and time_range anchors.
  • Mode outputs may declare akouo_version, apparatus (substrate, perception
    sources, known blind spots), listener, and memory links; routing plans
    may carry budget and preset_id; reports pin akouo_contract_version.
  • Synced across schemas/listening-report.schema.json,
    apps/web/app/lib/listening-contract.ts, and apps/web/app/lib/types.ts;
    the report page renders contract, budget, and preset when present.

Earworm v0.2 / akousma spec v1.1 batch surface

  • workers/akousmata_source.py reads both raw (v1.0) and enveloped (v1.1)
    listening entries, prefers record summaries, and surfaces summary, typed
    relations, consent status, and pipeline effects on prompt records.
  • New kinship and maintenance operations: related(), add_relation()
    (e.g. compares_with across an evaluation batch, idempotent),
    find_by_hash() recurrence lookup, and verify_store() integrity reports
    (absence is information). Query filters extend to tag/text/since/until on
    v0.2 stores with graceful fallback on older ones.
  • CLI: --related and --verify flags.

Provenance and openness instrumentation

  • Provider openness profiles derived on the registry and shown on the
    /providers page: open_source_internal, open_weights_local,
    open_code_hosted, closed_api — the literacy-or-capture axis made
    operational.
  • compute_provenance stamped from the registry at generation time in the
    pipeline (local hardware vs hosted endpoint vs cloud API); never guessed
    after the fact.
  • Standing review questions documented as the review protocol
    in docs/benchmark-methodology.md, mapped to existing fields.

Corpus discipline (unchanged)

No backfills: the v0.1.1 corpus keeps null routing plans, traces, provenance and consent
axes, and compute provenance. New fields activate only through actual routed,
traced, or scored passes.

Algophony v0.2.1

Choose a tag to compare

@emeisazam emeisazam released this 02 Jul 18:01

Algophony v0.2.1 Release Notes

Scope

v0.2.1 is a paper-alignment and contract release for the v0.2 local-mode
platform. It keeps the v0.1.1 procedural pilot corpus unchanged and still does
not claim a full ML model benchmark.

Changes Since v0.2

  • Normalized terminology: Algophonya is the condition; Algophony Framework is
    the evaluation layer.
  • Updated AKOÚŌ labels from v0.4 to v0.5 while preserving the already-synced
    contract: 13 listening modes, router, reference-layer, 16 commands, evidence
    ladder, claim permissions, routing plans, and reference maps.
  • Added schemas/earworm-trace.schema.json plus nullable earworm_trace
    fields on generation and listening-report schemas.
  • Added read-only dashboard rendering for Earworm/Akousmata trace status,
    event chains, attached signals, context bundles, retention policy, and memory
    operations.
  • Added docs/earworm-akousmata-integration.md to document traceable
    listening routes and non-audio context attachment.
  • Normalized the official public repository target to
    https://github.com/sonicfieldlabs/algophony.
  • Added strict README corpus-count validation that fails when public count
    claims drift from the canonical JSON/JSONL corpus.

Unchanged Boundaries

  • No Earworm traces are backfilled onto the v0.1.1 corpus.
  • Provenance and consent axes remain nullable and unscored until an actual reviewing
    pass scores them.
  • Public exports still exclude local benchmark data, generated metadata, report
    corpora, generated audio, uploads, secrets, private paths, and private local
    history.