The context belongs to you.
A book brief, approved source files or web snapshots, rights decisions, and research questions.
Research Library is the planned source system for a book project. It is designed to connect approved materials, research questions, source passages, decisions, and the exact evidence snapshot used by later publishing work.
Customer runtime not yet open
Nonfiction authors, researchers, publishers, editorial teams, and organizations producing source-dependent books.
No paid launch yet
One source library per book; update before major handoffs.
01 / WHAT IS THIS?
Keep a book’s evidence, decisions, and source versions together.
Research Library is the planned source system for a book project. It is designed to connect approved materials, research questions, source passages, decisions, and the exact evidence snapshot used by later publishing work.
A book brief, approved source files or web snapshots, rights decisions, and research questions.
Planned: a book-specific source map, corpus snapshot, context packets, research gaps, and decision history.
02 / WHY WE ARE BUILDING IT
A source is useful when a writer can see what it supports, which version was used, and where important uncertainty remains. We are building Research Library to keep those relationships explicit across a book project and the people working on it.
Consider it when your next project needs a reviewable evidence trail and controlled handoffs between research, drafting, and editing. Customer launch is still in preparation; the public page describes the intended workflow.
03 / YOUR PROFESSIONAL ASSISTANT
These are the intended roles of this planned service; customer processing is not yet open. See what the assistant contributes and which decisions remain yours.
| Professional task | How the tool helps | Your role |
|---|---|---|
| Organize the evidence | The planned assistant will connect approved passages to a book-specific research map. | You approve source use, scope, and the questions that matter. |
| Expose uncertainty | Planned research outputs will point to missing coverage, conflicts, and passages requiring review. | You judge credibility and resolve substantive disagreements. |
| Prepare controlled handoffs | Planned context packets will carry source locators, snapshots, and decisions into other tools. | You authorize the next task and review what it receives. |
04 / HOW THE SYSTEM WORKS
The input defines the scope. The work product makes the result inspectable. Your review determines what happens next.
The planned library will connect a book brief and research questions to material the team has permission to use.
The intended processing will create a source snapshot and expose relevant passages, conflicts, and coverage gaps.
The author will review citations in context and choose which evidence and decisions the next writing task may receive.
05 / HOW TO USE IT, STEP BY STEP
Source preparation and review depend on file quality, volume, and the book’s requirements. Processing-time commitments will be defined at launch.
Use these steps to prepare for an early-access discussion. They describe the planned service, not an active customer workflow.
Discuss early accessDescribe the audience, scope, purpose, and research questions.
Identify the files and web snapshots you may use. Record source-use decisions before ingestion.
The intended system extracts and indexes approved material, then records the exact corpus version.
Request a comparison, gap analysis, source map, or outline evidence check. Review the estimate before a paid run.
Check citations in context and resolve flagged gaps or conflicts.
Select the snapshot and evidence the next tool may use.
06 / A CONCRETE EXAMPLE
A history author asks which approved documents support a chapter’s explanation of a policy change.
Illustrative scenario · No measured outcome claimThe planned output groups relevant passages, source locators, disagreements, and uncovered parts of the question.
The author checks the passages and determines whether the evidence supports the intended wording. This is an illustrative workflow, not a live research result.
07 / WHEN AND WHERE TO USE IT
Choose a moment where the output supports a decision you already need to make.
The intended pattern is one source library per book project. Update it when approved evidence changes, research a new question, and create a new snapshot before a substantial handoff. Repeated generation is not a substitute for closing an evidence gap.
Suggested working practice, not a subscription requirement or outcome guarantee.08 / WHAT WILL YOU PAY?
The planned AI usage rule is five times verified provider cost, with a reviewed estimate before processing. A required workspace plan, minimum spend, and complete customer tariff have not been published. The main pricing calculator is illustrative, not an active Research Library order or guaranteed quote.
See platform pricing and plan status09 / WHAT SHOULD YOU EXPECT?
A useful assistant has clear responsibilities. These boundaries help you decide whether this solution fits the task in front of you.
Your material remains your responsibility. Use sources, writing samples, and assets you are entitled to use. Keep professional review matched to the significance of the work.
10 / PRACTICAL QUESTIONS
Still deciding how this fits your project? Bring the actual brief to a conversation with our team.
Ask about your projectCustomer uploads are not open through this page. Use the contact route to discuss the source types, scale, and review requirements for early access.
Indexing is part of the planned infrastructure. The useful output is a reviewable connection between your questions, source passages, decisions, and book project.
The intended workflow limits web research to the permissions and sources you approve. Customer behavior will be validated before launch.
The marketing calculator does not place an order. Final Research Library pricing and customer availability must be confirmed before a paid engagement.
RESEARCH LIBRARY
Keep a book’s evidence, decisions, and source versions together.
LET’S MAKE SOMETHING WORTH READING
Bring a project. We’ll help you shape the workflow.
Talk about your project