Prompt Engineering
Split Transcripts for AI — Meetings in Order, Decisions at the End

Hours of meetings exceed any message limit. Split transcripts at speaker-turn boundaries, deliver in order, and extract decisions only after every meeting has arrived.
Overview

Transcripts are deceptively large and structurally fragile: a decision's context lives in the turns before it, and a blind split severs exactly that. The package splits transcripts at paragraph and turn boundaries, keeps the meetings in chronological order, and holds the extraction task until the final chunk — because "every decision, owner, and open question" can only be answered across ALL the meetings, not per fragment. This setup loads a multi-meeting transcript in Analysis mode with exactly that extraction task waiting at the end.
Workflow

Split at speaker turns
Turn boundaries are paragraph boundaries — context stays attached to its discussion.
Keep chronology
Meetings arrive in order; cross-meeting threads stay followable.
Extract across everything
The final-chunk task spans all meetings — decisions reversed in week three stay reversed.
Why This Works

Turn-aligned splits preserve the context decisions depend on
Chronological delivery keeps multi-meeting threads intact
End-triggered extraction sees reversals and follow-ups blind fragments miss
Best for

Teams mining recurring meetings for decisions
Interview and research-call transcript analysis
Anyone whose transcript answers missed later meetings
Not for

Summarizing one meeting for humans — that's the Structured Summary Prompt's meeting mode
Continuing a chat about the meetings in a new session — that's the Context Handoff Builder
Use cases

Processing weeks of meeting transcripts at once
Keeping decisions attached to their discussion context
Extracting owners and open questions across meetings
Customize This Resource

Opens this scenario in Long Prompt Splitter. Split to get the full chunked package — then adjust the chunk size and delivery mode.
Open in Long Prompt Splitter
Prompt Template

CHUNKED CONTEXT PACKAGE

DELIVERY INSTRUCTIONS
- Send each chunk below as ONE message, in order, starting with Chunk 1.
- Wait for the model's acknowledgement ("Received chunk i of 2") before sending the next chunk.
- Do not edit the chunk contents — the markers and the content are designed to travel together.

CHUNK STRATEGY
- Content: 26,398 characters, ~6,000–7,333 tokens (Prose).
- Target model: Claude Opus (200,000-token window; verified June 2026).
- Chunk budget: ~4,000 tokens (14,400 characters max per chunk) → 2 chunks.
- Delivery mode: Analysis Mode — Analysis mode — reading rules up front, the full analysis task triggered by the final chunk.
- Boundary quality: 0 section breaks, 1 paragraph break, 0 line-level breaks, 0 hard cuts.

===== CHUNK 1 of 2 =====
- This content arrives in 2 parts for a full analysis at the end. The parts form ONE continuous document, in order.
- Do not begin the analysis until the final part says all chunks are delivered.
- After reading, reply ONLY: "Received chunk 1 of 2." Then wait for the next chunk.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.


----- END OF CHUNK 1 of 2 — do not respond yet; chunk 2 follows -----

===== CHUNK 2 of 2 =====
- Chunk 2 of 2 — part of the same continuous content. The earlier rules still apply.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

[14:02] Lena: The renewal numbers split sharply by cohort — accounts onboarded with a partner renew eleven points lower, and exit interviews keep naming expectation mismatches set during the sales handoff.
[14:04] Marco: Then the fix is upstream of the product. If we rewrite the partner enablement deck and gate certification on it, the mismatch should close within two quarters.
[14:06] Aiyana: Agreed, but we should still ship the in-app expectations checklist — it protects direct accounts too, and it gives us a measurable baseline either way.

===== ALL 2 CHUNKS DELIVERED =====
- All 2 chunks are delivered. Begin the full analysis now, drawing on EVERY chunk — not just this one.
- When you cite evidence, say which chunk it came from.

TASK
Extract every decision, owner, and open question across all meetings.

NOTE
- Chunk budgets use character-based token estimates, not tokenizer output; model windows verified June 2026.
Related Resources

Explore more resources that work well with this one.