rapier-runtime 0.1.0__tar.gz

rapier_runtime-0.1.0/.gitignore

@@ -0,0 +1,31 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+build/
+dist/
+.eggs/
+
+# Environments
+.venv/
+venv/
+env/
+
+# Secrets — never commit
+.env
+*.env
+!*.example.env
+
+# Test / tooling
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+
+# Rapier run artifacts (may contain decision content)
+runs/
+
+# Local test tooling (this environment lacks python3-venv)
+.tools/
+.pytmp/

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

rapier_runtime-0.1.0/PKG-INFO

@@ -0,0 +1,249 @@
+Metadata-Version: 2.4
+Name: rapier-runtime
+Version: 0.1.0
+Summary: A code-orchestrated engine that runs the SPARRING method: grounded, cross-vendor adversarial review for AI-in-the-loop decisions.
+Project-URL: Homepage, https://rapierruntime.com
+Project-URL: Repository, https://github.com/muddyone/rapier-runtime
+Project-URL: Issues, https://github.com/muddyone/rapier-runtime/issues
+Project-URL: Paper, https://doi.org/10.5281/zenodo.21210265
+Author-email: Bart Niedner <contact@resourceforge.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: adversarial-review,ai-governance,anti-sycophancy,decision-support,llm,sparring
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
+Requires-Python: >=3.10
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: requests>=2.31
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.2; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# Rapier Runtime
+
+**A code-orchestrated engine that runs the SPARRING method** — grounded,
+cross-vendor adversarial review for AI-in-the-loop decisions.
+
+Most AI tooling helps you *build* agent workflows. Rapier is different: it
+*governs* them. It runs a structured, adversarial, grounded review over an AI's
+proposed answer — cross-vendor by construction, with mechanical grounding
+checks and a correctness gate — so that confident wrongness is structurally
+hard to ship. The method is [SPARRING](https://github.com/muddyone/sparring-publicaccess);
+Rapier is the runtime that executes it.
+
+> **Method vs. runtime.** *SPARRING* is the method (the concept, described in
+> its own papers and framework). *Rapier* is the runtime that executes a
+> SPARRING method declared in a manifest. Upgrade the runtime, or swap a model
+> in a manifest, without changing the method.
+
+Free and open source (Apache-2.0). Not monetized.
+
+---
+
+## Status: pre-alpha — the full ceremony runs end-to-end (M0–M3 complete; M4 in progress)
+
+This is early software, pinned pre-1.0 — but the whole method runs. What works
+today:
+
+- **The full SPARRING ceremony, end-to-end.** The **Proposer** (divergent
+  generation → false-novelty filter → the Cut — a cross-vendor convergence loop)
+  hands a committed option to the **Resolver** (author → cross-vendor review →
+  anchored correction → a correctness *definitiveness* gate → an external-canon
+  citation gate → a two-part report). Run the Resolver alone (`spar`) or the
+  whole loop (`sparring`).
+- **Cross-vendor by construction.** Author and reviewer are always distinct
+  vendors when two keys are present, and it degrades *honestly* to single-vendor
+  (and says so) when only one is. Any role can be Anthropic, OpenAI, Gemini,
+  Grok, or any OpenAI-compatible endpoint — vendor and model names live only in
+  a manifest.
+- **A manifest *is* the method.** Reorder stages, swap a model, or point two
+  roles at two vendors — with no engine-code change. Built-in presets (`spar`,
+  `sparring`, `proposer`) cover the common cases; `--settle` and `--verify` tune
+  the resolver.
+- **Grounding + a correctness gate.** The definitiveness gate checks that every
+  hard specific in the answer is traceable to the given facts or explicitly
+  flagged as an estimate; the citation gate resolves cited external canon
+  (CWE / RFC / DOI / …). Both wrap one shared, battle-tested verification
+  service — no duplicate copies.
+- **Auditable and safe by design.** Opt-in, redacted, owner-only run
+  persistence; a verbatim model-call transcript; env-only secrets + redaction;
+  `yaml.safe_load`; a [threat model](docs/threat-model.md) and a
+  [security policy](SECURITY.md).
+
+116 tests pass. Cross-vendor runs are live-proven (Anthropic×OpenAI, Gemini×Grok).
+
+**Honest boundary.** The definitiveness gate, anchored correction, and the
+two-part trust rider are *exploratory* governance instruments — useful, but not
+yet validated by a pre-registered study. Rapier makes confident wrongness
+structurally *harder to ship*; it does not make an answer correct.
+
+## Quickstart
+
+```bash
+pip install .          # or: pip install git+https://github.com/muddyone/rapier-runtime.git
+
+export ANTHROPIC_API_KEY=...    # author + gate
+export OPENAI_API_KEY=...       # a distinct cross-vendor reviewer
+                                # (or GEMINI_API_KEY / XAI_API_KEY)
+
+rapier spar     --request "Should we adopt Kubernetes for one flat-traffic web app?"
+rapier sparring --request "Monorepo or separate repos for our three services?"
+```
+
+`spar` runs the Resolver on a chosen option; `sparring` runs the full four-phase
+ceremony. Add `--settle N` for extra decision-stability rounds, or
+`--verify off|gate|round` to tune the citation gate. Point `--ledger-dir` at a
+directory to persist the run's transcript, report, and records.
+
+No keys? The `mock` vendor needs none:
+
+```bash
+rapier run --manifest manifests/echo.yaml --request "should we ship X?"
+# -> [mock:rapier-echo-1] should we ship X?
+```
+
+Runtime dependencies are just `requests` and `pyyaml` — every vendor is called
+over the wire; no provider SDKs.
+
+## Configure your keys
+
+Rapier reads vendor keys from the **environment only** — never from a file it
+reads itself. Scaffold and check your setup:
+
+```bash
+rapier init      # writes .env.example (key names, no values)
+# fill in .env, then load it into your shell:
+set -a; source .env; set +a
+rapier doctor    # shows which vendors are configured (names only — never values)
+```
+
+`doctor` reports each vendor's key env var as set/unset and whether cross-vendor
+review is available (two or more keys). A ceremony launched with **no** keys
+fails loudly with an actionable message instead of producing empty output.
+
+### Keep your keys loaded
+
+Environment variables last only for the current shell, so `source .env` sets
+them up for **this session** — a new terminal starts empty. That's the same as
+`aws`, `gh`, and most API-key CLIs, and it's deliberate here: Rapier reads keys
+only from the environment and never persists a secret itself. To avoid re-running
+the command each time, set it up once:
+
+- **Load in every shell** — add the source line to your shell profile (e.g.
+  `~/.bashrc` or `~/.zshrc`), pointing at a keys file you keep outside any repo:
+
+  ```bash
+  # add once to ~/.bashrc
+  set -a; source ~/.config/rapier/keys.env; set +a
+  ```
+
+  Simplest for a personal machine. (Trade-off: the keys then load into *every*
+  shell, and live in a file on disk — fine for your own box, less so on a shared
+  one.)
+
+- **Load per directory — [`direnv`](https://direnv.net/)** — auto-loads a
+  project's `.env` when you `cd` in and unloads it when you leave. Cleaner
+  isolation; a one-time `direnv allow` per directory.
+
+- **Per session** — just run `set -a; source .env; set +a` when you sit down to
+  use it. Fine for occasional use.
+
+One gotcha: `source` runs the file as shell, so every value with spaces must be
+**quoted** (`FOO="a b c"`, not `FOO=a b c`) or `source` will try to run the extra
+words as a command. If sourcing errors, that's usually the cause.
+
+## Use it from an MCP client (optional)
+
+Expose `spar` / `sparring` (and a `rapier_doctor` check) as tools to any MCP
+client — Claude Desktop, editors, agents:
+
+```bash
+pip install "rapier-runtime[mcp]"
+```
+
+Point the client at the stdio server. Keys travel in the server's `env` block —
+the client launches the process with them, and the engine reads them from the
+environment (it still reads no secret from a file):
+
+```jsonc
+{
+  "mcpServers": {
+    "rapier": {
+      "command": "rapier",
+      "args": ["mcp"],
+      "env": { "ANTHROPIC_API_KEY": "…", "OPENAI_API_KEY": "…" }
+    }
+  }
+}
+```
+
+## Updating & staying current
+
+Check your version, and update to the latest release:
+
+```bash
+rapier --version                    # what you have (also shown by `rapier doctor`)
+pip install -U rapier-runtime       # update to the latest ( add [mcp] if you use the MCP server )
+```
+
+Because Rapier can read files, fetch URLs, and call model vendors, **staying
+current matters for security.** How to hear about issues:
+
+- **Security fixes** are published as **GitHub Security Advisories**, which flow
+  into the Python vulnerability databases — so `pip-audit` and GitHub Dependabot
+  will flag an affected version automatically if you use them.
+- **Watch [Releases](https://github.com/muddyone/rapier-runtime/releases)** on
+  GitHub (Watch → Custom → Releases) to be notified of new versions.
+- **Found a vulnerability?** Report it privately — see
+  [`SECURITY.md`](SECURITY.md). Please don't open a public issue.
+
+Rapier does **not** phone home to check for updates — nothing about your usage
+leaves your machine except the model calls you configure.
+
+## A manifest is the method
+
+```yaml
+name: echo
+pipeline:
+  - stage: echo
+    config: { note: "hello from Rapier" }
+    roles:
+      author: { vendor: mock, model: rapier-echo-1 }
+```
+
+Editing the manifest changes the method — reorder stages, swap a model, point
+two roles at two different vendors — without touching engine code.
+
+## Roadmap
+
+| Milestone | What | |
+|---|---|---|
+| M0 | Skeleton + threat model + security baseline | ✅ |
+| M1 | Resolver ported (one shared grounding/verification service) | ✅ |
+| M2 | The Proposer (convergence primitive; SPARK / Pattern Lock / the Cut; cross-vendor roles) | ✅ |
+| M3 | Full controller + the `spar` / `sparring` adapters (the whole ceremony end-to-end) | ✅ |
+| M4 | Hardening + packaging + first public release | in progress |
+
+## Development
+
+```bash
+pip install -e '.[dev]'
+pytest -q
+```
+
+## License
+
+Apache-2.0. See [LICENSE](LICENSE).
+
+---
+
+Rapier Runtime and the SPARRING method are projects of **[ResourceForge](https://resourceforge.com)**.