← Market Analyst · c7

PICKUP.md

c7 Pickup Note

Contents
  1. Where every thread stands
  2. The decision queue
  3. Suggested first hour at pickup
  4. Quick orientation

Parked: 2026-08-20 — Phase 1 (data exploration) and Phase 2 (analysis) complete with findings documented. Phase 3 (integration implementation) was deferred in March 2026. Note: c8.agent-pivot will handle re-extraction with new vocabularies and may integrate Avoma notes as supplementary context, reducing the scope of c7's implementation plan. Pickup is blocked on c8's prioritization of extraction work.

Where every thread stands

ThreadState
Data exploration (Phase 1)✅ Completed — 7 sample calls fetched with notes; structure analysis in findings.md
Comparative analysis (Phase 2)✅ Completed — 5-call side-by-side comparison; strengths/weaknesses cataloged in comparison.md
Integration planning (Phase 3 prep)✅ Completed — 4 integration strategies designed in integration-plan.md; steps 1-6 ordered by dependency
Schema additions❌ Not started — ActionItem, DecisionMaking, Risk interfaces not added to schemas/call.ts
Extraction prompt updates❌ Not started — decisionMaking, risks guidelines not added to pipeline/prompts/extract-call.md
Notes fetching script✅ Completed — fetch-sample-notes.ts exists; fetch logic ready to integrate into avoma.ts
Batch re-extraction❌ Not started — npm run extract:batch -- --force never run with integrated notes

Key artifacts in cycle:

  • findings.md — Note structure (7 samples), consistency matrix, data quality observations
  • comparison.md — 5-call side-by-side comparison (Claude extraction vs. Avoma notes quality)
  • integration-plan.md — 4 integration strategies (actionItems, decisionMaking, risks, notes as context) with step-by-step implementation
  • fetch-sample-notes.ts — Reusable script for fetching and formatting Avoma notes

The decision queue

Unlocking decisions:

  1. Will c8 integrate Avoma notes? — c8.agent-pivot may handle re-extraction with notes as supplementary context (matches Integration Strategy #4 in c7's plan). If so, much of c7's work is subsumed. Action: Clarify with c8 owner whether notes-as-context will be included in c8's extraction redesign.
  2. If c8 does NOT integrate notes: c7's implementation plan is ready to execute. Steps 1-6 are ordered; cost is ~$0.90 for batch re-extraction.

Canon/detail decisions (if c7 proceeds independently):

  • ActionItems parsing: do it at index time (build-index.ts) or via standalone enrich script? (Plan favors index time.)
  • RiskCategory taxonomy: Is the 5-category list complete (technical-compatibility, deployment-blocker, organizational, security-privacy, resource-constraints)? Or add others?
  • Notes sidecar format: Standardize on data/raw/{uuid}.notes.json for all calls (plan assumes this).

Suggested first hour at pickup

  1. Read integration-plan.md Section 1-3 (Strategy overview + 3 additions) — 5 min
  2. Check with c8 owner: Will Avoma notes be integrated into c8's re-extraction? — 10 min
  3. If c8 includes notes: Coordinate to ensure c7's fetch-sample-notes.ts + integration insights are reused; close c7 in favor of c8's extraction work. — 5 min
  4. If c8 does NOT include notes: Proceed with c7 implementation:
    • Step 1: Add schema interfaces (ActionItem, DecisionMaking, Risk) to schemas/call.ts — 10 min
    • Step 2: Update extract-call.md prompt with decisionMaking + risks guidelines — 10 min
    • Step 3: Integrate notes-fetching into avoma.ts (reuse fetch-sample-notes.ts logic) — 10 min
    • Then run batch re-extraction (~2 hours wall clock)

Quick orientation

  • Code readiness: All analysis done; implementation plan written; no code changes yet. fetch-sample-notes.ts is a utility script (not integrated into pipeline).
  • Data readiness: 22 calls have notes sidecars at data/raw/{uuid}.notes.json (fetched via Avoma API in c6.sagetap-integration). Future npm run fetch saves notes automatically.
  • Key paths: schemas/call.ts (where to add ActionItem, DecisionMaking, Risk), pipeline/prompts/extract-call.md (where to add decisionMaking + risks output schema), pipeline/extract.ts + pipeline/batch.ts (where to inject notes context), pipeline/build-index.ts (where to parse actionItems from notes)
  • Uncommitted work: Three docs (findings.md, comparison.md, integration-plan.md) + fetch-sample-notes.ts utility — all committed
  • Cost if re-extracting: ~$0.90 for 22 calls via batch API
  • Blocking: c8's decision on notes integration. If c8 includes Avoma notes in its extraction, c7's implementation is largely subsumed.

Qpoint Brand Style Guide