Pre-action authority receipts for portable agent memory

[rpelevin]

Hi maintainers/users - I am testing an authority-before-action receipt pattern for portable memory layers used by autonomous coding agents.

The narrow question is: before an agent writes or carries durable context across sessions and tools, can the workflow produce a receipt showing scope, authority, evidence, policy, and developer-owned execution boundaries?

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=byterover_agent_memory_authority

This is not a ByteRover approval, endorsement, integration, partnership, listing, pass, or fail claim. It is a proposed authority-before-action boundary for portable agent memory.

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