axonx 0.0.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- axonx-0.0.1/LICENSE +202 -0
- axonx-0.0.1/PKG-INFO +239 -0
- axonx-0.0.1/README.md +205 -0
- axonx-0.0.1/axon/__init__.py +7 -0
- axonx-0.0.1/axon/cli.py +258 -0
- axonx-0.0.1/axon/flows/__init__.py +5 -0
- axonx-0.0.1/axon/flows/demo_flow.py +60 -0
- axonx-0.0.1/axon/utils/__init__.py +7 -0
- axonx-0.0.1/axon/utils/dingtalk_utils.py +118 -0
- axonx-0.0.1/axon/utils/env_utils.py +32 -0
- axonx-0.0.1/axon/utils/logger_utils.py +36 -0
- axonx-0.0.1/axonx.egg-info/PKG-INFO +239 -0
- axonx-0.0.1/axonx.egg-info/SOURCES.txt +20 -0
- axonx-0.0.1/axonx.egg-info/dependency_links.txt +1 -0
- axonx-0.0.1/axonx.egg-info/entry_points.txt +2 -0
- axonx-0.0.1/axonx.egg-info/requires.txt +9 -0
- axonx-0.0.1/axonx.egg-info/top_level.txt +1 -0
- axonx-0.0.1/pyproject.toml +67 -0
- axonx-0.0.1/setup.cfg +4 -0
- axonx-0.0.1/tests/test_cli.py +78 -0
- axonx-0.0.1/tests/test_dingtalk_utils.py +121 -0
- axonx-0.0.1/tests/test_env_utils.py +47 -0
axonx-0.0.1/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 FlowLLM-AI
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
axonx-0.0.1/PKG-INFO
ADDED
|
@@ -0,0 +1,239 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: axonx
|
|
3
|
+
Version: 0.0.1
|
|
4
|
+
Summary: An extensible, Pydantic-based framework for defining, discovering, and running ordered flows.
|
|
5
|
+
Author-email: FlowLLM-AI <jinli.yl@alibaba-inc.com>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://github.com/FlowLLM-AI/Axon
|
|
8
|
+
Project-URL: Issues, https://github.com/FlowLLM-AI/Axon/issues
|
|
9
|
+
Project-URL: Repository, https://github.com/FlowLLM-AI/Axon
|
|
10
|
+
Keywords: workflow,pipeline,automation,cli,pydantic,plugins
|
|
11
|
+
Classifier: Development Status :: 3 - Alpha
|
|
12
|
+
Classifier: Intended Audience :: Developers
|
|
13
|
+
Classifier: Intended Audience :: Science/Research
|
|
14
|
+
Classifier: Operating System :: POSIX :: Linux
|
|
15
|
+
Classifier: Operating System :: MacOS
|
|
16
|
+
Classifier: Programming Language :: Python :: 3
|
|
17
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
18
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
19
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
20
|
+
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
|
|
21
|
+
Classifier: Topic :: Utilities
|
|
22
|
+
Requires-Python: >=3.11
|
|
23
|
+
Description-Content-Type: text/markdown
|
|
24
|
+
License-File: LICENSE
|
|
25
|
+
Requires-Dist: httpx>=0.28.1
|
|
26
|
+
Requires-Dist: loguru>=0.7.3
|
|
27
|
+
Requires-Dist: pydantic>=2.13.4
|
|
28
|
+
Provides-Extra: dev
|
|
29
|
+
Requires-Dist: build>=1.3.0; extra == "dev"
|
|
30
|
+
Requires-Dist: coverage>=7.10.0; extra == "dev"
|
|
31
|
+
Requires-Dist: pre-commit>=4.6.0; extra == "dev"
|
|
32
|
+
Requires-Dist: pytest>=8.4.0; extra == "dev"
|
|
33
|
+
Dynamic: license-file
|
|
34
|
+
|
|
35
|
+
<p align="center">
|
|
36
|
+
<img src="https://raw.githubusercontent.com/FlowLLM-AI/assets/main/axon/axon_logo.png" alt="Axon Logo" width="52%">
|
|
37
|
+
</p>
|
|
38
|
+
|
|
39
|
+
<p align="center">
|
|
40
|
+
<a href="https://pypi.org/project/axonx/"><img src="https://img.shields.io/pypi/v/axonx" alt="PyPI"></a>
|
|
41
|
+
<a href="https://www.python.org/"><img src="https://img.shields.io/badge/python-3.11%2B-blue" alt="Python 3.11+"></a>
|
|
42
|
+
<a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-green" alt="Apache-2.0 License"></a>
|
|
43
|
+
<a href="README_ZH.md"><img src="https://img.shields.io/badge/README-中文-orange" alt="Chinese README"></a>
|
|
44
|
+
</p>
|
|
45
|
+
|
|
46
|
+
Axon is a small, extensible framework for defining, discovering, and running ordered flows. Each flow combines a
|
|
47
|
+
strict Pydantic configuration, Python callables executed in order, a shared runtime context, and declared outputs.
|
|
48
|
+
Applications install their flows as providers and expose them through the same `axon` command.
|
|
49
|
+
|
|
50
|
+
The distribution is named `axonx`; the Python package and command are both named `axon`.
|
|
51
|
+
|
|
52
|
+
## Framework at a glance
|
|
53
|
+
|
|
54
|
+
| Layer | Contract | Responsibility |
|
|
55
|
+
|---|---|---|
|
|
56
|
+
| Configuration | `BaseConfig` | Validates typed inputs with unknown fields forbidden. |
|
|
57
|
+
| Flow | `BaseFlow` | Owns configuration, logger, shared context, steps, and outputs. |
|
|
58
|
+
| Step | `Callable[[], None]` | Performs one unit of work and reads or updates the flow context. |
|
|
59
|
+
| Registry | `@register("name")` | Maps a normalized action name to one flow class. |
|
|
60
|
+
| Discovery | `axon.flows` entry points | Imports installed provider modules so registration runs. |
|
|
61
|
+
| Runtime | `axon --action --field value` | Parses inputs, validates configuration, executes steps, and emits JSON. |
|
|
62
|
+
|
|
63
|
+
Axon deliberately keeps orchestration close to Python. A concrete list builds a fixed sequence; a generator can use
|
|
64
|
+
normal `if`, `for`, and `yield from` control flow to decide later steps after earlier steps update the context. There is
|
|
65
|
+
no separate workflow DSL or scheduler.
|
|
66
|
+
|
|
67
|
+
## Installation
|
|
68
|
+
|
|
69
|
+
Axon requires Python 3.11 or newer.
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
python -m pip install axonx
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
For framework development:
|
|
76
|
+
|
|
77
|
+
```bash
|
|
78
|
+
git clone https://github.com/FlowLLM-AI/Axon.git
|
|
79
|
+
cd Axon/packages
|
|
80
|
+
python -m pip install -e ".[dev]"
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
## Quick start
|
|
84
|
+
|
|
85
|
+
The framework includes a small `demo` flow:
|
|
86
|
+
|
|
87
|
+
```bash
|
|
88
|
+
axon --list
|
|
89
|
+
axon --demo --x 1 --y 2
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
The successful result is written to stdout as JSON:
|
|
93
|
+
|
|
94
|
+
```json
|
|
95
|
+
{"result": 3}
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
Every configuration argument is a `--field value` pair, including booleans. Hyphens in action and field names are
|
|
99
|
+
normalized to underscores. Unknown fields, duplicate fields, missing values, malformed values, and unknown actions
|
|
100
|
+
fail before flow execution.
|
|
101
|
+
|
|
102
|
+
## Define a flow
|
|
103
|
+
|
|
104
|
+
Subclass `BaseConfig` for inputs and `BaseFlow` for orchestration. Annotating `config` lets Axon infer the configuration
|
|
105
|
+
class. `build_steps()` returns or yields zero-argument callables, while `output_keys` declares which context values
|
|
106
|
+
must exist after execution.
|
|
107
|
+
|
|
108
|
+
```python
|
|
109
|
+
from collections.abc import Iterable
|
|
110
|
+
|
|
111
|
+
from axon.cli import BaseConfig, BaseFlow, Step, register
|
|
112
|
+
|
|
113
|
+
|
|
114
|
+
class GreetConfig(BaseConfig):
|
|
115
|
+
name: str
|
|
116
|
+
times: int = 1
|
|
117
|
+
|
|
118
|
+
|
|
119
|
+
@register("greet")
|
|
120
|
+
class GreetFlow(BaseFlow):
|
|
121
|
+
config: GreetConfig
|
|
122
|
+
output_keys = ("message",)
|
|
123
|
+
|
|
124
|
+
def build_steps(self) -> Iterable[Step]:
|
|
125
|
+
yield self.build_message
|
|
126
|
+
|
|
127
|
+
def build_message(self) -> None:
|
|
128
|
+
self.context["message"] = " ".join([f"hello {self.config.name}"] * self.config.times)
|
|
129
|
+
```
|
|
130
|
+
|
|
131
|
+
Import the module containing the class, then run:
|
|
132
|
+
|
|
133
|
+
```bash
|
|
134
|
+
axon --greet --name Axon --times 2
|
|
135
|
+
```
|
|
136
|
+
|
|
137
|
+
```json
|
|
138
|
+
{"message": "hello Axon hello Axon"}
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
The execution contract is intentionally small:
|
|
142
|
+
|
|
143
|
+
| Element | Rule |
|
|
144
|
+
|---|---|
|
|
145
|
+
| `config` annotation | Must resolve to a `BaseConfig` subclass. |
|
|
146
|
+
| `build_steps()` | Returns an iterable of zero-argument callables in execution order. |
|
|
147
|
+
| `self.context` | Starts with constructor keyword arguments and carries state between steps. |
|
|
148
|
+
| `output_keys` | Names required context keys and preserves their declared order in the result. |
|
|
149
|
+
| `execute()` | Runs every yielded step, then raises if any declared output is missing. |
|
|
150
|
+
|
|
151
|
+
Dynamic orchestration uses ordinary Python:
|
|
152
|
+
|
|
153
|
+
| Pattern | Expression |
|
|
154
|
+
|---|---|
|
|
155
|
+
| Task | `yield self.step` |
|
|
156
|
+
| Sequence | `yield from self.build_subsequence()` |
|
|
157
|
+
| Conditional | Use `if` while lazily yielding steps. |
|
|
158
|
+
| For each | Loop and yield a zero-argument callable; use `functools.partial` to bind arguments. |
|
|
159
|
+
|
|
160
|
+
Because a generator resumes between steps, conditions placed after a `yield` can observe context written by the
|
|
161
|
+
previous step.
|
|
162
|
+
|
|
163
|
+
## Publish a flow provider
|
|
164
|
+
|
|
165
|
+
An external package exposes its flows through the `axon.flows` entry-point group. For example, this repository's
|
|
166
|
+
[`pyproject.toml`](../pyproject.toml) connects `axon-core` to the framework with:
|
|
167
|
+
|
|
168
|
+
```toml
|
|
169
|
+
[project.entry-points."axon.flows"]
|
|
170
|
+
default = "core.default"
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
Axon imports `core.default`, whose package initialization imports the modules containing `@register(...)`. After the
|
|
174
|
+
provider is installed, its flows appear automatically:
|
|
175
|
+
|
|
176
|
+
```bash
|
|
177
|
+
axon --list
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
## Built-in flows
|
|
181
|
+
|
|
182
|
+
This table describes flows shipped by `axonx`. Provider packages should document their own flows in the same format,
|
|
183
|
+
making the catalog easy to extend as new flows are added.
|
|
184
|
+
|
|
185
|
+
| Flow | Config | Inputs | Output | Purpose |
|
|
186
|
+
|---|---|---|---|---|
|
|
187
|
+
| `demo` | `DemoConfig` | `x: int`, `y: int` | `result` | Demonstrates task, sequence, conditional, and loop-based step generation by adding two integers. |
|
|
188
|
+
|
|
189
|
+
## Utilities
|
|
190
|
+
|
|
191
|
+
The supported helpers are exported from `axon.utils`. Add one row when a new public utility is introduced so this
|
|
192
|
+
table remains the compact public catalog.
|
|
193
|
+
|
|
194
|
+
| Utility | Signature | Configuration | Behavior |
|
|
195
|
+
|---|---|---|---|
|
|
196
|
+
| `load_env` | `load_env(path=None, *, override=True) -> dict[str, str]` | Optional file path | Loads an explicit file or the nearest `.env` in the working directory or first five parents. Returns only values written to the environment. |
|
|
197
|
+
| `get_logger` | `get_logger()` | `AXON_LOG_DIR` | Lazily creates the shared Loguru INFO logger with stderr and daily rotating file sinks; file retention is seven days. |
|
|
198
|
+
| `send_dingtalk_message` | `send_dingtalk_message(title, text, msgtype="markdown", timeout=10.0) -> str` | `DINGTALK_CLIENT_ID`, `DINGTALK_CLIENT_SECRET`, `DINGTALK_CONVERSATIONS` | Sends Markdown or text through a DingTalk application robot to every configured, deduplicated conversation. |
|
|
199
|
+
|
|
200
|
+
`DINGTALK_CONVERSATIONS` must be a JSON object whose non-empty names map to non-empty conversation IDs, for example
|
|
201
|
+
`{"research":"cidxxx","operations":"cidyyy"}`. Credentials and group IDs are omitted from transport errors. Network
|
|
202
|
+
calls occur only when `send_dingtalk_message()` is invoked.
|
|
203
|
+
|
|
204
|
+
## Environment variables
|
|
205
|
+
|
|
206
|
+
Axon calls `load_env()` before CLI provider discovery, allowing provider imports to resolve environment-based defaults.
|
|
207
|
+
|
|
208
|
+
| Variable | Used by | Default | Purpose |
|
|
209
|
+
|---|---|---|---|
|
|
210
|
+
| `AXON_LOG_DIR` | Shared logger | `logs` | Directory for timestamped process log files. |
|
|
211
|
+
| `DINGTALK_CLIENT_ID` | DingTalk helper | Required on use | Application key and robot code. |
|
|
212
|
+
| `DINGTALK_CLIENT_SECRET` | DingTalk helper | Required on use | Application secret used to obtain an access token. |
|
|
213
|
+
| `DINGTALK_CONVERSATIONS` | DingTalk helper | Required on use | JSON object mapping names to group conversation IDs. |
|
|
214
|
+
|
|
215
|
+
Provider-specific variables belong in the provider's documentation rather than the framework package.
|
|
216
|
+
|
|
217
|
+
## Package layout
|
|
218
|
+
|
|
219
|
+
| Path | Contents |
|
|
220
|
+
|---|---|
|
|
221
|
+
| `axon/cli.py` | Configuration and flow bases, registry, provider discovery, argument parsing, execution, and CLI. |
|
|
222
|
+
| `axon/flows/` | Built-in flows; importing the package registers them. |
|
|
223
|
+
| `axon/utils/` | Environment, logging, and notification helpers. |
|
|
224
|
+
| `tests/` | Fast tests using temporary files and mocked network boundaries. |
|
|
225
|
+
|
|
226
|
+
## Development
|
|
227
|
+
|
|
228
|
+
```bash
|
|
229
|
+
python -m pytest -v --tb=long
|
|
230
|
+
pre-commit run --all-files
|
|
231
|
+
python -m build
|
|
232
|
+
```
|
|
233
|
+
|
|
234
|
+
Keep provider-specific business logic outside the framework. A provider may depend on `axonx`; `axonx` must not
|
|
235
|
+
depend on that provider.
|
|
236
|
+
|
|
237
|
+
## License
|
|
238
|
+
|
|
239
|
+
Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for details.
|
axonx-0.0.1/README.md
ADDED
|
@@ -0,0 +1,205 @@
|
|
|
1
|
+
<p align="center">
|
|
2
|
+
<img src="https://raw.githubusercontent.com/FlowLLM-AI/assets/main/axon/axon_logo.png" alt="Axon Logo" width="52%">
|
|
3
|
+
</p>
|
|
4
|
+
|
|
5
|
+
<p align="center">
|
|
6
|
+
<a href="https://pypi.org/project/axonx/"><img src="https://img.shields.io/pypi/v/axonx" alt="PyPI"></a>
|
|
7
|
+
<a href="https://www.python.org/"><img src="https://img.shields.io/badge/python-3.11%2B-blue" alt="Python 3.11+"></a>
|
|
8
|
+
<a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-green" alt="Apache-2.0 License"></a>
|
|
9
|
+
<a href="README_ZH.md"><img src="https://img.shields.io/badge/README-中文-orange" alt="Chinese README"></a>
|
|
10
|
+
</p>
|
|
11
|
+
|
|
12
|
+
Axon is a small, extensible framework for defining, discovering, and running ordered flows. Each flow combines a
|
|
13
|
+
strict Pydantic configuration, Python callables executed in order, a shared runtime context, and declared outputs.
|
|
14
|
+
Applications install their flows as providers and expose them through the same `axon` command.
|
|
15
|
+
|
|
16
|
+
The distribution is named `axonx`; the Python package and command are both named `axon`.
|
|
17
|
+
|
|
18
|
+
## Framework at a glance
|
|
19
|
+
|
|
20
|
+
| Layer | Contract | Responsibility |
|
|
21
|
+
|---|---|---|
|
|
22
|
+
| Configuration | `BaseConfig` | Validates typed inputs with unknown fields forbidden. |
|
|
23
|
+
| Flow | `BaseFlow` | Owns configuration, logger, shared context, steps, and outputs. |
|
|
24
|
+
| Step | `Callable[[], None]` | Performs one unit of work and reads or updates the flow context. |
|
|
25
|
+
| Registry | `@register("name")` | Maps a normalized action name to one flow class. |
|
|
26
|
+
| Discovery | `axon.flows` entry points | Imports installed provider modules so registration runs. |
|
|
27
|
+
| Runtime | `axon --action --field value` | Parses inputs, validates configuration, executes steps, and emits JSON. |
|
|
28
|
+
|
|
29
|
+
Axon deliberately keeps orchestration close to Python. A concrete list builds a fixed sequence; a generator can use
|
|
30
|
+
normal `if`, `for`, and `yield from` control flow to decide later steps after earlier steps update the context. There is
|
|
31
|
+
no separate workflow DSL or scheduler.
|
|
32
|
+
|
|
33
|
+
## Installation
|
|
34
|
+
|
|
35
|
+
Axon requires Python 3.11 or newer.
|
|
36
|
+
|
|
37
|
+
```bash
|
|
38
|
+
python -m pip install axonx
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
For framework development:
|
|
42
|
+
|
|
43
|
+
```bash
|
|
44
|
+
git clone https://github.com/FlowLLM-AI/Axon.git
|
|
45
|
+
cd Axon/packages
|
|
46
|
+
python -m pip install -e ".[dev]"
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
## Quick start
|
|
50
|
+
|
|
51
|
+
The framework includes a small `demo` flow:
|
|
52
|
+
|
|
53
|
+
```bash
|
|
54
|
+
axon --list
|
|
55
|
+
axon --demo --x 1 --y 2
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
The successful result is written to stdout as JSON:
|
|
59
|
+
|
|
60
|
+
```json
|
|
61
|
+
{"result": 3}
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
Every configuration argument is a `--field value` pair, including booleans. Hyphens in action and field names are
|
|
65
|
+
normalized to underscores. Unknown fields, duplicate fields, missing values, malformed values, and unknown actions
|
|
66
|
+
fail before flow execution.
|
|
67
|
+
|
|
68
|
+
## Define a flow
|
|
69
|
+
|
|
70
|
+
Subclass `BaseConfig` for inputs and `BaseFlow` for orchestration. Annotating `config` lets Axon infer the configuration
|
|
71
|
+
class. `build_steps()` returns or yields zero-argument callables, while `output_keys` declares which context values
|
|
72
|
+
must exist after execution.
|
|
73
|
+
|
|
74
|
+
```python
|
|
75
|
+
from collections.abc import Iterable
|
|
76
|
+
|
|
77
|
+
from axon.cli import BaseConfig, BaseFlow, Step, register
|
|
78
|
+
|
|
79
|
+
|
|
80
|
+
class GreetConfig(BaseConfig):
|
|
81
|
+
name: str
|
|
82
|
+
times: int = 1
|
|
83
|
+
|
|
84
|
+
|
|
85
|
+
@register("greet")
|
|
86
|
+
class GreetFlow(BaseFlow):
|
|
87
|
+
config: GreetConfig
|
|
88
|
+
output_keys = ("message",)
|
|
89
|
+
|
|
90
|
+
def build_steps(self) -> Iterable[Step]:
|
|
91
|
+
yield self.build_message
|
|
92
|
+
|
|
93
|
+
def build_message(self) -> None:
|
|
94
|
+
self.context["message"] = " ".join([f"hello {self.config.name}"] * self.config.times)
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
Import the module containing the class, then run:
|
|
98
|
+
|
|
99
|
+
```bash
|
|
100
|
+
axon --greet --name Axon --times 2
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
```json
|
|
104
|
+
{"message": "hello Axon hello Axon"}
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
The execution contract is intentionally small:
|
|
108
|
+
|
|
109
|
+
| Element | Rule |
|
|
110
|
+
|---|---|
|
|
111
|
+
| `config` annotation | Must resolve to a `BaseConfig` subclass. |
|
|
112
|
+
| `build_steps()` | Returns an iterable of zero-argument callables in execution order. |
|
|
113
|
+
| `self.context` | Starts with constructor keyword arguments and carries state between steps. |
|
|
114
|
+
| `output_keys` | Names required context keys and preserves their declared order in the result. |
|
|
115
|
+
| `execute()` | Runs every yielded step, then raises if any declared output is missing. |
|
|
116
|
+
|
|
117
|
+
Dynamic orchestration uses ordinary Python:
|
|
118
|
+
|
|
119
|
+
| Pattern | Expression |
|
|
120
|
+
|---|---|
|
|
121
|
+
| Task | `yield self.step` |
|
|
122
|
+
| Sequence | `yield from self.build_subsequence()` |
|
|
123
|
+
| Conditional | Use `if` while lazily yielding steps. |
|
|
124
|
+
| For each | Loop and yield a zero-argument callable; use `functools.partial` to bind arguments. |
|
|
125
|
+
|
|
126
|
+
Because a generator resumes between steps, conditions placed after a `yield` can observe context written by the
|
|
127
|
+
previous step.
|
|
128
|
+
|
|
129
|
+
## Publish a flow provider
|
|
130
|
+
|
|
131
|
+
An external package exposes its flows through the `axon.flows` entry-point group. For example, this repository's
|
|
132
|
+
[`pyproject.toml`](../pyproject.toml) connects `axon-core` to the framework with:
|
|
133
|
+
|
|
134
|
+
```toml
|
|
135
|
+
[project.entry-points."axon.flows"]
|
|
136
|
+
default = "core.default"
|
|
137
|
+
```
|
|
138
|
+
|
|
139
|
+
Axon imports `core.default`, whose package initialization imports the modules containing `@register(...)`. After the
|
|
140
|
+
provider is installed, its flows appear automatically:
|
|
141
|
+
|
|
142
|
+
```bash
|
|
143
|
+
axon --list
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
## Built-in flows
|
|
147
|
+
|
|
148
|
+
This table describes flows shipped by `axonx`. Provider packages should document their own flows in the same format,
|
|
149
|
+
making the catalog easy to extend as new flows are added.
|
|
150
|
+
|
|
151
|
+
| Flow | Config | Inputs | Output | Purpose |
|
|
152
|
+
|---|---|---|---|---|
|
|
153
|
+
| `demo` | `DemoConfig` | `x: int`, `y: int` | `result` | Demonstrates task, sequence, conditional, and loop-based step generation by adding two integers. |
|
|
154
|
+
|
|
155
|
+
## Utilities
|
|
156
|
+
|
|
157
|
+
The supported helpers are exported from `axon.utils`. Add one row when a new public utility is introduced so this
|
|
158
|
+
table remains the compact public catalog.
|
|
159
|
+
|
|
160
|
+
| Utility | Signature | Configuration | Behavior |
|
|
161
|
+
|---|---|---|---|
|
|
162
|
+
| `load_env` | `load_env(path=None, *, override=True) -> dict[str, str]` | Optional file path | Loads an explicit file or the nearest `.env` in the working directory or first five parents. Returns only values written to the environment. |
|
|
163
|
+
| `get_logger` | `get_logger()` | `AXON_LOG_DIR` | Lazily creates the shared Loguru INFO logger with stderr and daily rotating file sinks; file retention is seven days. |
|
|
164
|
+
| `send_dingtalk_message` | `send_dingtalk_message(title, text, msgtype="markdown", timeout=10.0) -> str` | `DINGTALK_CLIENT_ID`, `DINGTALK_CLIENT_SECRET`, `DINGTALK_CONVERSATIONS` | Sends Markdown or text through a DingTalk application robot to every configured, deduplicated conversation. |
|
|
165
|
+
|
|
166
|
+
`DINGTALK_CONVERSATIONS` must be a JSON object whose non-empty names map to non-empty conversation IDs, for example
|
|
167
|
+
`{"research":"cidxxx","operations":"cidyyy"}`. Credentials and group IDs are omitted from transport errors. Network
|
|
168
|
+
calls occur only when `send_dingtalk_message()` is invoked.
|
|
169
|
+
|
|
170
|
+
## Environment variables
|
|
171
|
+
|
|
172
|
+
Axon calls `load_env()` before CLI provider discovery, allowing provider imports to resolve environment-based defaults.
|
|
173
|
+
|
|
174
|
+
| Variable | Used by | Default | Purpose |
|
|
175
|
+
|---|---|---|---|
|
|
176
|
+
| `AXON_LOG_DIR` | Shared logger | `logs` | Directory for timestamped process log files. |
|
|
177
|
+
| `DINGTALK_CLIENT_ID` | DingTalk helper | Required on use | Application key and robot code. |
|
|
178
|
+
| `DINGTALK_CLIENT_SECRET` | DingTalk helper | Required on use | Application secret used to obtain an access token. |
|
|
179
|
+
| `DINGTALK_CONVERSATIONS` | DingTalk helper | Required on use | JSON object mapping names to group conversation IDs. |
|
|
180
|
+
|
|
181
|
+
Provider-specific variables belong in the provider's documentation rather than the framework package.
|
|
182
|
+
|
|
183
|
+
## Package layout
|
|
184
|
+
|
|
185
|
+
| Path | Contents |
|
|
186
|
+
|---|---|
|
|
187
|
+
| `axon/cli.py` | Configuration and flow bases, registry, provider discovery, argument parsing, execution, and CLI. |
|
|
188
|
+
| `axon/flows/` | Built-in flows; importing the package registers them. |
|
|
189
|
+
| `axon/utils/` | Environment, logging, and notification helpers. |
|
|
190
|
+
| `tests/` | Fast tests using temporary files and mocked network boundaries. |
|
|
191
|
+
|
|
192
|
+
## Development
|
|
193
|
+
|
|
194
|
+
```bash
|
|
195
|
+
python -m pytest -v --tb=long
|
|
196
|
+
pre-commit run --all-files
|
|
197
|
+
python -m build
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
Keep provider-specific business logic outside the framework. A provider may depend on `axonx`; `axonx` must not
|
|
201
|
+
depend on that provider.
|
|
202
|
+
|
|
203
|
+
## License
|
|
204
|
+
|
|
205
|
+
Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE) for details.
|