Send feedback
Email feedback@agentsessionrecord.org. Quote requirement IDs (for example ASR-200) when a comment is about a specific rule. Feedback is especially useful when it comes from implementation experience:- Harness authors: does the agent identity registry describe your IDs correctly? Does a conversion of your logs lose something you consider essential? What would make it practical for your harness to write ASR natively?
- Assistant and app teams: do participants, conversations, triggers and deliveries describe your sessions the way your product means them? Which facts end up only in vendor keys in the registry, and should any of them be standard?
- Tool builders: is a rule ambiguous, or impossible to implement from the text alone? Could you compute the active path and context view from the specification?
- Evaluation and training teams: does a stream carry what you need, and do the export rules in the ATIF companion match how you use ATIF?
- Agent Client Protocol (ACP) implementers: is the recorder mapping correct for your agent or client?
- Security and privacy reviewers: does Privacy and security cover the ways a record can leak, including the identities of people in group chats?
Propose a change
Typos, broken links and unclear wording can be sent by email as they are. Substantive changes to the format go through a Request for Dialog; see Governance.Contribute fixtures
The golden corpus needs real sessions from many harnesses, and it must never contain private data.- Submit only sessions you have the right to share.
- Never submit raw native logs. Sessions routinely contain source code, credentials, file paths and personal information.
- Redact first, record the redaction policy you used, and review the result by hand. Conformance does not make a file safe to share.
- Synthetic sessions that reproduce a real harness’s structure are welcome, and are often the better choice.