Skip to main content

Host Services

Some capability belongs to the platform itself rather than to third-party or tenant-authored packs.

Worka exposes that capability through host services, also described in the older docs as virtual packs. The important idea is the same: the platform gives you named, governed entry points for privileged operations.

Why host services matter

If the platform already provides a sanctioned path for something important, use it.

Examples include:

  • updating workspace views
  • invoking another AI team member
  • using pack-scoped database access

By using the host service, you let Worka keep:

  • authorization checks
  • audit trails
  • workspace state consistency
  • runtime boundary rules

Read these pages next

  1. Virtual Packs
  2. worka.runtime
  3. worka.ui
  4. worka.db