usagebassoon 0.1.0a1__tar.gz

usagebassoon-0.1.0a1/.github/CODEOWNERS

@@ -0,0 +1,4 @@
+# SPDX-FileCopyrightText: 2026 Israel Flores-Arbolay
+# SPDX-License-Identifier: AGPL-3.0-only
+
+* @israelflores8789

usagebassoon-0.1.0a1/.github/dependabot.yaml

@@ -0,0 +1,12 @@
+# SPDX-FileCopyrightText: 2026 Israel Flores-Arbolay
+# SPDX-License-Identifier: AGPL-3.0-only
+
+version: 2
+updates:
+- package-ecosystem: github-actions
+  directory: /
+  schedule:
+    interval: weekly
+  groups:
+    actions:
+      patterns: ["*"]

usagebassoon-0.1.0a1/.github/rulesets/apply-rulesets.sh

@@ -0,0 +1,32 @@
+#!/usr/bin/env bash
+
+# SPDX-FileCopyrightText: 2026 Israel Flores-Arbolay
+# SPDX-License-Identifier: AGPL-3.0-only
+
+# apply-rulesets.sh — create or update repository rulesets from
+# .github/rulesets/*.json. Idempotent: matches existing rulesets
+# by name and updates them in place, creating only what's missing.
+#
+# Requires: gh (authenticated as a repo admin) and jq.
+# Usage: ./apply-rulesets.sh
+set -euo pipefail
+shopt -s nullglob
+
+script_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+repo="$(gh repo view --json nameWithOwner --jq .nameWithOwner)"
+[[ "$repo" == "israelflores8789/usagebassoon" ]] || { echo "unexpected repo: $repo" >&2; exit 1; }
+
+for file in "$script_dir"/*.json; do
+  name="$(jq --raw-output .name "$file")"
+  id="$(gh api "repos/$repo/rulesets?per_page=100" --paginate \
+  | jq -r --arg name "$name" '[.[] | select(.name == $name) | .id] | .[0] // empty')"
+
+  body="$(jq 'del(.source_type)' "$file")"   # drop if API 422s without this
+  if [[ -n "$id" ]]; then
+    printf '%s' "$body" | gh api --method PUT "repos/$repo/rulesets/$id" --input - >/dev/null
+    echo "updated ruleset: $name (id $id)"
+  else
+    printf '%s' "$body" | gh api --method POST "repos/$repo/rulesets" --input - >/dev/null
+    echo "created ruleset: $name"
+  fi
+done

usagebassoon-0.1.0a1/.github/rulesets/protect-dev.json

@@ -0,0 +1,44 @@
+{
+  "name": "protect-dev",
+  "target": "branch",
+  "source_type": "Repository",
+  "enforcement": "active",
+  "conditions": {
+    "ref_name": {
+      "include": ["refs/heads/dev"],
+      "exclude": []
+    }
+  },
+  "bypass_actors": [
+    {
+      "actor_id": 5,
+      "actor_type": "RepositoryRole",
+      "bypass_mode": "always"
+    }
+  ],
+  "rules": [
+    { "type": "deletion" },
+    { "type": "non_fast_forward" },
+    {
+      "type": "pull_request",
+      "parameters": {
+        "required_approving_review_count": 0,
+        "dismiss_stale_reviews_on_push": false,
+        "require_code_owner_review": true,
+        "require_last_push_approval": false,
+        "required_review_thread_resolution": false,
+        "allowed_merge_methods": ["merge", "squash", "rebase"]
+      }
+    },
+    {
+      "type": "required_status_checks",
+      "parameters": {
+        "do_not_enforce_on_create": true,
+        "required_status_checks": [
+          { "context": "license/cla" }
+        ],
+        "strict_required_status_checks_policy": false
+      }
+    }
+  ]
+}

usagebassoon-0.1.0a1/.github/rulesets/protect-main.json

@@ -0,0 +1,44 @@
+{
+  "name": "protect-main",
+  "target": "branch",
+  "source_type": "Repository",
+  "enforcement": "active",
+  "conditions": {
+    "ref_name": {
+      "include": ["~DEFAULT_BRANCH"],
+      "exclude": []
+    }
+  },
+  "bypass_actors": [
+    {
+      "actor_id": 5,
+      "actor_type": "RepositoryRole",
+      "bypass_mode": "always"
+    }
+  ],
+  "rules": [
+    { "type": "deletion" },
+    { "type": "non_fast_forward" },
+    {
+      "type": "pull_request",
+      "parameters": {
+        "required_approving_review_count": 0,
+        "dismiss_stale_reviews_on_push": false,
+        "require_code_owner_review": true,
+        "require_last_push_approval": false,
+        "required_review_thread_resolution": false,
+        "allowed_merge_methods": ["merge", "squash", "rebase"]
+      }
+    },
+    {
+      "type": "required_status_checks",
+      "parameters": {
+        "do_not_enforce_on_create": true,
+        "required_status_checks": [
+          { "context": "license/cla" }
+        ],
+        "strict_required_status_checks_policy": false
+      }
+    }
+  ]
+}

usagebassoon-0.1.0a1/.github/rulesets/protect-release-tags.json

@@ -0,0 +1,27 @@
+{
+  "name": "protect-release-tags",
+  "target": "tag",
+  "source_type": "Repository",
+  "enforcement": "active",
+  "conditions": {
+    "ref_name": {
+      "include": ["refs/tags/v*"],
+      "exclude": []
+    }
+  },
+  "bypass_actors": [
+    {
+      "actor_id": 5,
+      "actor_type": "RepositoryRole",
+      "bypass_mode": "always"
+    }
+  ],
+  "rules": [
+    {
+      "type": "update"
+    },
+    {
+      "type": "deletion"
+    }
+  ]
+}

usagebassoon-0.1.0a1/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

usagebassoon-0.1.0a1/.pre-commit-config.yaml

@@ -0,0 +1,36 @@
+# SPDX-FileCopyrightText: 2026 Israel Flores-Arbolay
+# SPDX-License-Identifier: AGPL-3.0-only
+
+exclude: '^tests/fixtures/.*\.json$'
+
+repos:
+- repo: https://github.com/crate-ci/typos
+  rev: v1.50.0
+  hooks:
+  - id: typos
+
+- repo: https://github.com/google/yamlfmt
+  rev: v0.21.0
+  hooks:
+  - id: yamlfmt
+    args:
+    - -formatter
+    - indent=2,indentless_arrays=true,retain_line_breaks=true
+
+- repo: https://github.com/pre-commit/pre-commit-hooks
+  rev: v6.0.0
+  hooks:
+  - id: trailing-whitespace
+  - id: end-of-file-fixer
+
+- repo: https://github.com/rhysd/actionlint
+  rev: v1.7.12
+  hooks:
+  - id: actionlint
+
+- repo: https://github.com/pre-commit/pre-commit-hooks
+  rev: v6.0.0
+  hooks:
+  - id: check-yaml
+    args: [--unsafe, --allow-multiple-documents]
+  - id: check-added-large-files

usagebassoon-0.1.0a1/.python-version

@@ -0,0 +1 @@
+3.13

usagebassoon-0.1.0a1/.vscode/extensions.json

@@ -0,0 +1,19 @@
+{
+  "recommendations": [
+    "ms-python.python",
+    "ms-python.debugpy",
+    "meta.pyrefly",
+    "charliermarsh.ruff",
+    "nefrob.vscode-just-syntax",
+    "tamasfe.even-better-toml",
+    "tekumara.typos-vscode"
+  ],
+  "unwantedRecommendations": [
+    "ms-python.vscode-pylance",
+    "ms-python.pyright",
+    "detachhead.basedpyright",
+    "ms-python.flake8",
+    "ms-python.black-formatter",
+    "dbaeumer.vscode-eslint"
+  ]
+}

usagebassoon-0.1.0a1/.vscode/settings.json

@@ -0,0 +1,16 @@
+{
+  "python.languageServer": "None",
+  "[python]": {
+    "editor.defaultFormatter": "charliermarsh.ruff",
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.organizeImports.ruff": "always",
+      "source.fixAll.ruff": "always"
+    }
+  },
+  "ruff.enable": true,
+  "ruff.organizeImports": true,
+  "evenBetterToml.schema.associations": {
+    "pyproject.toml": "https://json.schemastore.org/pyproject.json"
+  }
+}

usagebassoon-0.1.0a1/AGENTS.md

@@ -0,0 +1,73 @@
+<!--
+SPDX-FileCopyrightText: 2026 Israel Flores-Arbolay
+SPDX-License-Identifier: AGPL-3.0-only
+-->
+
+# UsageBassoon — Agent Context
+
+## Purpose
+
+A Python CLI and library (pipx-installable, import usagebassoon) that persists `tokscale` JSON token usage statistics to a persistent data store into DuckDB or MotherDuck. This allows users to aggregate token usage across agentic environments.
+
+## Repository Structure
+```
+usagebassoon/
+├── pyproject.toml            # hatchling; pipx-installable; Python >= 3.11
+├── src/usagebassoon/
+│   ├── cli.py                # typer app
+│   ├── collector.py          # tokscale subprocess + retry
+│   ├── parsers/              # one module per payload kind
+│   │   ├── models.py         # per session×model rows → session_model_stats
+│   │   ├── report.py         # session metadata       → sessions (no LLM summary fields)
+│   │   ├── graph.py          # daily contributions    → daily_stats/daily_activity/run_metrics
+│   │   └── pricing.py        # rates + resolution     → pricing_snapshots + row stamps
+│   ├── backends/
+│   │   ├── base.py           # StorageBackend protocol
+│   │   ├── duckdb_local.py
+│   │   └── motherduck.py
+│   ├── merge.py              # staging + transactional merge + rebuild + session_label
+│   ├── reconcile.py          # cross-payload consistency checks
+│   ├── curation.py           # tags + notes
+│   ├── sanitize.py           # export-time pseudonymization (--sanitize)
+│   ├── report_term.py        # rich tables + plotext charts (+ --save/--sanitize)
+│   ├── api.py                # usagebassoon.query/connect (pandas default, polars opt-in)
+│   └── sql/                  # ddl + views, loaded as package data
+├── tests/
+│   ├── fixtures/             # sanitized golden captures: models, report, graph, pricing
+│   └── test_*.py             # incl. fixture-derived invariants
+└── .github/workflows/        # ci (ruff, pyrefly, pytest), release to PyPI
+```
+
+## Architecture
+
+- **Dependencies**: `duckdb`, `pandas`, `pydantic`, `typer`, `rich`, `plotext`, `polars` (optional).
+- **Dev Environment**: `uv`, `hatchling`, `twine`, `pyrefly`, `ruff`, `pytest`, `just`, `pre-commit`.
+
+## Commands
+
+Run all project tasks via `just` from the repository root. Use `just --list` to inspect available recipes.
+
+- USE `just install-dev` to synchronize all uv dependency groups.
+- USE `just test` to run the test suite; pass pytest arguments with `just test <args>`.
+- USE `just coverage` to run test suite with terminal coverage reporting.
+- USE `just lint` to perform Ruff linting and formatting checks.
+- USE `just typecheck` to perform Pyrefly type checks.
+- USE `just spell-diff` to run typos spelling checker.
+- PREFER `just ci` for combined test, lint, and typecheck recipes.
+- USE `just build` to clean `dist/` and build an sdist and wheel with Hatchling.
+- USE `just check-dist` to clean, build, and validate artifacts with Twine.
+- USE `just clean` to remove build artifacts and local caches.
+
+## Rules
+
+- USE Google-style docstrings for **all** source code.
+- KEEP comments concise yet clear. Do NOT use numbered headers (e.g. "1." or "(1)" etc).
+- NO version string is ever hard-coded in source; `hatch-vcs` manages version numbering from git tags (`v0.1.0` → `0.1.0`).
+
+### Prohibitions
+The following actions are **prohibited** and are reserved exclusively for the user. When encountering a task that involves a prohibited action, you MUST **stop** and **report** to the user the conflict:
+
+- NEVER modify the golden JSON fixtures in `tests/fixtures/`.
+- NEVER attempt to publish to PyPI or invoke any publishing command; consequently, NEVER use `just publish` or `just release`.
+- NEVER attempt to perform a release to GitHub or invoke any release command.
+- NEVER attempt to push git changes to GitHub.

usagebassoon-0.1.0a1/CLA.md

@@ -0,0 +1,84 @@
+# Contributor License Agreement
+
+**UsageBassoon Contributor License Agreement v1.0**
+
+*Based on the Project Harmony Individual Contributor License Agreement (HA-CLA-I v1.0), with modifications for dual licensing.*
+
+Thank you for your interest in contributing to UsageBassoon (the "Project"). In order to clarify the intellectual property license granted with Contributions from any person or entity, the Project maintainer, Israel Flores-Arbolay ("We" or "Us"), must have a Contributor License Agreement ("Agreement") on file that has been accepted by each Contributor, indicating agreement to the license terms below. This license is for Your protection as a Contributor as well as the protection of Us and the users of the Project; it does not change Your rights to use Your own Contributions for any other purpose.
+
+By clicking the acceptance checkbox, signing electronically via the CLA Assistant tool, or otherwise submitting a Contribution with an indication of Your acceptance of this Agreement, You accept and agree to be bound by the following terms and conditions for Your present and future Contributions submitted to the Project. Except for the license granted herein to Us and recipients of software distributed by Us, You reserve all right, title, and interest in and to Your Contributions.
+
+## 1. Definitions
+
+"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is entering into this Agreement with Us. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. 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.
+
+"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to Us for inclusion in, or documentation of, the Project. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to Us or Our 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, Us for the purpose of discussing and improving the Project, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
+
+## 2. Grant of Rights
+
+### 2.1 Copyright License
+
+Subject to the terms of this Agreement, You hereby grant to Us and to recipients of software distributed by Us 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 Your Contributions and such derivative works.
+
+### 2.2 Patent License
+
+Subject to the terms of this Agreement, You hereby grant to Us and to recipients of software distributed by Us 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 Your Contributions, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Project to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that Your Contribution, or the Project to which You have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or that work shall terminate as of the date such litigation is filed.
+
+### 2.3 Outbound License
+
+As a condition on the grant of rights in Sections 2.1 and 2.2, We agree to license Your Contribution only under the terms of the license or licenses which We are using on the Submission Date for the Project (the "Current License"). As of the date of this Agreement, the Current License is the GNU Affero General Public License v3.0 only (AGPL-3.0-only).
+
+**In addition**, You grant to Us the right to license Your Contributions, and derivative works thereof, under **any other license terms of Our choosing, including proprietary and commercial license terms**, at Our sole discretion. This additional grant exists to enable the Project's dual-licensing model: the Project is offered to the community under the Current License and may simultaneously be offered to commercial licensees under separate terms, revenue from which may support continued open-source development of the Project.
+
+### 2.4 Moral Rights
+
+To the fullest extent permitted under applicable law, You waive, and agree not to assert, any moral rights You may have in Your Contributions against Us and recipients of software distributed by Us. If moral rights cannot be waived under applicable law, You agree not to enforce them against such parties to the fullest extent permitted.
+
+### 2.5 Your Rights
+
+You retain ownership of the copyright in Your Contribution and have the same rights to use or license the Contribution which You would have had without entering into this Agreement.
+
+## 3. Representations
+
+You represent that:
+
+(a) each of Your Contributions is Your original work of authorship, or You have secured all rights necessary to submit it under this Agreement;
+
+(b) You are legally entitled to grant the license set forth in Section 2;
+
+(c) if Your employer(s) or other third party has rights to intellectual property that You create that includes Your Contributions, You represent that You have received permission to make Contributions on behalf of that employer or third party, that Your employer or such third party has waived such rights for Your Contributions to the Project, or that Your employer or such third party has executed a separate entity contributor license agreement with Us;
+
+(d) Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which You are personally aware and which are associated with any part of Your Contributions; and
+
+(e) You have disclosed all Third-Party Materials. "Third-Party Materials" means any material that is not Your original work of authorship contained within Your Contribution, along with the licenses and any restrictions applicable to such materials.
+
+## 4. Disclaimer
+
+EXCEPT FOR THE EXPRESS REPRESENTATIONS IN SECTION 3, THE CONTRIBUTION IS PROVIDED "AS IS" TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW. ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT, ARE DISCLAIMED BY BOTH YOU AND US.
+
+## 5. No Obligation
+
+You acknowledge that We are under no obligation to use, include, or continue to distribute Your Contribution at all, and that the decision to do so is made at Our sole discretion.
+
+## 6. Consequential Damage Waiver
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL YOU OR WE BE LIABLE FOR ANY LOSS OF PROFITS, LOSS OF ANTICIPATED SAVINGS, LOSS OF DATA, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF THIS AGREEMENT, REGARDLESS OF THE LEGAL OR EQUITABLE THEORY (CONTRACT, TORT, OR OTHERWISE) UPON WHICH THE CLAIM IS BASED.
+
+## 7. Term and Termination
+
+This Agreement comes into effect when You accept its terms, and remains in effect unless and until terminated in writing by either party. Termination of this Agreement does not affect the rights previously granted under Section 2 for Contributions submitted prior to termination; those licenses are perpetual and irrevocable.
+
+## 8. Miscellaneous
+
+This Agreement is the entire agreement between You and Us with respect to its subject matter and supersedes all prior or contemporaneous agreements, understandings, and communications, whether written or oral, between You and Us with respect to such subject matter. This Agreement is governed by the laws of the State of Delaware, excluding its conflict-of-laws provisions. If any provision of this Agreement is found void or unenforceable, such provision will be reformed to the extent necessary to make it enforceable, and the remainder of this Agreement will remain in full force and effect. Any notices under this Agreement should be directed to israelflores8789@gmail.com.
+
+We may assign or transfer this Agreement, and all rights granted hereunder, to any successor in interest, including without limitation any corporate entity We form or control, by merger, sale of assets, operation of law, or otherwise, without Your consent, provided the assignee agrees in writing to be bound by the terms of this Agreement.
+
+## 9. Acceptance
+
+We may publish revised versions of this Agreement from time to time. By clicking the acceptance control presented by CLA Assistant on a pull request to the Project (or otherwise indicating acceptance in writing), You agree to be bound by the terms of this Agreement for all present and future Contributions You submit to the Project, unless and until this Agreement is superseded by a subsequent version that You separately accept.
+
+
+---
+
+*UsageBassoon CLA v1.0. Structure adapted from the Project Harmony Individual Contributor License Agreement (harmonyagreements.org, HA-CLA-I v1.0), with the addition of the proprietary relicensing grant in Section 2.3 and other modifications.*