Skip to content

Releases: sonicfieldlabs/oida

Oída v0.10.0

Choose a tag to compare

@emeisazam emeisazam released this 11 Aug 23:24
4f934c7

What's Changed

Full Changelog: v0.9.2...v0.10.0

Oída v0.9.2

Choose a tag to compare

@emeisazam emeisazam released this 03 Aug 03:59
22a9966

What's Changed

  • Align GERM 0.3.2 compatibility reference by @emeisazam in #9
  • Separate machine inference from embodied hearing by @emeisazam in #10

Full Changelog: v0.9.1...v0.9.2

OÍDA v0.9.1 — Security hardening

Choose a tag to compare

@emeisazam emeisazam released this 03 Aug 01:19
46df4b1

Hardens the localhost gateway and macOS Keychain boundary, bounds covenant parsing, sanitizes public errors while retaining local diagnostics, documents the operator-selected audio boundary, and aligns the current GERM, Algophony, and ORAM compatibility references. The existing release workflow verified all canonical distributions and published sonicfield-oida 0.9.1 through the configured PyPI gate.

OÍDA v0.9.0 — Decision-first listening gateway

Choose a tag to compare

@emeisazam emeisazam released this 03 Aug 00:19

Introduces decision-first gateway v0.5, accountable listening event v0.3, AKOÚŌ context v2, corpus provenance, plural listening without false consensus, and an explicitly optional GERM capability. Pre-listening refusal remains a complete attributable result without fabricated hearing.

OÍDA 0.7.0 — The declared ear

Choose a tag to compare

@emeisazam emeisazam released this 17 Jul 19:04
c0c50dc

OÍDA 0.7.0 introduces LISTENING.md: an optional, empty-by-default, user-authored listening identity for situated attention, relation, questions, and voice. It remains strictly subordinate to the Listening Covenant, privacy rules, apparatus limits, routing, and evidence; it never affects deterministic DSP or exact transcription, and event and memory provenance carries only a content-free revision reference.

The release adds conflict-safe dashboard, REST, SSE, and MCP editing; one-revision-per-request and per-turn prompt integration; hosted-agent revision declarations through oida_harness; Covenant preflight guidance for Hermes, Claude Code, Codex, OpenClaw, and OpenCode; gateway oida/gateway/v0.3 and host-perception oida/host-perception/v0.2; 14 MCP tools; and explicit Covenant enforcement across secondary hearings. The release passed 316 tests plus isolated wheel, dependency, web, macOS build/package, and release smoke gates, and was published through the verified Trusted Publishing stack.

OÍDA 0.6.5 — Audited and hardened listening stack

Choose a tag to compare

@emeisazam emeisazam released this 17 Jul 02:55
4cd403d

OÍDA 0.6.5 — Audited and hardened listening stack

Hardens request validation, runtime API discovery, OpenAPI and media contracts, GERM handoff, and the local MOSS pipeline; removes dead dependencies and generated cache artifacts; strengthens package, dependency, and release verification; and publishes the complete Trusted Publishing Python stack with digital attestations: akouo-contract 0.7.0, akousma 0.4.0, akousmata 0.4.0, and sonicfield-oida 0.6.5.

OÍDA 0.6.0 — Evidence-grounded listening

Choose a tag to compare

@emeisazam emeisazam released this 15 Jul 04:31

OÍDA 0.6.0 — Evidence-grounded listening

Adds the installable Python release chain, evidence-citing conversation and re-listening, capability-aware provider routing, explicit external-audio consent, host handoff surfaces, secure credential boundaries, and the current Sonicfield listening-stack integrations.

oída 0.4.0 — the covenant engine: sonic sovereignty as runtime

Choose a tag to compare

@emeisazam emeisazam released this 12 Jul 22:59

Every listen surface can now run under a listening covenant — a plain-text declaration (English or Spanish) of what this ear will not listen to, will release after hearing, will not reveal, will not retain, will blur, or will refuse at certain hours, and why.

  • Four gates: input (refuse sources, quiet hours, max window — a refusal answers 423 with the covenant and rule named), content (ignored classes: their perception passes are never even run), output (withhold transcript / speaker-identity / affect / location / song-identity / events / spectral-detail, or coarsen location to a declared radius), retention (raw audio released, memory writes refused — reported, never silent).
  • The bridge, not the cage: rule lines the engine can't parse become commitments, carried verbatim and reported — sing to the river every equinox survives every hearing it accompanies.
  • Honest absence on the record: events, traces, and shared-store akousmata carry the covenant block (identity, lineage, rules applied, attributed withholding, commitment count); the navigator filters by it.
  • Surfaces: dashboard Covenant panel · GET/PUT /covenant + POST /covenant/activate · oida_covenant MCP tool (agents may propose; activation stays the operator's act) · per-listen covenant pin · remote-ear badges.
  • Empty by default — sovereignty is opted into, never imposed.

Contracts: akouo/v0.7 pin, components earworm/v0.4 + akousmata/v0.4, gateway stays oida/gateway/v0.2. 163 tests. Also ships the new listening-point app icon.

oída 0.3.0 — the remote ear and directed listening

Choose a tag to compare

@emeisazam emeisazam released this 12 Jul 03:50
  • The remote ear (/remote): phone records (PCM in the page, WAV on-device), attaches its GPS fix when granted, posts to POST /remote/listen; the server runs the full pipeline, keeps the WAV, writes the akousma — the sound + its listening file, with spec v1.2 location and capture — into the shared store, and returns the listening event to the remote UI. Served over the operator's private network (Tailscale); remote_ear_url reported by oida integrate remote.
  • Future / past listening: past slices the ring buffer that was already listening when the trigger fired; future records the window after it. Direction pill (⟲/⟳) in the floating listener, default in Settings, native mic ring 30s→120s with real bufferedSeconds, on-phone ring buffer in the remote ear (overwrites itself — nothing accumulates), capture_direction/capture_seconds/capture_trigger on /listen-event.
  • Geolocated listening: optional consent-scoped location on /listen-event, /gateway/listen, the germ handoff, and oida_listen (MCP) — plotted by the akousmata listening map at /library/.
  • MCP: oida_live gains capture (the past direction made callable); oida_listen gains location.
  • Contracts: components move to earworm/v0.3 + akousmata/v0.3; the gateway contract stays oida/gateway/v0.2 — everything is additive. 150 tests.