v0.11.0 - Governed Procedure Memory

Agent Memory Bridge 0.11 makes procedure memory safer to use at task time.

Thesis

0.11.0 = governed procedure memory without expanding the public MCP surface.

The public MCP surface remains the same 10 tools. The change is inside task
memory assembly: procedure records now carry lifecycle and boundary fields, and
governed packets can prefer trustworthy procedures while suppressing stale,
replaced, or unsafe ones.

What Shipped

• procedure governance parsing for:
  • procedure_status
  • when_not_to_use
  • prerequisites
  • failure_mode
  • rollback_path
• governed task-memory packets:
  • prefer validated procedures
  • keep draft procedures eligible but lower priority
  • keep legacy no-status procedures eligible with warnings
  • suppress stale, replaced, and unsafe procedures
• recall_first(...) now treats calm procedure, checklist, and runbook
  queries as local-first task-memory triggers
• a reviewed procedure-governance benchmark slice

Evidence

Current release snapshot:

• pytest: 175 passed
• public MCP tools: 10
• procedure-governance benchmark:
  • case_count = 7
  • flat_case_pass_rate = 0.429
  • governed_case_pass_rate = 1.0
  • flat_blocked_procedure_leak_rate = 1.0
  • governed_blocked_procedure_leak_rate = 0.0
  • governed_governance_field_completeness = 1.0

Why It Matters

Procedure memory is useful only if stale or unsafe playbooks do not keep leaking
back into task context. This release keeps procedures auditable in the store while
making the selected task packet more conservative.

Honest Boundaries

0.11.0 does not mean:

• procedure execution
• automatic procedure learning from raw transcripts
• a scheduler or worker runtime
• a new MCP tool surface
• a claim that broad retrieval ranking improved

Next

The next step is not another hidden automation layer. The next useful pressure
point is better dogfood observability: measuring how task packets, procedure
governance, and coordination signals behave across real sessions.