Publish an atomic capability
Export one reusable capability from a package root or isolated ESM subpath.
Recipes
Recipes start from a task you are likely to face while building an Action Engine. Each one uses code from a tested example in the Invokta repository, then shows how to run and verify the result locally.
Publish a capability library
Bundle related capabilities with literal default IDs and factory-injected dependencies.
Inject a dependency
Put a repository and classifier behind engine-owned ports, then wire their implementations at the composition root.
Authorize with domain data
Check a principal’s permission and resource constraint before the capability loads a ticket or calls a model.
Compose capabilities
Combine a local capability, atomic package exports, and a selected library without losing ID ownership.
Consume MCP stdio
Connect an independent harness with the official MCP client, discover a tool, invoke it, and close the child transport.
Wrap an external provider
Keep a provider credential and HTTP contract behind an outbound port while cancellation and safe errors cross the boundary.
Before you start
Section titled “Before you start”Run the recipes from the repository root with Node.js 22.20.0 or later and Yarn 1.22.22:
git clone https://github.com/vinilana/invokta.gitcd invoktayarn install --frozen-lockfileyarn buildIf this is your first Invokta engine, build the first-engine walkthrough before using these patterns. Browse the complete example catalog when you want to compare domains, provider boundaries, and workflow designs.