Pilot programme targeting Q3 2026. Register your interest now.Pilot EOI
UPAS
Guides

Guides

Detailed workflows for using UPAS

This section provides detailed guides for common UPAS workflows.

For Field Responders

Querying Guidance Offline

  1. Ensure UPAS is open and procedure packs are cached
  2. Type your question in natural language
  3. Review the stepwise guidance returned
  4. Check the provenance panel to verify the source
  5. 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:

  1. UPAS will display a notice indicating degraded mode
  2. Use the procedure library to browse documents manually
  3. Use the search function to find relevant sections
  4. Open documents directly for reference

For Curators

Creating Procedure Packs

Procedure packs are created through the curation pipeline:

  1. Collect: Gather SOPs, checklists, and reference materials
  2. Structure: Organise documents by domain and type
  3. Annotate: Add metadata (effective dates, categories, keywords)
  4. Process: Run through the chunking and embedding pipeline
  5. Review: Validate content and provenance metadata
  6. 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:

IssueCauseSolution
Slow first loadLarge model downloadUse smaller model; improve connection
"Model unavailable"WebGPU not supportedFalls back to WASM automatically
Stale contentOld cache versionClear caches and reload
Storage quota exceededDevice fullFree up device storage

Next Steps