Skip to main content

Chapter 1: What is Worka?

TL;DR

  • Host runtime: Worka is a secure host runtime that executes sandboxed packs and enforces explicit permissions.
  • Packs: All features are delivered as packs. A pack bundles UI views, tools, and a manifest (aip.json) that declares capabilities and dependencies.
  • Orchestration: A DAG‑based worker executes structured workflows so automation is reliable and auditable.

Welcome to the foundational concept of Worka v2. Before writing code, it’s important to understand the platform roles and how they interact.

Think of Worka like a secure operating system. The host provides core services and safety boundaries; packs deliver the actual functionality.

Worka is composed of three main conceptual layers:

1. The Host Runtime

The host runtime executes packs and enforces the security model. It is responsible for:

  • Sandboxing: Packs run in a WASM runtime. No raw filesystem or network access unless explicitly granted.
  • Permissions: Every capability is declared in the pack manifest and enforced at runtime.
  • Services: Storage, orchestration, and UI surfaces are provided as trusted host services.
  • Auditability: Every workflow step is recorded so outcomes are verifiable.

2. The Pack Ecosystem

All functionality in Worka is delivered through packs. A pack is a self‑contained bundle that can include:

  • A2UI views (structured UI definitions)
  • Tools (MCP methods)
  • Agents (orchestration policies)
  • Assets & locales (icons, translations, etc.)

Packs are installable, versioned, and isolated from each other unless a dependency is declared.

3. The Orchestrator

The orchestrator is the execution engine. It converts goals into a directed acyclic graph (DAG) of steps, executes them in order, and records results.

  • Planning: Converts goals to structured steps.
  • Execution: Runs steps with dependency checks.
  • Coordination: Routes tool calls and agent decisions safely.
  • Tracing: Produces audit logs and replayable histories.

This model enables complex, multi‑step workflows with predictable outcomes and accountability.