governed 0.1.0__tar.gz

governed-0.1.0/.github/dependabot.yml

@@ -0,0 +1,14 @@
+version: 2
+updates:
+  # Runtime and optional-provider dependencies declared in pyproject.toml.
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 10
+
+  # Actions pinned in .github/workflows/*.yml (actions/checkout, setup-python).
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"

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

@@ -0,0 +1,97 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+# A second push to the same branch/PR cancels the still-running check for the
+# previous one -- no point finishing a lint run for a commit that's already
+# been superseded.
+concurrency:
+  group: ci-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    name: Python ${{ matrix.python-version }}
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.10", "3.11", "3.12"]
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python ${{ matrix.python-version }}
+        uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+          cache: pip
+
+      - name: Install (core + dev + all optional providers)
+        run: pip install -e '.[dev]'
+
+      # Every check below is exactly what README's "Contributing" section
+      # asks a human to run before submitting -- CI just enforces it.
+      - name: Lint (ruff check)
+        run: ruff check .
+
+      - name: Format check (ruff format)
+        run: ruff format --check .
+
+      - name: Type-check (mypy --strict, src only)
+        run: mypy src
+
+      # --cov turns on coverage measurement and, via [tool.coverage.report]
+      # fail_under in pyproject.toml, gates on it -- plain `pytest` (every
+      # local run, per CONTRIBUTING.md) has no coverage overhead and isn't
+      # gated at all; only this explicit, full-suite CI invocation is.
+      - name: Test (offline -- no network, no API key)
+        run: pytest --cov=governed --cov-report=term-missing
+
+  dependency-audit:
+    name: Dependency & supply-chain audit
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      # pip itself ships with the runner image and is often behind -- audit
+      # it too, but upgrade first so a stale *pip* CVE doesn't fail the job
+      # for a package governed doesn't even declare a dependency on.
+      - name: Upgrade pip
+        run: pip install --upgrade pip
+
+      # Audits the full dependency tree governed can pull in -- core plus
+      # every optional provider/extra -- not just what a bare install
+      # resolves, since [all]'s pins are what most deployments actually run.
+      - name: Install (core + all optional providers, no dev tooling)
+        run: pip install -e '.[all]' pip-audit cyclonedx-bom
+
+      - name: Audit installed dependencies for known vulnerabilities
+        run: pip-audit --strict
+
+      # A framework whose pitch is auditability should be able to answer
+      # "what's actually in this build" for itself -- a CycloneDX SBOM of
+      # the exact environment `[all]` resolves to, attached to the run so
+      # it's inspectable (and diffable, run to run) without reproducing the
+      # install locally.
+      - name: Generate SBOM (CycloneDX)
+        run: |
+          cyclonedx-py environment --pyproject pyproject.toml \
+            --output-format JSON --output-file sbom.json "$(which python)"
+
+      - name: Upload SBOM
+        uses: actions/upload-artifact@v4
+        with:
+          name: sbom
+          path: sbom.json
+          retention-days: 90

governed-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,51 @@
+name: Release
+
+# Publishes to PyPI on every tag matching v*.*.* (e.g. v0.2.0). Uses PyPI
+# Trusted Publishing (OIDC) -- no API token stored in this repo. The PyPI
+# project must have this repo/workflow registered as a trusted publisher
+# first (see CONTRIBUTING.md / repo docs for the one-time setup).
+on:
+  push:
+    tags: ["v*.*.*"]
+
+jobs:
+  build:
+    name: Build sdist and wheel
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install build
+        run: pip install --upgrade build
+
+      - name: Build
+        run: python -m build
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write # required for OIDC trusted publishing
+
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1

governed-0.1.0/.gitignore

@@ -0,0 +1,24 @@
+__pycache__/
+*.pyc
+*.egg-info/
+build/
+dist/
+
+.venv/
+venv/
+
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+htmlcov/
+
+# runtime artifacts from examples/tests
+examples/workspace/
+examples/traces/
+examples/.agentloop/
+workspace/
+traces/
+.agentloop/
+
+.DS_Store

