arbiter-engine 0.1.0__tar.gz

arbiter_engine-0.1.0/.gitattributes

@@ -0,0 +1,30 @@
+# Line endings: normalize to LF in the repository, checkout per platform
+*text=auto eol=lf
+
+# Documentation and configuration files (explicit text)
+*.md text
+*.txt text
+*.rst text
+*.yaml text
+*.yml text
+*.json text
+*.cff text
+*.toml text
+
+# Binary file safety
+*.png binary
+*.jpg binary
+*.jpeg binary
+*.gif binary
+*.svg text
+*.pdf binary
+*.zip binary
+*.tar.gz binary
+*.ico binary
+
+# Language hints for GitHub Linguist
+*.md linguist-documentation
+LICENSE linguist-documentation
+NOTICE.md linguist-documentation
+AUTHORS.md linguist-documentation
+TRADEMARK.md linguist-documentation

arbiter_engine-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,80 @@
+---
+name: Bug report
+about: The engine reported something you believe is wrong
+title: ''
+labels: bug
+assignees: ''
+---
+
+## Before you write it up: read the declines
+
+`check()` returns four legs, and the answer is in `not_checked` more often than
+in `findings`. An axiom that declined did not fail — it reports a
+machine-readable reason for why it could not run, and that reason is usually the
+whole story.
+
+Two that account for most surprises:
+
+- **`not_applicable`** — some axioms decide whether they apply by reading the
+  indicator's name. `CONSISTENCY` wants `count`, `percent`/`pct` or `ratio` in
+  it; `RESPONSIVENESS` wants `response` or `latency`. This is a known rough
+  edge, not a rule you were supposed to infer.
+- **`insufficient_samples`** — the floor is per-axiom, and the decline states
+  both the count it had and the count it needed.
+
+If the decline explains it, you may not have a bug. Please open the issue
+anyway if the *reason* was unclear — a decline nobody can act on is a defect in
+its own right.
+
+## What happened
+
+<!-- One sentence. -->
+
+## What you expected
+
+<!-- Including which axiom you expected to fire, or to stay quiet. -->
+
+## The model
+
+<!-- The smallest domain YAML that shows it. Trim to the one entity type and
+     the one indicator if you can. -->
+
+```yaml
+
+```
+
+## How the session was fed
+
+<!-- Threshold axioms read the entity's `properties`; the temporal axioms read
+     observation history. Feeding only one is the commonest cause of a check
+     that reports nothing while a value is plainly out of range — so please
+     show both. -->
+
+```python
+
+```
+
+## The envelope
+
+<!-- ALL FOUR LEGS of check(). `not_checked` especially, verbatim. -->
+
+```json
+
+```
+
+## Environment
+
+- `arbiter-engine` version or commit:
+- Python version:
+- OS:
+- Optional extras installed (`scipy`, `rdflib`, `mcp`): <!-- these change which
+  modules import, so a difference here can change what you see -->
+
+## Anything else
+
+<!-- When it started, a workaround you found, a related issue. -->
+
+---
+
+**Security vulnerabilities do not belong here.** Use the private channel in
+[SECURITY.md](../../SECURITY.md).

arbiter_engine-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,57 @@
+## What this changes
+
+<!-- Pull requests are not being merged yet: the public API is pre-1.0 and still
+     moving, so a patch against it may not survive the month. See CONTRIBUTING.md.
+     This form is here because a pull request that arrives anyway should carry
+     what a reviewer would otherwise have to ask for, and it will be read.
+
+     One paragraph below: what the reader gets that they did not have. -->
+
+## Why
+
+<!-- The defect, the gap, or the case that motivated it. If it fixes an issue,
+     link it: Closes #N. -->
+
+## Kind of change
+
+- [ ] Bug fix
+- [ ] New capability
+- [ ] Documentation
+- [ ] Breaking change to a supported name
+- [ ] Other
+
+## Evidence
+
+<!-- How do you know it works? Prefer output over description. -->
+
+- [ ] A test that **fails without this change**. If the test passes both before
+      and after, it is not evidence yet — the quickest proof is to revert the
+      change and watch it go red.
+- [ ] For a checker change: the envelope before and after, including
+      `not_checked`. A finding that appears is only half the claim; the declines
+      it stopped or started producing are the other half.
+- [ ] For anything touching the eleven supported names or `arbiter_engine.api`:
+      said so explicitly below.
+
+```
+
+```
+
+## Supported surface
+
+<!-- Eleven names are a contract; everything deeper is importable and
+     unpromised. Which did you touch? -->
+
+- [ ] Supported surface unchanged
+- [ ] Supported surface changed — described above, and why it could not be done
+      behind it
+
+## Checklist
+
+- [ ] Read [CONTRIBUTING.md](CONTRIBUTING.md)
+- [ ] Agree to the [Code of Conduct](CODE_OF_CONDUCT.md)
+- [ ] Licensed under Apache-2.0, per [LICENSE](LICENSE)
+- [ ] If AI-assisted: reviewed the generated content and accept it as my own
+      contribution, per [AI_ATTRIBUTION.md](AI_ATTRIBUTION.md)
+
+## Anything reviewers should know

