unitaryguard 0.2.0__tar.gz

unitaryguard-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.

unitaryguard-0.2.0/NOTICE

@@ -0,0 +1,8 @@
+UnitaryGuard
+Copyright 2026 Ronaldo Rodrigues
+
+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

unitaryguard-0.2.0/PKG-INFO

@@ -0,0 +1,173 @@
+Metadata-Version: 2.4
+Name: unitaryguard
+Version: 0.2.0
+Summary: Property-based semantic-equivalence checking for quantum circuit transforms: sample circuits, verify the unitary is preserved, shrink failures to a minimal reproduction. Framework-independent (no Qiskit or other SDK dependency) -- see DESIGN.md.
+Author: Ronaldo Rodrigues
+License-Expression: Apache-2.0
+Project-URL: Repository, https://github.com/Ronaldoengenhariadacomputacao/unitaryguard
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering :: Physics
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: numpy>=1.24
+Dynamic: license-file
+
+# UnitaryGuard
+
+Property-based semantic-equivalence checking for quantum circuit transforms.
+**Framework-independent since v0.2** — no Qiskit or other SDK dependency
+anywhere (see "Why v0.2 has no Qiskit dependency" below).
+
+Points it at any `Circuit -> Circuit` function (a transform wrapping an
+external engine, a compression step, anything), samples random circuits, and
+checks one invariant that almost every transform is supposed to preserve but
+almost no test suite checks directly: **does the output implement the same
+unitary as the input?** When it finds a circuit where that's not true, it
+automatically shrinks it to a small reproduction — the same thing you'd do
+by hand while debugging, but for free.
+
+## Why
+
+This project exists because that exact manual process — sample circuits,
+compare `Operator()` before/after a transform, shrink the failing case by
+hand — found two real, silent correctness bugs in widely-used Clifford+T
+tooling:
+
+- Qiskit core's `OptimizeCliffordT` pass (merged fix:
+  [Qiskit/qiskit#16729](https://github.com/Qiskit/qiskit/pull/16729)).
+- `rsgridsynth`'s `NormalForm` syllable-merge formula (open PR:
+  [qiskit-community/rsgridsynth#49](https://github.com/qiskit-community/rsgridsynth/pull/49)).
+
+Both bugs had the same shape: the transform's gate-count/T-count output was
+correct, while the circuit's actual unitary silently changed. Neither was
+caught by T-count/gate-count/depth checks — only an explicit unitary
+comparison catches this class of bug. UnitaryGuard is that check, packaged
+so it doesn't have to be reinvented by hand each time. `tests/test_known_bugs.py`
+reproduces both bug *shapes* as regression tests and proves the tool catches
+them and shrinks each to a small reproduction.
+
+See `DESIGN.md` for the full design rationale and current scope/limitations,
+and `CASE_STUDIES.md` for every method used to find a real bug so far, each
+with a runnable example (random sampling, exhaustive search, cross-validating
+the tool's own oracle, and writing a native-language binding to reach code a
+wrapper doesn't exercise).
+
+## Why v0.2 has no Qiskit dependency
+
+v0.1 checked equivalence via `qiskit.quantum_info.Operator`, which works
+fine when the transform under test is unrelated to Qiskit -- but breaks
+down exactly when the transform IS a real Qiskit pass: the code being
+tested and the code judging it become the same library, so a shared bug in
+Qiskit's own gate-matrix definitions can never be caught, structurally, no
+matter how many circuits you sample. v0.2 replaces the Qiskit-based
+`QuantumCircuit` representation with a tiny native `Circuit`/`Gate` pair and
+a gate-matrix table (`unitaryguard/matrices.py`) derived directly from each
+gate's standard mathematical definition, built with `numpy` alone. See
+`DESIGN.md` ("v0.2: dropped the Qiskit dependency entirely") for the full
+writeup. The real-world case that prompted this: validating AutoQ EngineBR,
+an external, from-scratch transpiler -- see that project's own docs for a
+worked adapter example (not included in this repo, since it's specific to
+that engine's own wire protocol).
+
+## Install
+
+```bash
+pip install -e .
+```
+
+## Use as a library
+
+```python
+from unitaryguard import Circuit, Gate, CheckConfig, check_transform
+
+def my_pass(circ: Circuit) -> Circuit:
+    ...  # your Circuit -> Circuit transform (e.g. call an external engine)
+    return transformed_circ
+
+cfg = CheckConfig(
+    n_qubits=3,
+    gate_set=["h", "s", "sdg", "t", "tdg", "cx"],
+    n_samples=500,
+    seed=42,
+)
+report = check_transform(my_pass, cfg)
+print(report.summary())
+assert report.ok
+```
+
+`Circuit(n_qubits, gates)` and `Gate(kind, qubits, params=())` are plain
+dataclasses -- `Gate("cx", (0, 1))`, `Gate("rz", (0,), (1.23,))`. See
+`unitaryguard/matrices.py::GATE_TABLE` for the full supported vocabulary.
+
+## Use from the CLI
+
+```bash
+unitaryguard check mymodule:my_pass --qubits 3 --gates h,s,sdg,t,tdg,cx --samples 500 --seed 42
+```
+
+`my_pass` must be an importable `Circuit -> Circuit` callable.
+
+### Exhaustive mode (deterministic, targets gate-order/inversion bugs)
+
+```bash
+unitaryguard exhaustive mymodule:my_pass --qubits 1 --gates h,s,sdg,t,tdg --max-length 6
+```
+
+Tests *every* discrete circuit up to `--max-length` gates (no continuous
+parameters), shortest first. A gate-order/conjugation-formula transcription
+bug (like both bugs this tool was built to generalize from) is
+deterministic, not statistical -- exhaustive search guarantees finding the
+smallest counterexample the vocabulary can express, with no separate
+shrinking step needed.
+
+Add `--workers N` to split each length's search across a process pool.
+Defaults to 1 (sequential) unless you pass it explicitly.
+
+**Measured, not assumed** -- on a 20-logical-core machine (Xeon E5-2666,
+figures below are *specific to that machine*, not a universal constant):
+parallelism only pays off once the workload is large enough to amortize
+each worker's one-time Qiskit import cost (~1.4s/process). On a small
+search (1555 circuits, max length 4), throughput peaked at `--workers 4`
+(1.6x) and *degraded* past that. On a larger search (9331 circuits, max
+length 5), `--workers 8` gave a real 3.3x speedup, plateauing (not
+improving further) from 12 workers up to the machine's full 20.
+
+The **principle** generalizes across hardware, the **numbers** don't --
+if you're on a 4-core laptop, "8-12 workers" is meaningless (there's no 12
+cores to use, and oversubscribing usually hurts, not helps). Re-run the
+same small-vs-large comparison on your own machine before picking a
+`--workers` value for anything you'll run repeatedly; as a starting point,
+try `--workers <your core count>` and only go lower if you see the same
+kind of degradation documented above for a small search.
+
+## Current scope (v0.2)
+
+- Transforms that preserve qubit count (most gate-level optimization/
+  synthesis passes). Ancilla-widening transforms are not yet supported —
+  see `DESIGN.md`.
+- Unitary-only transforms — no mid-circuit measurement / classical control
+  yet.
+- Gate vocabulary: `h,x,y,z,s,sdg,t,tdg,sx,sxdg` (0-param, 1-qubit),
+  `rz,ry,rx,p` (1-param, 1-qubit), `u` (3-param), `r` (2-param),
+  `cx,cz,swap,iswap,dcx,ecr,cy,ch,csx` (0-param, 2-qubit),
+  `crz,crx,cry,cp,rzz,rxx,ryy,rzx` (1-param, 2-qubit),
+  `cu,xx_plus_yy,xx_minus_yy` (multi-param, 2-qubit),
+  `ccx,cswap,ccz,rccx` (0-param, 3-qubit) — see
+  `unitaryguard/matrices.py::GATE_TABLE`. No generic arbitrary-unitary
+  sampling (`UnitaryGate`-equivalent) yet — extending vocabulary further is
+  a matter of adding matrix functions + table entries to `matrices.py`;
+  every entry added so far was cross-validated against two independent
+  oracles (Ket and Qiskit's `Operator()`) before being trusted — see
+  `CASE_STUDIES.md`.
+- No longer wraps real Qiskit `PassManager`/pass objects directly (that
+  capability was removed in v0.2 along with the Qiskit dependency — see
+  "Why v0.2 has no Qiskit dependency" above).
+
+## Status
+
+Early prototype, private (not yet published to PyPI). v0.2 (2026-09-21):
+dropped Qiskit dependency entirely, see DESIGN.md.

unitaryguard-0.2.0/README.md

@@ -0,0 +1,155 @@
+# UnitaryGuard
+
+Property-based semantic-equivalence checking for quantum circuit transforms.
+**Framework-independent since v0.2** — no Qiskit or other SDK dependency
+anywhere (see "Why v0.2 has no Qiskit dependency" below).
+
+Points it at any `Circuit -> Circuit` function (a transform wrapping an
+external engine, a compression step, anything), samples random circuits, and
+checks one invariant that almost every transform is supposed to preserve but
+almost no test suite checks directly: **does the output implement the same
+unitary as the input?** When it finds a circuit where that's not true, it
+automatically shrinks it to a small reproduction — the same thing you'd do
+by hand while debugging, but for free.
+
+## Why
+
+This project exists because that exact manual process — sample circuits,
+compare `Operator()` before/after a transform, shrink the failing case by
+hand — found two real, silent correctness bugs in widely-used Clifford+T
+tooling:
+
+- Qiskit core's `OptimizeCliffordT` pass (merged fix:
+  [Qiskit/qiskit#16729](https://github.com/Qiskit/qiskit/pull/16729)).
+- `rsgridsynth`'s `NormalForm` syllable-merge formula (open PR:
+  [qiskit-community/rsgridsynth#49](https://github.com/qiskit-community/rsgridsynth/pull/49)).
+
+Both bugs had the same shape: the transform's gate-count/T-count output was
+correct, while the circuit's actual unitary silently changed. Neither was
+caught by T-count/gate-count/depth checks — only an explicit unitary
+comparison catches this class of bug. UnitaryGuard is that check, packaged
+so it doesn't have to be reinvented by hand each time. `tests/test_known_bugs.py`
+reproduces both bug *shapes* as regression tests and proves the tool catches
+them and shrinks each to a small reproduction.
+
+See `DESIGN.md` for the full design rationale and current scope/limitations,
+and `CASE_STUDIES.md` for every method used to find a real bug so far, each
+with a runnable example (random sampling, exhaustive search, cross-validating
+the tool's own oracle, and writing a native-language binding to reach code a
+wrapper doesn't exercise).
+
+## Why v0.2 has no Qiskit dependency
+
+v0.1 checked equivalence via `qiskit.quantum_info.Operator`, which works
+fine when the transform under test is unrelated to Qiskit -- but breaks
+down exactly when the transform IS a real Qiskit pass: the code being
+tested and the code judging it become the same library, so a shared bug in
+Qiskit's own gate-matrix definitions can never be caught, structurally, no
+matter how many circuits you sample. v0.2 replaces the Qiskit-based
+`QuantumCircuit` representation with a tiny native `Circuit`/`Gate` pair and
+a gate-matrix table (`unitaryguard/matrices.py`) derived directly from each
+gate's standard mathematical definition, built with `numpy` alone. See
+`DESIGN.md` ("v0.2: dropped the Qiskit dependency entirely") for the full
+writeup. The real-world case that prompted this: validating AutoQ EngineBR,
+an external, from-scratch transpiler -- see that project's own docs for a
+worked adapter example (not included in this repo, since it's specific to
+that engine's own wire protocol).
+
+## Install
+
+```bash
+pip install -e .
+```
+
+## Use as a library
+
+```python
+from unitaryguard import Circuit, Gate, CheckConfig, check_transform
+
+def my_pass(circ: Circuit) -> Circuit:
+    ...  # your Circuit -> Circuit transform (e.g. call an external engine)
+    return transformed_circ
+
+cfg = CheckConfig(
+    n_qubits=3,
+    gate_set=["h", "s", "sdg", "t", "tdg", "cx"],
+    n_samples=500,
+    seed=42,
+)
+report = check_transform(my_pass, cfg)
+print(report.summary())
+assert report.ok
+```
+
+`Circuit(n_qubits, gates)` and `Gate(kind, qubits, params=())` are plain
+dataclasses -- `Gate("cx", (0, 1))`, `Gate("rz", (0,), (1.23,))`. See
+`unitaryguard/matrices.py::GATE_TABLE` for the full supported vocabulary.
+
+## Use from the CLI
+
+```bash
+unitaryguard check mymodule:my_pass --qubits 3 --gates h,s,sdg,t,tdg,cx --samples 500 --seed 42
+```
+
+`my_pass` must be an importable `Circuit -> Circuit` callable.
+
+### Exhaustive mode (deterministic, targets gate-order/inversion bugs)
+
+```bash
+unitaryguard exhaustive mymodule:my_pass --qubits 1 --gates h,s,sdg,t,tdg --max-length 6
+```
+
+Tests *every* discrete circuit up to `--max-length` gates (no continuous
+parameters), shortest first. A gate-order/conjugation-formula transcription
+bug (like both bugs this tool was built to generalize from) is
+deterministic, not statistical -- exhaustive search guarantees finding the
+smallest counterexample the vocabulary can express, with no separate
+shrinking step needed.
+
+Add `--workers N` to split each length's search across a process pool.
+Defaults to 1 (sequential) unless you pass it explicitly.
+
+**Measured, not assumed** -- on a 20-logical-core machine (Xeon E5-2666,
+figures below are *specific to that machine*, not a universal constant):
+parallelism only pays off once the workload is large enough to amortize
+each worker's one-time Qiskit import cost (~1.4s/process). On a small
+search (1555 circuits, max length 4), throughput peaked at `--workers 4`
+(1.6x) and *degraded* past that. On a larger search (9331 circuits, max
+length 5), `--workers 8` gave a real 3.3x speedup, plateauing (not
+improving further) from 12 workers up to the machine's full 20.
+
+The **principle** generalizes across hardware, the **numbers** don't --
+if you're on a 4-core laptop, "8-12 workers" is meaningless (there's no 12
+cores to use, and oversubscribing usually hurts, not helps). Re-run the
+same small-vs-large comparison on your own machine before picking a
+`--workers` value for anything you'll run repeatedly; as a starting point,
+try `--workers <your core count>` and only go lower if you see the same
+kind of degradation documented above for a small search.
+
+## Current scope (v0.2)
+
+- Transforms that preserve qubit count (most gate-level optimization/
+  synthesis passes). Ancilla-widening transforms are not yet supported —
+  see `DESIGN.md`.
+- Unitary-only transforms — no mid-circuit measurement / classical control
+  yet.
+- Gate vocabulary: `h,x,y,z,s,sdg,t,tdg,sx,sxdg` (0-param, 1-qubit),
+  `rz,ry,rx,p` (1-param, 1-qubit), `u` (3-param), `r` (2-param),
+  `cx,cz,swap,iswap,dcx,ecr,cy,ch,csx` (0-param, 2-qubit),
+  `crz,crx,cry,cp,rzz,rxx,ryy,rzx` (1-param, 2-qubit),
+  `cu,xx_plus_yy,xx_minus_yy` (multi-param, 2-qubit),
+  `ccx,cswap,ccz,rccx` (0-param, 3-qubit) — see
+  `unitaryguard/matrices.py::GATE_TABLE`. No generic arbitrary-unitary
+  sampling (`UnitaryGate`-equivalent) yet — extending vocabulary further is
+  a matter of adding matrix functions + table entries to `matrices.py`;
+  every entry added so far was cross-validated against two independent
+  oracles (Ket and Qiskit's `Operator()`) before being trusted — see
+  `CASE_STUDIES.md`.
+- No longer wraps real Qiskit `PassManager`/pass objects directly (that
+  capability was removed in v0.2 along with the Qiskit dependency — see
+  "Why v0.2 has no Qiskit dependency" above).
+
+## Status
+
+Early prototype, private (not yet published to PyPI). v0.2 (2026-09-21):
+dropped Qiskit dependency entirely, see DESIGN.md.

unitaryguard-0.2.0/pyproject.toml

@@ -0,0 +1,31 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "unitaryguard"
+version = "0.2.0"
+description = "Property-based semantic-equivalence checking for quantum circuit transforms: sample circuits, verify the unitary is preserved, shrink failures to a minimal reproduction. Framework-independent (no Qiskit or other SDK dependency) -- see DESIGN.md."
+readme = "README.md"
+requires-python = ">=3.9"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+authors = [{ name = "Ronaldo Rodrigues" }]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Science/Research",
+    "Programming Language :: Python :: 3",
+    "Topic :: Scientific/Engineering :: Physics",
+]
+dependencies = [
+    "numpy>=1.24",
+]
+
+[project.urls]
+Repository = "https://github.com/Ronaldoengenhariadacomputacao/unitaryguard"
+
+[project.scripts]
+unitaryguard = "unitaryguard.cli:main"
+
+[tool.setuptools.packages.find]
+include = ["unitaryguard*"]

unitaryguard-0.2.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+