docs: Call non-archived conversations live - #938
Merged
Merged
Conversation
JeanMertz
force-pushed
the
grep-current2
branch
from
August 4, 2026 17:31
194ee82 to
5282388
Compare
`active` carried three meanings. `jp_workspace` and the `jp c use` output use it for the one conversation a session is working on; `jp_storage` used it for the non-archived partition; `jp c ls` did both in one file, marking the session's conversation in its output while `--archived`'s help called non-archived conversations active. The session sense keeps the word, since that is the one users read in `jp c use`'s output and in the archive confirmation prompt. The partition becomes `live`, so `jp c ls --archived` now reads "Show archived conversations instead of live ones". Leaving the pole unnamed was the other candidate, and it works while archive is a boolean. It stops working once location gains a third value: "not archived and not trashed and not whatever comes next" is not something you can say in a doc comment or to a colleague. `indexed` is accurate today but names a storage strategy rather than a state, and would go wrong the moment a conversation is indexed yet hidden from the default listing. Active, Live, and Archived Conversation are defined in the conversation cluster glossary, which also separates location (live, archived) from flags (pinned) so the two axes don't merge again. Signed-off-by: Jean Mertz <git@jeanmertz.com>
JeanMertz
force-pushed
the
grep-current2
branch
from
August 4, 2026 17:34
768a9fb to
1424297
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
activecarried three meanings.jp_workspaceand thejp c useoutput use it for the one conversation a session is working on;jp_storageused it for the non-archived partition;jp c lsdid both in one file, marking the session's conversation in its output while--archived's help called non-archived conversations active.The session sense keeps the word, since that is the one users read in
jp c use's output and in the archive confirmation prompt. The partition becomeslive, sojp c ls --archivednow reads "Show archived conversations instead of live ones".Leaving the pole unnamed was the other candidate, and it works while archive is a boolean. It stops working once location gains a third value: "not archived and not trashed and not whatever comes next" is not something you can say in a doc comment or to a colleague.
indexedis accurate today but names a storage strategy rather than a state, and would go wrong the moment a conversation is indexed yet hidden from the default listing.Active, Live, and Archived Conversation are defined in the conversation cluster glossary, which also separates location (live, archived) from flags (pinned) so the two axes don't merge again.