effectfence 0.1.3

Causal concurrency fence for multi-agent tool calls: an intent ledger, OCC read-sets, and atomic CAS domain reservation stop double-execution — same-instant races and late duplicate retries alike. Ships as a library and an MCP server.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

# Changelog

All notable changes to EffectFence.

## [0.1.1] — 2026-08-04

### Fixed
- **Precision: retired the "lock-free" claim.** The race *decision* is a
  single atomic `compare_exchange`, but the counter lookup sits behind a
  short mutex — so "lock-free" overstated the hot path. Docs, README,
  crate description, and comments now say exactly what the code does.
  For a correctness library, wording is part of the API.

## [Unreleased]
### Added
- **Wrap mode** (`effectfence wrap -- <command>`): stands in front of ANY
  MCP server and fences every tool call automatically — tool list mirrored
  1:1, intents derived from canonicalized `hash(tool + args)`, identical
  duplicates replayed at the proxy without reaching the child, tool-level
  errors and child failures free the intent for retry (fail-safe).
  Proven end-to-end wrapping the Python `once-mcp` server. Ships in v0.2.
- Roadmap: distributed backend exploration · CI integration test for wrap

## [0.1.0] — 2026-08-04

First public release.

### Added
- **Intent ledger** — attempts sharing an intent are the same logical action:
  one executes, later duplicates replay the recorded certificate; failed or
  unknown outcomes stay fenced until explicitly reconciled (`clear_intent`).
  Crashed holders lose their lease after a TTL.
- **CAS domain fencing** — same-instant races decided by a single
  `compare_exchange`; exactly one winner per expected sequence.
- **Content-addressed EffectCerts** — SHA-256-sealed records of every
  committed effect with causal `parent` chaining and per-agent vector clocks.
- **MCP stdio server** — `fence_prepare` / `fence_commit` / `fence_abort`
  tools for MCP-compatible agents; schemas auto-generated from Rust types.
- **Storm demo** (`cargo run --release --example storm`) — 1,000-attempt
  attack proving exactly-one execution; also enforced in CI on every commit.
- 19 tests: unit + forced-race chaos + live JSON-RPC wire test. CI: test
  matrix, no-default-features build, clippy `-D warnings`, rustfmt, storm gate.

### Honest scope
In-memory, single-process, advisory (fences calls routed through it).
The distributed, unbypassable gateway is roadmap, not fine print.