fuggers-py 0.1.0b1__tar.gz

fuggers_py-0.1.0b1/.gitattributes

@@ -0,0 +1,12 @@
+* text=auto eol=lf
+
+.github/ export-ignore
+.gitignore export-ignore
+.pre-commit-config.yaml export-ignore
+AGENTS.md export-ignore
+build/ export-ignore
+dist/ export-ignore
+private/ export-ignore
+__MACOSX/ export-ignore
+__pycache__/ export-ignore
+.DS_Store export-ignore

fuggers_py-0.1.0b1/CHANGELOG.md

@@ -0,0 +1,30 @@
+# Changelog
+
+## 0.1.0
+
+Initial release-focused cut of the Python analytics port.
+
+### Added
+
+- `core`: dates, prices, yields, spreads, calendars, day counts, and abstract curve/pricing/risk traits
+- `math`: solvers, interpolation, extrapolation, optimization, and linear algebra helpers
+- `curves`: discrete/wrapped curves, builders, calibration helpers, bumping, and multi-curve support
+- `bonds`: fixed-rate, zero-coupon, callable/putable, floating-rate, sinking-fund, index/fixing, and option-model workflows
+- `analytics`: yield, risk, spread, OAS, discount-margin, asset-swap, and YAS calculations
+- `portfolio`: holdings, ETF helpers, aggregation, stress, benchmark, credit, and key-rate tooling
+- `data`: typed ids, market/reference data, pricing specs, outputs, and in-memory research providers
+- `io`: file-backed providers, JSON codecs, SQLite-backed embedded storage, and storage/transport interfaces
+- `engine`: sync pricing router, batch pricing, curve builder, calculation graph, schedulers, market-data listener, builder, and reactive orchestration
+- deterministic examples, golden validations, benchmark harness, and release smoke coverage
+
+### Scope
+
+- This package targets Python analytics and research orchestration workflows.
+- Deterministic local adapters and notebook-friendly APIs are first-class.
+- Server runtimes, WASM, FFI bindings, MCP surfaces, and distributed service infrastructure remain out of scope for this release.
+
+### Changed
+
+- historical compatibility namespaces such as `fuggers_py.prelude`, `fuggers_py.traits`, and `fuggers_py.ext` are removed from the current public surface
+- removed the redundant top-level `fuggers_py.spreads` namespace
+- `fuggers_py.analytics.spreads` is the canonical spread namespace

fuggers_py-0.1.0b1/CODE_OF_CONDUCT.md

@@ -0,0 +1,39 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as maintainers and contributors pledge to make participation in the `fuggers-py` community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, education, socioeconomic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Being respectful of differing viewpoints and experiences.
+- Giving and accepting constructive feedback.
+- Taking responsibility for mistakes and learning from them.
+- Focusing on what is best for the project and its users.
+
+Examples of unacceptable behavior include:
+
+- Harassment, insults, or discriminatory language.
+- Trolling, personal or political attacks, or sustained disruption.
+- Publishing private information without explicit permission.
+- Any conduct that would be inappropriate in a professional setting.
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing this Code of Conduct. They may remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct, and may temporarily or permanently ban contributors for behavior they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces and when an individual is officially representing the project in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the maintainer at `skubik234@icloud.com`. Reports will be reviewed and investigated promptly and fairly.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.1.

fuggers_py-0.1.0b1/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing
+
+Thanks for contributing to `fuggers-py`.
+
+## Development setup
+
+```bash
+python -m pip install -e ".[dev,engine]"
+pre-commit install
+```
+
+The repository uses a `src/` layout. Most day-to-day work should happen against the editable install above.
+
+## Fast local checks
+
+Run these before opening or updating a pull request:
+
+```bash
+pre-commit run --all-files
+python tools/run_release_ruff.py
+mypy
+pytest -q
+```
+
+`pre-commit` is the fast path for file hygiene and Ruff checks. The explicit Ruff, mypy, and pytest commands remain the canonical CI gates.
+
+## Pull request expectations
+
+- Keep changes focused and explain the user-facing impact.
+- Add or update tests when behavior, public surface, packaging, or docs examples change.
+- Update `README.md`, `docs/`, and `CHANGELOG.md` when they would otherwise become stale.
+- Avoid broad refactors unless they are required for the task at hand.
+
+## Release process
+
+See [RELEASING.md](RELEASING.md) for the exact tag-driven release steps.
+
+## Reporting problems
+
+- Security issues: follow [SECURITY.md](SECURITY.md).
+- Community expectations: follow [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md).

