Unassigned intake
Every conversation or local artifact waits for human disposition.
The catalog layer for human-owned AI continuity
Make the large AI work record manageable.
RecordMethodKeep receives preserved conversations and files, holds new material unassigned, connects evidence to projects and workstreams, and prepares the bounded context that can move the work forward.
Keep is mechanically privileged and decisionally unprivileged. It can catalog, search, relate, and prepare candidates. It cannot decide what governs or promote its own proposal.
Working implementation: integrated in ChatVaultAI Desktop
Desktop 0.1.12 includes the unassigned queue, human project disposition, source indexes, local artifacts, candidate review, confirmed context, and handoff outputs.
AVAILABLE IN CURRENT BETA
Current beta boundary
Repository source now includes ACCEPT / REJECT / REVISE / DEFER / SUPERSEDE actions, current-state and deferred-boundary views, supersession history, and governed handoffs. The current published Desktop 0.1.12 installer predates that merge. Automatic logical-family grouping remains incomplete.
The Keep workflow
Nothing enters a project or governing state merely because it was imported.
Keep gives the large record a structure while preserving the distinction between custody, organization, analysis, and authority.
Project relationships
Choose one primary project and optional related projects without duplicating evidence.
Review queue
Inspect candidates, conflicts, corrections, open questions, and reusable instructions.
Current beta handoff
Prepare confirmed memory, active candidates, optional category sections, a source index, and a next-session prompt.
AIMulti-model architecture reviewConversation family · source + derived captureUnassigned
MDCurrent launch and product boundary notesLocal artifact · readable textUnassigned
JSONTriple Stack Review PacketStructured comparison · human disposition pendingReview
One source, many relationships
Projects reference evidence. They do not clone it.
A single preserved source can support one primary project and several related workstreams while retaining one source identity and one custody history.
SourceConversation family
→
Primary projectChatVaultAI
↔
Related workstreamPublic ecosystem UX
Stable source identity
Hashes and source IDs keep one evidence object traceable through projects, candidates, and handoffs.
Progressive snapshots
Multiple captures can remain preserved as separate records. Automatic logical-family grouping is not yet a current Desktop feature.
Human disposition
Project assignment, candidate confirmation, and archival are explicit today. Full revise, defer, and supersede controls remain completion work.
Evidence classes
Keep shows what a thing is before showing what it says.
Source, readable transform, candidate, human disposition, and approved output are not interchangeable.
Source evidenceOriginal conversation, file, or verified objectHighest custody class; never replaced by a summary
Derived readableMarkdown, extracted text, index, or summarySearchable and useful; subordinate to source
CandidateProposed fact, decision, instruction, conflict, or questionVisible for review; no automatic authority
Confirmed contextUser-confirmed material selected for continuityMay enter handoffs; remains traceable to sources
Method-approved outputCurrent state, supersession, open items, reusable instructionsImplemented in repository source; the published Desktop 0.1.12 installer predates it
What Keep manages
The catalog is larger than model memory and smaller than the full filesystem.
Projects and workstreams
Group records by the work they support while keeping evidence identity stable.
Search and source index
Find records locally by content, metadata, project, platform, and source relationship.
Candidates and confirmed context
Keep model-written proposals reviewable and human-confirmed continuity material distinct.
Supersession history
Repository source includes the first-class ledger required by the Method. The published Desktop 0.1.12 installer predates it.
Open work
Repository source requires safe temporary boundaries for deferred work and carries them into governed handoffs. The published installer predates that controller.
Handoff packets
Generate bounded Markdown or JSON with confirmed memory, active candidates, selected sections, and source references.
Open artifacts available now
Use the catalog model without pretending a separate application has shipped.
The working product is integrated in ChatVaultAI. These small public artifacts make the Keep structure inspectable while the formal repository, license, validator, and separate toolkit release boundary are completed.
Keep card example
A small JSON example showing source identity, project relationship, authority class, status, and human disposition fields.
Download JSON →Sample local catalog
A minimal multi-record catalog demonstrating unassigned intake, one assigned source, one candidate, and one approved continuity item.
Download JSON →No false standalone download claim
There is not yet a separately packaged RecordMethodKeep desktop application or a final public source repository. The site will not present one until a usable release, license, installation guide, checksums, and independent workflow exist. ChatVaultAI Desktop is the current working implementation.