Vector Conflict Check

When to run

• After bulk edits to ground-truth or CRM.
• Periodically (weekly) when running on Pinecone.
• Before relying on semantic-recall for high-stakes calls (offer comparisons, pivot decisions).

Procedure

1. Resolve config + guard

${CAREER_DATA_DIR}/config.json → WORKING_FOLDER, CONTEXT_STORE, PINECONE_INDEX. Bail if CONTEXT_STORE != pinecone.

2. Pull index inventory

Use the Pinecone MCP to enumerate vector IDs + metadata for the configured index. Each vector should carry metadata: source_path, content_hash, embedded_at, namespace (set by pinecone-sync).

If metadata is missing on a meaningful fraction of vectors, bail with: "index lacks source-path metadata — run /career:pinecone-sync --reindex first."