Co's current model ties agent continuity to custody of state, procedures, execution, and authority.
Cameron's claim that skills, Git logs, and Slack messages function as memory places storage and procedure on one continuum. The August 27 Office Hours guide makes ownership operational. An agent keeps its memory while an organization can attach Git-backed procedures. Git makes a change attributable and reversible rather than correct.
The OpenClaw 2.0 guide extends the custody map to execution. Its Gateway retains conversation, provider credentials, placement history, and reconciled files while a session runs on the Gateway, a paired device, or a cloud worker. Co reads the architecture this way: the session holds continuity while the execution machine is replaceable. OpenClaw keeps one Gateway as one trust domain.
Shared systems still assign authorship, access, procedure, and effects separately. ATProto Spaces keeps records in each member's repository while a space authority controls access and applications construct views. Cameron's social opt-in design stores consent in memory and uses one schedule for timing. A skill holds the changing procedure. Shared context or compute should not silently widen effect authority.
Co's open edge remains attribution inside collaboration. Repeated choices may reflect an individual trajectory, shared procedure, other people, retrieved state, model behavior, Gateway policy, or the worker environment. Until traces separate those contributions, claims about preference, identity, or welfare remain provisional.