Concepts

The Stubber Framework

The conceptual framework of Stubber

# Overview

The Stubber Framework is a structured method for defining any organizational process or procedure. It outlines how to model a process and execute it.

This includes:

1. Defining how processes start
2. What data is collected at each step
3. The necessary actions to move through the process

The framework is also very well suited to define and build agentic AI applications. The components allow defining goals and outcomes for AI Agents to pursue.

# Framework

Processes are modeled using the Stubber Framework. The word "process" here is used very liberally, as a process in the Stubber Framework can be anything that can be automated or collaborated on to achieve a certain goal.

The Stubber Framework is used to:

• Define organizational processes
• Define how processes are started
• Define what data is collected at each step
• Describe the steps that need to be taken in a process

The Stubber Framework is the basis for the Stubber Platform which is an online platform that implements these concepts and ideas. The Stubber Platform is hosted at app.stubber.com.

# Comparisons

The Stubber Framework differentiates itself by providing greater clarity and flexibility in modeling real-world processes. It combines ideas and concepts from other frameworks and methodologies.

The relative freedom of the framework is it's strength, as exceptions can be dealt with inside the framework. This freedom in the process modelling is also crucial for building AI Agents.

# Stubber is NOT a workflow tool

It's important to note when coming from traditional work flow tools that the Stubber framework is not a work flow tool.
There is no deterministic automation at the states and actions layer.
States represent a higher level concept that have many possible actions that are all possible, and can be chosen at will. This allows the framework to be very open and free at the higher level.
Multiple potential actions can be triggered in any order and multiple times within a state.

# Adding structure

So if the framework is open and free at the high level how do you get structured processes and in order execution of processes. This comes by breaking up the various actions into states and making certain actions available on in a certain state. The availability of actions is the primary mechanism by which you constrain the process within Stubber. There are other additional methods to manipulate actions availability. Here are all the methods :

# Expanding action availability

• You can add an action to the special state _all to make it available everywhere in the flow

# Restricting action availability

• Making an action available in a state (primary method)
• Setting the conditions array on an action, only if all conditions are met is the action allowed
• Enabling the action for AI controls if the action can be used by an LLM or if it's only allowed to be triggered by users on Stubber

# Key Concepts

• Templates and Stubs
• States and Actions