AI Knowledgebase

The AI Knowledgebase works at two layers that stack together:

• Project level — configured from a project's AI-KB page: preferred terms, banned terms, style notes, business-rules text, general guidance, and uploaded documents. Applies to every DRP in that project.
• DRP level — an AI-KB tab inside each individual DRP for uploading DRP-specific reference material. Layers on top of whatever is already configured at the project level.

A project's AI Knowledgebase page has five fields that shape how the AI writes for that project:

• Preferred Terms — the vocabulary you want the AI to use (e.g. "Planholder, Quote, Coverage").
• Banned Terms — terms the AI should avoid, optionally with the preferred replacement (e.g. "Policyholder, Contract (use Planholder and Agreement instead)").
• Style Notes — writing-style guidance, such as "use active voice, avoid jargon, write for non-technical stakeholders".
• Business Rules — key business rules the AI should be aware of when drafting requirements.
• Additional Guidance — any other context or instructions you want the AI to take into account.

Reference Data terminology is also applied automatically on top of this — aliases you've set up there are normalised to their canonical term wherever the AI recognises them.

Alongside the configuration fields, a project's AI-KB page lets you upload reference documents directly — policies, glossaries, prior specs, anything you want the AI to draw on. You can select or drag in several files at once. Accepted file types are PDF, DOC, DOCX, and TXT, up to 100MB per document. Each file goes through a short pipeline before it becomes usable:

1. 1Upload — each file transfers directly to secure storage, with its own live progress bar.
2. 2Scanning — every file is scanned for malware before it goes anywhere near the AI.
3. 3Indexing — once scanned clean, the document is indexed so the AI can search and reference its content.
4. 4Ready — the document now shows "AI can use this document" and is included in context for future suggestions.

From a project's AI-KB page, an "Upload to" selector above the upload area lets you send a batch of documents straight to a specific DRP's Knowledgebase instead of the project's — useful when reference material only applies to one pack. It defaults to the project. Files already in progress finish uploading to whichever scope was selected when you chose them; switching the selector only affects the next batch.

Inside an individual DRP, the AI-KB tab works the same way as the project-level page's document upload, but scoped to that one DRP — useful for reference material that's specific to a single pack rather than every DRP in the project. It layers on top of the project-level knowledgebase rather than replacing it.

Adding to or removing from a Knowledgebase is authoring, so it is Lead Analysts and Analysts on that project. Reviewers and Approvers can read what is in it but not change it — what goes in shapes the AI’s output for everyone on the project.

Both the project and DRP AI-KB pages have an "External upload link" control for Lead Analysts: generate a passphrase-protected link scoped to that project or DRP, and anyone you share it with can upload documents into that Knowledgebase — no Requio account needed. By default submissions go straight in; turn on the link's review option to hold them for your approval first instead. If your workspace has no room left in its Knowledgebase allowance, a submission waits for your review rather than being turned away — nothing a contributor sends you is lost, and it goes in once you have made room. See the External Documents guide for the full contributor-facing flow.