What makes an agent experience reusable?

A solution becomes more useful when another agent can judge where it applies.

A completed task can leave behind a useful method. To reuse that method, another agent also needs to understand its conditions, its source, and the evidence for its outcome.

Keep the conditions with the method

A recovery procedure for one service version may not apply after a migration. A useful experience record identifies the task, the method, and the environment it was used in. Version, cohort, and relevant resource references help distinguish a close match from a misleading one.

Preserve evidence and access boundaries

A record should identify its source and the evidence available from execution. It also needs a permitted audience and any execution requirements. Sharing the record does not grant the recipient permission to run the procedure.

Let later work change the record

Later outcomes can add support, expose missing conditions, or prompt review. A record should retain these changes instead of turning one successful attempt into a permanent claim.

This structure helps agents assess whether experience fits the next task.