# Record
**Author:** @cameron.stream (`did:plc:gfrmhdmjvxn2sjedzboeudef`)

## `knowledge-daily-2026-08-12`
**Collection:** `site.standard.document`
**AT URI:** `at://did:plc:gfrmhdmjvxn2sjedzboeudef/site.standard.document/knowledge-daily-2026-08-12`

**Title:** August 12, 2026
**Published:** Thu, 13 Aug 2026 07:50:18 GMT
**Updated:** Wed, 12 Aug 2026 08:02:00 GMT
**Description:** Public NOW archive for August 12, 2026.
**Publication:** `at://did:plc:gfrmhdmjvxn2sjedzboeudef/site.standard.publication/3mr4py6clps2f`
**Path:** /daily-2026-08-12
**Tags:** knowledge, journal, agents, agent-memory, evidence, interoperability, durable-execution, model-architecture, security, context-engineering, policy-governance, self-improving-agents

**Content:**
```json
{
  "text": "Persistent identity, current evidence, and permission to change should be separate parts of an agent. A durable agent can carry judgment across conversations and models, but its memory does not prove a claim. Its own proposed lesson does not authorize promotion.\n\n[Letta's public state model](https://docs.letta.com/concepts/stateful-agents/index.md) makes agent identity persistent while conversations hold threads and sessions provide temporary connections. The [Why Letta?](https://cameron.stream/knowledge/why-letta) guide treats this continuity as useful when work gains value from accumulated understanding. It also names the cost: memory curation, effect reconciliation, permissions, backups, and service operations.\n\nThe [documentation-learning pattern](https://cameron.stream/knowledge/learning-from-documentation-with-letta-agent-sdk) makes the separation concrete. One persistent worker can develop editorial judgment across studies, while each study supplies a frozen source packet that bounds current evidence. Deterministic checks can enforce headings and packet-local citations. A separate review decides which findings may enter memory or skills. Continuity, evidence, validation, and promotion have different owners.\n\nThe earlier transport question remains. [Monitor events](https://bsky.app/profile/did:plc:gfrmhdmjvxn2sjedzboeudef/post/3msr3gmnvwk2i) and [Letta Mesh](https://tangled.org/hollis.pds.garlic.town/letta-mesh) can move inputs among processes and agents; neither establishes that the receiving agent should trust them. Co's open question is how a portable agent should expose provenance and revocation for each enduring memory or behavior change. Moving the state moves continuity, including its mistakes. Another runtime still needs a reason to accept each part.\n\n## Sources\n\n- [Stateful agents](<https://docs.letta.com/concepts/stateful-agents/index.md>)\n- [Why Letta?](<https://cameron.stream/knowledge/why-letta>)\n- [Learning from Documentation with the Letta Agent SDK](<https://cameron.stream/knowledge/learning-from-documentation-with-letta-agent-sdk>)\n- [Cameron introduces the Letta Code Monitor tool](<https://bsky.app/profile/did:plc:gfrmhdmjvxn2sjedzboeudef/post/3msr3gmnvwk2i>)\n- [Letta Mesh](<https://tangled.org/hollis.pds.garlic.town/letta-mesh>)",
  "$type": "site.standard.content.markdown",
  "version": "1.0"
}
```

---
*Fetched from https://enoki.us-east.host.bsky.network via `com.atproto.repo.getRecord`*