flux-sim-engine 0.2.0__tar.gz

flux_sim_engine-0.2.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.

flux_sim_engine-0.2.0/NOTICE

@@ -0,0 +1,10 @@
+FLUX Simulation Engine
+Copyright 2026 Agentics Transformation Limited
+
+This product includes a vendored fallback copy of `flux_spec`
+(Apache License, Version 2.0; Copyright 2026 The FLUX Project authors)
+under flux_engine/_vendor/flux_spec/ -- see that directory's own NOTICE
+and VENDOR-NOTES.md for attribution details and the exact upstream
+commit it was taken from.
+
+Third-party dependency licenses are listed in THIRD_PARTY_LICENSES.md.

flux_sim_engine-0.2.0/PKG-INFO

@@ -0,0 +1,108 @@
+Metadata-Version: 2.4
+Name: flux-sim-engine
+Version: 0.2.0
+Summary: FLUX Simulation Engine: the runtime for FLUX bundles -- deterministic, governed simulation under a referenced FLUID contract.
+Author: Agentics Transformation Ltd
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/Agenticstiger/flux-engine
+Keywords: FLUX,FLUID,simulation,synthetic data,data contracts
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+License-File: flux_engine/_vendor/flux_spec/NOTICE
+Requires-Dist: numpy<3,>=1.26
+Requires-Dist: pydantic<3,>=2.7
+Requires-Dist: pyyaml>=6
+Requires-Dist: jsonschema>=4.22
+Requires-Dist: rfc8785>=0.1
+Requires-Dist: cloudevents<3,>=1.10
+Requires-Dist: cryptography>=42
+Requires-Dist: flux-spec<0.6,>=0.5
+Provides-Extra: lineage
+Requires-Dist: openlineage-python>=1.20; extra == "lineage"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.4; extra == "dev"
+Requires-Dist: pytest-cov>=4.1; extra == "dev"
+Requires-Dist: hypothesis>=6.100; extra == "dev"
+Requires-Dist: mypy>=1.10; extra == "dev"
+Requires-Dist: ruff>=0.5; extra == "dev"
+Requires-Dist: black==26.10.1; extra == "dev"
+Requires-Dist: import-linter>=2.0; extra == "dev"
+Requires-Dist: pytest-xdist>=3.6; extra == "dev"
+Requires-Dist: pytest-timeout>=2.3; extra == "dev"
+Requires-Dist: sybil==10.1.0; extra == "dev"
+Requires-Dist: reuse[charset-normalizer]==6.3.0; extra == "dev"
+Dynamic: license-file
+
+# FLUX Simulation Engine
+
+Describe your customers and what they do in YAML, and this engine turns that into synthetic rows that follow a [FLUID](https://open-data-protocol.github.io/fluid/) data contract: the same rows every time, with a report that says plainly what the run does not show.
+
+## Try it
+
+You need [uv](https://docs.astral.sh/uv/). (Until the package is on PyPI you also need a clone of this repository and `git`: run `uv build --wheel` in the clone and pass the wheel's path after `--from` instead of the package name.)
+
+<!-- skip: next "the package is not on PyPI yet; the First run workflow runs these same commands from a built wheel" -->
+```bash
+uvx --from flux-sim-engine fluxsim init demo && cd demo && uvx --from flux-sim-engine fluxsim run . --verify --ship -o out
+```
+
+That writes a small project, runs a 500-customer simulation, checks the result and packs an evidence archive into `out/`, in a few seconds. With the command installed (`uv tool install flux-sim-engine`, or `pip install flux-sim-engine` in a virtual environment), the same two steps print this:
+
+```console
+$ fluxsim init demo
+created demo with a small FLUX bundle and its FLUID contract (10 files):
+...
+$ cd demo
+$ fluxsim run . --verify --ship -o out
+...
+emitted payment_recovery_moment: 154 rows (scenario)
+reproducible: not checked | validity: not asserted
+...
+shipped out/demo.flux.tgz
+run 8dec55892096169f complete; shipped to out
+```
+
+Open `.flux/runs/<runId>/EVIDENCE.md` first: its last section, "What Was Not Proven", lists what the run does not show. The [tutorial](docs/tutorial/first-evidence-pack.md) goes through each step.
+
+## What it is
+
+- **Repeatable.** The same bundle and the same seed give the same bytes on every system the project's CI checks (Linux and macOS, Python 3.11 to 3.13). `fluxsim replay` runs a recorded plan again and refuses unless it reaches the digest you give it.
+- **Declarative.** A bundle is YAML documents for the world, the personas, the signals, the journeys and the treatments. It refers to a FLUID contract and never restates it, so the rows have the shape the contract expects.
+- **Six steps, one command each.** `validate`, `plan`, `apply`, `run`, `verify`, `ship`. `ship` packs the bundle, the run and a manifest into one archive, writes two unsigned in-toto statements beside it, and the report inside always ends in a section called "What Was Not Proven".
+
+## What it is not
+
+- **Not evidence about the real world.** The engine reproduces the scenario you describe. Whether the scenario matches reality is a separate question, and in this release the report answers it `validity: not asserted`.
+- **Not a privacy or fairness tool.** The rows are made from the numbers you declare. The pack makes no claim about privacy, fairness or any model trained on the rows.
+- **Not finished.** The agentic tier, the sweep executor for `fidelity: stochastic`, calibration with `pyabc`, synthesis with `synthcity` and an OpenLineage transport are absent, and the engine says so instead of degrading quietly. `fluxsim describe --self` says whether the libraries behind four of them (`agentic`, `calibrate_abc`, `synth`, `lineage_transport`) are installed, and a bundle that asks for `fidelity: stochastic` is refused with an error.
+
+## Where to go next
+
+- [Tutorial](docs/tutorial/README.md): your first evidence pack in five minutes.
+- [How-to guides](docs/how-to/README.md): model customers, add a journey, use the FLUID seam, calibrate from aggregates, ship with evidence.
+- [Explanation](docs/explanation/README.md): the six-step loop, determinism and the seed tree, the seam, and what an evidence pack does not claim.
+- [Reference](docs/reference/README.md): every command, every error code, the Python API and the schemas.
+- The FLUX specification: [Agenticstiger/flux](https://github.com/Agenticstiger/flux).
+
+## Develop
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). The short version:
+
+```text
+uv sync --extra dev
+make check
+```
+
+`make check` runs the static checks and the fast tests; `make ci-local` runs every check in `.github/workflows/ci.yml`. `make docs-test` runs every page of the documentation as a test, and `make docs-gen` rewrites the generated reference pages. The decisions behind the design are in [docs/adr/](docs/adr/).
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE). Third-party components are listed in [THIRD_PARTY_LICENSES.md](THIRD_PARTY_LICENSES.md).

flux_sim_engine-0.2.0/README.md

@@ -0,0 +1,65 @@
+# FLUX Simulation Engine
+
+Describe your customers and what they do in YAML, and this engine turns that into synthetic rows that follow a [FLUID](https://open-data-protocol.github.io/fluid/) data contract: the same rows every time, with a report that says plainly what the run does not show.
+
+## Try it
+
+You need [uv](https://docs.astral.sh/uv/). (Until the package is on PyPI you also need a clone of this repository and `git`: run `uv build --wheel` in the clone and pass the wheel's path after `--from` instead of the package name.)
+
+<!-- skip: next "the package is not on PyPI yet; the First run workflow runs these same commands from a built wheel" -->
+```bash
+uvx --from flux-sim-engine fluxsim init demo && cd demo && uvx --from flux-sim-engine fluxsim run . --verify --ship -o out
+```
+
+That writes a small project, runs a 500-customer simulation, checks the result and packs an evidence archive into `out/`, in a few seconds. With the command installed (`uv tool install flux-sim-engine`, or `pip install flux-sim-engine` in a virtual environment), the same two steps print this:
+
+```console
+$ fluxsim init demo
+created demo with a small FLUX bundle and its FLUID contract (10 files):
+...
+$ cd demo
+$ fluxsim run . --verify --ship -o out
+...
+emitted payment_recovery_moment: 154 rows (scenario)
+reproducible: not checked | validity: not asserted
+...
+shipped out/demo.flux.tgz
+run 8dec55892096169f complete; shipped to out
+```
+
+Open `.flux/runs/<runId>/EVIDENCE.md` first: its last section, "What Was Not Proven", lists what the run does not show. The [tutorial](docs/tutorial/first-evidence-pack.md) goes through each step.
+
+## What it is
+
+- **Repeatable.** The same bundle and the same seed give the same bytes on every system the project's CI checks (Linux and macOS, Python 3.11 to 3.13). `fluxsim replay` runs a recorded plan again and refuses unless it reaches the digest you give it.
+- **Declarative.** A bundle is YAML documents for the world, the personas, the signals, the journeys and the treatments. It refers to a FLUID contract and never restates it, so the rows have the shape the contract expects.
+- **Six steps, one command each.** `validate`, `plan`, `apply`, `run`, `verify`, `ship`. `ship` packs the bundle, the run and a manifest into one archive, writes two unsigned in-toto statements beside it, and the report inside always ends in a section called "What Was Not Proven".
+
+## What it is not
+
+- **Not evidence about the real world.** The engine reproduces the scenario you describe. Whether the scenario matches reality is a separate question, and in this release the report answers it `validity: not asserted`.
+- **Not a privacy or fairness tool.** The rows are made from the numbers you declare. The pack makes no claim about privacy, fairness or any model trained on the rows.
+- **Not finished.** The agentic tier, the sweep executor for `fidelity: stochastic`, calibration with `pyabc`, synthesis with `synthcity` and an OpenLineage transport are absent, and the engine says so instead of degrading quietly. `fluxsim describe --self` says whether the libraries behind four of them (`agentic`, `calibrate_abc`, `synth`, `lineage_transport`) are installed, and a bundle that asks for `fidelity: stochastic` is refused with an error.
+
+## Where to go next
+
+- [Tutorial](docs/tutorial/README.md): your first evidence pack in five minutes.
+- [How-to guides](docs/how-to/README.md): model customers, add a journey, use the FLUID seam, calibrate from aggregates, ship with evidence.
+- [Explanation](docs/explanation/README.md): the six-step loop, determinism and the seed tree, the seam, and what an evidence pack does not claim.
+- [Reference](docs/reference/README.md): every command, every error code, the Python API and the schemas.
+- The FLUX specification: [Agenticstiger/flux](https://github.com/Agenticstiger/flux).
+
+## Develop
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). The short version:
+
+```text
+uv sync --extra dev
+make check
+```
+
+`make check` runs the static checks and the fast tests; `make ci-local` runs every check in `.github/workflows/ci.yml`. `make docs-test` runs every page of the documentation as a test, and `make docs-gen` rewrites the generated reference pages. The decisions behind the design are in [docs/adr/](docs/adr/).
+
+## License
+
+Apache License 2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE). Third-party components are listed in [THIRD_PARTY_LICENSES.md](THIRD_PARTY_LICENSES.md).

flux_sim_engine-0.2.0/flux_engine/__init__.py

@@ -0,0 +1,22 @@
+# Copyright 2026 Agentics Transformation Limited
+#
+# SPDX-License-Identifier: Apache-2.0
+
+"""FLUX Simulation Engine -- the runtime for FLUX bundles.
+
+The sibling of the FLUID standard and CLI (``fluid``, ``data-product-forge``):
+FLUX is the "wind tunnel" that runs a declarative simulation bundle and emits,
+under a referenced FLUID contract, the exact rows that contract will see in
+production.
+"""
+
+from __future__ import annotations
+
+from importlib import metadata as _metadata
+
+try:
+    __version__ = _metadata.version("flux-sim-engine")
+except _metadata.PackageNotFoundError:  # pragma: no cover - editable/dev tree, no metadata yet
+    __version__ = "0.2.0"
+
+__all__ = ["__version__"]

flux_sim_engine-0.2.0/flux_engine/_links.py

@@ -0,0 +1,55 @@
+# Copyright 2026 Agentics Transformation Limited
+#
+# SPDX-License-Identifier: Apache-2.0
+
+"""Where the documentation lives, in one place.
+
+Every URL the command line prints comes from here: the docs link at the foot of
+``--help``, the page a failing command points at, the support link. That is what
+keeps a printed URL stable. It is a function of a code or a command name and
+nothing else, so a page can be moved by changing one constant, and a test
+(``tests/docs/test_generated_docs.py``) holds that every URL this module builds
+names a page that exists in ``docs/``.
+
+The layout it relies on, relative to the root of these docs::
+
+    reference/cli/README.md          every command          <base>reference/cli/
+    reference/cli/<command>.md       one command            <base>reference/cli/<command>.html
+    reference/errors/README.md       every FLX code         <base>reference/errors/
+    reference/errors/FLX-nnnn.md     one code               <base>reference/errors/FLX-nnnn.html
+
+The base is the address these docs are published at. They are written in this
+repository and join the FLUX specification's site as its ``engine/`` folder. That
+site is built with VuePress at ``base: '/flux/'``, which its config locks because
+every published schema ``$id`` depends on it, so ``docs/engine/reference/errors/FLX-nnnn.md``
+there is served as ``/flux/engine/reference/errors/FLX-nnnn.html``. Until the pages
+are in the site they are not reachable: printing the address early is deliberate,
+because the address is what has to stay stable.
+
+**These addresses are public.** Every released version prints them, and a printed
+address cannot be recalled. Moving a page means leaving something behind at the
+old address. ``test_the_published_addresses_do_not_move`` in
+``tests/docs/test_generated_docs.py`` holds the literal strings, so a change to
+the base or to the layout above fails a test instead of passing quietly because
+the page and the address moved together.
+"""
+
+from __future__ import annotations
+
+__all__ = ["DOCS_URL", "ISSUES_URL", "command_url", "error_url"]
+
+#: The folder of the published site these docs live in. Ends with a slash.
+DOCS_URL = "https://agenticstiger.github.io/flux/engine/"
+
+#: Where a person reports a problem with the engine.
+ISSUES_URL = "https://github.com/Agenticstiger/flux-engine/issues"
+
+
+def error_url(code: str) -> str:
+    """The page that explains *code* (``FLX-nnnn``)."""
+    return f"{DOCS_URL}reference/errors/{code}.html"
+
+
+def command_url(command: str = "") -> str:
+    """The reference page of one top-level command, or the index when *command* is empty."""
+    return f"{DOCS_URL}reference/cli/{command}.html" if command else f"{DOCS_URL}reference/cli/"

flux_sim_engine-0.2.0/flux_engine/_vendor/__init__.py

@@ -0,0 +1,5 @@
+# Copyright 2026 Agentics Transformation Limited
+#
+# SPDX-License-Identifier: Apache-2.0
+
+"""Vendored fallback copies of third-party packages flux_engine depends on."""

flux_sim_engine-0.2.0/flux_engine/_vendor/flux_spec/NOTICE

@@ -0,0 +1,19 @@
+flux_spec (vendored copy)
+Copyright 2026 The FLUX Project authors
+
+This product includes software from the FLUX specification project
+(https://github.com/Agenticstiger/flux), licensed under the Apache
+License, Version 2.0. A copy of the License is available at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+See VENDOR-NOTES.md in this directory for the exact upstream commit this
+copy was taken from and the minimal edits applied to make the validator,
+enforcement gate, and bundler resolve their data paths from inside this
+vendored package layout instead of a checked-out FLUX repository.
+
+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.

flux_sim_engine-0.2.0/flux_engine/_vendor/flux_spec/VENDOR-NOTES.md

@@ -0,0 +1,104 @@
+# Vendor notes — `flux_engine/_vendor/flux_spec/`
+
+## Provenance
+
+Copied verbatim (byte-for-byte, then edited as listed below) from
+`Agenticstiger/flux`. The pinned commit below is the provenance; it is
+reproducible from a clone of that repository anywhere.
+
+**Upstream commit pinned:** `0181eeb21f35355c1f88bb8f06c8335493d94611`
+
+Retrieved via `git show <commit>:<path>` rather than the working tree,
+because the FLUX checkout had uncommitted, in-flight changes at copy time
+(a `feat/flux-spec-package` branch already mid-refactor into a `flux_spec/`
+package with `scripts/*.py` becoming compatibility shims — exactly the
+public-distribution work owner decision 2 describes for a later
+increment, W1). Pinning to the last commit keeps this vendor copy
+reproducible and independent of that unmerged, unstable work.
+
+Files copied, each verified byte-identical to the pinned blob before any
+edit was applied:
+
+| Vendored path | Upstream path (at the pinned commit) |
+|---|---|
+| `validate.py` | `scripts/validate.py` |
+| `enforce.py` | `scripts/enforce.py` |
+| `bundle.py` | `scripts/bundle.py` |
+| `schema/*.json` (11 files) | `schema/*.json` |
+| `vendor/fluid/*.json` (3 files) | `vendor/fluid/*.json` |
+| `vectors/enforcement-vectors.json` | `tests/enforcement-vectors.json` |
+
+`tests/test_regression.py` was read for context (not vendored — flux_engine
+has its own test suite; `test_spec_shim.py` exercises this vendored copy
+directly instead of re-running the upstream regression file).
+
+## Lines changed (minimal edits, path resolution only)
+
+No logic, control flow, or behavior was changed. Every edit is a
+`Path(__file__)`-relative constant, changed because this copy lives
+directly inside the vendored package directory instead of two levels
+below a repository root under `scripts/`.
+
+### `validate.py`
+
+```diff
+-REPO = Path(__file__).resolve().parent.parent
++REPO = Path(__file__).resolve().parent
+ FLUX_SCHEMA_PATH = REPO / "schema" / "flux-schema-latest.json"
+ FLUID_VENDOR_DIR = REPO / "vendor" / "fluid"
+```
+
+`FLUX_SCHEMA_PATH` and `FLUID_VENDOR_DIR` are unchanged — they already
+resolve correctly once `REPO` points at this directory (which now itself
+contains `schema/` and `vendor/fluid/`).
+
+Left intentionally unfixed (inert in flux_engine's usage): `main()`'s
+no-argument branch does `(REPO / "examples").iterdir()` to discover bundle
+directories for the standalone `python3 scripts/validate.py` CLI. This
+vendored copy has no `examples/` directory and `flux_engine.spec.validate`
+never calls `main()` — only `Bundle`, `canonical_digest`,
+`load_yaml_docs`, and `semver_satisfies` are imported by the shim
+(`flux_engine/spec/validate.py`). If a future increment wants the
+standalone CLI to work from this vendored copy, that branch needs its own
+fix at that time.
+
+### `enforce.py`
+
+```diff
+-REPO = Path(__file__).resolve().parent.parent
+-DEFAULT_VECTORS = REPO / "tests" / "enforcement-vectors.json"
++REPO = Path(__file__).resolve().parent
++DEFAULT_VECTORS = REPO / "vectors" / "enforcement-vectors.json"
+```
+
+The vectors file is vendored under `vectors/` (not `tests/`) per the task
+spec, so the directory segment changed along with the `.parent` count.
+
+### `bundle.py`
+
+```diff
+-REPO = Path(__file__).resolve().parent.parent
+-sys.path.insert(0, str(REPO / "scripts"))
+-from validate import Bundle, load_yaml_docs  # noqa: E402
++REPO = Path(__file__).resolve().parent
++from .validate import Bundle, load_yaml_docs  # noqa: E402
+```
+
+`validate.py` is now a sibling module inside the same Python package
+(`flux_engine._vendor.flux_spec`) rather than a same-directory *script*
+next to `bundle.py` on `sys.path`, so the `sys.path.insert` + bare
+top-level `import validate` becomes an ordinary package-relative import.
+`import sys` was dropped from the top-of-file import block because the
+removed `sys.path.insert` call was its only use in the module.
+
+`SCHEMA_PATH`, `MANIFEST_SCHEMA_PATH`, and the `-o/--out` argparse default
+(`REPO / "dist"`) are unchanged — all already resolve correctly under the
+one-level-shallower `REPO`.
+
+## License
+
+Apache License, Version 2.0. See `NOTICE` in this directory.
+
+## Provenance check (2026-09-06)
+
+All vendored JSON files are byte-identical to `origin/main` (`35d979f`) of Agenticstiger/flux; the three Python modules are identical to `origin/main` except for the path edits listed above.

flux_sim_engine-0.2.0/flux_engine/_vendor/flux_spec/__init__.py

@@ -0,0 +1,9 @@
+"""Vendored fallback copy of the ``flux_spec`` distribution (Apache-2.0).
+
+See ``NOTICE`` for attribution and ``VENDOR-NOTES.md`` for the upstream
+commit this copy was taken from and every line changed to make it resolve
+its data paths from inside this package instead of a checked-out FLUX
+repository. ``flux_engine.spec`` is the only supported entry point into
+this package from the rest of flux_engine — nothing else should import
+``flux_engine._vendor.flux_spec`` directly except to resolve a data path.
+"""