policy-pattern 0.3.0__tar.gz → 0.4.1__tar.gz

{policy_pattern-0.3.0 → policy_pattern-0.4.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: policy-pattern
-Version: 0.3.0
+Version: 0.4.1
 Summary: A minimal, embeddable ReBAC authorization engine for Python, inspired by Google Zanzibar.
 Keywords: python,authorization,access-control,rebac,zanzibar,security
 Author: Guillem Pozo Sebastián
@@ -45,8 +45,7 @@ Description-Content-Type: text/markdown
     </a>
 </p>
 
-`policy-pattern` is a standalone Python library for relationship-based access control (ReBAC). It models
-authorization as relationships between subjects and objects and evaluates those relationships through composable
+`policy-pattern` is a standalone Python library for relationship-based access control (ReBAC). It models authorization as relationships between subjects and objects and evaluates those relationships through composable
 authorization rules.
 
 - **No authorization server**
@@ -131,18 +130,15 @@ evaluator = Evaluator(model=compiled, store=store)
 evaluator.check(alice, "viewer", document_42)  # True — alice owns the parent folder
 ```
 
-`viewer` here means "the document's own owner, or the owner of whatever folder it lives in" — a document under
-`folder:engineering` inherits access from that folder without copying a permission onto every document.
+`viewer` here means "the document's own owner, or the owner of whatever folder it lives in" — a document under `folder:engineering` inherits access from that folder without copying a permission onto every document.
 
-See the [Usage Guide](docs/usage/README.md) for the full, runnable walkthrough — every rewrite operator, nested
-groups, `EvaluationBudget`, and error handling.
+See the [Usage Guide](docs/usage/README.md) for the full, runnable walkthrough — every rewrite operator, nested groups, `EvaluationBudget`, and error handling.
 
 ---
 
 ## Documentation
 
-The repository uses specifications and architecture documents as part of the implementation contract — they
-describe **what must be true**, independent of any one adapter's implementation.
+The repository uses specifications and architecture documents as part of the implementation contract — they describe **what must be true**, independent of any one adapter's implementation.
 
 ```text
 docs/
@@ -153,8 +149,9 @@ docs/
 └── errors.md        — the PPxxx error code ranges and what each one means
 ```
 
-Start with the [Usage Guide](docs/usage/README.md) to see the library working end to end, then
-[Architecture](docs/architecture.md) to understand why the model is shaped the way it is.
+Start with the [Usage Guide](docs/usage/README.md) to see the library working end to end, then [Architecture](docs/architecture.md) to understand why the model is shaped the way it is.
+
+See [`CODE_STYLE.md`](.github/CODE_STYLE.md) and [`TESTING.md`](TESTING.md) for contributor conventions no tool enforces.
 
 ---
 

{policy_pattern-0.3.0 → policy_pattern-0.4.1}/README.md

@@ -20,8 +20,7 @@
     </a>
 </p>
 
-`policy-pattern` is a standalone Python library for relationship-based access control (ReBAC). It models
-authorization as relationships between subjects and objects and evaluates those relationships through composable
+`policy-pattern` is a standalone Python library for relationship-based access control (ReBAC). It models authorization as relationships between subjects and objects and evaluates those relationships through composable
 authorization rules.
 
 - **No authorization server**
@@ -106,18 +105,15 @@ evaluator = Evaluator(model=compiled, store=store)
 evaluator.check(alice, "viewer", document_42)  # True — alice owns the parent folder
 ```
 
-`viewer` here means "the document's own owner, or the owner of whatever folder it lives in" — a document under
-`folder:engineering` inherits access from that folder without copying a permission onto every document.
+`viewer` here means "the document's own owner, or the owner of whatever folder it lives in" — a document under `folder:engineering` inherits access from that folder without copying a permission onto every document.
 
-See the [Usage Guide](docs/usage/README.md) for the full, runnable walkthrough — every rewrite operator, nested
-groups, `EvaluationBudget`, and error handling.
+See the [Usage Guide](docs/usage/README.md) for the full, runnable walkthrough — every rewrite operator, nested groups, `EvaluationBudget`, and error handling.
 
 ---
 
 ## Documentation
 
-The repository uses specifications and architecture documents as part of the implementation contract — they
-describe **what must be true**, independent of any one adapter's implementation.
+The repository uses specifications and architecture documents as part of the implementation contract — they describe **what must be true**, independent of any one adapter's implementation.
 
 ```text
 docs/
@@ -128,8 +124,9 @@ docs/
 └── errors.md        — the PPxxx error code ranges and what each one means
 ```
 
-Start with the [Usage Guide](docs/usage/README.md) to see the library working end to end, then
-[Architecture](docs/architecture.md) to understand why the model is shaped the way it is.
+Start with the [Usage Guide](docs/usage/README.md) to see the library working end to end, then [Architecture](docs/architecture.md) to understand why the model is shaped the way it is.
+
+See [`CODE_STYLE.md`](.github/CODE_STYLE.md) and [`TESTING.md`](TESTING.md) for contributor conventions no tool enforces.
 
 ---
 

{policy_pattern-0.3.0 → policy_pattern-0.4.1}/policy_pattern/evaluator.py

@@ -2,6 +2,7 @@
 Evaluator: resolves check() over a CompiledModel and a TupleStore.
 """
 
+from collections.abc import Sequence
 from dataclasses import dataclass, field
 
 from .errors import EvaluationError, UnknownNameError, UnknownTypeError
@@ -24,7 +25,11 @@ from .ports import TupleStore, View
 @dataclass(frozen=True, slots=True)
 class EvaluationBudget:
     """
-    Per-`check()` resource limits.
+    Resource limits for one `check()` or `check_many()` call.
+
+    `max_nodes` and `max_store_reads` accumulate across a `check_many()` call.
+    `max_depth` bounds the live `context.visited` frontier and resets as each
+    request finishes, so it does not accumulate across the batch.
 
     No `__post_init__` validation — a degenerate value (e.g. `max_depth=0`)
     is well-defined without a guard: it simply fails on the first node
@@ -35,16 +40,16 @@ class EvaluationBudget:
         EvaluationBudget(max_depth=10, max_nodes=500, max_store_reads=100)
     """
 
-    # Maximum recursion depth for a single `check()` call. Each recursive call
+    # Maximum recursion depth for one call. Each recursive call
     # to `_check_name()` adds one to the depth; exceeding this limit raises an
     # `EvaluationError`.
     max_depth: int = 25
 
-    # Maximum number of nodes visited during a single `check()` call. Each
+    # Maximum number of nodes visited during one call. Each
     # call to `_check_name()` increments this count; exceeding this limit raises an `EvaluationError`.
     max_nodes: int = 10_000
 
-    # Maximum number of store reads during a single `check()` call. Each call
+    # Maximum number of store reads during one call. Each call
     # to `_charge_read()` increments this count; exceeding this limit raises an `EvaluationError`.
     max_store_reads: int = 1_000
 
@@ -52,7 +57,7 @@ class EvaluationBudget:
 @dataclass(slots=True)
 class EvaluationContext:
     """
-    Live bookkeeping for exactly one `check()` call.
+    Live bookkeeping for exactly one `check()` or `check_many()` call.
 
     Deliberately mutable, unlike almost everything else in this package —
     this is not a domain value, it is the in-flight state of one
@@ -63,13 +68,19 @@ class EvaluationContext:
     (added before recursing, discarded after returning) — anything
     permanently resolved lives in `memo` instead, so the two never overlap
     in meaning.
+
+    The key carries the subject because one `check()` has a constant subject,
+    while `check_many()` can mix subjects; a narrower key could reuse one
+    subject's cached decision for another and cause a false allow.
     """
 
     view: View
     budget: EvaluationBudget
-    visited: set[tuple[ObjectReference, str]] = field(default_factory=lambda: set[tuple[ObjectReference, str]]())
-    memo: dict[tuple[ObjectReference, str], bool] = field(
-        default_factory=lambda: dict[tuple[ObjectReference, str], bool]()
+    visited: set[tuple[Subject, ObjectReference, str]] = field(
+        default_factory=lambda: set[tuple[Subject, ObjectReference, str]]()
+    )
+    memo: dict[tuple[Subject, ObjectReference, str], bool] = field(
+        default_factory=lambda: dict[tuple[Subject, ObjectReference, str], bool]()
     )
     node_count: int = 0
     store_read_count: int = 0
@@ -120,11 +131,28 @@ class Evaluator:
             context = EvaluationContext(view=view, budget=budget)
             return self._check_name(subject, name, object, context)
 
+    def check_many(
+        self,
+        requests: Sequence[tuple[Subject, str, ObjectReference]],
+        budget: EvaluationBudget | None = None,
+    ) -> list[bool]:
+        """
+        Returns one decision per request, preserving input order and duplicates.
+
+        The whole batch shares one snapshot, context, and budget. An error on
+        any request aborts the call and propagates without partial results.
+        """
+        if budget is None:
+            budget = EvaluationBudget()
+        with self._store.snapshot() as view:
+            context = EvaluationContext(view=view, budget=budget)
+            return [self._check_name(subject, name, object, context) for subject, name, object in requests]
+
     def _check_name(self, subject: Subject, name: str, object: ObjectReference, context: EvaluationContext) -> bool:
         """
         Dispatches (object, name) to a relation or permission check, with cycle/memo/budget bookkeeping.
         """
-        key = (object, name)
+        key = (subject, object, name)
         if key in context.memo:
             return context.memo[key]
         if key in context.visited:

{policy_pattern-0.3.0 → policy_pattern-0.4.1}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "policy-pattern"
-version = "0.3.0"
+version = "0.4.1"
 description = "A minimal, embeddable ReBAC authorization engine for Python, inspired by Google Zanzibar."
 readme = "README.md"
 license = "Apache-2.0"
@@ -38,7 +38,7 @@ Repository = "https://github.com/guillem-ps/policy-pattern"
 Issues = "https://github.com/guillem-ps/policy-pattern/issues"
 
 [build-system]
-requires = ["uv_build>=0.11.16,<0.13.0"]
+requires = ["uv_build>=0.11.16,<0.14.0"]
 build-backend = "uv_build"
 
 [tool.uv.build-backend]

{policy_pattern-0.3.0 → policy_pattern-0.4.1}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "policy-pattern"
-version = "0.3.0"
+version = "0.4.1"
 description = "A minimal, embeddable ReBAC authorization engine for Python, inspired by Google Zanzibar."
 readme = "README.md"
 authors = [
@@ -37,7 +37,7 @@ Repository = "https://github.com/guillem-ps/policy-pattern"
 Issues = "https://github.com/guillem-ps/policy-pattern/issues"
 
 [build-system]
-requires = ["uv_build>=0.11.16,<0.13.0"]
+requires = ["uv_build>=0.11.16,<0.14.0"]
 build-backend = "uv_build"
 
 [tool.uv.build-backend]