memjudge 0.1.0__tar.gz

memjudge-0.1.0/.dockerignore

@@ -0,0 +1,16 @@
+# Only what runner/Dockerfile copies: pyproject.toml, README.md, LICENSE, src, connectors, runner.
+**/.venv
+**/__pycache__
+**/*.pyc
+**/.pytest_cache
+**/.mypy_cache
+**/.ruff_cache
+.git
+runs
+selections
+tests
+runner/tests
+docs
+*.log
+*.key
+.env*

memjudge-0.1.0/.gitignore

@@ -0,0 +1,224 @@
+# 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
+
+# MemJudge
+runs/
+selections/
+*.key
+.memjudge-cache/

memjudge-0.1.0/CHANGELOG.md

@@ -0,0 +1,73 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project uses
+[Semantic Versioning](https://semver.org/). Changes that alter scores are marked **[scoring]**.
+
+## [0.1.0] - 2026-11-02
+
+First release.
+
+### Added
+- Core engine and `memjudge` CLI: `run` (with `--resume`), `report`, `rejudge`, `estimate`,
+  `calibrate` (compares several judges), `crosscheck` (second-judge sample check), `keygen`,
+  `sign`, `verify`, `cleanup`, `conversations`, `datasets`, `connectors`,
+  `validate-dataset`, `schema`.
+- Canonical dataset format with SHA-256 hashing, errata overlays and adapters for LoCoMo and
+  LongMemEval (cleaned S and oracle), downloaded from pinned upstream revisions. LongMemEval
+  abstention questions keep their question type as category **[scoring]**.
+- Connectors: BM25 baseline, Mem0 Platform (v3), Mem0 open source (in-process, full
+  multi-signal setup), Zep Cloud (v3), Zep Graphiti open source (in-process, local
+  FalkorDB), Supermemory (v5), Letta (v1), Recalld (v1 API, vendor-maintained by the
+  MemJudge maintainer), and an offline replay of recorded results. Each connector's SDK is
+  an install extra (`memjudge[mem0]`, `[mem0-oss]`, `[zep]`, `[graphiti]`, `[supermemory]`,
+  `[letta]`, or `[all]`), pinned to the version it was written against.
+- Connector contract (ADR 0007): `retrieve` takes `top_k`. `connector.yaml` lists the
+  settings that name models (`models:`, or `vendor` when the vendor hides them; ADR 0014),
+  named setting overrides (`presets:`) and `max_concurrency` (ADR 0013). Every system that
+  lets you choose its LLM runs GPT-6 Luna. Optional batch ingestion (`ingest_batch`,
+  ADR 0010) uploads the whole run at once; Recalld uses it.
+- Top 10 and Top 30 (ADR 0018): every run scores two result sizes from one ingestion. Each
+  question is retrieved twice, for up to 10 and up to 30 items, and each size is judged on
+  its own. The two calls alternate their order from question to question. Zep and Graphiti
+  split the size into facts and entities, 20 + 10 and 7 + 3. **[scoring]**
+- Judge-only scoring (ADR 0001) with routes for Anthropic, OpenAI, Google and OpenRouter
+  (provider pinned, no fallback). A reply holding more than one JSON object counts its last
+  valid verdict. **[scoring]**
+- Seasons (ADR 0015): `src/memjudge/judge/seasons.json` lists every season's judging rules
+  (judge, effort, prompt version and hash) with a name, start date, summary, details link and
+  how earlier runs get in (`upgrade`: `re-judge` or `re-run`). Tests freeze each season's
+  prompt file, and CI rejects changes to past seasons. Season 1 is Claude Sonnet 5.5 with
+  judge prompt v3. **[scoring]**
+- Re-judging: `memjudge rejudge` judges a run's stored contexts again and records
+  `rejudged_from`, keeping the earlier run's connector record.
+- Metrics: accuracy with cluster-bootstrap 95% CI, context tokens, efficiency, latency,
+  ingestion time until searchable (`per-session` or `batch`, ADR 0017), abstention accuracy,
+  stale-fact rate, evidence recall, error rate, truncation rate, flagged questions, judge
+  cost, and the usage each memory system reports.
+- A run stops when an ingestion fails or 5 retrievals fail in a row. Completed
+  conversations are saved; `memjudge run --resume` redoes the unfinished ones.
+- Every connector accepts a `base_url` setting; results record the endpoint called (without
+  credentials) and flag custom endpoints (localhost, staging, self-hosted).
+- Partial runs: `--conversation`, `--category`, `--smallest`, `--sample`, and
+  `memjudge conversations` to list conversations by size.
+- `--keep-data`, `--reuse-ingestion` and `memjudge cleanup`: rerun only retrieval and
+  judging against data kept by an earlier run (local-only; labelled in the result).
+- `memjudge estimate` (also `--json`): what the memory system must ingest (sessions, write
+  calls, turn tokens), and the judge cost, typical and upper bound, for both result sizes.
+- RFC 8785 + Ed25519 signing and verification. `memjudge verify` trusts the bundled hosted
+  runner key `478df5eb628bfa74`; `memjudge sign --artifact-url-prefix` records each
+  artifact's URL in the signed payload.
+- HTML report per result size with ECharts (loaded from a CDN with subresource integrity)
+  and a 2–4 run compare view.
+- Hosted runner (`runner/`, package `memjudge-runner`, ADR 0009): Runner API, retrieve job
+  and finish job on Google Cloud Run, with GitHub login. Each connector's jobs may reach only
+  its declared domains (`memjudge-runner egress`). A stopped run can be resumed within 48
+  hours, at most 3 times, on the jobs of its own release (ADR 0011). Owners see the job log
+  and each result records its stops and resumes (ADR 0016). Anyone signed in can re-judge a
+  published run into the current season with their own judge key. Mem0 Platform and Zep
+  Cloud are local-only, because their terms forbid publishing benchmark results without the
+  vendor's consent. `.github/workflows/runner.yml` builds the image and deploys one job set
+  per release.
+
+[0.1.0]: https://github.com/memjudge/memjudge/releases/tag/v0.1.0

memjudge-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,10 @@
+# Code of Conduct
+
+MemJudge adopts the [Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).
+
+In short: be respectful, assume good faith, critique work rather than people, and do not
+harass anyone. This applies in issues, pull requests, discussions and any MemJudge space.
+
+Report unacceptable behaviour to **admin@memjudge.org**. Reports are handled confidentially
+by the maintainers, who may warn, temporarily ban or permanently ban contributors, following
+the Covenant's enforcement guidelines.

memjudge-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,41 @@
+# Contributing to MemJudge
+
+Thanks for helping make memory benchmarks trustworthy.
+
+## Development setup
+
+```bash
+python -m venv .venv && source .venv/bin/activate   # Windows: .venv\Scripts\activate
+pip install -e ".[dev,all]"
+pytest && ruff check . && ruff format --check . && mypy
+```
+
+CI runs the same checks on Python 3.11–3.13. Pull requests must keep CI green.
+
+## What we accept
+
+- **Connectors** — see [docs/adding-a-connector.md](docs/adding-a-connector.md).
+- **Datasets** — see [docs/adding-a-dataset.md](docs/adding-a-dataset.md); include the
+  licence and a pinned source.
+- **Errata** — corrections to gold answers with evidence from the source conversation.
+- **Bug fixes and docs.** For larger changes, open an issue first.
+
+## Standards
+
+- Typed (mypy strict), documented, small modules. Avoid new dependencies unless needed;
+  explain why in the PR.
+- Tests for anything that affects scoring, signing, dataset adapters or connectors.
+- Significant design decisions get a short ADR in `docs/decisions/`.
+- Never commit secrets, test keys or personal data.
+- Changes that alter scores (judge prompt, metrics, adapters) must say so in the PR and in
+  `CHANGELOG.md`.
+
+## Conflicts of interest
+
+If you work for or with a memory-system vendor, say so in your PR. Vendors are welcome to
+review and maintain connectors for their own systems (`label: vendor-maintained`).
+
+## Releases
+
+Semantic versioning; tagged releases published to PyPI by CI, which also builds and deploys
+the hosted runner's container image for each release.

memjudge-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 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 2026 Bit Robotics Ltd
+
+   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.