loopgraph 0.2.0__py3-none-any.whl

loopgraph-0.2.0.dist-info/METADATA

@@ -0,0 +1,165 @@
+Metadata-Version: 2.4
+Name: loopgraph
+Version: 0.2.0
+Summary: Event-driven graph workflow engine with native loop support.
+Author: LoopGraph Team
+License: MIT
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+Provides-Extra: test
+Requires-Dist: pytest>=7.4.0; extra == "test"
+Requires-Dist: pytest-asyncio>=0.21.0; extra == "test"
+Provides-Extra: lint
+Requires-Dist: ruff>=0.6.4; extra == "lint"
+Requires-Dist: mypy>=1.11.0; extra == "lint"
+
+# LoopGraph
+
+**The agent workflow engine that treats loops as a first-class citizen.**
+
+Build graph-based AI agent workflows where cycles, re-entry, and iterative reasoning are native — not hacks. More intuitive and lightweight than LangGraph, with loops as a first-class primitive.
+
+- **Zero dependencies** — pure Python 3.10+, nothing to install beyond your own agents
+- **Native loop support** — cycles in your graph are validated, tracked, and safe by design
+- **Event-driven** — every state transition emits events; hook in logging, metrics, or triggers anywhere
+- **Async-first** — built on `asyncio`, handles concurrent nodes without blocking
+- **Recoverable** — snapshot and replay any run from any point
+
+```bash
+pip install loopgraph
+```
+
+---
+
+## Quickstart
+
+```python
+import asyncio
+from loopgraph.core.graph import Graph, Node, Edge, NodeKind
+from loopgraph.bus.eventbus import EventBus
+from loopgraph.registry.function_registry import FunctionRegistry
+from loopgraph.scheduler.scheduler import Scheduler
+
+async def my_agent(payload):
+    # your agent logic here
+    return {"result": "done", "loop_again": False}
+
+async def router(payload):
+    # return the next node id
+    return "end" if not payload.get("loop_again") else "agent"
+
+graph = Graph(
+    nodes=[
+        Node(id="agent", kind=NodeKind.TASK),
+        Node(id="router", kind=NodeKind.SWITCH),
+        Node(id="end", kind=NodeKind.TASK),
+    ],
+    edges=[
+        Edge(source="agent", target="router"),
+        Edge(source="router", target="agent"),   # the loop back-edge
+        Edge(source="router", target="end"),
+    ],
+    entry="agent",
+)
+
+registry = FunctionRegistry()
+registry.register("agent", my_agent)
+registry.register("router", router)
+registry.register("end", lambda p: p)
+
+bus = EventBus()
+scheduler = Scheduler(graph=graph, registry=registry, bus=bus)
+
+asyncio.run(scheduler.run(payload={"input": "hello"}))
+```
+
+---
+
+## Why LoopGraph?
+
+Most workflow engines assume a DAG — a graph with no cycles. That works for linear pipelines, but agent workflows are inherently iterative: an agent reasons, reflects, decides to try again, and loops back. Forcing that into a DAG requires awkward workarounds.
+
+LoopGraph makes loops explicit and safe:
+
+- **Back-edges are first-class** — declare a cycle in your graph and the engine handles reset, visit tracking, and state management automatically
+- **Loop safety** — the engine validates your graph at construction time; overlapping loops that share nodes are rejected before anything runs
+- **Full observability** — every loop iteration emits events (`NODE_SCHEDULED`, `NODE_COMPLETED`, `NODE_FAILED`) so you always know where you are
+
+---
+
+## Event Hooks
+
+Subscribe to any workflow event to add logging, metrics, or side effects:
+
+```python
+from loopgraph.core.types import EventType
+
+async def on_completed(event):
+    print(f"{event.node_id} finished → {event.payload}")
+
+bus.subscribe(EventType.NODE_COMPLETED, on_completed)
+```
+
+Available events: `NODE_SCHEDULED`, `NODE_STARTED`, `NODE_COMPLETED`, `NODE_FAILED`.
+
+---
+
+## Custom Events from Handlers
+
+Wrap your handler in a closure to emit custom events mid-execution:
+
+```python
+def make_handler(bus, base_handler):
+    async def wrapper(payload):
+        await bus.emit(Event(id="pre", graph_id="g", node_id="n",
+                             type=EventType.NODE_SCHEDULED, payload={"stage": "pre"}))
+        result = await base_handler(payload)
+        await bus.emit(Event(id="post", graph_id="g", node_id="n",
+                             type=EventType.NODE_COMPLETED, payload={"stage": "post"}))
+        return result
+    return wrapper
+
+registry.register("my_node", make_handler(bus, my_agent))
+```
+
+---
+
+## Loop Re-entry Rules
+
+- Re-entry is triggered by a `SWITCH` node selecting a back-edge
+- Only `COMPLETED` nodes can be reset for re-entry
+- Reset clears upstream-completion tracking and preserves cumulative `visit_count`
+- Overlapping loops sharing any node are rejected at graph construction time
+
+---
+
+## Installation
+
+```bash
+pip install loopgraph
+```
+
+Requires Python 3.10+. No runtime dependencies.
+
+---
+
+## Development
+
+```bash
+git clone https://github.com/your-org/loopgraph
+cd loopgraph
+python3 -m venv .venv && source .venv/bin/activate
+pip install -e ".[test,lint]"
+pytest
+```
+
+---
+
+## Design Principles
+
+- **Keep the core compact.** Nodes stay stateless and the scheduler stays simple, with minimum opinionated design and maximum freedom for users to compose their own workflow patterns. Handlers capture their own context (event bus, metrics, side effects) so the framework never grows special cases for custom behaviour.
+- **Push heavy lifting to the edge.** Long-running work should run via remote APIs, threads, or separate nodes/clusters. We avoid building a distributed fan-out scheduler; users orchestrate their own parallelism while the engine focuses on deterministic single-node execution.
+- **Flexible aggregation semantics.** Aggregator nodes may proceed when only a subset of upstream nodes finish — as long as those nodes reach a terminal state. Fail-fast and error-tolerance are user-level workflow patterns, and the engine stays policy-light so users can implement either.
+- **Retries live with handlers.** The framework doesn't implement automatic retries. Each handler decides whether to retry, abort, or compensate, keeping recovery logic close to the business code.
+- **Pluggable concurrency.** A shared ConcurrencyManager (semaphore or priority-aware) controls global slots. Multiple schedulers can share one manager, but there's no hidden magic — users choose the policy, preserving clarity and control.
+- **Recovery through snapshots.** The engine snapshots execution state and event logs so users can resume or replay runs without re-executing nodes. Payloads flow naturally between nodes, satisfying replay needs without extra APIs.

