anma 0.5.5__tar.gz

anma-0.5.5/.claude/hooks/anma_pretooluse.py

@@ -0,0 +1,18 @@
+#!/usr/bin/env python3
+"""ANMA PreToolUse hook (generated). Exit code 2 blocks the tool call.
+
+Thin shim: the real logic lives in `anma.hook`, so it is tested and upgradable
+via `pip install -U anma` without re-running `anma sync`. Fails OPEN (allows the
+edit) with a warning if anma is not importable, so a missing install never blocks
+your work — CI and pre-commit remain the hard gate.
+"""
+import sys
+
+try:
+    from anma.hook import run_hook
+except Exception:
+    sys.stderr.write("ANMA hook: `anma` not importable in this environment; "
+                     "skipping in-session check (CI/pre-commit still enforce).\n")
+    sys.exit(0)
+
+sys.exit(run_hook(sys.stdin.read()))

anma-0.5.5/.claude/rules/boundaries.md

@@ -0,0 +1,12 @@
+<!-- Generated by `anma sync`. -->
+# Module boundaries (ANMA)
+
+IMPORTANT: This repo enforces module boundaries. Before adding any import
+between modules, confirm it is allowed in the source module's `anma.yaml`
+(`depends_on`). Cross-module access must go through the target module's public
+interface — never its internals.
+
+To change a boundary: edit the module's `anma.yaml`, run `anma sync`, and add a
+one-line entry to `DECISIONS.md`. Do not work around the boundary in code.
+
+Verify with: `anma check`

anma-0.5.5/.claude/settings.json

@@ -0,0 +1,12 @@
+{
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Edit|Write|MultiEdit",
+        "hooks": [
+          { "type": "command", "command": "python3 .claude/hooks/anma_pretooluse.py" }
+        ]
+      }
+    ]
+  }
+}

anma-0.5.5/.github/CODEOWNERS

@@ -0,0 +1,3 @@
+# Generated by `anma sync` from each module's `owners` field.
+
+/anma/ @nxy

anma-0.5.5/.github/workflows/anma.yml

@@ -0,0 +1,13 @@
+# Generated by `anma sync`.
+name: anma
+on: [push, pull_request]
+jobs:
+  boundaries:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.10" }
+      - run: pip install anma[tach]
+      - run: anma sync --check   # fail if generated docs/config drifted from contracts
+      - run: anma check          # enforce module boundaries

anma-0.5.5/.github/workflows/ci.yml

@@ -0,0 +1,38 @@
+name: ci
+on: [push, pull_request]
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install -e .[dev]
+      - run: python -m pytest tests/ -q
+
+  audit:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: python -m pip install --upgrade pip
+      - run: pip install -e .[dev]
+      - run: pip-audit --skip-editable
+
+  dogfood:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - run: pip install -e .
+      - run: anma sync --check .
+      - run: anma check .

anma-0.5.5/.github/workflows/release.yml

@@ -0,0 +1,45 @@
+name: release
+on:
+  release:
+    types: [published]
+
+permissions:
+  contents: write      # attach SBOM to the release
+  id-token: write      # OIDC for PyPI Trusted Publishing + attestations
+  attestations: write  # build provenance
+
+jobs:
+  build-and-publish:
+    runs-on: ubuntu-latest
+    environment: pypi
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Build distributions
+        run: |
+          pip install build
+          python -m build
+
+      - name: Generate CycloneDX SBOM
+        run: |
+          pip install cyclonedx-bom
+          cyclonedx-py environment --output-format JSON --output-file sbom.json
+
+      - name: Attest build provenance
+        uses: actions/attest-build-provenance@v1
+        with:
+          subject-path: "dist/*"
+
+      - name: Attach SBOM to the GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: sbom.json
+
+      # No API token: OIDC Trusted Publishing. Configure the publisher on PyPI.
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist/

anma-0.5.5/.gitignore

@@ -0,0 +1,28 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.eggs/
+build/
+dist/
+.venv/
+venv/
+
+# Test / tooling caches
+.pytest_cache/
+.mypy_cache/
+.tox/
+.coverage
+htmlcov/
+
+# ANMA benchmark outputs (generated by `python -m bench.run`)
+benchmarks/results/
+
+# Local Claude Code project memory (never commit)
+CLAUDE.local.md
+
+# OS / editor
+.DS_Store
+*.swp
+.idea/
+.vscode/

