Overview

Faimulus is a runtime for building AI-powered applications from explicit workflows.

Instead of putting application behavior inside a large prompt or autonomous agent loop, you describe the allowed execution paths as a workflow and use AI models only for the steps that benefit from reasoning. The workflow graph makes control flow visible: deterministic nodes can validate data, call tools, branch, retry, pause for approval, and handle failures around model-driven steps.

Workflows are packaged with their manifests, node implementations, and configuration so they can be validated before execution. At runtime, Faimulus tracks each run, persists state for long-running or suspended work, and resumes execution when a schedule, callback, or human response arrives.

Core and server

Core (@faimulus/core) is the reusable workflow runtime. It loads and validates workflow packages, executes their graphs, coordinates AI models and tools, persists run state, and manages schedules, callbacks, channels, and interactions. Applications can embed Core directly when they need to host Faimulus inside another Node.js process.

Server (@faimulus/server) is the ready-to-run network host for Core. It adds HTTP endpoints for starting and managing runs, receives webhooks and callbacks, and publishes runtime events over WebSockets. Use Server when workflows need to be operated as a standalone service or reached by other applications over the network.

Both use workspace configuration to connect workflows to model providers, memory backends, channel transports, and external toolsets. Those integrations remain separate from workflow control flow, so deployments can change providers or infrastructure without rewriting the application graph.

Choose a path

• Workflow author: read workflow packages, graph and expressions, and built-in nodes.
• Operator: begin with deployment, then review configuration and security and recovery.
• Extension developer: use extension points, channel drivers, and the TypeScript API.

What is authoritative?

This site documents the current source, tests, manifests, and examples. Generated TypeScript pages reflect the public driver and core packages at build time.