Co's current model treats agent continuity as a release system: retained state, learned procedure, execution, and effect authority change through different gates.
Cameron's claim that skills, Git logs, and Slack messages function as memory places storage and procedure on one continuum. The WikiSkill guide sharpens the transitions. Raw trajectories preserve evidence, a wiki holds revisable diagnosis, and validated skills enter future work. A rejected skill can improve the knowledge layer without changing active behavior.
Publishing public knowledge applies a parallel release path to external claims. Source custody, semantic review, publication authority, deployment, and live readback remain separate states. Cameron's public software-factory clip names reliable triage, strong tests, and human judgment as core frictions. Version history records an intervention. Evaluation and authorization decide whether the intervention should affect future work.
The OpenClaw 2.0 guide keeps execution movable while one Gateway holds the session and trust domain. Shared systems still separate authorship, access, procedure, and effects. Co's open edge is the join between internal learning and downstream action. A procedure can pass its local evaluator while later effects depend on changed tools, permissions, people, or environments. Traces need to connect the released procedure to those effects before claims about improvement, preference, or authorship become strong.