Skip to main contentLinking Knowledge
This guide provides detailed instructions for linking knowledge documents to scenarios in XOOS.
Before You Start
Ensure you have:
- Knowledge documents uploaded to the Knowledge section
- Hierarchy defined (Workstreams → Contact Drivers → Scenarios)
- Clear understanding of what each scenario covers
Linking from a Scenario
Step 1: Open the Scenario
- Navigate to Context Engineering
- Open the relevant Workstream
- Open the relevant Contact Driver
- Click on the Scenario you want to map
Step 2: Find the Knowledge Section
In the scenario detail view, locate the Linked Knowledge or Knowledge Documents section.
Step 3: Add Documents
- Click Link Document or Add
- Use the search box to find documents by title
- Or browse by category
- Click on documents to select them
- Click Add or Link to confirm
Step 4: Review and Organize
After linking:
- Review the list of linked documents
- Remove any that aren’t directly relevant
- Note any missing documents
Linking from a Document
You can also link in the opposite direction:
Step 1: Open the Document
- Navigate to Knowledge > Documents
- Click on the document you want to map
Step 2: Find Linked Scenarios
Look for Linked Scenarios or Used In section.
Step 3: Add Scenario Links
- Click Link to Scenario
- Navigate the hierarchy to find scenarios
- Select scenarios where this document applies
- Confirm the links
What to Link
Always Link
- Primary SOP: The main procedure document for this scenario
- Applicable Policies: Rules that affect how this scenario is handled
- Required Templates: Templates agents need to use
Consider Linking
- Reference Materials: Product info, system docs
- Related SOPs: For edge cases or escalations
- Training Materials: If they contain relevant details
Don’t Link
- General Documents: Company history, unrelated policies
- Outdated Materials: Superseded procedures
- Tangential Content: Documents that mention but don’t explain the topic
Managing Links
Removing a Link
- Open the scenario
- Find the linked document
- Click Remove or the unlink icon
- Confirm removal
Replacing a Link
When a document is replaced by an updated version:
- Link the new document
- Remove the old document
- The scenario now references current information
Bulk Operations
For large-scale mapping:
By Category
- Filter knowledge documents by category
- Work through each category
- Link each document to relevant scenarios
By Workstream
- Open one workstream at a time
- Work through all its scenarios
- Complete one workstream before moving to the next
By Document Type
- Start with SOPs (most important)
- Then policies
- Then templates
- Finally, reference materials
Tracking Progress
Add tags to track mapping status:
- On scenarios:
has-knowledge, needs-knowledge
- On documents:
mapped, unmapped, needs-review
Using a Checklist
Create a simple tracking sheet:
| Scenario | Primary SOP | Policies | Templates | Status |
|---|
| Cancel Order | ✓ | ✓ | ✓ | Ready |
| Modify Order | ✓ | ✗ | ✓ | Missing policy |
| Track Shipment | ✗ | - | - | Needs SOP |
Troubleshooting
Can’t Find a Document
- Check if it’s been uploaded
- Try different search terms
- Verify you have access to the document
Document Seems Relevant to Many Scenarios
This is normal for policy documents. Link to all scenarios where the policy applies.
Scenario Has No Relevant Documents
This indicates a gap:
- Is there tribal knowledge to document?
- Does this procedure need to be created?
- Is the scenario too specific?
Next Steps
With knowledge linked to scenarios:
- Start Writing Step Guides
- Learn Step Guide Writing Techniques