badgerflow 0.1.0__tar.gz

badgerflow-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

badgerflow-0.1.0/NOTICE

@@ -0,0 +1,11 @@
+BadgerFlow Python SDK (the `badgerflow` package)
+Copyright 2026 Influence AI
+
+Licensed under the Apache License, Version 2.0. See LICENSE.
+
+SCOPE. This licence covers the contents of this `sdk/` directory only — the
+client library, the `bf` and `agiel` CLIs, and the contract schemas they carry.
+
+The rest of the repository this directory sits in is the BadgerFlow platform and
+is NOT licensed under Apache-2.0, or under any other open-source licence. No
+permission to use, copy, modify or distribute it is granted by this file.

badgerflow-0.1.0/PKG-INFO

@@ -0,0 +1,210 @@
+Metadata-Version: 2.4
+Name: badgerflow
+Version: 0.1.0
+Summary: BadgerFlow Python SDK: governed pro-code agents, the platform REST client, and the bf / agiel CLIs
+License-Expression: Apache-2.0
+Keywords: langgraph,agents,llm,governance,badgerflow,mlops
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: httpx>=0.27
+Requires-Dist: pydantic>=2.0
+Requires-Dist: pyjwt[crypto]>=2.8
+Requires-Dist: openai>=1
+Requires-Dist: typer>=0.12
+Requires-Dist: pyyaml>=6
+Requires-Dist: rich>=13
+Requires-Dist: jsonschema>=4.23
+Provides-Extra: langgraph
+Requires-Dist: langgraph<2,>=1.2; extra == "langgraph"
+Requires-Dist: langchain-core<2,>=1.6; extra == "langgraph"
+Requires-Dist: langchain-openai<2,>=1.6; extra == "langgraph"
+Provides-Extra: otel
+Requires-Dist: opentelemetry-sdk>=1.27; extra == "otel"
+Requires-Dist: opentelemetry-exporter-otlp-proto-http>=1.27; extra == "otel"
+Requires-Dist: opentelemetry-instrumentation-httpx>=0.48b0; extra == "otel"
+Requires-Dist: opentelemetry-instrumentation-logging>=0.48b0; extra == "otel"
+Provides-Extra: server
+Requires-Dist: fastapi>=0.115; extra == "server"
+Requires-Dist: uvicorn>=0.30; extra == "server"
+Requires-Dist: prometheus_client>=0.20; extra == "server"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.24; extra == "dev"
+Requires-Dist: respx>=0.21; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Provides-Extra: langchain
+Requires-Dist: langchain>=0.2; extra == "langchain"
+Requires-Dist: langchain-core>=0.2; extra == "langchain"
+Provides-Extra: crewai
+Requires-Dist: crewai>=0.30; extra == "crewai"
+Provides-Extra: autogen
+Requires-Dist: pyautogen>=0.2; extra == "autogen"
+Dynamic: license-file
+
+# badgerflow
+
+The Python SDK for building **pro-code agents** that run as your own service and
+are governed by [BadgerFlow](https://github.com/facileai/agiel) anyway.
+
+You deploy the container. BadgerFlow holds the release, the approval, the
+guardrail profile, the spend and the audit trail. Your agent never handles a
+credential and is never called by anyone but the platform.
+
+## Install
+
+```bash
+pip install 'badgerflow[server,langgraph]'
+```
+
+## A LangGraph agent in one command
+
+```bash
+bf init claims-triage --langgraph
+cd claims-triage
+bf dev                      # serve it locally, no platform needed
+```
+
+`bf init` writes `agent.py`, `badgerflow.yaml`, a `Dockerfile` and a
+`.dockerignore`. The agent is an ordinary `StateGraph`; the only BadgerFlow
+addition is a `@node(uses=...)` decorator declaring what each node may touch:
+
+```python
+@node(uses=Uses(knowledge=["claims-manual"]), determinism="recorded_effect")
+async def retrieve(state: State) -> State:
+    chunks = await ctx.knowledge.retrieve(state["input"]["description"], top_k=4)
+    return {"excerpts": [c.text for c in chunks]}
+
+app = Agent.from_langgraph(build_graph(), name="claims-triage", version="0.1.0",
+                           input=Claim, output=Triage)
+```
+
+Those declarations are the contract. The platform compiles them into a graph it
+can render, checks them against what exists in your namespace at release time,
+and denies a node at runtime that reaches for something it never declared.
+
+## Work that outlives a request
+
+An invocation is an HTTP request, and some agents run longer than one should be
+held open. Call `ctx.accept()` and the platform stops waiting on the reply:
+
+```python
+@app.run
+async def triage(ctx: Context, claim: Claim) -> Triage:
+    ctx.accept()                 # answered 202; the platform now waits on events
+    await slow_work(claim)       # minutes, not seconds
+    return Triage(...)           # becomes the run's `complete` event
+```
+
+Nothing else changes. `ctx.step`, the governed clients and cancellation behave
+identically, and the return value still becomes the run's result — it reaches
+the platform as the terminal event rather than as the response body.
+
+Two things to know. The platform's clock keeps running, so silence past the
+`timeout_seconds` you registered fails the run; raise it at registration if the
+work takes longer. And once you accept, you have accepted: the reply is 202 even
+if the handler happens to finish first, so the same code cannot take one
+governance path on a fast machine and another on a slow one.
+
+## Human review in a LangGraph agent
+
+Use LangGraph's own `interrupt()` — nothing BadgerFlow-specific:
+
+```python
+def gate(state):
+    decision = interrupt({"question": f"Approve {state['amount']}?"})
+    return {"decision": decision}
+```
+
+The run pauses, appears in the platform's Paused Inbox, and resumes when a
+reviewer answers; `interrupt()` returns their answer. `interrupt_before=[...]`
+works the same way, with the prompt naming the node it stopped before.
+
+LangGraph needs a checkpointer to resume, and your pods are stateless: the pod
+that resumes is usually not the pod that paused, often days later. So the SDK
+binds `BadgerFlowCheckpointSaver`, which exports the graph's checkpoint into
+the pause and restores it on the resume. You never configure it, and your
+compiled graph is never modified.
+
+Keep large values out of the graph state. The checkpoint travels with the pause
+and is capped; a state that is too big fails the run with a clear reason rather
+than producing a pause the platform cannot file. Hold a reference instead.
+
+## Streaming a run
+
+Ask for `text/event-stream` and the invocation answers with the run's event
+frames as they happen, the last one terminal:
+
+```
+data: {"seq":1,"type":"step_started","payload":{"node_id":"retrieve",...}}
+data: {"seq":2,"type":"step_completed",...}
+data: {"seq":3,"type":"complete","payload":{"output":{...}}}
+```
+
+Nothing in the handler changes: the same `ctx.step` blocks and the same return
+value. What changes is where the evidence goes. On a streamed invocation the
+frames ride the response instead of being posted to the platform's event
+ingest, because both would record the run twice.
+
+## Register and release
+
+Deploy the container, then point the platform at it:
+
+```bash
+bf sync --wait-for-endpoint 120 --image "$IMAGE@$DIGEST"
+```
+
+The platform fetches `/.well-known/badgerflow-agent.json` from your endpoint and
+records what **it** saw, so a registration is evidence rather than a claim.
+`bf sync` exits non-zero when what the platform fetched is not what your
+checkout compiles to, which is what makes it safe in CI.
+
+Registering does not change what runs. A governed release does:
+
+```bash
+bf release submit --wait     # then a second human approves it in the UI
+```
+
+Each environment runs its own BadgerFlow with its own approvers, so run this
+once per environment. Pass the image **digest**, never a tag: it is what a
+rollback names and what makes "the same build" promoted from UAT to production
+provable.
+
+## Commands
+
+| | |
+|---|---|
+| `bf init [--langgraph]` | scaffold a project |
+| `bf dev` | serve locally, run-token verification off |
+| `bf validate` | build the manifest offline, print its hash |
+| `bf compile [--check]` | the graph the platform will see, and its hash |
+| `bf register` / `bf sync` | register a build; `sync` is the CI form |
+| `bf status` | registration, release, and hash agreement |
+| `bf release submit \| status` | the governed release and its scorecard |
+
+## Versioning
+
+The SDK follows semantic versioning. Its version is not decoration: it lands in
+every manifest's `sdk` block and the platform stores it with the release, so it
+is part of what an auditor sees. The wire contract is versioned **separately**
+as `contract_version` — an SDK major bump does not imply a contract bump, and a
+contract bump is announced on its own.
+
+## Requires
+
+Python 3.11+. The `server` extra pulls FastAPI and uvicorn, `langgraph` pulls
+LangGraph and langchain-core, `otel` pulls the OpenTelemetry SDK. Without an
+extra the corresponding surface is inert rather than broken.
+
+## Licence
+
+Apache-2.0, and it covers **this SDK only**. The BadgerFlow platform the SDK
+talks to is not open source and is licensed separately. See `LICENSE` and
+`NOTICE`.

badgerflow-0.1.0/README.md

@@ -0,0 +1,159 @@
+# badgerflow
+
+The Python SDK for building **pro-code agents** that run as your own service and
+are governed by [BadgerFlow](https://github.com/facileai/agiel) anyway.
+
+You deploy the container. BadgerFlow holds the release, the approval, the
+guardrail profile, the spend and the audit trail. Your agent never handles a
+credential and is never called by anyone but the platform.
+
+## Install
+
+```bash
+pip install 'badgerflow[server,langgraph]'
+```
+
+## A LangGraph agent in one command
+
+```bash
+bf init claims-triage --langgraph
+cd claims-triage
+bf dev                      # serve it locally, no platform needed
+```
+
+`bf init` writes `agent.py`, `badgerflow.yaml`, a `Dockerfile` and a
+`.dockerignore`. The agent is an ordinary `StateGraph`; the only BadgerFlow
+addition is a `@node(uses=...)` decorator declaring what each node may touch:
+
+```python
+@node(uses=Uses(knowledge=["claims-manual"]), determinism="recorded_effect")
+async def retrieve(state: State) -> State:
+    chunks = await ctx.knowledge.retrieve(state["input"]["description"], top_k=4)
+    return {"excerpts": [c.text for c in chunks]}
+
+app = Agent.from_langgraph(build_graph(), name="claims-triage", version="0.1.0",
+                           input=Claim, output=Triage)
+```
+
+Those declarations are the contract. The platform compiles them into a graph it
+can render, checks them against what exists in your namespace at release time,
+and denies a node at runtime that reaches for something it never declared.
+
+## Work that outlives a request
+
+An invocation is an HTTP request, and some agents run longer than one should be
+held open. Call `ctx.accept()` and the platform stops waiting on the reply:
+
+```python
+@app.run
+async def triage(ctx: Context, claim: Claim) -> Triage:
+    ctx.accept()                 # answered 202; the platform now waits on events
+    await slow_work(claim)       # minutes, not seconds
+    return Triage(...)           # becomes the run's `complete` event
+```
+
+Nothing else changes. `ctx.step`, the governed clients and cancellation behave
+identically, and the return value still becomes the run's result — it reaches
+the platform as the terminal event rather than as the response body.
+
+Two things to know. The platform's clock keeps running, so silence past the
+`timeout_seconds` you registered fails the run; raise it at registration if the
+work takes longer. And once you accept, you have accepted: the reply is 202 even
+if the handler happens to finish first, so the same code cannot take one
+governance path on a fast machine and another on a slow one.
+
+## Human review in a LangGraph agent
+
+Use LangGraph's own `interrupt()` — nothing BadgerFlow-specific:
+
+```python
+def gate(state):
+    decision = interrupt({"question": f"Approve {state['amount']}?"})
+    return {"decision": decision}
+```
+
+The run pauses, appears in the platform's Paused Inbox, and resumes when a
+reviewer answers; `interrupt()` returns their answer. `interrupt_before=[...]`
+works the same way, with the prompt naming the node it stopped before.
+
+LangGraph needs a checkpointer to resume, and your pods are stateless: the pod
+that resumes is usually not the pod that paused, often days later. So the SDK
+binds `BadgerFlowCheckpointSaver`, which exports the graph's checkpoint into
+the pause and restores it on the resume. You never configure it, and your
+compiled graph is never modified.
+
+Keep large values out of the graph state. The checkpoint travels with the pause
+and is capped; a state that is too big fails the run with a clear reason rather
+than producing a pause the platform cannot file. Hold a reference instead.
+
+## Streaming a run
+
+Ask for `text/event-stream` and the invocation answers with the run's event
+frames as they happen, the last one terminal:
+
+```
+data: {"seq":1,"type":"step_started","payload":{"node_id":"retrieve",...}}
+data: {"seq":2,"type":"step_completed",...}
+data: {"seq":3,"type":"complete","payload":{"output":{...}}}
+```
+
+Nothing in the handler changes: the same `ctx.step` blocks and the same return
+value. What changes is where the evidence goes. On a streamed invocation the
+frames ride the response instead of being posted to the platform's event
+ingest, because both would record the run twice.
+
+## Register and release
+
+Deploy the container, then point the platform at it:
+
+```bash
+bf sync --wait-for-endpoint 120 --image "$IMAGE@$DIGEST"
+```
+
+The platform fetches `/.well-known/badgerflow-agent.json` from your endpoint and
+records what **it** saw, so a registration is evidence rather than a claim.
+`bf sync` exits non-zero when what the platform fetched is not what your
+checkout compiles to, which is what makes it safe in CI.
+
+Registering does not change what runs. A governed release does:
+
+```bash
+bf release submit --wait     # then a second human approves it in the UI
+```
+
+Each environment runs its own BadgerFlow with its own approvers, so run this
+once per environment. Pass the image **digest**, never a tag: it is what a
+rollback names and what makes "the same build" promoted from UAT to production
+provable.
+
+## Commands
+
+| | |
+|---|---|
+| `bf init [--langgraph]` | scaffold a project |
+| `bf dev` | serve locally, run-token verification off |
+| `bf validate` | build the manifest offline, print its hash |
+| `bf compile [--check]` | the graph the platform will see, and its hash |
+| `bf register` / `bf sync` | register a build; `sync` is the CI form |
+| `bf status` | registration, release, and hash agreement |
+| `bf release submit \| status` | the governed release and its scorecard |
+
+## Versioning
+
+The SDK follows semantic versioning. Its version is not decoration: it lands in
+every manifest's `sdk` block and the platform stores it with the release, so it
+is part of what an auditor sees. The wire contract is versioned **separately**
+as `contract_version` — an SDK major bump does not imply a contract bump, and a
+contract bump is announced on its own.
+
+## Requires
+
+Python 3.11+. The `server` extra pulls FastAPI and uvicorn, `langgraph` pulls
+LangGraph and langchain-core, `otel` pulls the OpenTelemetry SDK. Without an
+extra the corresponding surface is inert rather than broken.
+
+## Licence
+
+Apache-2.0, and it covers **this SDK only**. The BadgerFlow platform the SDK
+talks to is not open source and is licensed separately. See `LICENSE` and
+`NOTICE`.

badgerflow-0.1.0/agiel/__init__.py

@@ -0,0 +1,57 @@
+"""
+``agiel`` — deprecated import path for :mod:`badgerflow.client`.
+
+The ``agiel`` distribution moved into the ``badgerflow`` package as
+``badgerflow.client``. This shim keeps ``from agiel import AgiellClient`` (and
+the resource classes and exceptions) working for one release cycle so existing
+scripts, generated exports and docs do not break at import time.
+
+It warns once on import. New code should import from ``badgerflow.client``.
+"""
+
+import warnings
+
+from badgerflow import __version__
+from badgerflow.client import (
+    AgiellClient,
+    AgiellError,
+    AuthError,
+    ConflictError,
+    NotFoundError,
+    ServerError,
+    ValidationError,
+)
+from badgerflow.client.resources.agents import AgentClient
+from badgerflow.client.resources.auth import AuthClient
+from badgerflow.client.resources.guardrail_profiles import GuardrailProfilesClient
+from badgerflow.client.resources.guardrails import GuardrailsClient
+from badgerflow.client.resources.models import ModelRegistryClient
+from badgerflow.client.resources.namespaces import NamespaceClient
+from badgerflow.client.resources.rag import RAGClient
+from badgerflow.client.resources.webhooks import WebhookClient
+
+warnings.warn(
+    "the 'agiel' package is deprecated; import from 'badgerflow.client' instead "
+    "(e.g. 'from badgerflow.client import AgiellClient')",
+    DeprecationWarning,
+    stacklevel=2,
+)
+
+__all__ = [
+    "__version__",
+    "AgiellClient",
+    "AgiellError",
+    "AuthError",
+    "ConflictError",
+    "NotFoundError",
+    "ServerError",
+    "ValidationError",
+    "AgentClient",
+    "AuthClient",
+    "GuardrailProfilesClient",
+    "GuardrailsClient",
+    "ModelRegistryClient",
+    "NamespaceClient",
+    "RAGClient",
+    "WebhookClient",
+]

badgerflow-0.1.0/badgerflow/__init__.py

@@ -0,0 +1,38 @@
+"""
+badgerflow — the BadgerFlow Python SDK
+======================================
+
+One installable package with two halves:
+
+* ``badgerflow.client`` — the async REST client (``AgiellClient``) and the
+  ``agiel`` CLI that used to ship as the ``agiel`` distribution. The old
+  ``agiel`` import path still works through a deprecated shim.
+* ``badgerflow.procode`` and friends — the pro-code surface (a governed
+  ``@app.run`` server, ``Context``, the LangGraph bridge, the ``bf`` CLI).
+  These packages are skeletons filled in by later work packages; each one's
+  docstring names the WP that owns it.
+
+The package never imports the platform's ``libs/`` or ``services/``. The
+constants both sides must agree on are vendored under ``badgerflow.contract``
+and pinned to ``CONTRACT_VERSION``.
+
+This module stays import-light on purpose: ``import badgerflow`` must not
+pull in httpx, typer or any optional framework, so the version is the only
+thing defined eagerly. ``badgerflow.current()`` — the running invocation's
+``Context`` — is resolved lazily on first access so that the server package
+(fastapi, prometheus_client) loads only for code that actually calls it.
+"""
+
+from typing import Any
+
+__version__ = "0.1.0"
+
+__all__ = ["__version__", "current"]
+
+
+def __getattr__(name: str) -> Any:
+    if name == "current":
+        from .procode.current import current
+
+        return current
+    raise AttributeError(f"module {__name__!r} has no attribute {name!r}")