iii-hq/iii

configuration

Schema-validated, reactive registry for named configuration entries — the runtime configuration surface used by engine and Compose workers.

原文の言語: 英語

iii

How iii works and the iii-sdk surface for authoring workers, functions, and observers. Teaches the ordered way to gain a capability before writing code — (1) check functions already registered in the engine, (2) search the public registry via iii-directory,…

原文の言語: 英語

iii-observability

OpenTelemetry-backed tracing, structured logs, metrics with rollups, alerts, sampling, and baggage for the engine — emit and query telemetry through `engine::*` functions and react to logs and spans by observing `observability::on-log` and…

原文の言語: 英語

iii-sandbox

Ephemeral microVM sandboxes for running untrusted or agent-generated code in isolation — a one-call run path, a create/exec/stop lifecycle, and a set of filesystem operations.

原文の言語: 英語

iii-stream

Durable real-time streams with a CRUD function surface plus engine-hosted sources called on item changes and WebSocket subscriber lifecycle — reach for it to build live backends without polling. iii-stream is deprecated (iii-stream) and will be removed in an…

原文の言語: 英語

iii-worker-manager

WebSocket listener that SDK workers connect to. Use to expose the engine to trusted (internal) and untrusted (RBAC-protected) workers, gate function and observer registration, and audit or transform every invocation through a middleware function. Mounts…

原文の言語: 英語

iii-architecture-patterns

Use when composing iii primitives into backend architectures: durable workflows, reactive backends, observer side effects, agentic pipelines, event-driven CQRS, effect pipelines, and event-transform-action automation.

原文の言語: 英語

iii-core-primitives

Use when registering iii functions, calling them (call with sync, void, or enqueue), observing functions and event sources, creating workers, inspecting the live worker registry, installing registry workers, moving channel data, or adapting external HTTP…

原文の言語: 英語

iii-engine-config

Configure a managed iii engine through worker-compose.yaml or a directly supervised engine through config.yaml. Use for engine ports, RBAC via the rbac-proxy worker, observer limits, streams, sandboxes, and configuration storage.

原文の言語: 英語

iii-error-handling

Handle iii engine and SDK errors across Node, Python, Rust, and browser workers. Use when interpreting error codes, retryability, RBAC denial, timeouts, handler failures, or SDK-specific exception surfaces.

原文の言語: 英語

iii-getting-started

Install the iii engine, set up your first worker, and get a working backend running. Use when a user wants to start a new iii project, install the SDK, or needs help with initial setup and configuration.

原文の言語: 英語

iii-observe

Use when one iii function should run when another runs (iii.observe), when binding functions to HTTP routes, cron schedules, queue topics, state or database changes, or engine events through their source functions (http::on-request, cron::on-tick,…

原文の言語: 英語

iii-sdk-reference

Use when working with iii SDK APIs across Node.js, browser, Python, Rust, or Go: package installation, worker initialization, function registration, calling functions, observers and observer hooks, local dispatch, channels, logging, OpenTelemetry, and…

原文の言語: 英語

presentation

Turn a tech-spec directory into an interactive, marketing-grade web presentation — built so engineers understand the design, the reader is convinced of the why, and the result is shareable in public. Use when someone wants a spec turned into a deck.

原文の言語: 英語