Wrap-up — session archiver

The "hard drive" half of the Karpathy + Pinecone architecture (see vault [[Memory Architecture]] and [[CLAUDE]] rule §5). Every substantial conversation gets a one-shot summary vectorized into Pinecone so future sessions can recall it semantically.

When to trigger

User invokes manually: /wrap-up [optional title] → execute immediately.

Auto-propose (you ASK the user, never execute silently): when ≥2 of these signals fire in the current session:

• 3+ files created or significantly modified
• A new decision-type note appeared in 50 — Decisions & Bets/
• User said "looks good", "approved", "ship it", "done", "let's continue", or similar milestone acknowledgment
• An architecture / CLAUDE.md change was made
• ≥30 minutes of active work since the last wrap-up
• User explicitly asked for a summary, status, or TLDR

Propose like this (don't be verbose):

Looks like we just wrapped a substantial chunk — {1-line description}. Want me to /wrap-up so it's archived to Pinecone? (Or keep going — your call.)

If the user says yes → execute. If no → continue, don't re-ask for ~15 minutes.

What it does (execution steps)

1. Generate a structured summary in this exact shape (markdown):

   # {Title} — {YYYY-MM-DD}

   ## What changed
   - Files: {bulleted list of paths created or modified, with vault-relative paths}

   ## Decisions made
   - {Decision} → {Rationale}

   ## Hypotheses moved
   - 🟢 confirmed: {hypothesis} — {evidence}
   - 🔴 disconfirmed: {hypothesis} — {evidence}
   - 🟡 ambiguous: {hypothesis} — {gap}

   ## Open follow-ups
   - {Items carried forward}

   ## Key user quotes (intent signal)
   > "{verbatim quote}"

Keep total summary 200-500 words. This is a recall handle, not a transcript.

1. Construct the Pinecone record:

• id: convo-{YYYY-MM-DD}-{kebab-case-title} (e.g. convo-2026-05-23-pinecone-architecture-setup)
• text: the full markdown summary above (this is what gets embedded — the fieldMap.text field of the jove-memory index)
• date: ISO YYYY-MM-DD
• project: short tag (default jove-labs; override if session was about a different domain)
• files_touched: array of vault-relative paths
• decision_count: integer
• tags: array of relevant tags (e.g. ["architecture", "pinecone", "wrap-up"])

1. Upsert via Pinecone MCP:

   mcp__pinecone__upsert-records:
     name: jove-memory
     namespace: conversations
     records:
       - id: {id}
         text: {summary}
         date: {date}
         project: {project}
         files_touched: {array}
         decision_count: {N}
         tags: {array}

1. Write the summary to the project's wrap-ups folder (corrected 11 Aug 2026: the old 99 — Meta/log.md path was the pre-migration vault layout and exists on no current machine, so this step silently no-opped for every project):

• JoVE work → ~/dev/jove-hq/knowledge/copilot/wrap-ups/{id}.md, the convention in use since 6 Aug 2026. Frontmatter: type: wrap-up, status: archived, date, project, files_touched. Use the Write tool so the reindex hook can fire, and if the session is not rooted at jove-hq run node tools/vault-index/ingest.mjs --file knowledge/copilot/wrap-ups/{id}.md yourself, because the hook only loads there.
• Other projects (invest, connecting-dots, mentors): Pinecone is the record; add a file only if that project has its own wrap-ups convention. Do not invent one.

1. Confirm to user in one line:

Archived as {id}. Recall later by asking "do you remember when we…" or "what did we decide about…".

Companion behavior — recall before generating

When the user says "do you remember when we discussed…" / "what did we decide about…" / "have we talked about…" — before answering from session memory:

1. Search the conversations namespace:

   mcp__pinecone__search-records:
     name: jove-memory
     namespace: conversations
     query:
       inputs: { text: {user's question} }
       topK: 5

1. If a record scores ≥0.75 similarity, cite the record id in your answer: "Per {id} on {date}, we decided…"
2. If no record scores well, say so explicitly: "I don't see a wrap-up matching that. Either it wasn't archived, or it was before we set up Pinecone."

Pre-Pinecone-index fallback

If mcp__pinecone__list-indexes doesn't show jove-memory (e.g. running before the index is created):

1. Write the summary to the same wrap-ups folder as step 4 (~/dev/jove-hq/knowledge/copilot/wrap-ups/{id}.md for JoVE work) with frontmatter:

   ---
   type: wrap-up
   status: pending_pinecone
   date: {YYYY-MM-DD}
   project: {project}
   files_touched: {array}
   ---

1. Once jove-memory exists, batch-upload all pending_pinecone: true files in one pass and flip the frontmatter to status: archived.

What NOT to wrap up

• Single-question Q&A with no artifacts produced
• "What's the state of X?" status pings
• Skill discussions that didn't change vault state
• Conversations under ~10 minutes that produced nothing concrete
• Routine vault edits (rename a note, fix a typo)

Anti-patterns

• ❌ Don't auto-execute. Always propose first.
• ❌ Don't store the full transcript — only the structured summary. Pinecone is semantic recall, not blob storage.
• ❌ Don't propose more than once per ~15-minute window if user declined.
• ❌ Don't include personally identifying info beyond what the user has already put in vault notes.
• ❌ Don't generate a wrap-up that's just "we talked about X" — it needs the decisions / file / hypothesis structure to be useful.

ADDENDUM (15 Aug 2026, superseding the same day): Pinecone REINSTATED

Pinecone was retired on the morning of 15 Aug 2026 and reinstated the same day with a fresh API key. The retirement was a dead quota misread as a lost capability: jove-memory held all 8,865 vectors throughout. Claim C-pinecone-retired is retracted. Semantic recall and archival upserts work normally again; treat any older note in this file that says otherwise as superseded by this line.