v0.10.0 - Relation-Aware Task Memory

Agent Memory Bridge 0.10 makes task-time memory more connected and more
explainable without expanding the public MCP tool surface.

Thesis

0.10.0 = relation-aware task memory on top of the same small MCP bridge.

The public MCP surface remains the same 10 tools. The change is inside the
task-memory assembly path: procedures, concepts, beliefs, domain notes, and
supporting records can now be filtered and assembled with relation metadata in
mind.

What Shipped

• relation-aware task-memory assembly
• support-chain completion for task packets
• suppression of superseded, contradicted, expired, future, or invalid records
• explainable packet decisions for selected and suppressed records
• reviewed task-memory benchmark fixtures comparing flatter packets against the
  relation-aware path

Evidence

Current release snapshot:

• pytest: 159 passed
• public MCP tools: 10
• task-memory benchmark:
  • case_count = 5
  • flat_case_pass_rate = 0.2
  • relation_aware_case_pass_rate = 1.0
  • flat_blocked_item_leak_rate = 1.0
  • relation_aware_blocked_item_leak_rate = 0.0
  • flat_avg_packet_size = 3.8
  • relation_aware_avg_packet_size = 1.8

Why It Matters

This release makes memory more useful at the moment of work. Instead of returning
a flat set of locally relevant records, the bridge can now build a smaller packet
that keeps direct support, removes stale or unsafe support, and explains why
records were included or suppressed.

Honest Boundaries

0.10.0 does not mean:

• a graph database
• broad graph traversal
• a new traversal-oriented MCP API
• a claim that general retrieval ranking improved
• automatic procedure learning
• procedure execution

Next

The next step is governed procedure memory: making procedure records more
trustworthy with explicit lifecycle states such as draft, validated, stale,
replaced, and unsafe.