arbiter_engine-0.1.0/.gitignore

@@ -0,0 +1,32 @@
+# Python build + cache artefacts.
+#
+# `__pycache__` is the load-bearing line: the build compiles the tree to prove
+# it imports standalone, and compiled bytecode embeds the absolute path of the
+# source it was compiled from. The build sweeps it and the staging copy filters
+# it, so this is the third net rather than the only one -- but it is the one
+# that decides what `git add -A` does in a release target.
+__pycache__/
+*.py[cod]
+*.so
+
+# Packaging
+build/
+dist/
+*.egg-info/
+.eggs/
+
+# Environments
+.venv/
+venv/
+
+# Test + type-checker caches
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.coverage
+htmlcov/
+
+# Editors
+*.swp
+*.swo
+.DS_Store

arbiter_engine-0.1.0/AI_ATTRIBUTION.md

@@ -0,0 +1,55 @@
+# AI Attribution
+
+Arbiter Project ("Arbiter") is developed using a workflow that combines human authorship with AI assistance. This file documents that workflow transparently, names the AI tools involved, and describes how the human-versus-AI contribution boundary is handled.
+
+This file is a disclosure mechanism, not a legal instrument. License terms are in [LICENSE](LICENSE); the attribution notice the licence requires is in [NOTICE](NOTICE); name-use policy is in [TRADEMARK.md](TRADEMARK.md); security reporting is in [SECURITY.md](SECURITY.md).
+
+## Tools used
+
+Arbiter's development uses the following AI tools alongside conventional editing, version control, and review:
+
+- **Claude Code** (CLI agent published by Anthropic) — primary AI development assistant. Used for code generation, refactoring, documentation drafting, test scaffolding, and architectural discussion.
+- **Anthropic Claude** large language models (currently the Opus family) — the underlying model that powers Claude Code.
+
+The project does not use other code-generation AI tools (e.g., GitHub Copilot, Cursor, etc.) at the time of writing. If that changes, this file will be updated.
+
+AI tools are licensed by the human author at the consumer / individual subscription tier.
+
+## Workflow division
+
+The author treats the following contribution categories as distinct:
+
+- **Human-authored** — design decisions, architectural choices, strategic decomposition, problem framing, the decision records those produce, methodology codified from review, narrative framing, and review of all generated output. The human author retains direct authorship of these surfaces.
+- **AI-assisted** — code and documentation where the human directs the AI tool with concrete instructions, then reviews, modifies, and integrates the output. The substantive selection, arrangement, and editorial control rest with the human; the AI tool generates candidate text/code that the human accepts, rejects, or modifies.
+- **AI-generated boilerplate** — purely mechanical scaffolding (e.g., test boilerplate, repetitive type stubs, format conversions) produced by AI on direct request without significant creative selection. This category is minimized in practice; most output is reviewed-and-modified before commit.
+
+Reviewers and downstream users should assume that any source file or documentation in this repository may contain AI-assisted content unless otherwise noted. The human author has reviewed and accepted all committed content.
+
+## Commit-level transparency
+
+Commits that include AI-assisted content carry a `Co-Authored-By:` trailer that names the specific model used — at the time of writing, `Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>`. **The named model changes as the tooling does, and the version in any given commit's trailer is the one that produced it**; this line records the form, not a constant. It previously quoted a superseded model version as though it were the current one, which is the failure mode a disclosure file can least afford. This trailer is a transparency marker — it documents AI involvement in the commit's authorship process. It does not assert that the AI is a legally recognized co-author; under current US copyright doctrine (US Copyright Office guidance, 2023), AI tools are not eligible for copyright authorship.
+
+The presence of the trailer is informational. Its absence on older commits does not imply they were free of AI assistance — the trailer was adopted partway through the project's history and has been applied consistently going forward.
+
+## Legal posture
+
+The legal treatment of AI-assisted and AI-generated content is unsettled in most jurisdictions. The project's working posture is:
+
+- **Copyright (human-contributed portions)**: the human author claims copyright in design choices, selection, arrangement, prompts, review/editorial control, and integration work. These contributions are licensed under the [Apache License 2.0](LICENSE) granted by the human author.
+- **Copyright (AI-generated portions)**: under current US Copyright Office guidance, content produced solely by AI without sufficient human authorship may not be eligible for copyright protection. The project does not assert copyright over such portions, nor does it deny that the Apache 2.0 grant applies to them. Downstream users may treat the entire repository as Apache-2.0-licensed for practical purposes; readers concerned about the legal status of specific portions are encouraged to seek their own counsel.
+- **Training-data inheritance**: large language models are trained on broad code and documentation corpora, including open-source-licensed material. The project's AI tool vendor (Anthropic) provides assurances regarding output rights; the project relies on those assurances. Downstream legal developments (e.g., pending or future rulings on AI training-data licensing) may affect this posture. The project will update this file if material changes warrant it.
+
+This file is not legal advice. Users with substantive copyright, licensing, or compliance concerns should consult qualified counsel.
+
+## What this means for reusers and contributors
+
+- **Reusers**: treat the repository as Apache-2.0-licensed for practical use, integration, and redistribution per [LICENSE](LICENSE). If you are deploying Arbiter in a context with strict provenance requirements (regulated industries, contractual provenance audits, etc.), incorporate this disclosure into your audit trail.
+- **Contributors**: if you submit a pull request, you are representing that any AI-assisted portion of your contribution complies with your AI tool vendor's terms and that you have the right to license your contribution under the project's Apache License 2.0. The project does not require disclosure of AI assistance in contributions, but welcomes it where the contributor wishes to document the workflow.
+
+## Updates
+
+This file is updated when the project's AI-tool usage materially changes — new tools adopted, vendor terms change, legal landscape shifts, or workflow division evolves. Minor model version bumps (e.g., Opus 4.6 → 4.7) do not require an update unless the vendor's terms change.
+
+## License of this file
+
+This AI_ATTRIBUTION file is part of the Arbiter Project documentation and is covered by the project's [Apache License 2.0](LICENSE). See also [TRADEMARK.md](TRADEMARK.md) for Arbiter Project name-use policy.

