agentforge-framework 0.2.0__tar.gz → 0.2.2__tar.gz

{agentforge_framework-0.2.0 → agentforge_framework-0.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentforge-framework
-Version: 0.2.0
+Version: 0.2.2
 Summary: A modular framework for coordinating specialized software agents.
 Author: Yash Mhatre
 License-Expression: Apache-2.0
@@ -20,7 +20,7 @@ Dynamic: license-file
 
 AgentForge is a standalone Python framework for coordinating specialized software agents through reusable workflows.
 
-A human states a Task. The Orchestrator files a GitHub issue carrying a frozen plan and the Roster of Roles that will execute it. `agentforge implement <n>` runs the Issue's Workflow and opens a draft pull request for a human to sign off. No workflow ever merges.
+A human states a Task. The Orchestrator grills them on it, writes a spec, cuts the spec into Slices, and files a GitHub issue for each -- every one carrying a frozen plan, the Roster of Roles that will execute it, and the issues that block it. `agentforge implement <n>` runs one Issue's Workflow and opens a draft pull request for a human to sign off. No workflow ever merges.
 
 ![An Issue carries the frozen plan and the Roster. Each Agent reads that Issue and appends its result as the Run Log. The Workflow ends at a draft pull request that only a human can merge.](docs/assets/one-issue-number.svg)
 
@@ -42,11 +42,26 @@ Answer them, or press Enter on an empty line to plan with what it has.
   Retry on 5xx only, or timeouts too?
   > both, cap it at three attempts
 
+This cuts into 1 Slice(s), each filed as its own issue:
+
+  1. Add a bounded retry to the orders loader  [retry]
+       Delivers: The orders loader retries a failed fetch up to three times.
+       Blocked by: nothing -- can start immediately
+       - A 5xx or a timeout is retried; a 4xx is not.
+
+Blockers are filed first, and a Slice waits for the ones it names.
+
+File these? [y/N] y
+
+Interview: 2 question(s) answered
+
 Filed issue #12: https://github.com/acme/pipelines/issues/12
+  Add a bounded retry to the orders loader
   Roster: implementer (standard)
-  Interview: 2 question(s) answered
 
-Run it with:  agentforge implement 12
+Start with:  agentforge implement 12
+
+  Cost: $0.41
 
 $ agentforge implement 12 --allow-commands
   [ok] implementer (standard) — Wrapped the fetch in a bounded retry.
@@ -127,9 +142,14 @@ without notice. See
 
 ## Install
 
-AgentForge publishes to no package index yet, so neither route below is
-`pip install agentforge-framework`. Both put the same `agentforge` command on
-your path.
+```console
+$ pip install agentforge-framework
+$ agentforge --version
+agentforge 0.2.2
+```
+
+That is the whole of it. The two routes below the naming note are for a machine
+that cannot reach PyPI, and for working on AgentForge itself.
 
 The distribution is `agentforge-framework` and it imports as
 `agentforge_framework`, because an older and larger project holds `agentforge`
@@ -143,15 +163,13 @@ other project installed, because its 0.5.0 through 0.6.5 declare an `agentforge`
 command too and whichever was installed last wins. See
 [ADR-0013](docs/adr/0013-the-name-stays-the-import-path-moves.md).
 
-**From a release wheel**, to run AgentForge against your own repositories.
-Download the wheel attached to the
-[latest release](https://github.com/yashmhatre/AgentForge/releases/latest) and
-install the file you downloaded:
+**From a release wheel**, for a machine with no route to PyPI. Every release
+attaches the same wheel and sdist that were uploaded to the index; download one
+from the [latest release](https://github.com/yashmhatre/AgentForge/releases/latest)
+and install the file:
 
 ```console
-$ pip install agentforge_framework-0.2.0-py3-none-any.whl
-$ agentforge --version
-agentforge 0.2.0
+$ pip install agentforge_framework-0.2.2-py3-none-any.whl
 ```
 
 Publishing a release is a wizard rather than a checklist:
@@ -170,6 +188,7 @@ $ cd AgentForge
 $ pip install -e ".[dev]"
 ```
 
+Step by step, with every command and flag: [docs/GUIDE.md](docs/GUIDE.md).
 What each release contains is in [CHANGELOG.md](CHANGELOG.md).
 
 ## Requirements
@@ -185,8 +204,9 @@ AgentForge never touches a model API and handles no credentials of its own. What
 
 | Command | What it does |
 | --- | --- |
-| `agentforge plan "<task>"` | Runs the Orchestrator at the `deep` tier and files an issue carrying the plan and roster. |
-| `agentforge implement <n>` | Reads Issue `<n>`, runs its Workflow on a branch, posts each Agent Result, and opens a draft PR. Add `--allow-commands` when the Workflow must execute a suite. |
+| `agentforge plan "<task>"` | Grills you on the task, writes a spec, cuts it into Slices, and files one issue per Slice carrying the plan, the roster, and the issues that block it. Add `--yes` to file without reviewing the cut. |
+| `agentforge decompose <path>` | The same pipeline over a plan document you already wrote. Use it when the plan is longer than a sentence and already lives in the repository. |
+| `agentforge implement <n>` | Reads Issue `<n>`, runs its Workflow on a branch, posts each Agent Result, and opens a draft PR. Refuses to start while an issue it declares as a blocker has not signed off; `--ignore-blockers` overrides. Add `--allow-commands` when the Workflow must execute a suite. |
 | `agentforge run [<command> args]` | Runs a chore a Plugin contributes -- `agentforge run scaffold-dbt-model orders` writes the files and exits. With no command name it lists what this repository has. No issue, no Run, no model involved. |
 | `agentforge unslop <file>` | Scans prose for machine-writing tells. Deterministic; no model involved. |
 

{agentforge_framework-0.2.0 → agentforge_framework-0.2.2}/README.md

@@ -2,7 +2,7 @@
 
 AgentForge is a standalone Python framework for coordinating specialized software agents through reusable workflows.
 
-A human states a Task. The Orchestrator files a GitHub issue carrying a frozen plan and the Roster of Roles that will execute it. `agentforge implement <n>` runs the Issue's Workflow and opens a draft pull request for a human to sign off. No workflow ever merges.
+A human states a Task. The Orchestrator grills them on it, writes a spec, cuts the spec into Slices, and files a GitHub issue for each -- every one carrying a frozen plan, the Roster of Roles that will execute it, and the issues that block it. `agentforge implement <n>` runs one Issue's Workflow and opens a draft pull request for a human to sign off. No workflow ever merges.
 
 ![An Issue carries the frozen plan and the Roster. Each Agent reads that Issue and appends its result as the Run Log. The Workflow ends at a draft pull request that only a human can merge.](docs/assets/one-issue-number.svg)
 
@@ -24,11 +24,26 @@ Answer them, or press Enter on an empty line to plan with what it has.
   Retry on 5xx only, or timeouts too?
   > both, cap it at three attempts
 
+This cuts into 1 Slice(s), each filed as its own issue:
+
+  1. Add a bounded retry to the orders loader  [retry]
+       Delivers: The orders loader retries a failed fetch up to three times.
+       Blocked by: nothing -- can start immediately
+       - A 5xx or a timeout is retried; a 4xx is not.
+
+Blockers are filed first, and a Slice waits for the ones it names.
+
+File these? [y/N] y
+
+Interview: 2 question(s) answered
+
 Filed issue #12: https://github.com/acme/pipelines/issues/12
+  Add a bounded retry to the orders loader
   Roster: implementer (standard)
-  Interview: 2 question(s) answered
 
-Run it with:  agentforge implement 12
+Start with:  agentforge implement 12
+
+  Cost: $0.41
 
 $ agentforge implement 12 --allow-commands
   [ok] implementer (standard) — Wrapped the fetch in a bounded retry.
@@ -109,9 +124,14 @@ without notice. See
 
 ## Install
 
-AgentForge publishes to no package index yet, so neither route below is
-`pip install agentforge-framework`. Both put the same `agentforge` command on
-your path.
+```console
+$ pip install agentforge-framework
+$ agentforge --version
+agentforge 0.2.2
+```
+
+That is the whole of it. The two routes below the naming note are for a machine
+that cannot reach PyPI, and for working on AgentForge itself.
 
 The distribution is `agentforge-framework` and it imports as
 `agentforge_framework`, because an older and larger project holds `agentforge`
@@ -125,15 +145,13 @@ other project installed, because its 0.5.0 through 0.6.5 declare an `agentforge`
 command too and whichever was installed last wins. See
 [ADR-0013](docs/adr/0013-the-name-stays-the-import-path-moves.md).
 
-**From a release wheel**, to run AgentForge against your own repositories.
-Download the wheel attached to the
-[latest release](https://github.com/yashmhatre/AgentForge/releases/latest) and
-install the file you downloaded:
+**From a release wheel**, for a machine with no route to PyPI. Every release
+attaches the same wheel and sdist that were uploaded to the index; download one
+from the [latest release](https://github.com/yashmhatre/AgentForge/releases/latest)
+and install the file:
 
 ```console
-$ pip install agentforge_framework-0.2.0-py3-none-any.whl
-$ agentforge --version
-agentforge 0.2.0
+$ pip install agentforge_framework-0.2.2-py3-none-any.whl
 ```
 
 Publishing a release is a wizard rather than a checklist:
@@ -152,6 +170,7 @@ $ cd AgentForge
 $ pip install -e ".[dev]"
 ```
 
+Step by step, with every command and flag: [docs/GUIDE.md](docs/GUIDE.md).
 What each release contains is in [CHANGELOG.md](CHANGELOG.md).
 
 ## Requirements
@@ -167,8 +186,9 @@ AgentForge never touches a model API and handles no credentials of its own. What
 
 | Command | What it does |
 | --- | --- |
-| `agentforge plan "<task>"` | Runs the Orchestrator at the `deep` tier and files an issue carrying the plan and roster. |
-| `agentforge implement <n>` | Reads Issue `<n>`, runs its Workflow on a branch, posts each Agent Result, and opens a draft PR. Add `--allow-commands` when the Workflow must execute a suite. |
+| `agentforge plan "<task>"` | Grills you on the task, writes a spec, cuts it into Slices, and files one issue per Slice carrying the plan, the roster, and the issues that block it. Add `--yes` to file without reviewing the cut. |
+| `agentforge decompose <path>` | The same pipeline over a plan document you already wrote. Use it when the plan is longer than a sentence and already lives in the repository. |
+| `agentforge implement <n>` | Reads Issue `<n>`, runs its Workflow on a branch, posts each Agent Result, and opens a draft PR. Refuses to start while an issue it declares as a blocker has not signed off; `--ignore-blockers` overrides. Add `--allow-commands` when the Workflow must execute a suite. |
 | `agentforge run [<command> args]` | Runs a chore a Plugin contributes -- `agentforge run scaffold-dbt-model orders` writes the files and exits. With no command name it lists what this repository has. No issue, no Run, no model involved. |
 | `agentforge unslop <file>` | Scans prose for machine-writing tells. Deterministic; no model involved. |
 

{agentforge_framework-0.2.0 → agentforge_framework-0.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "agentforge-framework"
-version = "0.2.0"
+version = "0.2.2"
 description = "A modular framework for coordinating specialized software agents."
 readme = "README.md"
 requires-python = ">=3.11"

{agentforge_framework-0.2.0 → agentforge_framework-0.2.2}/src/agentforge_framework/__init__.py

@@ -1,3 +1,3 @@
 """AgentForge — coordination of specialized software agents through reusable workflows."""
 
-__version__ = "0.2.0"
+__version__ = "0.2.2"