unicode-fol-kit 0.3.0__tar.gz → 0.4.0__tar.gz

{unicode_fol_kit-0.3.0 → unicode_fol_kit-0.4.0}/.gitignore

@@ -1,182 +1,182 @@
-# Byte-compiled / optimized / DLL files
-__pycache__/
-*.py[cod]
-*$py.class
-
-# C extensions
-*.so
-
-# Distribution / packaging
-.Python
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-wheels/
-share/python-wheels/
-*.egg-info/
-.installed.cfg
-*.egg
-MANIFEST
-
-# PyInstaller
-#  Usually these files are written by a python script from a template
-#  before PyInstaller builds the exe, so as to inject date/other infos into it.
-*.manifest
-*.spec
-
-# Installer logs
-pip-log.txt
-pip-delete-this-directory.txt
-
-# Unit test / coverage reports
-htmlcov/
-.tox/
-.nox/
-.coverage
-.coverage.*
-.cache
-nosetests.xml
-coverage.xml
-*.cover
-*.py,cover
-.hypothesis/
-.pytest_cache/
-cover/
-
-# Translations
-*.mo
-*.pot
-
-# Django stuff:
-*.log
-local_settings.py
-db.sqlite3
-db.sqlite3-journal
-
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
-# PyBuilder
-.pybuilder/
-target/
-
-# Jupyter Notebook
-.ipynb_checkpoints
-
-# IPython
-profile_default/
-ipython_config.py
-
-# pyenv
-#   For a library or package, you might want to ignore these files since the code is
-#   intended to run in multiple environments; otherwise, check them in:
-# .python-version
-
-# pipenv
-#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
-#   However, in case of collaboration, if having platform-specific dependencies or dependencies
-#   having no cross-platform support, pipenv may install dependencies that don't work, or not
-#   install all needed dependencies.
-#Pipfile.lock
-
-# UV
-#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#uv.lock
-
-# poetry
-#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-#poetry.lock
-
-# pdm
-#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#pdm.lock
-#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
-#   in version control.
-#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
-.pdm.toml
-.pdm-python
-.pdm-build/
-
-# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
-__pypackages__/
-
-# Celery stuff
-celerybeat-schedule
-celerybeat.pid
-
-# SageMath parsed files
-*.sage.py
-
-# Environments
-.env
-.venv
-env/
-venv/
-ENV/
-env.bak/
-venv.bak/
-
-# Spyder project settings
-.spyderproject
-.spyproject
-
-# Rope project settings
-.ropeproject
-
-# mkdocs documentation
-/site
-
-# mypy
-.mypy_cache/
-.dmypy.json
-dmypy.json
-
-# Pyre type checker
-.pyre/
-
-# pytype static type analyzer
-.pytype/
-
-# Cython debug symbols
-cython_debug/
-
-# PyCharm
-#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
-#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
-#  and can be added to the global gitignore or merged into this file.  For a more nuclear
-#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
-#.idea/
-
-# Ruff stuff:
-.ruff_cache/
-
-# PyPI configuration file
-.pypirc
-
-# Cursor  
-#  Cursor is an AI-powered code editor.`.cursorignore` specifies files/directories to 
-#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
-#  refer to https://docs.cursor.com/context/ignore-files
-.cursorignore
-.cursorindexingignore
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Cursor  
+#  Cursor is an AI-powered code editor.`.cursorignore` specifies files/directories to 
+#  exclude from AI features like autocomplete and code analysis. Recommended for sensitive data
+#  refer to https://docs.cursor.com/context/ignore-files
+.cursorignore
+.cursorindexingignore
 .claude

unicode_fol_kit-0.4.0/CHANGELOG.md

