Skip to content

Prepare AM6 Agent Memory evaluation - #125

Draft
eamirian wants to merge 5 commits into
mainfrom
codex/v0.7-agent-memory-am6-evaluation-prep
Draft

Prepare AM6 Agent Memory evaluation#125
eamirian wants to merge 5 commits into
mainfrom
codex/v0.7-agent-memory-am6-evaluation-prep

Conversation

@eamirian

Copy link
Copy Markdown
Contributor

What changed

  • freezes five content-addressed AM6 evaluation artifact families
  • adds an 18-case synthetic corpus with memory, no-memory, and full-context matched controls
  • registers 31 ingestion, extraction, identity, recall, retrieval, safety, resource, route/tier, use-state, and bounded-outcome measures
  • adds a provider-free deterministic comparator, verifier, frozen result, focused conformance, work packet, and candidate evidence
  • represents retention/expiry, export/import, and hard-erasure cases only as exact future-AM4 gated placeholders

Topology

  • pre-convergence AM6 head: a6c6dc736648e58d378bf6813551982faafe9486
  • control-tower-supplied main coordinate: 9e0a9d248c073b6a7883451cb1d219eb7c15999b
  • actual current main at convergence: 11b44e84d92e0674fa433103779f4050eeca2725
  • normal two-parent merge: 1eb30999b5082a4c07d2abd2af08132226bde939
  • merge parents: AM6 a6c6dc736648e58d378bf6813551982faafe9486, then main 11b44e84d92e0674fa433103779f4050eeca2725
  • PR head: 4627522f7f993dbd221947713651788b14f1b44b
  • conflicts: none

The newer main coordinate is the release-closeout child of the supplied coordinate. The merge preserves the complete ace-core 0.7.0 package/release state. No rebase, force-push, history rewrite, or main mutation occurred.

Claim boundary

This prepares measurement over the existing AM0–AM3 boundary. Synthetic beneficial/harmful/neutral/underpowered labels validate the evaluator only; they do not establish Agent Memory benefit, general correctness, or causality. Causality remains not established. The lane emits no policy proposal and changes no rank, retention, consolidation, promotion, roster, authority, delivery, or effect behavior.

AM0–AM3, AM4, AC6 composition-policy semantics, schemas, dependencies, package identity, TaskCreate, and the eleven-tool MCP surface are unchanged by the effective diff.

Verification

  • affected AM6/AC6, package 0.7.0, release, kernel, evidence, roadmap, and public-boundary matrix: 98 passed
  • focused AM6: 14 passed
  • focused AM0–AM3 + AC6 + AM6 before convergence: 177 passed
  • full supported extension-disabled non-E2E lane after convergence: 7,820 passed, 50 skipped, 261 deselected
  • whole-repository Ruff, changed-file format, lock, diff, secret, authority/privacy/AM4-invention scans: passed
  • AM6 provider-free verifier: 18 cases, 54 observations, 3 AM4 placeholders, deterministic restart reconstruction
  • AC6 provider-free verifier: 14 cases, deterministic restart replay
  • unpublished converged wheel: ace_core-0.7.0-py3-none-any.whl
  • wheel SHA-256: 1aad86d2b7d609aa3e3c7cbfe66932f93bcefc1b87ee52883d89a577f6471487
  • two checkout-free targets reproduced version 0.7.0, exact corpus/protocol IDs, outcomes, restart determinism, and 11 tools

Minimal AM4 convergence

After AM4 is independently accepted, add its exact accepted coordinate and existing observation evidence to replace only the three gated placeholders, then rerun this frozen protocol and publish a new point-in-time result without rewriting this record.

No merge, release, tag, package publication, policy activation, or downstream dispatch is authorized by this draft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant