BusinessOgre
Business Ogre is a business abstraction layer that neatens workflows in your code, forces self-documentation, and simplifies interaction with stakeholders.
If you are new, start with docs/Installation.md and then docs/Quick Start.md.
Example usage of Workflow and WorkflowBlock classes:
The key to using business ogre is defining the code blocks. These are classes that inherit from the WorkflowBlock class, and add some cool functionality.
Standard import style used in this project:
import business_ogre as ogr
# Define some example WorkflowBlocks
class MakeTextUppercase(ogr.WorkflowBlock):
input_type = (str,) # Required for validation
output_type = (str,) # Required for validation
# This is the actual action that is happening in your block.
def action(self, input_data: str) -> str:
return input_data.upper()
# Creating one more:
class AddExclamation(ogr.WorkflowBlock):
input_type = (str,)
output_type = (str,)
def action(self, input_data: str) -> str:
return input_data + '!'
Next you need to instantiate the blocks:
# Instantiating each block:
make_uppercase_step = MakeTextUppercase('Uppercase')
add_exclamation_step = AddExclamation('Add Exclamation')
Now that the blocks are instantiated, you can create pipelines using the >> operator.
# Using the >> operator joins the blocks into a workflow
excited_workflow = MakeTextUppercase('Uppercase') >> AddExclamation('Add Exclamation')
You can treat excited_workflow like you would a function.
# excited_workflow is callable, inputs will consecutively pass through the blocks:
excited_workflow('A piece of test text')
>>> 'A PIECE OF TEST TEXT!'
str(excited_workflow)
>>> "Workflow(steps='Uppercase >> Add Exclamation')"
Here is how you check that all the blocks match up:
# Check that the output type of each step matches the input type of the next step.
# Raises an error if there is a mismatch, otherwise returns True.
excited_workflow.validate()
>>> True
Because the flows are callable, they can easily be passed to frontend code that requires a single, neat callable.
For prompt patterns that help generate cleaner workflow files with coding assistants, see:
docs/Prompt Strategies/Workflow Build Prompts.mddocs/Prompt Strategies/Usable Business File Prompts.md
Release files for business-ogre 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| business_ogre-0.1.1.tar.gz | 22.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| business_ogre-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.4 kB
Release files / business_ogre-0.1.1.tar.gz
| Download URL | business_ogre-0.1.1.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
07f8c08a4e044ca7aebb958023b6bd20beb6aecf69ee79200fa2f129a4a0f3d6
|
|
BLAKE2b-256 checksum How to use checksums |
e90d5c7c8fd6fa9c7a7fdfec4616011c23d72798c993816d230eafdc59825721
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency logRelease files / business_ogre-0.1.1-py3-none-any.whl
| Download URL | business_ogre-0.1.1-py3-none-any.whl |
|---|---|
| Size | 15.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9075711c0d57701b28ae42fa4b415f0c17bab359ea5888fa498e918970f74d1c
|
|
BLAKE2b-256 checksum How to use checksums |
693a7f3e0944df0a57a39a903c60f736f11511a6c85325cfbecd8419b895f5a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency log