temper

Create and verify state machines defined in IOA TOML using Rust and Z3.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/loren-arthur/flow-state --skill temper-loren-arthur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: temper
Source: https://github.com/loren-arthur/flow-state/tree/main/skills/temper-openclaw
Command: npx skills add https://github.com/loren-arthur/flow-state --skill temper-loren-arthur

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rust, z3, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables the creation and management of state machines, streamlining workflows and ensuring that transitions are consistent and verifiable.

Core Features & Use Cases

  • State Machine Creation: Design state machines using IOA TOML for defining entities, states, actions, and transitions.
  • Verification: Perform a four-level verification cascade (L0-L3) to ensure state machine integrity.
  • Multi-Tenancy: Supports multiple applications within a single server instance, maintaining isolation and security.
  • OpenClaw Integration: Offers a plugin for real-time, two-way communication with OpenClaw agents.
  • Use Case: Imagine you need to manage a task queue with multiple states and transitions. Use this Skill to define the states and transitions in an IOA spec and implement a state machine that automatically updates based on task status changes.

Quick Start

Use the 'temper' skill to define a state machine for a task queue. First, create an IOA spec file named 'task_queue.ioa.toml' in your 'specs' directory. Then, run 'temper serve' to start the state machine server.

Frequently Asked Questions about temper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate workflow orchestration and maintain data integrity using state machines?

Automating workflow orchestration with state machines involves defining entities, states, and transitions in an IOA TOML spec. This ensures transitions are consistent, verifiable, and maintain data integrity across complex task queues or process control systems.

How do I verify state machine integrity for complex task queues?

Verifying state machine integrity uses a four-level verification cascade (L0-L3) to ensure transitions are consistent. This process validates that your task queue state logic remains structurally sound and free from invalid transition paths.

Do I need Rust and Z3 to build and manage state machines for workflow automation?

Yes, building and verifying state machines for workflow automation requires Rust and Z3. These dependencies provide the foundational environment for state machine construction, automated verification, and ensuring data integrity.

What's the best way to define entities and transitions for process control state machines?

The best way to define process control state machines is creating an IOA TOML spec file. You define entities, states, actions, and transitions in this file, then run a serve command to start the automated state machine server.

Does this workflow automation approach support multi-tenancy for multiple applications?

Yes, this workflow automation approach supports multi-tenancy within a single server instance. It maintains application isolation and security while managing multiple state machines concurrently across different tenants.

Can I integrate real-time communication with OpenClaw agents into workflow orchestration?

Yes, you can integrate real-time, two-way communication with OpenClaw agents into workflow orchestration. A dedicated plugin enables continuous communication, allowing external agents to interact directly with your state machine server.