b123d-recognisers 0.1.0__tar.gz

b123d_recognisers-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,35 @@
+name: CI
+
+on:
+  push:
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6
+      - uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7
+        with:
+          enable-cache: true
+      - run: uv sync --dev
+      - run: uv run ruff check .
+
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python: ["3.10", "3.12", "3.14"]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6
+      - uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python }}
+      - run: uv sync --dev
+      - run: uv run pytest

b123d_recognisers-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,121 @@
+name: Publish distributions
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: Existing GitHub release tag whose assets will be promoted
+        required: true
+        type: string
+      target:
+        description: Stop after TestPyPI, or promote the same artifact to both indexes
+        required: true
+        default: testpypi
+        type: choice
+        options:
+          - testpypi
+          - both
+
+concurrency:
+  group: publish-${{ github.event.release.tag_name || inputs.tag }}
+  cancel-in-progress: false
+
+permissions: {}
+
+jobs:
+  prepare:
+    name: Verify GitHub release assets
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    env:
+      RELEASE_TAG: ${{ github.event.release.tag_name || inputs.tag }}
+    steps:
+      - uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6
+        with:
+          persist-credentials: false
+      - name: Validate release tag
+        shell: bash
+        run: |
+          if [[ ! "$RELEASE_TAG" =~ ^v[0-9][0-9A-Za-z.!+-]*$ ]]; then
+            echo "invalid release tag: $RELEASE_TAG" >&2
+            exit 1
+          fi
+      - name: Download reviewed release distributions
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: gh release download "$RELEASE_TAG" --pattern "*.whl" --pattern "*.tar.gz" --dir dist
+      - name: Verify tag and artifact identity
+        run: python tools/verify_release_assets.py --dist dist --tag "$RELEASE_TAG"
+      - uses: actions/upload-artifact@b7c566a772e6b6bfb58ed0dc250532a479d7789f # v6
+        with:
+          name: python-package-distributions
+          path: dist/
+          if-no-files-found: error
+          retention-days: 7
+
+  publish-testpypi:
+    name: Publish to TestPyPI
+    needs: prepare
+    runs-on: ubuntu-latest
+    environment:
+      name: testpypi
+      url: https://test.pypi.org/p/b123d-recognisers
+    permissions:
+      id-token: write # Trusted Publishing exchanges OIDC for a short-lived index token.
+    steps:
+      - uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
+        with:
+          name: python-package-distributions
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          skip-existing: true
+
+  verify-testpypi:
+    name: Install from TestPyPI
+    needs: publish-testpypi
+    runs-on: ubuntu-latest
+    env:
+      RELEASE_TAG: ${{ github.event.release.tag_name || inputs.tag }}
+    steps:
+      - uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7
+        with:
+          enable-cache: false
+          ignore-empty-workdir: true
+      - name: Install published wheel and import public API
+        shell: bash
+        run: |
+          version="${RELEASE_TAG#v}"
+          uv venv
+          uv pip install "build123d>=0.9,<0.12"
+          for attempt in {1..12}; do
+            if uv pip install --no-deps --index-url https://test.pypi.org/simple/ \
+              "b123d-recognisers==$version"; then
+              break
+            fi
+            if [[ "$attempt" == 12 ]]; then exit 1; fi
+            sleep 10
+          done
+          uv run --no-sync python -c \
+            "import b123d_recognisers as r; assert r.__version__ == '$version'; assert r.recognise_holes"
+
+  publish-pypi:
+    name: Publish to PyPI
+    if: github.event_name == 'release' || inputs.target == 'both'
+    needs: verify-testpypi
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/b123d-recognisers
+    permissions:
+      id-token: write # Trusted Publishing exchanges OIDC for a short-lived index token.
+    steps:
+      - uses: actions/download-artifact@37930b1c2abaa49bbe596cd826c3c89aef350131 # v7
+        with:
+          name: python-package-distributions
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # release/v1

b123d_recognisers-0.1.0/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.coverage
+.pytest_cache/
+.ruff_cache/
+.venv/
+build/
+dist/
+htmlcov/
+

b123d_recognisers-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,25 @@
+# Contributing
+
+Contributions are welcome. By intentionally submitting a contribution for inclusion in this
+project, you agree that it is provided under the Apache License 2.0, as described by section 5 of
+that licence, unless you explicitly state otherwise in writing.
+
+## Architectural rules
+
+- Recognition is geometry-only: no drawing, editing-session, CAM-operation or UI policy.
+- Public results are immutable, typed and serialisable without leaking build123d/OCP objects.
+- A base recogniser accepts `part` first and keyword-only tuning or injected dependencies.
+- A derived recogniser is a pure function over already-recognised records.
+- Recognisers do not rerun sibling recognisers; orchestration computes shared evidence once.
+- Empty means confidently absent within supported topology. Ambiguous and unsupported cases are
+  explicit diagnostics.
+- Changes to a load-bearing contract require an ADR update.
+
+## Local checks
+
+```bash
+uv sync --dev
+uv run ruff check .
+uv run pytest
+```
+

b123d_recognisers-0.1.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.

b123d_recognisers-0.1.0/NOTICE

@@ -0,0 +1,8 @@
+b123d-recognisers
+Copyright 2024-2026 Paul Fremantle
+
+The initial hole, boss, cylinder and pattern recognition implementation was
+derived from build123d-drafting-helpers, an Apache-2.0 project copyright
+Paul Fremantle, and was subsequently developed in Draftwright. It is released
+here under Apache-2.0 by the copyright owner.
+

b123d_recognisers-0.1.0/PKG-INFO