fuggers_py-0.1.0b1/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 [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.

fuggers_py-0.1.0b1/MANIFEST.in

@@ -0,0 +1,12 @@
+prune .git
+prune __MACOSX
+prune build
+prune dist
+prune .hypothesis
+prune .mypy_cache
+prune .pytest_cache
+prune .ruff_cache
+
+global-exclude .DS_Store
+global-exclude *.py[cod]
+global-exclude __pycache__

fuggers_py-0.1.0b1/PKG-INFO

@@ -0,0 +1,156 @@
+Metadata-Version: 2.4
+Name: fuggers-py
+Version: 0.1.0b1
+Summary: Fixed-income analytics, market-data traits, and research-oriented engine workflows.
+Author-email: Stanislaw Kubik <skubik234@icloud.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/stanislawkubik/fuggers-py
+Project-URL: Repository, https://github.com/stanislawkubik/fuggers-py
+Project-URL: Documentation, https://github.com/stanislawkubik/fuggers-py/tree/main/docs
+Project-URL: Issues, https://github.com/stanislawkubik/fuggers-py/issues
+Project-URL: Changelog, https://github.com/stanislawkubik/fuggers-py/blob/main/CHANGELOG.md
+Keywords: fixed-income,bonds,yield-curves,quant-finance,credit,analytics
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Financial and Insurance Industry
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Topic :: Office/Business :: Financial
+Classifier: Topic :: Scientific/Engineering :: Mathematics
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: numpy>=1.26
+Provides-Extra: dev
+Requires-Dist: build>=1; extra == "dev"
+Requires-Dist: coverage[toml]>=7; extra == "dev"
+Requires-Dist: hypothesis>=6; extra == "dev"
+Requires-Dist: jupytext>=1.16; extra == "dev"
+Requires-Dist: mypy>=1.14; extra == "dev"
+Requires-Dist: nbformat>=5.10; extra == "dev"
+Requires-Dist: pre-commit>=4; extra == "dev"
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-asyncio>=0.23; extra == "dev"
+Requires-Dist: pytest-cov>=5; extra == "dev"
+Requires-Dist: ruff<0.16,>=0.15.6; extra == "dev"
+Provides-Extra: engine
+Requires-Dist: croniter>=2; extra == "engine"
+Dynamic: license-file
+
+# fuggers-py
+
+`fuggers-py` is a Python library for fixed-income analytics. It is organized as a native Python package with explicit submodules for domain models, analytics, data, I/O, and engine workflows.
+
+## Package layout
+
+- `fuggers_py.core`: dates, prices, yields, spreads, calendars, day counts, base errors, interfaces
+- `fuggers_py.math`: root finding, interpolation, extrapolation, optimization, linear algebra
+- `fuggers_py.curves`: discount and credit curves, builders, calibration, bumping, multicurve tools
+- `fuggers_py.bonds`: bond instruments, conventions, schedules, pricing helpers, options
+- `fuggers_py.analytics`: yield, spread, risk, pricing, and YAS-style calculations
+- `fuggers_py.portfolio`: aggregate analytics, benchmarking, contribution, liquidity, stress, ETF workflows
+- `fuggers_py.data`: identifiers, market data, reference data, pricing specs, output records
+- `fuggers_py.io`: file adapters, JSON codecs, SQLite-backed storage, storage and transport interfaces
+- `fuggers_py.engine`: pricing router, reactive engine, schedulers, engine configuration
+
+Canonical usage is explicit submodule imports. The package no longer exposes `prelude`, `traits`, or `ext` namespaces.
+
+## Public API policy
+
+- Use package roots such as `fuggers_py.analytics`, `fuggers_py.bonds`, and `fuggers_py.io` for common entry points.
+- Import specialized exception subclasses from plural `errors` modules such as `fuggers_py.analytics.errors` and `fuggers_py.data.errors`.
+- Deprecated compatibility aliases may remain temporarily, but they are not part of the stable long-term surface.
+
+## Installation
+
+```bash
+pip install fuggers-py
+pip install "fuggers-py[dev]"
+pip install "fuggers-py[engine]"
+```
+
+## Quickstart
+
+```python
+from decimal import Decimal
+
+from fuggers_py.analytics import yield_to_maturity
+from fuggers_py.bonds import FixedBondBuilder
+from fuggers_py.core import Currency, Date, Frequency, Price
+
+settlement = Date.from_ymd(2026, 1, 15)
+bond = (
+    FixedBondBuilder.new()
+    .with_issue_date(Date.from_ymd(2024, 1, 15))
+    .with_maturity_date(Date.from_ymd(2031, 1, 15))
+    .with_coupon_rate(Decimal("0.0450"))
+    .with_frequency(Frequency.SEMI_ANNUAL)
+    .with_currency(Currency.USD)
+    .build()
+)
+
+clean_price = Price.new(Decimal("101.25"), Currency.USD)
+ytm = yield_to_maturity(bond, clean_price, settlement)
+print(ytm.as_percentage())
+```
+
+## Engine and data workflows
+
+```python
+from fuggers_py.core import Date
+from fuggers_py.data import MarketDataProvider, ReferenceDataProvider
+from fuggers_py.engine import PricingEngineBuilder
+
+engine = (
+    PricingEngineBuilder.new()
+    .with_market_data_provider(MarketDataProvider())
+    .with_reference_data_provider(ReferenceDataProvider())
+    .with_settlement_date(Date.from_ymd(2026, 3, 13))
+    .build()
+)
+
+assert engine.reactive_engine is not None
+```
+
+## Testing
+
+```bash
+python -m pip install -e ".[dev,engine]"
+pytest -q
+```
+
+The test suite includes deterministic validation fixtures under `tests/validation/` and a pinned external-reference corpus under `tests/fixtures/golden/validation_corpus.json`.
+
+## Community
+
+- Contributor guide: [CONTRIBUTING.md](CONTRIBUTING.md)
+- Code of conduct: [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)
+- Security reporting: [SECURITY.md](SECURITY.md)
+
+## Examples
+
+Examples live under `examples/` as paired `.py` and `.ipynb` files. A good starting set is:
+
+- `examples/public_api_surface_examples.ipynb`
+- `examples/data_provider_surface_examples.ipynb`
+- `examples/io_file_and_storage_examples.ipynb`
+- `examples/engine_reactive_examples.ipynb`
+- `examples/portfolio_etf_surface_examples.ipynb`
+
+## Docs
+
+- `docs/CORE_DOCS.md`
+- `docs/MATH_DOCS.md`
+- `docs/CURVES_DOCS.md`
+- `docs/BONDS_DOCS.md`
+- `docs/ANALYTICS_DOCS.md`
+- `docs/PORTFOLIO_DOCS.md`
+- `docs/DATA_DOCS.md`
+- `docs/IO_DOCS.md`
+- `docs/ENGINE_DOCS.md`
+- `docs/ARCHITECTURE.md`
+- `docs/validation_strategy.md`

fuggers_py-0.1.0b1/README.md

@@ -0,0 +1,113 @@
+# fuggers-py
+
+`fuggers-py` is a Python library for fixed-income analytics. It is organized as a native Python package with explicit submodules for domain models, analytics, data, I/O, and engine workflows.
+
+## Package layout
+
+- `fuggers_py.core`: dates, prices, yields, spreads, calendars, day counts, base errors, interfaces
+- `fuggers_py.math`: root finding, interpolation, extrapolation, optimization, linear algebra
+- `fuggers_py.curves`: discount and credit curves, builders, calibration, bumping, multicurve tools
+- `fuggers_py.bonds`: bond instruments, conventions, schedules, pricing helpers, options
+- `fuggers_py.analytics`: yield, spread, risk, pricing, and YAS-style calculations
+- `fuggers_py.portfolio`: aggregate analytics, benchmarking, contribution, liquidity, stress, ETF workflows
+- `fuggers_py.data`: identifiers, market data, reference data, pricing specs, output records
+- `fuggers_py.io`: file adapters, JSON codecs, SQLite-backed storage, storage and transport interfaces
+- `fuggers_py.engine`: pricing router, reactive engine, schedulers, engine configuration
+
+Canonical usage is explicit submodule imports. The package no longer exposes `prelude`, `traits`, or `ext` namespaces.
+
+## Public API policy
+
+- Use package roots such as `fuggers_py.analytics`, `fuggers_py.bonds`, and `fuggers_py.io` for common entry points.
+- Import specialized exception subclasses from plural `errors` modules such as `fuggers_py.analytics.errors` and `fuggers_py.data.errors`.
+- Deprecated compatibility aliases may remain temporarily, but they are not part of the stable long-term surface.
+
+## Installation
+
+```bash
+pip install fuggers-py
+pip install "fuggers-py[dev]"
+pip install "fuggers-py[engine]"
+```
+
+## Quickstart
+
+```python
+from decimal import Decimal
+
+from fuggers_py.analytics import yield_to_maturity
+from fuggers_py.bonds import FixedBondBuilder
+from fuggers_py.core import Currency, Date, Frequency, Price
+
+settlement = Date.from_ymd(2026, 1, 15)
+bond = (
+    FixedBondBuilder.new()
+    .with_issue_date(Date.from_ymd(2024, 1, 15))
+    .with_maturity_date(Date.from_ymd(2031, 1, 15))
+    .with_coupon_rate(Decimal("0.0450"))
+    .with_frequency(Frequency.SEMI_ANNUAL)
+    .with_currency(Currency.USD)
+    .build()
+)
+
+clean_price = Price.new(Decimal("101.25"), Currency.USD)
+ytm = yield_to_maturity(bond, clean_price, settlement)
+print(ytm.as_percentage())
+```
+
+## Engine and data workflows
+
+```python
+from fuggers_py.core import Date
+from fuggers_py.data import MarketDataProvider, ReferenceDataProvider
+from fuggers_py.engine import PricingEngineBuilder
+
+engine = (
+    PricingEngineBuilder.new()
+    .with_market_data_provider(MarketDataProvider())
+    .with_reference_data_provider(ReferenceDataProvider())
+    .with_settlement_date(Date.from_ymd(2026, 3, 13))
+    .build()
+)
+
+assert engine.reactive_engine is not None
+```
+
+## Testing
+
+```bash
+python -m pip install -e ".[dev,engine]"
+pytest -q
+```
+
+The test suite includes deterministic validation fixtures under `tests/validation/` and a pinned external-reference corpus under `tests/fixtures/golden/validation_corpus.json`.
+
+## Community
+
+- Contributor guide: [CONTRIBUTING.md](CONTRIBUTING.md)
+- Code of conduct: [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md)
+- Security reporting: [SECURITY.md](SECURITY.md)
+
+## Examples
+
+Examples live under `examples/` as paired `.py` and `.ipynb` files. A good starting set is:
+
+- `examples/public_api_surface_examples.ipynb`
+- `examples/data_provider_surface_examples.ipynb`
+- `examples/io_file_and_storage_examples.ipynb`
+- `examples/engine_reactive_examples.ipynb`
+- `examples/portfolio_etf_surface_examples.ipynb`
+
+## Docs
+
+- `docs/CORE_DOCS.md`
+- `docs/MATH_DOCS.md`
+- `docs/CURVES_DOCS.md`
+- `docs/BONDS_DOCS.md`
+- `docs/ANALYTICS_DOCS.md`
+- `docs/PORTFOLIO_DOCS.md`
+- `docs/DATA_DOCS.md`
+- `docs/IO_DOCS.md`
+- `docs/ENGINE_DOCS.md`
+- `docs/ARCHITECTURE.md`
+- `docs/validation_strategy.md`

fuggers_py-0.1.0b1/RELEASING.md

@@ -0,0 +1,48 @@
+# Releasing
+
+## Private beta from a local wheel
+
+```bash
+python -m build
+python -m venv /tmp/fuggers-beta-venv
+/tmp/fuggers-beta-venv/bin/pip install --upgrade pip
+/tmp/fuggers-beta-venv/bin/pip install dist/fuggers_py-*.whl
+/tmp/fuggers-beta-venv/bin/python -c "import fuggers_py; print(fuggers_py.__version__)"
+```
+
+Share the wheel in `dist/` for private testers, or install it directly the same way on their machines.
+
+## One-time PyPI Trusted Publisher setup
+
+1. Make the GitHub repository public.
+2. In the PyPI project settings for `fuggers-py`, add a GitHub Trusted Publisher with:
+   - owner: `stanislawkubik`
+   - repository: `fuggers-py`
+   - workflow file: `release.yml`
+3. Leave the GitHub environment field empty. The workflow does not use one.
+
+## First public release
+
+1. Ensure `main` is ready and CI is green.
+2. Push the release tag:
+
+```bash
+git tag v0.1.0
+git push origin v0.1.0
+```
+
+3. GitHub Actions runs `release.yml`, builds the distributions, smoke-tests them, and publishes to PyPI.
+
+`setuptools_scm` maps the Git tag `v0.1.0` to the package version `0.1.0`.
+
+## Subsequent releases
+
+1. Update `CHANGELOG.md` as needed.
+2. Push the next tag, for example:
+
+```bash
+git tag v0.1.1
+git push origin v0.1.1
+```
+
+No packaging-file edits should be required for later releases.

fuggers_py-0.1.0b1/SECURITY.md

@@ -0,0 +1,18 @@
+# Security Policy
+
+## Supported Versions
+
+Security fixes are applied to the latest released version on PyPI and, when needed, to the current default branch.
+
+## Reporting a Vulnerability
+
+Please do not open public GitHub issues for suspected vulnerabilities.
+
+Report security issues to `skubik234@icloud.com` with:
+
+- a short description of the issue
+- affected versions or commit range
+- reproduction steps or a proof of concept
+- any suggested mitigations if you have them
+
+The maintainer will acknowledge receipt, investigate, and coordinate a fix and disclosure timeline.