Make task boundaries and stopping conditions explicit.

A deterministic pretask controller for state, admissible actions, required evidence and stop decisions.

Review repository terms

Software use follows the repository’s terms. Installation, integration and model usage are separate considerations.

View source & setup guide ↗Discuss setup or integration ↗

Usage pattern

Task state
Admissibility check
Record or stop

A guide to how the project is used. Read its requirements and limits before installation.

Your starting point

An agent task with uncertain progress, consequences and stopping conditions.

An ended loop or a confident message is not evidence that a goal was reached.

The capability to add

Inspect why the next action is admissible and what would count as done.

A transition model evaluates task state and environment inputs, selects admissible moves and records decisions.

What’s in the project

A tool you can inspect.

Capabilities

Start state, end state and consequence model
Admissibility and evidence checks
Redacted JSONL decision traces

Requirements

Python and the repository’s configuration
Task-state inputs and a separately scoped integration with your runtime

Important limits

This is not an operating-system sandbox or a permissions system.
Live tool behavior and external evidence require actual integration; simulated signals are not live checks.

A useful fit

Consider this when…

Engineers designing inspectable task contracts and bounded control loops.

A different starting point

Choose another approach when…

Buyers expecting a universal security layer or automatic control over every tool.

Inspect the implementation

Public source, with a specific scope.

The repository and the files below show the implementation available to inspect. They do not establish results for your workflow.

Reviewed source snapshot: abe34e67dc42.

Compatibility and behavior must be checked in your environment. No customer-result or quality-improvement guarantee is implied.

Code and implementation help

Choose the help you need.

Software. Review repository terms. Read the repository’s terms and installation guide.

Setup and integration. Bring your current tools, a workflow and your desired result. Scope, fees, delivery and support are confirmed before work starts.

Operating costs. Existing CLI subscriptions, model-provider usage and hosting may apply depending on the tool and your configuration.

Compare published service scopes and prices ↗

Your next step

Inspect it. Then decide what to add.

Use the source and requirements to judge fit. If you want help adapting it to your workflow, start with a scoped conversation.

Discuss Fresh Pattern Controller setup ↗

No setup fee is agreed or payment taken on this page.