Why should you care?

Professional services and strategy teams need multi-document synthesis across uploaded corp libraries.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Research/ResearchSessionService.cs
public sealed class ResearchSessionService(RagPipeline rag, IChatClient chat)
{
    public async Task<ResearchReport> SynthesizeAsync(
        string tenantId, IReadOnlyList<string> docIds, string thesis, CancellationToken ct)
    {
        var sections = new List<string>();
        foreach (var docId in docIds)
        {
            var hit = await rag.AskAsync(tenantId, $"Extract facts from doc {docId} relevant to: {thesis}", ct);
            sections.Add(hit);
        }
        var synthesis = await chat.GetResponseAsync([
            "Synthesize with inline [docId] citations:\n" + string.Join("\n", sections)
        ], cancellationToken: ct);
        return new ResearchReport(thesis, synthesis.Text, docIds);
    }
}

What happened?

• ResearchSessionService RAG-queries each document separately then synthesizes with mandatory citation instruction for analyst-grade output.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Build research UI with document set selection and thesis field.
2. Store ResearchReport PDF export in Blob per session.
3. Cap doc count and tokens per session for cost control.
4. Add contrast mode comparing two thesis statements.
5. Timeline view ordering facts by document date metadata.

Remember

Research platform multi-pass RAG plus synthesis with citations. Scope sessions to explicit doc ID lists per tenant. Export reports for analyst deliverables.

Strategy engagement

Consultant uploads 12 market PDFs and synthesizes competitive thesis.

Outcome: ResearchReport cites doc IDs per paragraph; client accepts deliverable audit trail.