iii-core-primitives

This skill documents the core primitives of the iii backend platform — Function (a named unit of work), Trigger (an event source bound to a function), and Worker (a process that connects to the engine and executes functions) — and how to use them across TypeScript, Python, and Rust. It solves the problem of getting started with iii's building blocks: registering local or HTTP-invoked functions, binding triggers, selecting invocation modes, creating and installing workers, and inspecting the live engine registry.

It covers function registration for both local handlers and existing HTTP services, trigger binding, and the `trigger()` call for invoking any function by ID. Worker guidance spans writing your own worker with registerWorker/registerFunction/registerTrigger and installing capability workers from the public registry at workers.iii.dev via `iii worker add`, including version pinning, OCI images, local paths, and lockfile replay with `iii worker sync`. A worker manifest example shows how iii starts a local worker project. Built-in discovery functions read the live registry of workers, functions, triggers, and trigger types. It tabulates built-in trigger shapes (http, cron, durable subscriber, subscribe, state, stream, log) with their config and handler payloads, and the sync, void, and enqueue invocation modes. The guidance explicitly warns not to put secrets in metadata. Worked examples appear in all three languages.

The target users are backend developers building on iii who need the exact syntax for registering functions, binding triggers, choosing invocation modes, creating workers, or installing registry capabilities. It is the reference-level companion to the higher-level architecture-patterns skill.