Guides
Guides
Detailed workflows for using UPAS
This section provides detailed guides for common UPAS workflows.
For Field Responders
Querying Guidance Offline
- Ensure UPAS is open and procedure packs are cached
- Type your question in natural language
- Review the stepwise guidance returned
- Check the provenance panel to verify the source
- Follow the recommended actions
UPAS works best with specific, actionable questions. Instead of "Tell me about triage", try "What is the mass casualty triage protocol?"
Verifying Provenance
Every response includes provenance metadata:
- Source: Document title and section
- Version: Pack version number
- Publisher: Authoritative source
- Date: When the guidance was published
- Hash: Integrity verification
Click the provenance panel to expand details and access the original document.
Working in Degraded Mode
If the AI model is unavailable:
- UPAS will display a notice indicating degraded mode
- Use the procedure library to browse documents manually
- Use the search function to find relevant sections
- Open documents directly for reference
For Curators
Creating Procedure Packs
Procedure packs are created through the curation pipeline:
- Collect: Gather SOPs, checklists, and reference materials
- Structure: Organise documents by domain and type
- Annotate: Add metadata (effective dates, categories, keywords)
- Process: Run through the chunking and embedding pipeline
- Review: Validate content and provenance metadata
- Publish: Create a versioned release with integrity hashes
Pack Manifest Structure
{
"id": "emergency-response",
"version": "3.2.1",
"publisher": "Example Organisation",
"publishedAt": "2026-01-15T00:00:00Z",
"domain": "emergency-response",
"locale": "en",
"integrity": "sha256-abc123...",
"documents": [
{
"id": "triage-protocol",
"title": "Mass Casualty Triage Protocol",
"type": "sop",
"effectiveDate": "2025-06-01"
}
]
}Version Management
Follow semantic versioning for procedure packs:
- Major: Breaking changes to structure or significant content updates
- Minor: New documents or sections added
- Patch: Corrections, clarifications, typo fixes
Always increment the version number when publishing updates. Devices use version comparison to determine when to sync.
For Administrators
Monitoring Cache Health
Check service worker cache status:
// List cached URLs
const cache = await caches.open('upas-cache-v1');
const keys = await cache.keys();
console.log('Cached URLs:', keys.map(r => r.url));Clearing Caches
To force a fresh download:
// Clear all UPAS caches
const cacheNames = await caches.keys();
for (const name of cacheNames) {
if (name.startsWith('upas-')) {
await caches.delete(name);
}
}
// Reload to re-cache
location.reload();Troubleshooting
Common issues and solutions:
| Issue | Cause | Solution |
|---|---|---|
| Slow first load | Large model download | Use smaller model; improve connection |
| "Model unavailable" | WebGPU not supported | Falls back to WASM automatically |
| Stale content | Old cache version | Clear caches and reload |
| Storage quota exceeded | Device full | Free up device storage |