the fork point, and then they can explore different strategies. Multiplayer is another property. Sharing an agent with someone should not mean having to copy some transcript and paste it into Slack. If the log is the agent, sharing means you simply grant access to that history, so that somebody else can view it and edit it. A teammate can open the session, they can see what happened, a manager can observe without taking over, and even another agent could consume the same session as context. This is really important because it means that the value is not just what the agent produced, it's also the log, which indicates how it got there. Migration follows the same pattern. If an agent's identity is trapped in provider-specific threads and memories and formats and runtime assumptions, moving providers becomes really painful. But if the log is the agent, migration is just a adapter problem. Different models may want different projections of the log, and different runtimes may need different schemas, but those are all become just engineering problems. They're not identity problems. The agent should then be able to start on Claude, continue on GPT, and finish on Gwen without losing itself. The log serves as a source of continuity.