Personal session library — v0.2 (save, resume, acquire, publish)

Status: descriptive. It describes release/0.545.0. The code is in collector/routes/memory.py (the /library/* content routes) and collector/routes/tenants.py (/library/sessions, /library/ensure, publish targets, profiles). Gaps are listed under §7 *Open*.

Every signed-in person has a private library for their agent sessions: raw transcripts, scrubbed of secrets, that can be resumed later. The library belongs to your account, not to a web address. It is a free, private personal tenant created on first use (tenants.py:resolve_or_create_personal_tenant: plan=personal, no hostname, never sold, never expires). Everything in it is staged and private. Nothing in the library is ever published unless you publish it explicitly (§5).

All /library/* content routes require a signed-in human (401 otherwise). They are scoped to the caller's own library, so you can only ever read or write your own entries.

Re-staging carries the entry's parent, acquired_from, compact_version, tokens and summary forward (_LIB_CARRY), so an edit never cuts the entry out of its lineage.

Every saved version is a git tag in the memory projection whose commit date is the publish event's timestamp, i.e. the push time (rebuild-stable: a JSONL replay re-derives the same date). The list reads every tag's date in ONE git for-each-ref --format='%(refname) %(creatordate:iso-strict)' over the tag namespace (MemoryProjection.tag_dates) — never a git log per row.

1. What it is

2. Saving and reading

3. Acquiring a marketplace item — POST /library/acquire/{cid} (library_acquire)

4. Refunds end the licence (WP-13a) — _refuse_revoked_copy

5. Publishing to the marketplace — POST /library/session/{cid}/publish-to/{tenant} (library_publish_to)

6. Retention

7. Open