VibeBlocks
AI-First Orchestration for Python.
VibeBlocks evolves the concept of task orchestration into an AI-ready framework. It maintains the "Zero-Gravity" architecture (no external dependencies) while introducing a Semantic Layer for LLM integration and dynamic flow generation.
Key Concepts
- Block: The atomic unit of execution.
- Chain: A linear sequence of Blocks.
- Flow: High-level orchestrator with failure strategies.
Installation
pip install vibeblocks
Quick Start
1. Classic Usage
from vibeblocks import Flow, ExecutionContext, block, execute_flow
# 1. Define your blocks with @block decorator
@block(description="Extracts data from source")
def extract(ctx: ExecutionContext):
print("Extracting data...")
ctx.data["raw"] = [1, 2, 3, 4, 5]
return ctx.data["raw"]
@block(description="Doubles the input values")
def transform(ctx: ExecutionContext):
print("Transforming data...")
data = ctx.data["raw"]
ctx.data['processed'] = [x * 2 for x in data]
return ctx.data['processed']
@block(description="Loads data to destination")
def load(ctx: ExecutionContext):
print(f"Loading data: {ctx.data['processed']}")
return True
# 2. Create the Flow
pipeline = Flow("ETL_Flow", [extract, transform, load])
# 3. Execute
result = execute_flow(pipeline, data={})
if result.status == "SUCCESS":
print("Flow completed successfully!")
else:
print(f"Flow failed: {result.errors}")
2. AI-Driven Dynamic Flows
VibeBlocks allows LLMs to generate flows on the fly using JSON schemas.
from vibeblocks.vibeblocks import VibeBlocks
# JSON definition (could come from an LLM)
flow_request = {
"name": "DynamicETL",
"blocks": ["extract", "transform", "load"],
"strategy": "ABORT"
}
# Available blocks registry
blocks_registry = {
"extract": extract,
"transform": transform,
"load": load
}
# Execute dynamically
result = VibeBlocks.run_from_json(flow_request, initial_data={}, available_blocks=blocks_registry)
License
MIT License. See LICENSE for details.
Metadata
Release files for vibeblocks 0.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| vibeblocks-0.1.4.tar.gz | 16.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vibeblocks-0.1.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 39.0 kB
Release files / vibeblocks-0.1.4.tar.gz
| Download URL | vibeblocks-0.1.4.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e46b77adb010d67e15417667890af6b9473d2bef9a344a3c943c7ae3dd49c7bd
|
|
BLAKE2b-256 checksum How to use checksums |
d28427a16b53c87ad94c809e00bc36a4a6cb9ef5a0c2a22d7af5e816263a152f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 26, 2026.
Transparency logRelease files / vibeblocks-0.1.4-py3-none-any.whl
| Download URL | vibeblocks-0.1.4-py3-none-any.whl |
|---|---|
| Size | 22.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c319db9f431aad5d04ecddf28b7fb04223653044d0870f4702f3da88a5fd003
|
|
BLAKE2b-256 checksum How to use checksums |
d6886f47538323a0bd4f5ae78e0c913fc679187cee5e5fffcd7bc6357bb54532
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 26, 2026.
Transparency logSecurity for vibeblocks 0.1.4
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for vibeblocks-0.1.4.tar.gz
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 Mar 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.