loopgraph-0.2.0.dist-info/RECORD

@@ -0,0 +1,24 @@
+loopgraph/__init__.py,sha256=hfsbTvpGMIagxsEkuPrhIjEN_LQ1MSWSmemZ7lVVP-I,1007
+loopgraph/_debug.py,sha256=916xk9zxdqQo9UElyz1YbyYxqdWSW8HK6Ch8oBqUiQI,1280
+loopgraph/py.typed,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+loopgraph/bus/__init__.py,sha256=SGmZyIdrjgBOXjzo8thuM8wbcYn2GZFaavoAPMesIco,167
+loopgraph/bus/eventbus.py,sha256=stKB0codg14F8dOALFdtoDg2Xi_vHOvLUcmbVAM_Kac,6576
+loopgraph/concurrency/__init__.py,sha256=mv8MZ5RpVMpMvhOBKuVnp9RsbmsbuYKHzg2Ogjn8hFg,202
+loopgraph/concurrency/policies.py,sha256=VtOoCyWnFYrTEBrfYxkrAd53sZo8NHF7bktz9HfbzmU,6710
+loopgraph/core/__init__.py,sha256=lZh69PG91I7HbZXboz6lfpIGLGal4j5R1OuimQZXh70,392
+loopgraph/core/graph.py,sha256=__dbQDw4zPILlmaEjB9VKd_F9854WZw3Zg1jUUC682I,18003
+loopgraph/core/state.py,sha256=xwiFdQe25MAGp_XqDSv69ohm20I8r2zCPij0GY7x4Pc,17687
+loopgraph/core/types.py,sha256=qQMdIPVqvyQcQA5RpYQ98b4wjd8qQ2iD9rU5ymH9XU8,2005
+loopgraph/diagnostics/__init__.py,sha256=E3lCV2g0pNzoMga52bmZYVzwmxwUdPp9Sm9k-ssadKg,148
+loopgraph/diagnostics/inspect.py,sha256=b726Mqk4xi3rPLQoEsaD_Ss1mvCaLfSOfzS4LMNB1j0,2532
+loopgraph/persistence/__init__.py,sha256=oKUSFK-yWJ9S3x4QpFT100LGfwVOzfNX8lgvq6_oPbI,255
+loopgraph/persistence/event_log.py,sha256=MWAvZMvqcP_cNo6mtvZRQtlyhYMEzibhdf0Cc1-DuBE,1983
+loopgraph/persistence/snapshot.py,sha256=wK10SjyEpia3j1WYFf0mfXHHFo5epaVN0cRAVgQo1iY,1802
+loopgraph/registry/__init__.py,sha256=Ou_Ji9iYBkg6CAK6KFU7NLDgKi6BNJT7UztwUZ00kEc,36
+loopgraph/registry/function_registry.py,sha256=WSBpk3SJG7QmeoudKI7NSR1Htc3oCqCTQzjrbHJ-4aw,3760
+loopgraph/scheduler/__init__.py,sha256=Y7DD-fSnWqGyjAojoNQqoT1CWEeV6DkVlSEvG5NVZOU,87
+loopgraph/scheduler/scheduler.py,sha256=EyBHQopWyvzGGbMccigDXtX3Q5WH9iak3coMwhOOViI,24801
+loopgraph-0.2.0.dist-info/METADATA,sha256=3lQSXTizoQ8BOrBG8KJXFSjuvN8to3ub8vgRHrqVe5g,6355
+loopgraph-0.2.0.dist-info/WHEEL,sha256=aeYiig01lYGDzBgS8HxWXOg3uV61G9ijOsup-k9o1sk,91
+loopgraph-0.2.0.dist-info/top_level.txt,sha256=bTwyu1IHllBA8-cY8U9uCwndzhBMtR1HgxJgfruAmG4,10
+loopgraph-0.2.0.dist-info/RECORD,,

loopgraph-0.2.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (82.0.1)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

loopgraph-0.2.0.dist-info/top_level.txt

@@ -0,0 +1 @@
+loopgraph