graphon 0.1.0__tar.gz

graphon-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 LangGenius, Inc.
+
+   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.

graphon-0.1.0/PKG-INFO

@@ -0,0 +1,270 @@
+Metadata-Version: 2.4
+Name: graphon
+Version: 0.1.0
+Summary: Graph execution engine for agentic AI workflows.
+License-Expression: Apache-2.0
+License-File: LICENSE
+Requires-Dist: charset-normalizer>=3.4.4
+Requires-Dist: httpx~=0.28.0
+Requires-Dist: json-repair>=0.55.1
+Requires-Dist: jsonschema>=4.25.1
+Requires-Dist: orjson>=3.10.0,<4.0.0
+Requires-Dist: pandas[excel]~=3.0.1
+Requires-Dist: pydantic~=2.12.5
+Requires-Dist: pydantic-extra-types~=2.11.0
+Requires-Dist: pypdfium2==5.6.0
+Requires-Dist: python-docx~=1.2.0
+Requires-Dist: pyyaml~=6.0.1
+Requires-Dist: tiktoken~=0.12.0
+Requires-Dist: transformers~=5.3.0
+Requires-Dist: typing-extensions>=4.10.0
+Requires-Dist: unstructured[docx,epub,md,ppt,pptx]~=0.21.5
+Requires-Dist: pypandoc~=1.13
+Requires-Dist: webvtt-py~=0.5.1
+Requires-Python: >=3.11
+Project-URL: source, https://github.com/langgenius/graphon
+Project-URL: homepage, https://github.com/langgenius/graphon
+Project-URL: issues, https://github.com/langgenius/graphon/issues
+Description-Content-Type: text/markdown
+
+# Graphon (Under Construction)
+
+This repository is still being organized.
+
+## Development Workflow
+
+By default, use `make` for routine development commands in this repository.
+
+That is the recommended path because:
+
+- it reflects the repository's intended workflow
+- it keeps formatting, linting, and testing commands consistent
+- it reduces command drift across contributors and CI
+
+If you know exactly what you are doing, using `ruff`, `pytest`, or `prek` directly is still your choice. Those tools remain fully available, but they should be treated as the lower-level interface rather than the default one.
+
+## Commit and PR Title Convention
+
+All commit messages must follow the
+[Conventional Commits](https://www.conventionalcommits.org/) specification.
+
+This is a repository requirement, not a suggestion.
+
+The required commit types are:
+
+- `feat`
+- `fix`
+- `docs`
+- `style`
+- `refactor`
+- `perf`
+- `test`
+- `build`
+- `ci`
+- `chore`
+- `revert`
+
+Use the Conventional Commits structure consistently, for example:
+
+```text
+feat: add graph snapshot export
+fix(runtime): avoid duplicate node completion events
+docs(readme): document development workflow
+refactor(variable-pool): simplify selector lookup
+test(encoders): cover nested dataclass encoding
+feat!: drop legacy workflow payload format
+refactor(api)!: remove deprecated runtime entrypoint
+```
+
+Pull request titles must follow the exact same convention.
+
+If a change is breaking, the commit message and the PR title must include `!`.
+
+Examples:
+
+```text
+feat!: remove deprecated graph initialization path
+fix(parser)!: change selector parsing semantics
+```
+
+In other words:
+
+- every commit message should use Conventional Commits
+- every PR title should also use Conventional Commits
+- every breaking change must be marked with `!`
+- the PR title must stay aligned with the final change being merged
+
+Do not use free-form PR titles that diverge from the commit message standard.
+
+## Quick Start
+
+### Prerequisites
+
+- `uv`
+- `make`
+- `git`
+
+### Initial Setup
+
+This project uses `uv` for dependency and virtual environment management.
+
+```bash
+make dev
+source .venv/bin/activate
+```
+
+`make dev` will:
+
+- run `uv sync`
+- ensure `prek` hooks are installed
+
+After that, the repository will have a local `.venv`, the project will be installed in editable mode, and Git hooks will be ready.
+
+## Recommended Commands
+
+Use these commands by default:
+
+```bash
+make dev
+make format
+make lint
+make check
+make test
+make pre
+```
+
+What they do:
+
+- `make dev`: run `uv sync` and ensure `prek` is installed
+- `make format`: run `ruff format`
+- `make lint`: run `ruff check --fix`
+- `make check`: run `ruff format --check && ruff check`
+- `make test`: run `uv run --frozen pytest`
+- `make pre`: run `format`, `lint`, and `test` in sequence
+
+Additional targets:
+
+- `make build`: build the package
+- `make clean`: remove build artifacts, caches, and `__pycache__`
+
+## Recommended Daily Flow
+
+For normal development, the expected flow is:
+
+```bash
+make dev
+make pre
+```
+
+For day-to-day iteration, the usual commands are:
+
+```bash
+make format
+make lint
+make test
+```
+
+## Tooling Details
+
+### `uv`
+
+`uv` is responsible for environment and dependency management.
+
+Common commands:
+
+```bash
+uv sync
+uv run pytest
+uv run ruff check
+uv run prek run -a
+```
+
+Use `uv` when you need to:
+
+- create or refresh the local virtual environment
+- install project and development dependencies
+- run low-level commands without activating `.venv`
+
+### `make`
+
+`make` is the default command surface for this repository.
+
+If you are unsure which command to use, start with `make`.
+
+This is especially true for:
+
+- initial setup
+- formatting
+- linting
+- running the test suite
+- running the standard pre-check flow
+
+### `ruff`
+
+`ruff` handles both formatting and linting.
+
+Direct usage is supported, but it is secondary to `make`.
+
+Common direct commands:
+
+```bash
+ruff format
+ruff check --fix
+ruff format --check
+ruff check
+```
+
+Prefer direct `ruff` usage when:
+
+- you want to target a specific file or rule
+- you are debugging a particular lint issue
+- you intentionally want something more precise than the `Makefile` wrapper
+
+### `pytest`
+
+`pytest` runs the test suite.
+
+Common direct commands:
+
+```bash
+uv run pytest
+uv run pytest tests
+uv run pytest tests/utils/test_condition_processor.py
+uv run pytest -k condition
+```
+
+Notes:
+
+- the current default configuration includes `-n auto`
+- `testpaths` is set to `tests`
+- `make test` is the default wrapper and should be preferred unless you need a more specific invocation
+
+### `prek`
+
+`prek` manages Git hooks for this repository. Its configuration is stored in `prek.toml`.
+
+Common direct commands:
+
+```bash
+uv run prek install
+uv run prek run -a
+uv run prek list
+uv run prek validate-config
+```
+
+Notes:
+
+- `uv run prek install`: install Git hooks into `.git/hooks/`
+- `uv run prek run -a`: run hooks against all files in the repository
+- the current configuration mainly includes:
+  - built-in cleanup and validation hooks
+  - local `make format` / `make lint` hooks
+
+## Direct Tool Usage
+
+If you know what you are doing, direct tool usage is completely acceptable.
+
+The important distinction is:
+
+- default recommendation: use `make`
+- advanced or targeted usage: use `ruff`, `pytest`, or `prek` directly

graphon-0.1.0/README.md

@@ -0,0 +1,241 @@
+# Graphon (Under Construction)
+
+This repository is still being organized.
+
+## Development Workflow
+
+By default, use `make` for routine development commands in this repository.
+
+That is the recommended path because:
+
+- it reflects the repository's intended workflow
+- it keeps formatting, linting, and testing commands consistent
+- it reduces command drift across contributors and CI
+
+If you know exactly what you are doing, using `ruff`, `pytest`, or `prek` directly is still your choice. Those tools remain fully available, but they should be treated as the lower-level interface rather than the default one.
+
+## Commit and PR Title Convention
+
+All commit messages must follow the
+[Conventional Commits](https://www.conventionalcommits.org/) specification.
+
+This is a repository requirement, not a suggestion.
+
+The required commit types are:
+
+- `feat`
+- `fix`
+- `docs`
+- `style`
+- `refactor`
+- `perf`
+- `test`
+- `build`
+- `ci`
+- `chore`
+- `revert`
+
+Use the Conventional Commits structure consistently, for example:
+
+```text
+feat: add graph snapshot export
+fix(runtime): avoid duplicate node completion events
+docs(readme): document development workflow
+refactor(variable-pool): simplify selector lookup
+test(encoders): cover nested dataclass encoding
+feat!: drop legacy workflow payload format
+refactor(api)!: remove deprecated runtime entrypoint
+```
+
+Pull request titles must follow the exact same convention.
+
+If a change is breaking, the commit message and the PR title must include `!`.
+
+Examples:
+
+```text
+feat!: remove deprecated graph initialization path
+fix(parser)!: change selector parsing semantics
+```
+
+In other words:
+
+- every commit message should use Conventional Commits
+- every PR title should also use Conventional Commits
+- every breaking change must be marked with `!`
+- the PR title must stay aligned with the final change being merged
+
+Do not use free-form PR titles that diverge from the commit message standard.
+
+## Quick Start
+
+### Prerequisites
+
+- `uv`
+- `make`
+- `git`
+
+### Initial Setup
+
+This project uses `uv` for dependency and virtual environment management.
+
+```bash
+make dev
+source .venv/bin/activate
+```
+
+`make dev` will:
+
+- run `uv sync`
+- ensure `prek` hooks are installed
+
+After that, the repository will have a local `.venv`, the project will be installed in editable mode, and Git hooks will be ready.
+
+## Recommended Commands
+
+Use these commands by default:
+
+```bash
+make dev
+make format
+make lint
+make check
+make test
+make pre
+```
+
+What they do:
+
+- `make dev`: run `uv sync` and ensure `prek` is installed
+- `make format`: run `ruff format`
+- `make lint`: run `ruff check --fix`
+- `make check`: run `ruff format --check && ruff check`
+- `make test`: run `uv run --frozen pytest`
+- `make pre`: run `format`, `lint`, and `test` in sequence
+
+Additional targets:
+
+- `make build`: build the package
+- `make clean`: remove build artifacts, caches, and `__pycache__`
+
+## Recommended Daily Flow
+
+For normal development, the expected flow is:
+
+```bash
+make dev
+make pre
+```
+
+For day-to-day iteration, the usual commands are:
+
+```bash
+make format
+make lint
+make test
+```
+
+## Tooling Details
+
+### `uv`
+
+`uv` is responsible for environment and dependency management.
+
+Common commands:
+
+```bash
+uv sync
+uv run pytest
+uv run ruff check
+uv run prek run -a
+```
+
+Use `uv` when you need to:
+
+- create or refresh the local virtual environment
+- install project and development dependencies
+- run low-level commands without activating `.venv`
+
+### `make`
+
+`make` is the default command surface for this repository.
+
+If you are unsure which command to use, start with `make`.
+
+This is especially true for:
+
+- initial setup
+- formatting
+- linting
+- running the test suite
+- running the standard pre-check flow
+
+### `ruff`
+
+`ruff` handles both formatting and linting.
+
+Direct usage is supported, but it is secondary to `make`.
+
+Common direct commands:
+
+```bash
+ruff format
+ruff check --fix
+ruff format --check
+ruff check
+```
+
+Prefer direct `ruff` usage when:
+
+- you want to target a specific file or rule
+- you are debugging a particular lint issue
+- you intentionally want something more precise than the `Makefile` wrapper
+
+### `pytest`
+
+`pytest` runs the test suite.
+
+Common direct commands:
+
+```bash
+uv run pytest
+uv run pytest tests
+uv run pytest tests/utils/test_condition_processor.py
+uv run pytest -k condition
+```
+
+Notes:
+
+- the current default configuration includes `-n auto`
+- `testpaths` is set to `tests`
+- `make test` is the default wrapper and should be preferred unless you need a more specific invocation
+
+### `prek`
+
+`prek` manages Git hooks for this repository. Its configuration is stored in `prek.toml`.
+
+Common direct commands:
+
+```bash
+uv run prek install
+uv run prek run -a
+uv run prek list
+uv run prek validate-config
+```
+
+Notes:
+
+- `uv run prek install`: install Git hooks into `.git/hooks/`
+- `uv run prek run -a`: run hooks against all files in the repository
+- the current configuration mainly includes:
+  - built-in cleanup and validation hooks
+  - local `make format` / `make lint` hooks
+
+## Direct Tool Usage
+
+If you know what you are doing, direct tool usage is completely acceptable.
+
+The important distinction is:
+
+- default recommendation: use `make`
+- advanced or targeted usage: use `ruff`, `pytest`, or `prek` directly