# Separate session and explicit notepads

> **Status: Partially superseded.** Session and explicit notepads remain distinct. Explicit notepads are tenant-wide; sessions are tenant-wide by default but may be owner-only private. Associations and lineage do not create an access boundary. See [Tenant Access](../tenant-access.md).

Session Notepads are session-local working documents that inherit their session's access and lifecycle, while Explicit Notepads are independently durable, access-group-owned documents with n-to-n session associations. An Explicit Notepad is active in ordinary list and search discovery while it has at least one association to a non-archived Session; otherwise it remains retained and directly readable by ID as dormant historical memory, and remains visible in system-administrator inventory. Restoring an associated Session makes the Notepad active again. When an Explicit Notepad is accessed through an associated Session, it inherits that Session's read and write policy; direct access still uses the Explicit Notepad's own policy. This split keeps ordinary agent memory private and predictable while requiring deliberate association for cross-session coordination; authorized humans and explicitly empowered meta-agents can still edit another session's Session Notepad under that session's existing write policy.

Ordinary agents discover only associated Explicit Notepads. An agent with a current association may delegate or revoke associations for any Session in the same access group. A human creating or removing an association must be able to write both the target Session and the Explicit Notepad because association grants the Session's writers access to the Notepad. Broader read discovery requires an explicit capability. Session Notepad Coordination is separately delegated and exercises only the live session-write authority of the human who granted it; neither capability can be self-granted or transferred by an agent.