arbiter_engine-0.1.0/AUTHORS.md

@@ -0,0 +1,22 @@
+# Authors
+
+## Primary author
+
+**James Sheen** — primary author, designer, and current maintainer of the Arbiter Project.
+
+- GitHub: [@james-sheen](https://github.com/james-sheen)
+- Contact: see [SECURITY.md](SECURITY.md) for security disclosures; general project inquiries via the GitHub repository's issue tracker.
+
+The primary author retains copyright in design decisions, architectural choices, strategic decomposition, problem framing, decision documents, codified methodology, partner-materials narrative, and review of all committed content. See [LICENSE](LICENSE) for the Apache 2.0 grant covering project code and documentation, and [AI_ATTRIBUTION.md](AI_ATTRIBUTION.md) for the workflow division between human-authored and AI-assisted content.
+
+## Contributors
+
+Additional contributors will be acknowledged here and in commit history as they join. The Arbiter Project welcomes contributions per [CONTRIBUTING.md](CONTRIBUTING.md); contributor names are added to commit metadata and acknowledged in release notes where applicable.
+
+## Updates
+
+This file is updated when significant author or contributor changes occur. Routine commits do not require updates.
+
+## License of this file
+
+This AUTHORS file is part of the Arbiter Project documentation and is covered by the project's [Apache License 2.0](LICENSE). See also [TRADEMARK.md](TRADEMARK.md) for Arbiter Project name-use policy.

arbiter_engine-0.1.0/CITATION.cff

@@ -0,0 +1,21 @@
+cff-version: 1.2.0
+message: "If you reference Arbiter in academic work, please cite as follows."
+title: "Arbiter: a detection engine that reports what it did not check"
+abstract: "A domain-agnostic detection engine. Invariants are declared per indicator in a YAML domain model rather than in code, and evaluated by eight axiom checkers covering bounds, stability, baseline recovery, direction, conservation, topology, agreement and deadlines. Every pass returns findings alongside the evaluations that declined to run, each carrying a machine-readable reason, together with a count of evaluations attempted. A clean result is therefore distinguishable from one where nothing was testable, which is the property the engine exists to provide. Released under Apache 2.0."
+type: software
+authors:
+  - family-names: "Sheen"
+    given-names: "James"
+    alias: "james-sheen"
+  - name: "Arbiter Project"
+license: Apache-2.0
+version: "0.1.0"
+date-released: "2026-08-12"
+repository-code: "https://github.com/james-sheen/arbiter"
+url: "https://github.com/james-sheen/arbiter"
+keywords:
+  - anomaly-detection
+  - invariants
+  - ontology
+  - digital-twin
+  - observability

arbiter_engine-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,12 @@
+# Code of Conduct
+
+Arbiter follows the [Contributor Covenant Code of Conduct v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+
+All participants in Arbiter's issue tracker, discussions, and any community forum are expected to abide by these standards. Violations may be reported to the maintainers via the private channel described in [SECURITY.md](SECURITY.md) (GitHub Private Vulnerability Reporting routes confidentially to maintainers and is the appropriate intake for conduct reports as well as security disclosures).
+
+## Summary
+
+- Be kind. Assume good faith.
+- Critique ideas, not people.
+- Adversarial-finding reports describe bypass behavior; they do not describe testers as adversaries.
+- Harassment, abuse, and deliberate dissemination of harmful content are out of scope.

arbiter_engine-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,58 @@
+# Contributing
+
+The most useful thing you can send is a case where the engine reported a clean
+pass over something it did not actually evaluate. That is the failure the whole
+design exists to prevent, and it is the bug report this project wants most.
+
+## What is open right now
+
+**Issues: open.** Bug reports, adversarial findings, and questions about
+modelling a domain are all welcome. The bug form asks for the things that
+actually reproduce a defect here — the smallest domain model that shows it, how
+the session was fed, and all four legs of the envelope.
+
+**Pull requests: not being merged yet.** The public API surface is pre-1.0 and
+still moving, and a patch merged against a surface that changes next month
+helps nobody. This is a decision about timing rather than about the value of
+outside work, and it is recorded the same way in `ROADMAP.md`.
+
+A pull request template ships anyway, and that is deliberate: if you open one
+regardless, the form collects what a reviewer would otherwise have to ask for,
+and it will be read even while the merge queue is closed. An issue describing
+the change is the faster route to a decision.
+
+## Reporting well
+
+A decline you cannot act on is a defect in the thing this project claims to be
+good at. If `not_checked` gave you a reason and you could not work out what to
+do about it, that is worth an issue on its own — the reason is supposed to be
+actionable, and if it is not then the vocabulary or the documentation is wrong.
+
+Two reasons account for most surprises. `insufficient_samples` reports both the
+count it had and the count it needed. `not_applicable` means a checker decided
+the axiom does not apply at all, and some of them decide that by reading the
+indicator's name — a rough edge rather than a rule you should have to infer.
+
+## Sign-off
+
+Contributions are accepted under the Developer Certificate of Origin. There is
+no CLA and no copyright assignment. Sign your commits:
+
+```bash
+git commit -s
+```
+
+That adds a `Signed-off-by` line asserting you have the right to submit the work
+under this project's licence. Everything here is Apache 2.0.
+
+## AI-assisted contributions
+
+They are welcome and much of this repository was written that way; see
+`AI_ATTRIBUTION.md`. The requirement is the same as for anything else: you have
+read it, you understand it, and you are prepared to stand behind it. Generated
+code you have not reviewed is not a contribution, it is a request that someone
+else review it for you.
+
+## Conduct
+
+See `CODE_OF_CONDUCT.md`.

arbiter_engine-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 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.

arbiter_engine-0.1.0/NOTICE

@@ -0,0 +1,18 @@
+Arbiter
+Copyright 2023-2026 Arbiter Project
+
+This product includes software developed as part of the Arbiter Project.
+
+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.
+
+"Arbiter" is a project name, not a licence grant. Apache License Section 6
+withholds any trademark grant; TRADEMARK.md, alongside this file, states what
+use of the name IS permitted.