Guides
How to scope your first corpus
The first corpus determines whether the trial produces useful evidence. Choose a team or function boundary that is painful, repeated, source-backed, and reviewable.
You should leave with one corpus candidate and a clear reason it is worth processing first.
Use this filter
- It contains recurring work where better guidance would matter.
- The process is spread across several source files or people's memory.
- There is a reviewer with authority to approve or reject the output.
- The team would use a good SOP, decision tree, macro, or gap report this week.
- The corpus boundary can be described in one sentence.
Good first corpora
- Support refund and replacement escalation artifacts.
- Onboarding handoff notes, records, and transcripts.
- Billing dispute tickets, policy notes, and macros.
- Account access helpdesk corpus.
- Implementation blocker records.
- Bug-report triage examples.
- Escalation path threads.
Avoid these first
- Whole-company knowledge cleanup.
- Generic document search.
- A process with no source material.
- A politically sensitive policy area with no reviewer commitment.
- A request for autonomous decisions or workflow execution.
Read next
Prepare source filesGather relevant files, tickets, notes, transcripts, exports, or pasted excerpts from one bounded team corpus before uploading them into Company Brain.Support ticket SOPsTurn recurring support tickets into reviewed SOPs, decision rules, gaps, conflicts, and reusable support drafts.