OpenBrain v1.0.1
Patch release focused on write-path reliability and replay safety for production ingest flows, with no breaking API
changes.
Highlights
- Enforced write idempotency ledger on OSS write path (
idempotency_keynow replay-safe). - Deterministic write receipts added (additive response metadata).
- HTTP and MCP parity for idempotency behavior.
- New DB-backed tests for replay, mismatch rejection, workspace scoping, bounded receipts, and persistence across
reconnects. - README/runtime truth-sync documentation cleanup.
What Changed
Reliability: Idempotent Writes + Receipts
- First write with
(workspace, idempotency_key)writes normally and stores a receipt. - Replay with same key + same payload returns prior receipt with
replayed=trueand does not duplicate objects/
events. - Same key + different payload is rejected deterministically with:
OB_INVALID_REQUESTreason_code=OB_IDEMPOTENCY_KEY_REUSE_MISMATCH
Additive Write Response Fields
POST /v1/write / openbrain.write now include additive receipt metadata (non-breaking):
replayedrequest_id(optional)accepted_countobject_ids(bounded)receipt_hash(optional)
Compatibility
v1.0.1is backward-compatible withv1.0.0clients.- No endpoint renames, no schema-breaking contract changes.
- Response additions are optional/additive only.
Upgrade Notes
- Apply latest migrations before running production writes.
- Recommended for webhook/event ingest users needing replay safety.
Known Follow-up
- Future-incompat warning from
sqlx-postgresremains tracked in follow-upIT13B / IT9C.2.