governed-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic
+status, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior they deem inappropriate,
+threatening, offensive, or harmful.
+
+Maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned with this Code of Conduct, and will communicate reasons for
+moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces (issues, pull
+requests, discussions, and any other governed-affiliated forum), and also
+applies when an individual is officially representing the community in
+public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainers via GitHub's private reporting channel
+for this repository (see the Security tab, or open an issue asking for a
+private channel — the same route [`SECURITY.md`](SECURITY.md) uses for
+vulnerabilities not suited to a public issue). All complaints will be
+reviewed and investigated promptly and fairly.
+
+All maintainers are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Maintainers will follow these Community Impact Guidelines in determining the
+consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning, providing clarity around the
+nature of the violation and an explanation of why the behavior was
+inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved for a specified period of time. This
+includes avoiding interactions in community spaces as well as external
+channels. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public
+or private interaction with the people involved is allowed during this
+period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][mozilla].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[mozilla]: https://github.com/mozilla/diversity
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][faq]. Translations are available
+at [https://www.contributor-covenant.org/translations][translations].
+
+[faq]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

governed-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,131 @@
+# Contributing to governed
+
+Issues and PRs welcome. This document is the practical how-to; the
+[README](README.md) is the reference for what the framework does and why it's
+built the way it is — read that first if you're touching unfamiliar code,
+since most non-obvious design choices here are argued for there, not repeated
+in this file.
+
+Found a security vulnerability rather than a bug? See
+[SECURITY.md](SECURITY.md) instead of opening a public issue or PR.
+
+Participation in this project — issues, PRs, discussions — is governed by the
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+## Setup
+
+```bash
+git clone https://github.com/poorani/governed && cd governed
+pip install -e '.[dev]'
+```
+
+`[dev]` pulls in every optional provider extra (`anthropic`, `openai`,
+`gemini`, `data`, `yaml`) plus `pytest`, `mypy`, and `ruff` — the same set CI
+installs, so a clean local run means a clean CI run.
+
+## Before opening a PR
+
+```bash
+ruff check . && ruff format --check .
+mypy src
+pytest
+```
+
+[`.github/workflows/ci.yml`](.github/workflows/ci.yml) runs exactly these
+four checks on every push and PR, across Python 3.10/3.11/3.12. The whole
+suite is offline — no network, no API keys, ever (see "Testing conventions"
+below) — so there's no reason a local run and CI should disagree on whether
+the tests pass.
+
+CI's test step additionally runs with coverage measurement
+(`pytest --cov=governed --cov-report=term-missing`), gated by
+`fail_under` in `pyproject.toml`'s `[tool.coverage.report]` — currently 85%,
+a floor below the actual total (~90%) on purpose, so it catches a genuinely
+untested new module or code path, not everyday variance. Plain `pytest` (no
+`--cov`) never measures or gates on coverage, so this doesn't slow down or
+complicate the everyday local loop above; run
+`pytest --cov=governed --cov-report=term-missing` yourself before a PR that
+adds a new file or a large new code path, to see the same numbers CI will.
+
+A separate `dependency-audit` job runs on the same triggers: `pip-audit`
+against the full dependency tree (core plus every optional provider), and a
+CycloneDX SBOM of the resolved environment, uploaded as a build artifact.
+[Dependabot](.github/dependabot.yml) opens a PR weekly for anything outdated
+or flagged, for both Python dependencies and the GitHub Actions themselves.
+You don't need to run either locally; they don't gate on dependencies your
+PR doesn't touch.
+
+## Where new code goes
+
+- **A new tool** belongs in `src/governed/tools/`, ships with tests, and
+  its docstring must justify why it isn't better served by `execute_code` —
+  see "Adding a tool" in the README for the shape (`name`/`description`/
+  `safety`/`Input`/`run`) and the guidelines that earn their keep
+  (`description` is written for the model, not your teammates; every error
+  gets a `remediation`; output is bounded).
+- **A new skill** belongs in `skills/<name>/SKILL.md` and should encode
+  judgement, not syntax — "Writing a skill" in the README has the frontmatter
+  shape and what makes a skill worth shipping.
+- **A new LLM provider, or anything else selectable by name from config**
+  (a tool, a skill source, a decision-ledger sink/store, an event sink, a
+  state store) almost always belongs behind the existing plugin-registry
+  pattern rather than a new core dependency or a new special case in
+  `bootstrap.py`. `register_provider`/`register_tool`/`register_skill_source`/
+  `register_event_sink`/`register_decision_ledger_sink`/
+  `register_decision_ledger_store`/`register_state_store` all follow the
+  same shape: a factory function, registered under a name, selectable from
+  data from then on. See "Plugin registries" in the README before adding a
+  vendor SDK to `pyproject.toml`'s core dependencies — the core has exactly
+  one (`pydantic`), and that's deliberate.
+- **A new deterministic scanner** (in the shape of `InjectionScanner` /
+  `SecretExfiltrationScanner` / `PIIScanner`) belongs in
+  `security/guardrails.py`, subclassing `_RegexScanner`. State plainly, in
+  the docstring, what it does and doesn't catch — every scanner in this
+  codebase is upfront about being detection, not a boundary. If the change
+  touches guardrails, governance, the decision ledger, or approval flow,
+  update [`docs/RESPONSIBLE_AI.md`](docs/RESPONSIBLE_AI.md) too: it's the
+  one place that draws the line between what's structurally guaranteed and
+  what's detection, and a new scanner or toggle that isn't reflected there
+  is a documentation regression, not just a missing docstring.
+
+## Testing conventions
+
+No test may require network access or a real API key. The two seams that
+make this possible, used throughout:
+
+- **`ScriptedClient`** (`governed.llm`) for anything exercising the agent
+  loop end-to-end — hand it a scripted sequence of `LLMResponse`s instead of
+  a real provider.
+- **Injected fake SDK doubles** for anything exercising a specific
+  provider's request/response translation — `tests/test_llm_factory.py`
+  stands in a `SimpleNamespace` for `anthropic.Anthropic`/`openai.OpenAI`
+  via each client's existing `client=` constructor argument, so the test
+  verifies governed's own translation logic, not a vendor's wire format.
+
+For anything that shells out to a subprocess or an external CLI (a code
+execution backend, an HTTP sink), monkeypatch `subprocess.Popen`/`.run` or
+the relevant transport rather than requiring the real binary or endpoint —
+`tests/test_code_execution.py`'s `DockerCodeExecutionBackend` tests are the
+template: real Docker is never required, but the command construction, the
+timeout/kill path, and the "CLI not found" path are all exercised.
+
+Registry mutations in tests go through `monkeypatch.setitem` on the
+underlying private dict (e.g. `_TOOL_REGISTRY`, `_SKILL_SOURCE_REGISTRY`),
+not the public `register_*()` function directly — this gets automatic
+cleanup with no risk of one test's registration leaking into the next.
+`tests/test_plugin_registries.py` is the reference.
+
+## Style
+
+`ruff` (lint + format) and `mypy --strict` are the enforced style — there's
+no separate style guide beyond what those two catch. Beyond that, match the
+codebase's existing voice: docstrings explain *why* a design choice was
+made and what its limits are, not just what a function does; comments are
+rare and reserved for non-obvious constraints. Read a few existing modules
+(`security/guardrails.py` and `llm/factory.py` are good examples) before
+writing a large amount of new code.
+
+## License
+
+By contributing, you agree your contribution is licensed under this
+project's [Apache License 2.0](LICENSE), per §5 of that license.

governed-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the
+      purposes of this License, Derivative Works shall not include works
+      that remain separable from, or merely link (or bind by name) to the
+      interfaces of, the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on behalf of Yourself, assuming 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 governed contributors
+
+   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.