@@ -0,0 +1,98 @@
+# Changelog
+
+All notable changes to this project are documented in this file. The format is
+loosely based on [Keep a Changelog](https://keepachangelog.com/). Versioning is
+semantic, but the project is pre-1.0 (alpha): a **minor** release may contain
+breaking changes.
+
+## [0.4.0] - 2026-06-23
+
+A large feature release adding model-theoretic and many-valued semantics, an
+in-process theorem prover, more solver back-ends, and lambda/normal-form tooling,
+plus a set of correctness fixes. **Includes one breaking change** (see *Changed*).
+
+### Added
+
+- **Tarskian model theory** (`unicode_fol_kit.semantics.tarski`): define a
+  `Structure` (a "world" with a domain of individuals and interpretations of
+  constants, functions, predicates, and — for MSFOL — sorts) and compute a
+  formula's truth value with `satisfies()` / `models()` / `term_value()`.
+  Equality is built in; sorted quantifiers range over their sort universe.
+- **Łukasiewicz fuzzy evaluator** (`fuzzy_evaluate`): the truth degree in [0, 1]
+  of an FL/MSFL formula under a valuation (`∀` = inf, `∃` = sup).
+- **Fuzzy satisfiability / validity** via Z3 reals: `fuzzy_is_satisfiable`,
+  `fuzzy_is_valid`, `fuzzy_get_model`, `degree_expr`.
+- **Arithmetic-aware Z3 translation**: `to_z3_arith`, `is_satisfiable_arith`,
+  `is_valid_arith`, `get_model_arith` interpret `+ - * /` and the comparisons
+  over Z3 reals/integers (the default `to_z3` keeps them uninterpreted).
+- **Built-in first-order resolution prover** (`unicode_fol_kit.atp.resolution`):
+  `prove`, `is_valid_resolution`, `to_clauses`, `refute` — sound entailment and
+  validity checking in-process, without an external prover. Deliberately
+  incomplete under a step bound (never reports a non-theorem as proved);
+  `=` is treated as an uninterpreted predicate.
+- **Lambda tooling**: `eliminate_lambdas` (beta-eta normalise and verify
+  lambda-free), `reduce_trace`, `beta_reduce_step`, `has_lambdas`.
+- **Normal forms**: `to_dnf` (equivalence-preserving) and `to_tseitin_cnf`
+  (equisatisfiable, avoids the distributive blow-up).
+- **Robinson unification**: `unify` (most general unifier with occurs-check) and
+  `apply_subst`.
+- **Command-line interface**: `python -m unicode_fol_kit "<formula>" --mode … --to …`.
+- **Typing**: a `py.typed` marker (PEP 561).
+- **AST helper**: `Node.map_children`, the single structural-recursion engine.
+
+### Changed
+
+- **BREAKING — AST nodes are now frozen dataclasses.** Every node is immutable
+  and **hashable**, so nodes can be put in sets, used as dict keys, and
+  deduplicated.
+- **BREAKING — `Function.args` and `Atom.args` are now `tuple`s, not `list`s.**
+  Construction stays lenient: a list passed to the constructor is coerced to a
+  tuple, so `Atom("P", [x])` still works and `node == node` comparisons are
+  unaffected. Code that relied on `.args` being a *list* (in-place mutation,
+  `isinstance(node.args, list)`, or comparing `node.args == [...]`) must switch
+  to tuples.
+
+### Fixed
+
+- `Xor.to_tptp` emitted `~|` (TPTP **NOR**); now emits `<~>` (correct XOR /
+  non-equivalence).
+- TPTP arithmetic comparisons (`<`, `>`, `≤`, `≥`) are now emitted as prefix
+  dollar-word predicates (`$less(a, b)`), not as invalid infix expressions.
+- Prover9 export: quantified variables are uppercased to match the emitted
+  `set(prolog_style_variables)`; nullary predicates render as bare propositional
+  atoms instead of the invalid `P()`.
+- `to_latex` escapes the underscore in `c_`-prefixed constants (otherwise read as
+  a LaTeX subscript).
+- Prover9 entailment: the temporary input file is no longer leaked when the
+  `prover9_path` is invalid (now cleaned up in a `finally`).
+- Several README inaccuracies (clone URL, "three" vs "four" parser modes, the
+  exception class raised on mixing same-level connectives, the `Quantifier`
+  AST-table annotation), and the `formulas_are_equivalent` / `is_valid`
+  docstrings.
+
+### Documentation
+
+- Clarified that `to_fol` / `to_msfol` is a classical **Boolean projection**
+  (the strong and weak Łukasiewicz connectives both collapse to `And`/`Or`), not
+  a fuzzy-preserving translation — use `fuzzy_evaluate` / the fuzzy Z3 solver for
+  many-valued degrees.
+
+### Internal
+
+- Refactored the duplicated structural recursions (`free_variables`,
+  substitution, beta/eta reduction, scope resolution, `to_msfol`/`_relativize`,
+  term substitution) onto the shared `Node.map_children` / `_child_nodes`
+  helpers, removing the per-node `isinstance` chains while preserving the
+  binder-aware special cases and the public `TypeError` contracts.
+
+## [0.3.1] - earlier
+
+- LaTeX export, normal forms, Horn check, Z3 models, traversal API, Graphviz export.
+
+## [0.3.0] - earlier
+
+- `to_unicode_str()` with parser round-trip.
+
+## [0.2.1] - earlier
+
+- README patch release.

{unicode_fol_kit-0.3.0 → unicode_fol_kit-0.4.0}/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 Felix Vossel
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+MIT License
+
+Copyright (c) 2026 Felix Vossel
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.