Tools and Integration Overview

Once you can run a Devlish program, you may want another application to call it, limit its external actions, or keep records of its use. This section explains those surrounding capabilities. You can use the integration pages without adopting the release and audit workflow.

Here, a tool means a callable program with named inputs and a result. A host is the application that runs the program and supplies external operations such as file access. An artifact is the compiled bytecode package for a particular program version.

Connect a program to an application

Use MCP Server when an AI client needs to discover and call Devlish tools. Use JavaScript Runtime when your own application needs to execute compiled programs directly. Checkpoints describe how a program can stop and return intermediate context for review.

Control external actions

Permissions describe the capabilities a program declares. Local Tools and Policy explain how a policy decides whether a specific request is allowed. Supported operations and enforcement depend on the host and execution profile.

Track a rule from testing to use

When a rule needs formal review, these pages form a sequence:

1. Governed Rules give it an identifier, version, and effective dates.
2. Evidence Bundles record how that compiled version performed on named test cases.
3. Controlled Releases record proposal, approval, and publication, and explain how native execution checks the registry.
4. Audit and Replay record an actual run and explain how captured external responses can reproduce it later.

An identifier describes the rule, tests check specific cases, and an audit log records an execution. Each answers a different question. The pages explain their limits as well as their commands.

Toolrun Compression is a separate development utility for reducing the command output sent to an AI assistant.