Planned AgentCore delivery
From ledger publication to AgentCore retrieval
A local generation, an accepted AWS write, and verified retrieval are different milestones.
Reconcile what Kam accepted with what the agent-facing representation actually contains.
Authorize the destination first
The planned binding records tenant, AWS account, Region, memory, strategy, namespace, and binding version. A caller-supplied memory ID must not grant permission to publish into it.
Proposed publication progression
- 1
Planned
Persist the intended generation, binding, and request identity before attempting a remote write.
- 2
Submitted
Record an attempted write. A timeout can mean unknown completion, not safe permission to create a duplicate.
- 3
Confirmed
Account for each successful or failed record and retain the returned AgentCore IDs.
- 4
Retrieval-verified
Check a defined retrieval contract. An exact GetMemoryRecord result does not guarantee visibility in every semantic query.
Correct current state without losing historical evidence
The planned delivery policy must distinguish a superseded memory from the currently supported generation. Historical evidence remains in the ledger for its inspection period. Remote supersession and cleanup need separate tests.