@@ -0,0 +1,88 @@
+Metadata-Version: 2.5
+Name: b123d-recognisers
+Version: 0.1.0
+Summary: Deterministic, geometry-only feature recognition for build123d solids
+Project-URL: Repository, https://github.com/pzfreo/b123d-recognisers
+Project-URL: Issues, https://github.com/pzfreo/b123d-recognisers/issues
+Author-email: Paul Fremantle <pzfreo@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+License-File: THIRD_PARTY_NOTICES.md
+Keywords: brep,build123d,cad,feature-recognition,step
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Manufacturing
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: <3.15,>=3.10
+Requires-Dist: build123d<0.12,>=0.9
+Description-Content-Type: text/markdown
+
+# b123d-recognisers
+
+Deterministic, geometry-only feature recognition for build123d solids and imported STEP models.
+
+This is the standalone Apache-2.0 recognition layer extracted from
+[Draftwright](https://github.com/pzfreo/draftwright). It reports immutable geometric records and
+does not own drawing, manufacturing, editing, or consumer-cache policy.
+
+## Usage
+
+Run the complete shared recognition orchestration when a consumer needs one consistent inventory:
+
+```python
+from b123d_recognisers import build_recognition_result
+
+result = build_recognition_result(part)
+for hole in result.holes:
+    print(hole.diameter, hole.depth, hole.through)
+```
+
+Individual recognisers remain public for focused consumers. Reusable evidence is explicitly
+injected so it is not rediscovered:
+
+```python
+from b123d_recognisers import analyse_cylinders, recognise_hole_patterns, recognise_holes
+
+cylinders = analyse_cylinders(part)
+holes = recognise_holes(part, cyls=cylinders)
+patterns = recognise_hole_patterns(holes)
+```
+
+Every `recognise_*` function returns a deterministic list of frozen dataclass records. Records
+provide `to_dict()` projections containing only JSON-serialisable geometry values. See
+[`docs/adr/0002-uniform-deterministic-recogniser-contract.md`](docs/adr/0002-uniform-deterministic-recogniser-contract.md)
+for the complete contract.
+
+## Migrated behavior
+
+The initial `0.1` release series preserves the recognition behavior of Draftwright commit
+`3fe20b0f71a71deced06b310943dd44cc66e355e`. The migration includes every public recogniser,
+shared cylinder/level substrates, the aggregate result, and `feature_census`. There are no feature
+policy changes; one previously platform-dependent numerical axis tie is normalized to the pinned
+baseline result. The checked-in semantic corpus records and continuously verifies the compatibility
+boundary; see [`migration/PARITY.md`](migration/PARITY.md).
+
+The dependency direction is:
+
+```text
+consumer → b123d-recognisers → build123d/OCP
+```
+
+The runtime package does not import Draftwright and does not return build123d or OCP objects in
+public feature records.
+
+Maintainers: see [the release guide](docs/releasing.md) for the TestPyPI-first, OIDC-only
+publication process.
+
+## Licence
+
+Apache License 2.0. See [`LICENSE`](LICENSE), [`NOTICE`](NOTICE), and
+[`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md).

b123d_recognisers-0.1.0/README.md

@@ -0,0 +1,61 @@
+# b123d-recognisers
+
+Deterministic, geometry-only feature recognition for build123d solids and imported STEP models.
+
+This is the standalone Apache-2.0 recognition layer extracted from
+[Draftwright](https://github.com/pzfreo/draftwright). It reports immutable geometric records and
+does not own drawing, manufacturing, editing, or consumer-cache policy.
+
+## Usage
+
+Run the complete shared recognition orchestration when a consumer needs one consistent inventory:
+
+```python
+from b123d_recognisers import build_recognition_result
+
+result = build_recognition_result(part)
+for hole in result.holes:
+    print(hole.diameter, hole.depth, hole.through)
+```
+
+Individual recognisers remain public for focused consumers. Reusable evidence is explicitly
+injected so it is not rediscovered:
+
+```python
+from b123d_recognisers import analyse_cylinders, recognise_hole_patterns, recognise_holes
+
+cylinders = analyse_cylinders(part)
+holes = recognise_holes(part, cyls=cylinders)
+patterns = recognise_hole_patterns(holes)
+```
+
+Every `recognise_*` function returns a deterministic list of frozen dataclass records. Records
+provide `to_dict()` projections containing only JSON-serialisable geometry values. See
+[`docs/adr/0002-uniform-deterministic-recogniser-contract.md`](docs/adr/0002-uniform-deterministic-recogniser-contract.md)
+for the complete contract.
+
+## Migrated behavior
+
+The initial `0.1` release series preserves the recognition behavior of Draftwright commit
+`3fe20b0f71a71deced06b310943dd44cc66e355e`. The migration includes every public recogniser,
+shared cylinder/level substrates, the aggregate result, and `feature_census`. There are no feature
+policy changes; one previously platform-dependent numerical axis tie is normalized to the pinned
+baseline result. The checked-in semantic corpus records and continuously verifies the compatibility
+boundary; see [`migration/PARITY.md`](migration/PARITY.md).
+
+The dependency direction is:
+
+```text
+consumer → b123d-recognisers → build123d/OCP
+```
+
+The runtime package does not import Draftwright and does not return build123d or OCP objects in
+public feature records.
+
+Maintainers: see [the release guide](docs/releasing.md) for the TestPyPI-first, OIDC-only
+publication process.
+
+## Licence
+
+Apache License 2.0. See [`LICENSE`](LICENSE), [`NOTICE`](NOTICE), and
+[`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md).

b123d_recognisers-0.1.0/RELEASE_NOTES.md

@@ -0,0 +1,28 @@
+# Release notes
+
+## 0.1.0
+
+First stable release of the standalone Apache-2.0 recognition package.
+
+- Promotes `0.1.0a1` after the packaged cutover merged in Draftwright PR #1168
+  (`d659e7a6`), with the duplicate embedded recogniser implementation removed.
+- Retains the 17 pinned semantic golden fixtures, public-inventory/serialization contracts, and
+  cross-platform Python 3.10/3.12/3.14 matrix; this release contains no new recognition behaviour.
+- Uses the reviewed TestPyPI-first Trusted Publishing path to promote one exact wheel and sdist
+  to PyPI without rebuilding between indexes.
+
+The complete migration, provenance, and performance evidence remains in
+[`migration/PARITY.md`](migration/PARITY.md).
+
+## 0.1.0a1
+
+First prerelease of the standalone Apache-2.0 recognition package extracted from Draftwright.
+
+- Includes every recogniser, shared geometry substrate, aggregate result, and feature census from
+  Draftwright commit `3fe20b0f71a71deced06b310943dd44cc66e355e`.
+- Matches all 17 pinned semantic golden fixtures and preserves the ADR 0002 public contract.
+- Normalizes an exact dominant-axis numerical tie to the pinned result across Windows, macOS, and
+  Linux; no feature-policy changes are included.
+- Ships typed Python sources plus `LICENSE`, `NOTICE`, and `THIRD_PARTY_NOTICES.md`.
+
+The complete migration and performance evidence is in [`migration/PARITY.md`](migration/PARITY.md).

b123d_recognisers-0.1.0/THIRD_PARTY_NOTICES.md

@@ -0,0 +1,30 @@
+# Third-party notices
+
+`b123d-recognisers` declares build123d as a runtime dependency; it does not vendor or redistribute
+the dependency source or native binaries in its wheel.
+
+## build123d
+
+- Project: <https://github.com/gumyr/build123d>
+- Licence: Apache-2.0
+- Copyright: the build123d contributors
+
+build123d was originally derived from portions of CadQuery. Its distribution includes the
+applicable Apache-2.0 notice.
+
+## CadQuery OCP bindings
+
+- Project: <https://github.com/CadQuery/OCP>
+- Licence: Apache-2.0
+
+build123d uses the CadQuery OCP Python bindings to access Open CASCADE Technology.
+
+## Open CASCADE Technology
+
+- Project: <https://github.com/Open-Cascade-SAS/OCCT>
+- Licence: GNU LGPL version 2.1 with the Open CASCADE additional exception
+
+OCCT remains under its own licence. Nothing in the Apache-2.0 licence for this project changes
+the licence or redistribution conditions of OCCT or any other dependency. A distributor that
+bundles dependency binaries must review and satisfy the corresponding binary-distribution terms.
+

b123d_recognisers-0.1.0/docs/adr/0001-standalone-geometry-only-apache-library.md

@@ -0,0 +1,39 @@
+# ADR 0001 — Standalone geometry-only Apache library
+
+- **Status:** Accepted
+- **Date:** 2026-08-15
+- **Decider:** Paul Fremantle
+
+## Context
+
+Draftwright and build123d-mcp both need to recover feature measurements from imported or otherwise
+unattributed B-rep solids. Draftwright previously owned recognition to avoid coupling recognition
+changes to its rendering dependency, but recognition itself is not drawing-specific. Keeping a
+copy in each consumer causes algorithm and bug-fix drift.
+
+Draftwright's ADRs 0007 and 0013 already selected a standalone package named
+`b123d-recognisers`; the earlier deployment gate was organizational rather than architectural.
+The copyright owner has now chosen to establish that package.
+
+## Decision
+
+Create distribution `b123d-recognisers`, imported as `b123d_recognisers`, under Apache-2.0.
+
+The library accepts build123d shapes, using OCP internally where necessary, and returns geometric
+records, measurables, evidence and recognition diagnostics. It does not own:
+
+- drawing requirements, dimensions, callouts, views, placement or lint severity;
+- editing-session state, reconstruction commands or CAM operation selection;
+- consumer caches tied to a drawing, document or server lifecycle.
+
+Consumers adapt records into their own domain IR. The dependency direction is always
+`consumer → b123d-recognisers → build123d/OCP`.
+
+## Consequences
+
+- Recognition algorithms can be reused by Apache, proprietary and copyleft consumers.
+- Cross-repository releases become necessary, so the public surface must remain small and stable.
+- Draftwright's `RecognitionCache` stays in Draftwright because it implements build/lint lifecycle
+  policy; only immutable recognition values cross the boundary.
+- Existing recognition code is deliberately relicensed during migration by its copyright owner.
+