Metadata-Version: 2.4
Name: genie_flow
Version: 0.9.0a6
Summary: Core classes for Genie Flow
Maintainer-email: Willem van Asperen <willem.van.asperen@paconsulting.com>
License-Expression: Apache-2.0
Project-URL: Homepage, https://genieversum.github.io
Project-URL: Repository, https://github.com/genieversum/genie-flow
Classifier: Development Status :: 5 - Production/Stable
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Operating System :: OS Independent
Classifier: Framework :: Celery
Classifier: Framework :: FastAPI
Classifier: Framework :: Pydantic
Classifier: Topic :: Communications :: Chat
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
Classifier: Typing :: Typed
Requires-Python: >=3.11.0
Description-Content-Type: text/markdown
License-File: NOTICES
Requires-Dist: genie-flow-invoker~=0.6.0
Requires-Dist: loguru~=0.7
Requires-Dist: python-statemachine~=2.3
Requires-Dist: pydantic~=2.11
Requires-Dist: jinja2~=3.1
Requires-Dist: fastapi~=0.115
Requires-Dist: celery~=5.5
Requires-Dist: redis~=5.2
Requires-Dist: python-redis-lock~=4.0
Requires-Dist: dependency-injector~=4.42
Requires-Dist: jmespath-community~=1.1
Requires-Dist: python-snappy~=0.7
Requires-Dist: ulid-py~=1.1
Requires-Dist: pyaml~=25.1
Requires-Dist: pymongo~=4.12.1
Requires-Dist: uvicorn==0.34
Provides-Extra: test
Requires-Dist: pytest; extra == "test"
Requires-Dist: pytest-docker; extra == "test"
Dynamic: license-file

# Genieversum
[![PyPI version](https://badge.fury.io/py/genie-flow.svg?icon=si%3Apython)](https://badge.fury.io/py/genie-flow)
![PyPI - Downloads](https://img.shields.io/pypi/dm/genie-flow)

## Our Mission
Genie Flow (or simply Genie) is a modular AI platform designed to help you build intelligent, 
reusable agents that can automate tasks, process data, and interact with users or systems. 
Whether you're a seasoned developer or just starting out, Genie Flow offers a flexible and 
approachable way to create smart workflows.

Our vision is that a _good_ agentic framework should be:

* **Code First** – We do not have a "low code" environment. We believe in the power of 
  expression of well-written code.
* **Deployable** – A Genie agent is ready to deploy as an API. There is no magic engine or 
  deployment formula. Your agent is built into a Docker container and comes with a well-documented 
  API out of the box.
* **Scalable** – Work is queued to be picked up by workers. This makes your agent immediately 
  scalable. From your laptop to large server clusters. One code base. Scalable out of the box.
* **Community Driven** – AI should be available for everyone, and everyone should be able to
  contribute.

We do consulting. We are not a software house. We are not a product company. We are not a 
service or hosting provider. We make our living by helping large organisations to make the 
best use of AI. We are the company where Next is Made Real.

## What is Genie
Simply put: Genie is an agentic AI orchestrator. It manages the dialogue between an actor 
(human or machine) and a cascade of calls to external systems. Many of these external systems 
may be Large Language Models, but the dialogue flow typically combines that with other sources 
of information and operational systems that can be reached via an API.

### Example Genie Agent
Imagine the following use case:

> As a user, I want to have a dialogue with a Large Language Model.

Three steps:

1. Create your data model
2. Define how you want the dialogue to flow
3. Specify the templates to use in each of the steps

#### Defining your data model
First, you define your `GenieModel` - a Pydantic data model of information that you want to 
carry during the dialogue session.

```python
class MyFirstModel(GenieModel):

    # there are no specific data elements I need to carry

    # link this model to the state machine
    @classmethod
	def get_state_machine_class(cls) -> type[GenieStateMachine]:
        return GenieStateMachine
```

#### Define the flow of your dialogue
Next, you define how your dialogue needs to flow by creating your dialogue's state machine:

```python
class MyFirstMachine(GenieStateMachine):
    
    # STATES
    into = State(initial=True, value=100)
    ai_creates_response = State(value=200)
    user_enters_query = State(value=300)

    # EVENTS & TRANSITIONS
	user_input = (
        intro.to(ai_creates_response)
        | user_enters_query.to(ai_creates_response)
    )
    ai_extraction = (
        ai_creates_response.to(user_enters_query)
    )

    # TEMPLATES
    templates = dict(
        intro="response/intro.jinja2",
        ai_creates_response="llm/ai_creates_response.jinja2",
        user_enters_query="response/user_enters_query.jinja2",
    )
```

This creates a dialogue that looks like:

```mermaid
stateDiagram-v2
	direction LR
	[*] --> intro
	intro --> ai_creates_response: user_input
	ai_creates_response --> user_enters_query: processing_done
    user_enters_query --> ai_creates_response: user_input
	
    intro: Intro
	ai_creates_response: AI Creates Response
    user_enters_query: User Enters Query
```

The most basic dialogue flow:

1. The Agent introduces themselves and asks a question
2. The user sends their input
3. An LLM formulates a response
4. The engine signals that processing is done
5. The user views the response and sends new input
6. Back to point 3

#### Creating the templates
We just need to define the templates. First template, the `intro.jinja2` template:

``` title="intro.jinja2"
Welcome to this simple Question and Answer dialogue Genie Flow example!

How can I help? Please go ahead and ask me anything.
```

We also need to define the prompt that will get sent to the LLM. This happens in the file 
`ai_creates_response.jinja2`:

```yaml title="ai_creates_response.jinja2"
- role: system
  content: |
    You are a friendly chatbot, aiming to have a dialogue with a human user.
    Your aim is to respond logically, taking the dialogue you had into account.
    Be succinct, to the point, but friendly.
    Stick to the language that the user start their conversation in.

{{ chat_history }}

- role: user
  content: |
{{ actor_input|indent(width=4, first=True) }}
```

This template defines the `system` prompt, followed by the `{chat_history}`, followed by the 
input from the previous actor. That will be the human user in our case.

And then, the final template, `user_enters_query.jinja2`:
``` title="user_enters_query.jinja2"
{{ actor_input }}
```
Here, the user is presented with the response from the previous actor (the LLM in this case).

#### Switch on
That's it! This defines a fully fledged AI agent.

Deploying this would mean: create a `main.py` that tells Genie where your and data model class 
live, run the worker, run the API and spin up a front-end that talks to your API. We have 
provided a simple command-line interface that we use in anger during development, and a simple 
React chat interface that you can get started with.

## Where from here?

- [Documentation](https://genieversum.github.io) for in-depth documentation of the framework.
- [Getting Started](https://genieversum.github.io/getting_started/) for a step-by-step guide to run the above example.
- [Under the Hood](https://genieversum.github.io/under_the_hood/under_the_hood/) for a detailed description of the underlying architecture.
- [Contribute](https://genieversum.github.io/community/contributing/)
