opteryx-access 0.0.1__tar.gz

opteryx_access-0.0.1/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 2026 Justin Joyce (@joocer)
+
+   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.

opteryx_access-0.0.1/PKG-INFO

@@ -0,0 +1,401 @@
+Metadata-Version: 2.4
+Name: opteryx_access
+Version: 0.0.1
+Summary: Permission checks and grant/revoke for the Opteryx platform
+Author-email: joocer <justin.joyce@joocer.com>
+License:                                  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 2026 Justin Joyce (@joocer)
+        
+           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.
+        
+Project-URL: Homepage, https://github.com/mabel-dev/opteryx-access
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.13
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: firestore
+Requires-Dist: google-cloud-firestore==2.*; extra == "firestore"
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Requires-Dist: pytest-cov>=5; extra == "dev"
+Requires-Dist: opteryx_access[firestore]; extra == "dev"
+Dynamic: license-file
+
+# opteryx-access
+
+Permission checks and grant/revoke for the Opteryx platform, as an installable
+library rather than a service. Every consumer imports `opteryx_access` and
+calls it in-process against policies it already has in hand -- a JWT's
+`policies` claim, or a `PolicyStore` backed by whatever it uses for storage
+(Firestore, today). There is no `opteryx-access` HTTP surface, and this
+package makes no network calls of its own beyond what a storage adapter does.
+
+## Why this exists
+
+Three independent, subtly incompatible implementations of "does this role
+satisfy this requirement" already exist in the fleet:
+
+- **policy.opteryx** / **control.opteryx** (`app/routes/v1/access.py`,
+  `app/models/policy.py` -- byte-for-byte duplicated between the two repos):
+  a rank-based `ROLES = ("owner", "admin", "writer", "reader")` used to
+  decide who may create/update/revoke a policy, and whether a new grant is
+  redundant against one the principal already holds.
+- **opteryx-core** (`opteryx/managers/permissions/__init__.py`): a
+  set-based `ACTION_MAP` deciding which roles may `READ`/`DELETE`/`DROP`/etc.
+  a resource once a query actually runs. `admin` is deliberately absent from
+  every entry -- it never grants data access, only grant-management
+  authority. This is the piece the rank-based model above cannot replace: a
+  naive `owner > admin > writer > reader` comparison would silently hand
+  admins data-write access they've never had.
+- **odata.opteryx** (`app/auth/permissions.py`): a binary
+  `role_allows_read` used for listing/visibility, plus its own
+  `fnmatch.fnmatchcase`-based pattern matcher -- deliberately case-sensitive,
+  unlike the plain `fnmatch.fnmatch` used elsewhere, which folds case per-OS.
+
+On top of that, `policy.opteryx`/`control.opteryx`/`odata.opteryx`/
+`register.opteryx` each carry their own copy of "parse the `policies` claim
+out of a decoded JWT." Comments in several of these point at an
+`authorize.opteryx` service (`app.routes.v1.evaluate`) as the semantics every
+copy is meant to mirror -- but no such repo exists anywhere in this
+workspace. Whether it's a real service in another org/remote or was never
+built, every consumer today reimplements its own understanding of "role +
+pattern -> allowed" independently, which is exactly the drift this package
+is meant to stop.
+
+## What lives here
+
+| Module | Ported from | Purpose |
+|---|---|---|
+| `roles.py` | `policy.opteryx/app/models/policy.py` | The canonical `ROLES` tuple. Two separate notions of "outranks": `ADMINISTRATIVE_ROLES` (owner/admin -- may manage grants) and rank (`ROLE_RANK`, used only for conflict detection). **Not** used to decide data actions. |
+| `actions.py` | `opteryx-core/opteryx/managers/permissions/__init__.py` | `ACTION_ROLES`: which roles may perform `READ`/`WRITE`/`DELETE`/`CREATE`/`DROP`/`ALTER`/`REFRESH`/`MANIFEST`, plus `GRANT`/`REVOKE` (new -- makes policy-administration authority explicit in the same table instead of an implicit rule elsewhere). |
+| `patterns.py` | `policy.opteryx/app/models/policy.py` + `app/routes/v1/access.py` | `resource_matches` (case-sensitive `fnmatchcase` -- see "Behavior changes" below), the wildcard-principal rule, and the reserved-workspace (`public`/`personal`/`information_schema`) rule. |
+| `models.py` | `authenticate.opteryx/app/policies.py` | `Grant` (role+pattern, the JWT-carried shape) and `Policy` (principal+role+pattern+metadata, the stored shape), plus `parse_policy_claim` for the `[role, pattern]` pairs a token carries. |
+| `checks.py` | `opteryx-core`'s `can_perform_action`/`can_perform_workspace_action` + `policy.opteryx`'s `_check_pattern_access`/`_check_workspace_access`/`_check_workspace_owner_access` | The evaluation layer: data-plane checks over `Grant`s, administrative-plane checks over `Policy` documents. |
+| `store.py` | `policy.opteryx/app/routes/v1/access.py`'s `create_policy`/`update_policy`/`delete_policy`/`create_genesis_policies` | Where policies are actually granted, updated, and revoked: the `PolicyStore` protocol plus `grant()`/`update_grant()`/`revoke()`/`bootstrap_workspace()`, which enforce every invariant those routes did (self-grant prevention, pattern-authority, conflict detection, wildcard/reserved-resource validation) against any storage backend. |
+| `adapters/firestore.py` | (new) | `FirestorePolicyStore`, matching the `{workspace}/$policies/access` layout policy.opteryx/control.opteryx already write to -- a drop-in for their inline Firestore calls. |
+| `exceptions.py` | (new) | Plain exceptions (`SelfAccessError`, `AccessDeniedError`, `PolicyConflictError`, ...) instead of `HTTPException` -- each caller translates to its own transport. |
+
+## Two axes, not one rank
+
+`admin` sits between `owner` and `writer` on the grant-management axis
+(`ADMINISTRATIVE_ROLES`) but is excluded from every entry in `ACTION_ROLES`.
+That split is real, existing platform behavior (see opteryx-core's
+`ACTION_MAP`), not an oversight this library introduces -- an admin can grant
+and revoke other people's access but cannot themselves `SELECT`/`INSERT`/
+`DELETE` against a resource they don't separately hold `writer`/`owner` on.
+Anything built on top of this package should keep asking the right one of
+the two questions:
+
+- "May this identity administer grants on this pattern?" -> `checks.can_administer_pattern`
+- "May this role perform this SQL-shaped action on this resource?" -> `checks.can_perform_action`
+
+## Usage
+
+```python
+from opteryx_access import Grant, can_perform_action
+
+grants = [Grant(role="writer", pattern="analytics.sales.*")]
+can_perform_action(grants, "analytics.sales.q1", "DELETE")  # True
+can_perform_action(grants, "analytics.sales.q1", "DROP")    # False -- writer, not owner
+```
+
+```python
+from opteryx_access import grant, revoke, AccessDeniedError
+from opteryx_access.adapters.firestore import FirestorePolicyStore
+
+store = FirestorePolicyStore(db)  # db: google.cloud.firestore.Client
+try:
+    policy_id = grant(
+        store, actor="alice", workspace="analytics",
+        principal="bob", role="writer", pattern="analytics.sales.*",
+    )
+except AccessDeniedError:
+    ...  # translate to a 403, same as the route used to do inline
+```
+
+## Behavior changes from the ported originals
+
+Ported faithfully except for one deliberate fix, worth calling out before
+anything is cut over:
+
+- **`resource_matches` uses `fnmatch.fnmatchcase`, not `fnmatch.fnmatch`.**
+  `policy.opteryx`/`control.opteryx`/opteryx-core's data-action check all use
+  plain `fnmatch`, which folds case per the OS Python runs on -- the same
+  policy would decide differently on macOS versus Linux. opteryx-core's own
+  `can_perform_action` already avoids `fnmatch` for exactly this reason when
+  matching its hardcoded implicit policies. odata.opteryx already uses
+  `fnmatchcase` for its read check. This package standardizes on the
+  deterministic, already-precedented behavior. If any live policy pattern
+  relies on the OS case-folding today, cutting a service over to this
+  package will change what that specific pattern matches -- worth an audit
+  of stored patterns before cutover, not assumed to be a no-op.
+
+## Suggested migration (not yet done)
+
+This repo is the library only -- nothing outside it has been changed yet.
+Suggested order, each independently shippable:
+
+1. **opteryx-core**: replace `opteryx/managers/permissions/__init__.py`'s
+   `ACTION_MAP`/`can_perform_action`/`can_perform_workspace_action`/
+   `implicit_policies` with thin wrappers around `opteryx_access.actions`/
+   `opteryx_access.checks` (converting `ExecutionContext.access_policies`
+   dicts to `Grant`s at the boundary). Zero new dependencies -- this package
+   has none by default.
+2. **odata.opteryx**: replace `app/auth/permissions.py`'s
+   `role_allows_read`/`read_grant_for_relation`/pattern matching with
+   `opteryx_access.checks.can_perform_action` (action="READ"). Leaves
+   `entitlements_from_claims`/`billing_account_from_claims` alone -- those
+   are a different concern (entitlements/billing), not permissions.
+3. **policy.opteryx** and **control.opteryx**: thin `app/routes/v1/access.py`
+   down to request parsing, calling `opteryx_access.store.grant`/
+   `update_grant`/`revoke`/`bootstrap_workspace` via `FirestorePolicyStore`,
+   and mapping the typed exceptions to `HTTPException`. The
+   resource-existence check (`_resource_exists`), user-status lookup
+   (`_lookup_user_record`), age gate, and audit logging all stay where they
+   are -- see `store.py`'s module docstring for why those are out of scope
+   here. Given `control.opteryx` is the in-progress merge target for
+   `policy.opteryx` (see its `docs/design/consolidation.md`), do this once,
+   on `control.opteryx`, and let the `policy.opteryx` cutover carry it along
+   rather than porting both routes separately.
+4. **register.opteryx** and any other claims-parsing copy: swap to
+   `opteryx_access.models.parse_policy_claim` for the `policies` claim
+   specifically. Token *verification* (signature, issuer, JWKS) stays
+   service-specific -- this package has no opinion on how a JWT gets from
+   bytes to a trusted claims dict, only on what to do with the `policies`
+   claim once you have one.
+
+## Installing
+
+```
+pip install opteryx_access
+pip install "opteryx_access[firestore]"  # for adapters.firestore
+```
+
+No hard dependencies. `google-cloud-firestore` is an optional extra;
+`adapters/firestore.py` never imports it at all (it's duck-typed against
+whatever `db` object it's handed), so importing `opteryx_access` itself never
+requires it -- consistent with opteryx-core's zero-dependency convention.
+
+## CI/CD
+
+- `.github/workflows/tests.yaml` -- pytest (3.13, 3.14) + ruff lint/format,
+  on every push to `main` and every PR.
+- `.github/workflows/release.yaml` -- on a pushed tag matching `version-*`:
+  runs the full test workflow, checks the tag matches `pyproject.toml`'s
+  `version` (exactly, or with a `.`-delimited suffix), then builds and
+  publishes to PyPI via
+  [trusted publishing](https://docs.pypi.org/trusted-publishers/) (OIDC --
+  no stored API token). The `opteryx_access` PyPI project needs this repo +
+  the `release.yaml` workflow registered as a trusted publisher before the
+  first tag push, or the publish step will fail with no valid credentials.
+
+To cut a release: bump `version` in `pyproject.toml`, merge to `main`, then
+`git tag version-X.Y.Z && git push origin version-X.Y.Z`.
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE) for details.