anma-0.5.5/.pre-commit-config.yaml

@@ -0,0 +1,9 @@
+# Generated by `anma sync`.
+repos:
+  - repo: local
+    hooks:
+      - id: anma-check
+        name: anma check (module boundaries)
+        entry: anma check
+        language: system
+        pass_filenames: false

anma-0.5.5/CHANGELOG.md

@@ -0,0 +1,123 @@
+# Changelog
+
+All notable changes to ANMA are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/); the **contract schema**
+(`schema_version`) is versioned independently of the tool — see
+[docs/CONCEPTS.md](docs/CONCEPTS.md#stability).
+
+## [Unreleased]
+
+## [0.5.5] — 2026-06-06
+
+### Fixed
+- The generated CI workflow (`.github/workflows/anma.yml`) is now **seed-once and
+  not drift-checked**, like `settings.json` and `.pre-commit-config.yaml`. It is a
+  starting point users customize (e.g. the install path), so regenerating and
+  drift-checking it was wrong — a hand-edited CI file no longer fails
+  `anma sync --check`.
+
+## [0.5.4] — 2026-06-06
+
+### Changed
+- Documentation rewritten around the first hardened result (Claude Haiku 4.5,
+  `payments-boundary`, n=20: control 13/19 violations vs ANMA 0/20,
+  Fisher `p < 0.0001`). README, QUICKSTART, CONCEPTS, and BENCHMARKS now lead with
+  the evidence-backed, two-tier positioning — ANMA as insurance for cheaper agents
+  plus a CI/governance guarantee — and explicitly separate the benchmarked
+  *guidance* win from the separately-verified *enforcement* hook. The frontier
+  (Opus 4.8) null result is published rather than hidden.
+
+## [0.5.3] — 2026-06-06
+
+### Added
+- `--scenario NAME` filter on the benchmark runner (repeatable) so a focused run
+  (e.g. 20 trials on one scenario) doesn't spend tokens on the whole suite.
+
+### Changed
+- `docs/BENCHMARKS.md` rewritten around the first real results: a two-tier
+  finding (frontier models respect documented architecture unaided; cheaper
+  models violate routinely and ANMA drives that to zero), with the enforcement
+  layer verified by a direct hook test. Positions ANMA as insurance for cheaper
+  agents plus a CI/governance guarantee, and publishes the frontier null result.
+
+## [0.5.2] — 2026-06-06
+
+Follow-ups from the second live run (which showed the harness mis-attributing a
+control-arm permission denial as an ANMA hook block, and both arms tying at 0
+violations because a strong model passed the easy scenarios).
+
+### Fixed
+- Harness attributes hook blocks to ANMA **only when the ANMA hook is installed**
+  in that arm; the control arm now reports `—` for hook blocks instead of a
+  misleading count.
+
+### Added
+- `orders-inventory` adversarial scenario: the easy implementation crosses the
+  forbidden `orders → inventory` boundary and the correct path (caller-injected
+  callback) is non-obvious — designed so a capable model tends to slip in the
+  control arm, giving ANMA something to prevent.
+
+## [0.5.1] — 2026-06-06
+
+Fixes from the first live `claude-code` benchmark run, which surfaced two real
+enforcement bugs and a harness that mis-scored blocked runs.
+
+### Fixed
+- **Hook now judges the proposed edit, not the project's current state.** The
+  PreToolUse hook reconstructs the post-edit content and blocks (exit 2) only
+  when *that edit* introduces a new disallowed import. This fixes a deadlock
+  (a project red for any reason blocked every edit, including the fix) and makes
+  the headline claim true (a violating edit is blocked as it is made, not on the
+  next edit). Hook logic moved into the package (`anma.hook`) so it is tested and
+  upgradable via `pip install -U`; the generated hook is a thin shim that fails
+  open with a warning if `anma` isn't importable.
+- **`anma sync` now qualifies `public` interface paths** to the module's import
+  path in `tach.toml` (e.g. `accounts.service.get_user` →
+  `domains.accounts.service.get_user`). Previously these were emitted verbatim,
+  so `tach check` failed out of the box for any module nested under a source
+  root. (The single-module-at-root dogfood had masked this.)
+
+### Changed
+- Benchmark harness parses `claude --output-format json`: real `num_turns`, hook
+  blocks counted from `permission_denials`, and a per-trial `status`
+  (`ok`/`no_change`/`error`). Runs that changed no code or errored are flagged
+  and excluded from violation scoring, so an incomplete run can no longer be read
+  as a clean pass.
+
+## [0.5.0] — 2026-06-05
+
+Ground-up rewrite around a single goal: *with ANMA, Claude Code makes fewer
+architectural mistakes, preserves architecture across sessions, respects module
+boundaries, and coordinates parallel work better than a normal repo.* The
+previous "7 principles / 24 linter checks" framing is gone; ANMA is now a thin
+layer over Claude Code's native memory + hooks plus a real boundary engine.
+
+### Added
+- `anma sync --check` — drift detection; fails if generated artifacts no longer
+  match the contracts (for CI).
+- `anma check --warn` and per-module `deprecated_deps` — incremental adoption
+  without a red build on day one.
+- `anma check --json` — machine-readable output, with documented exit codes.
+- Monorepo support via `source_roots:` (multiple roots).
+- `schema_version` with a SemVer stability promise; contracts newer than the
+  tool are rejected rather than misread.
+- `owners:` per module → generated `.github/CODEOWNERS`.
+- `exclude:` in project config plus a default-ignore set (`node_modules`,
+  `.venv`, build dirs, …) so discovery skips non-source trees.
+- Security model + disclosure policy (`SECURITY.md`), a signed-release pipeline
+  (PyPI Trusted Publishing + build-provenance attestations + CycloneDX SBOM),
+  and `pip-audit` in CI.
+- A reproducible benchmark harness (`benchmarks/`) with an independent violation
+  scorer and a deterministic replay mode; scenarios for the boundary and
+  cross-session-persistence goals.
+- ANMA dogfoods itself: the repo carries its own contracts, enforced in CI.
+
+### Changed
+- Single source of truth: contracts compile to `CLAUDE.md`, nested `CLAUDE.md`,
+  rules, the PreToolUse hook, `tach.toml`, and CI.
+- Boundary engine is swappable: `tach` (default, interface-aware) with a
+  zero-dependency builtin `ast` fallback.
+- Apache-2.0; the published wheel ships only the `anma` package.
+
+### Removed
+- The "7 architectural principles" and the legacy multi-check linter.

anma-0.5.5/CLAUDE.md

@@ -0,0 +1,61 @@
+# anma
+
+ANMA turns per-module `anma.yaml` contracts into the artifacts that keep Claude
+Code inside module boundaries: a generated architecture map, nested `CLAUDE.md`
+files, a PreToolUse hook, and a boundary-check engine. Contracts are the single
+source of truth — never hand-edit generated files.
+
+## Commands
+- `pip install -e .[dev]` — install with pytest
+- `python -m pytest tests/ -q` — run tests (keep them green before commits)
+- `anma sync .` — regenerate all artifacts after editing any `anma.yaml`
+- `anma check .` — enforce boundaries (also runs in CI and the pre-commit hook)
+
+## Internal architecture
+This package is intentionally small (~650 LOC). The internal dependency
+direction is strict — lower layers must NOT import higher ones:
+
+    contracts.py   leaf: load + validate contracts (no internal imports)
+    templates.py   leaf: generated-artifact strings (no internal imports)
+    scaffold.py    leaf: `anma init` example (no internal imports)
+    engine.py      depends on: contracts            (tach adapter + builtin checker)
+    compile.py     depends on: contracts, templates (renders all artifacts)
+    cli.py         depends on: all of the above     (orchestrator / entry point)
+
+INVARIANT: core (`contracts`, `engine`, `compile`, `templates`, `scaffold`)
+must never import `cli`. `cli` is the only place argparse and I/O wiring live.
+
+INVARIANT: `tach` is optional. `engine.py` must keep working with zero extra
+dependencies via the builtin `ast` checker. Never make tach a hard import.
+
+## What not to edit by hand (generated by `anma sync`)
+- the `ANMA:MAP` block below
+- `anma/CLAUDE.md`, `.claude/rules/`, `.claude/hooks/`, `tach.toml`,
+  `.github/workflows/anma.yml`
+To change behavior, edit a contract or `anma/templates.py`, then re-sync.
+
+## Dogfooding note (known limitation)
+ANMA currently models a "module" as a *directory* with an `anma.yaml`. This
+package is a single flat module, so `anma check` enforces the *workflow* here
+(generated CLAUDE.md + green CI) but cannot yet enforce the internal layering
+above — that needs file/layer-level modules. Tracked as the next core feature;
+it also matters for enterprise layered-monolith packages.
+
+<!-- ANMA:MAP:START -->
+## Architecture map (generated by `anma sync` — do not edit by hand)
+
+This project uses ANMA contracts. **Respect these module boundaries.** A module
+may only import from modules listed under "uses". Going outside that is blocked
+by a pre-commit hook and CI.
+
+- **anma** — The ANMA tool itself — contracts compile to CLAUDE.md, hooks, and a boundary engine.  
+  uses: (nothing)
+
+**Rules**
+- Import other modules only through their public interface (listed in each
+  module's own `CLAUDE.md`). Do not reach into a module's internals.
+- If you need a dependency that isn't allowed, do not add the import. Update the
+  source module's `anma.yaml` (`depends_on`), run `anma sync`, and record why in
+  `DECISIONS.md` — then the boundary is real and persists to the next session.
+- Run `anma check` before committing. It also runs in CI.
+<!-- ANMA:MAP:END -->

anma-0.5.5/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing
+
+ANMA is deliberately small (~780 lines). The bar for new code is high: prefer
+making the existing primitives sharper over adding surface area. If a change
+grows the tool a lot, it probably belongs in a plugin or a separate scenario, not
+the core.
+
+## Dev setup
+
+```bash
+git clone https://github.com/anma-labs/anma
+cd anma
+pip install -e .[dev]      # pytest + pip-audit; add [tach] for the tach engine
+python -m pytest tests/ -q
+```
+
+## ANMA dogfoods itself
+
+The repo carries its own contracts, so the same checks you ship run here:
+
+```bash
+anma sync --check .        # generated docs/config are current with the contracts
+anma check .               # internal boundaries respected
+```
+
+Both must pass before a PR merges (CI enforces them in the `dogfood` job).
+
+## PR checklist
+
+- [ ] `python -m pytest tests/ -q` green (and `benchmarks/` tests if you touched the harness)
+- [ ] `anma sync --check .` and `anma check .` clean — if you changed a contract or a template, re-run `anma sync .` and commit the regenerated files
+- [ ] `pip-audit` clean
+- [ ] New behavior has a test; new contract fields are documented in `docs/CONCEPTS.md`
+- [ ] `CHANGELOG.md` updated under "Unreleased"
+
+## The schema-stability rule (read before touching contracts)
+
+The contract schema is ANMA's real public API — users commit to it. Treat it like
+one:
+
+- Adding an **optional** field with a safe default is a minor change.
+- Removing or renaming a field, changing a field's meaning, or making a field
+  required is a **breaking** change: bump `SUPPORTED_SCHEMA` in
+  `anma/contracts.py`, bump the tool's major version, and ship a migration path.
+- Never make the tool silently reinterpret existing contracts.
+
+## Code shape
+
+- Keep `cli.py` as the only place argparse/IO wiring lives; core modules
+  (`contracts`, `engine`, `compile`, `templates`, `scaffold`) must not import it.
+- `tach` stays optional — `engine.py` must keep working via the builtin checker
+  with zero extra dependencies.
+- Generated artifacts are produced by pure `render_*` functions in `compile.py`
+  so `anma sync` and `anma sync --check` share one code path. Keep them pure.
+
+## Reporting security issues
+
+See [SECURITY.md](SECURITY.md) — do not open public issues for vulnerabilities.

anma-0.5.5/DECISIONS.md

@@ -0,0 +1,8 @@
+# Architecture decisions (ANMA)
+
+Append-only. Each entry explains *why* a boundary is the way it is, so neither
+you nor Claude relitigates it next session. Newest on top.
+
+## 2026-06-05 — Adopted ANMA contracts
+Module boundaries are now declared in per-module `anma.yaml` files and enforced
+by `anma check` (pre-commit + CI + Claude Code PreToolUse hook).

anma-0.5.5/LICENSE

@@ -0,0 +1,200 @@
+
+                                 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 the 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 the 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 any 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. Please also get an approval
+      for your intended use before applyting the License.
+
+   Copyright 2026 ANMA Labs LLC
+
+   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.