sentrykit 0.1.0rc1__tar.gz

sentrykit-0.1.0rc1/.gitignore

@@ -0,0 +1,44 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+*.so
+
+# Testing / coverage
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+# Hypothesis writes its own `.hypothesis/.gitignore` containing `*`, so git has always
+# skipped this -- which is why it is easy to miss that nothing else does. The sdist builder
+# does not read nested ignore files, and shipped 328 cache files until it was named here.
+.hypothesis/
+.coverage
+coverage.xml
+htmlcov/
+
+# pixi
+.pixi/
+# keep pixi.lock committed for reproducible dev envs
+
+# Env / editors
+.venv/
+venv/
+.env
+.idea/
+.vscode/
+.DS_Store
+
+# sentrykit local artifacts (never commit real audit logs or secrets)
+*.audit.jsonl
+secrets.local.*
+
+# The example apps' demo database, when SENTRYKIT_DEMO_DB points at a file rather than
+# letting it live in memory. Seeded from code and reproducible, so there is nothing here
+# worth committing and a stale copy is worse than none.
+examples/.demo/
+
+# Local research workspace (not shipped, not committed)
+/research/

sentrykit-0.1.0rc1/CHANGELOG.md

@@ -0,0 +1,141 @@
+# Changelog
+
+All notable changes to this project are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows SemVer.
+
+## [Unreleased]
+
+<!-- Add an entry in the *fix & document* step of each loop iteration. -->
+
+## [0.1.0] - 2026-11-09
+
+The first release.
+
+sentrykit is a self-hosted, framework-agnostic authorization layer for Python, built on
+[AWS Cedar](https://www.cedarpolicy.com/). Clip one `@protect` decorator onto any callable — a
+web route, a plain function, an agent tool — and it decides, per call, whether the principal may
+invoke it, **which arguments they may pass**, and **which defaults to inject when they pass
+none**, then writes a masked, hash-chained record of what it decided. The caller proposes; the
+policy decides, and what it decides includes the arguments, not only the call.
+
+Version numbers below this one appear in the project's development history. None was ever tagged
+or published, so this is the first release anyone can install, and it is the whole library.
+
+### Added
+
+- **`@protect`, and one pipeline behind it.** The decorator guards any sync or async callable and
+  runs gate, filter the proposed arguments, inject the defaults policy supplies, validate,
+  invoke, report. One module imports `cedarpy`, parsing the policy set, the entity graph and an
+  optional schema at wiring time and reusing those handles per decision. The core imports no web
+  framework and no agent SDK, so the decision path is identical wherever it runs.
+- **Ambient context, fail-closed.** `establish()` binds the principal, the channel and the facts
+  a policy may read — `now`, `break_glass`, `on_behalf_of`, `justification`; `bind_context()`
+  carries the scope across a thread-pool offload. With no principal established the call is
+  refused rather than run unguarded, so forgetting to wire a boundary denies instead of opening.
+- **Per-(principal, action) argument constraints.** Allow-sets, deny-sets, patterns, numeric
+  bounds, `required` and a per-principal `default`, resolved for the principal and the action and
+  decided one argument at a time. A deny-set is matched against what a value *contains* as well
+  as against the value itself, so wrapping a forbidden value in a list does not get it past.
+- **Narrow-and-continue instead of refuse.** A proposed value the principal may not have is
+  rejected and their own default fills the gap, so the call proceeds. It is reject-and-refill
+  rather than a clamp: the bound a value breached is never substituted for it. With no default
+  the argument is dropped, and if nothing the caller supplied survives the call is refused with
+  `NoValidArguments` — narrowing refines a proposal, it does not invent one.
+- **Policy-supplied defaults, checked like everything else.** A default fills an argument the
+  caller omitted *and* one that was just dropped, and is itself checked against the constraint
+  governing it and withheld if it fails, so omitting an argument is not a way around its rule. A
+  constraint nothing could satisfy — an uncompilable pattern, a minimum above a maximum, an
+  allow-set member the other rules reject, a default the constraint would refuse — is refused at
+  the grant write rather than found by whoever calls next.
+- **A governed parameter cannot quietly take its value from the function definition.** Where a
+  parameter has no surviving value, Python would fill the slot from the callable's own signature,
+  which no constraint ever saw. One that satisfies its constraint is named in
+  `signature_defaults`; one that does not refuses the call with `SignatureDefaultRejected`, whose
+  `declared` flag says whether the rule was reviewed policy or the principal's own grant.
+- **Argument ceilings, declared in reviewed policy text.** A `@constraints` annotation on a Cedar
+  `permit` carries `{argument: {rule: value}}` and says what *anybody* may pass for that action.
+  Ceilings and grants intersect and can only narrow — allow-sets intersect, deny-sets union,
+  bounds move inward, `required` is sticky, two patterns must both match — and a ceiling may not
+  set a `default`, because per-principal values stay in the store. Declarations are checked at
+  load, since Cedar does not type-check annotation values, and a policy set declaring any ceiling
+  refuses an engine failure rather than proceeding unbounded. A ceiling is the one declaration a
+  policy can make that reaches narrow-and-continue rather than the gate.
+- **An envelope that reports the outcome, not only the exceptions.** Every decision reports what
+  was processed, rejected, defaulted and withheld, trimmed by `verbosity`, plus `narrowed`,
+  `narrowed_arguments` and `guidance` — a narrowed call *succeeds*, on values the principal is
+  entitled to, and reporting only its exceptions describes that success in the vocabulary of a
+  failure. Those three name no value and no policy id, so a caller who may not be told *what* was
+  narrowed is still told *that* the result is good. It arrives as the `_authz` key on a mapping
+  return, via `last_envelope()` for any other return type, and out of band per boundary:
+  `x-sentrykit-narrowed` response headers, MCP `_meta` keys with an appended text block, and a
+  Pydantic-AI `ToolReturn` that displaces no data.
+- **A refusal says which kind it is**: `AuthzDenied` for a policy denial, `NoContext` for no
+  principal, and `NoValidArguments`, `DefaultUnavailable`, `ArgumentRejected`,
+  `SignatureDefaultRejected`, `ReservedKey` and `ValidationFailed` for the argument layer.
+  `fail_mode` arbitrates engine failure alone: a denial and a missing principal deny either way.
+- **Relationships resolved by Cedar's entity hierarchy.** Nested relationships spanning entities
+  — user → team → division → project → resource, delegation, on-behalf-of, expiry,
+  break-the-glass — resolve deterministically rather than through a ladder of application `if`
+  statements, so a policy names only the far end of a chain and severing one edge ends the access.
+- **A masked, hash-chained audit trail.** One record per decision and per admin mutation: the
+  principal's effective attributes at decision time, the arguments proposed, processed, rejected
+  and defaulted, the policies that decided, and a `policy_set_hash` pinning the record to the
+  exact policy text. Sensitive values are masked *before* the append-only write, never at report
+  time — `redact`, `partial`, `hmac` or `tokenize`, chosen by a Cedar obligation, an
+  `Annotated[..., Sensitive(...)]` marker or the configured default, with keyed HMAC the default
+  because it alone lets an auditor correlate records without the store holding the value; a
+  principal's own allow-set, deny-set and pattern are masked the same way. Each record's hash
+  covers its predecessor's, so `verify_chain` catches an edited record and a deleted one, and a
+  record a sink refused is admitted by the next that lands, so an outage cannot read as an intact
+  window. Tampering is detected, not prevented.
+- **Four context providers, each one extra line of wiring.** `FastAPIProvider` (pure-ASGI
+  middleware, an `async` context dependency, error handlers, `protect_app`), `FlaskProvider`
+  (`before_request` / `teardown_request`, `protect_app`, `protect_blueprint`), `MCPProvider`
+  (middleware around `tools/call`, `governed_tool`, `protect_server`) and `PydanticAIProvider`
+  (`RunContext.deps` bridged to ambient context, `governed_tool`, `tool_adapter`, `tool_prepare`,
+  `tool_filter`). Each establishes the principal at the boundary and renders a refusal in that
+  boundary's vocabulary; one built with no `identify=` warns once, because its own fallback ends
+  at something the request supplies.
+- **Per-caller tool manifests, filtered by the decision that enforces the call.** A tool is
+  hidden from a principal if and only if invoking it would be refused. Hiding is a courtesy to
+  the model and never the control: a client that skips the manifest and calls a hidden tool by
+  name is refused the same. Arguments policy supplies are re-advertised as optional, so a model
+  can omit them and receive its own defaults.
+- **A Cedar policy pack, shipped as data.** Eight domain-neutral patterns — `rbac`, `groups`,
+  `ownership`, `delegation`, `expiry`, `break-glass`, `separation-of-duties`, `jit-elevation` —
+  under a `pack://` DSN, composed through the same union as your own directory. None names a
+  role, a resource type or an action: the resource declares what it requires and the grant store
+  supplies the principal's edges. Half the pack **forbids**, and that half is what contains
+  rather than permits — reopening an emergency-only resource demands an entitlement, the flag
+  *and* a justification, because a permit conditioned on a caller-supplied boolean alone
+  authorizes anyone. The schema is opt-in, `link_template` makes a time-boxed grant from a Cedar
+  template, and the pack ships no permit for the admin actions: a library does not get to ship
+  the rule that hands out authority.
+- **Four extension points, one mechanism.** Policy sources, grant stores, audit sinks and context
+  providers are each a `Protocol`, a DSN, a `register_*` decorator and an entry point, so a
+  third-party backend is indistinguishable from a built-in. Shipped: `file://` and `pack://`
+  policy sources, `memory://` and `jsonfile://` grant stores, `memory://` and `jsonl://` audit
+  sinks. Pass a list instead of one DSN and the composite satisfies the same `Protocol` — sources
+  union, grant stores merge or route by namespace, sinks fan out.
+- **The `sentrykit` command line**, over `argparse` and no added dependency. `policy validate`
+  type-checks a directory against its schema, groups errors by `@id` and exits non-zero, so it
+  belongs in CI. `grant`, `revoke` and `grants` are the admin surface, each a protected callable
+  decided by the same governor the application uses — built from the policy-processed arguments
+  and not from `argv`, so a policy governs who may administer grants *and which grants they may
+  make*. `audit-report` windows a sink into markdown, aggregating by outcome, with a tamper
+  verdict and its own mutations section.
+- **Five runnable examples over one shared domain.** An orders-and-refunds desk modelled
+  identically as a FastAPI app, a Flask app, an MCP tool server and a Pydantic-AI agent — the
+  same protected callables, the same reviewed `.cedar` directory and the same grant data, so only
+  the boundary wiring differs — each driving its flows against a seeded database and printing
+  what policy did to every call. The fifth proposes nine named attacks, from exfiltration by
+  `limit` and an instruction planted in a ticket thread to a destructive call whose damage sits
+  in its Python default, and runs each twice over the same function bodies: once past the policy
+  and once around it. Three of the nine the gate does not win, and they are in the suite on
+  purpose — a layer that ships only the cases it wins describes a feature, not a boundary.
+- **Python 3.11, 3.12 and 3.13**, on a typed, documented public API: `mypy --strict` over the
+  package, `py.typed` in the wheel, and the docstrings the API reference is generated from. The
+  extras install only what a boundary needs — `fastapi`, `flask`, `mcp`, `pydantic-ai`, `web`,
+  `agents`, `all` — and the one core pin worth knowing about is `cedarpy >= 4.8, < 5`, the floor
+  exposing the parse-once API the engine is built on. Each release attaches the documentation as
+  HTML, a PDF, `llms.txt` and `llms-full.txt`, the last meant to be sufficient on its own.

sentrykit-0.1.0rc1/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 [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.