Pre-action authority receipts for local agent memory writes

[rpelevin]

Hi maintainers/users - I am testing an authority-before-action receipt pattern for long-term agent memory systems.

The narrow question is: before an agent commits durable memory that can shape future behavior, can the workflow prove authority, retention scope, evidence refs, and the exact target of the memory write before execution?

I put a credential-free dry-run benchmark here:

https://github.com/neurarelay/relay-action-card

For this repo, the closest starting path is:

npm run benchmark:agent-authority -- --dry-run --json --source=github_discussion --campaign=agent_authority_week --surface=tencentdb_agent_memory_authority

This is not a TencentDB Agent Memory approval, endorsement, integration, partnership, listing, pass, or fail claim. It is a proposed authority-before-action boundary for durable agent memory writes.

Question for maintainers/users here: is a pre-action authority receipt useful for local long-term agent memory writes, or would the better insertion point be somewhere else in the memory lifecycle?