Arxo Charter 1945 MCP Server

arxo-charter-1945

Pinned canon, executable as it stands: source text with provenance, the model built over it and the scenarios that check its answers. The norms here are data — they are executed by law; this repository carries no rule code of its own.

Contents

How it is verified

Every package is built by package.py with the pinned toolchain: compilation, §267 scenarios on both evaluators, replay of saved evaluations and a rebuild from the release itself. A failure of any step stops the build.

python3 tools/toolchain.py download --lock toolchain.lock.json --out /tmp/law-tools
python3 /tmp/law-tools/package.py packages/<name> \
    --lawc /tmp/law-tools/law-cli --offline --out /tmp/<name>-release

Dependencies

Dependency bytes are pinned under packages/<name>/deps/ and verified against the contentHash recorded in law.lock: the build and the CI are offline.

Worked cases

Each collection is a case package of its own: the facts, the questions and the answers, with the pinned canon as its dependency. Ask one from its directory with law ask . — nothing is downloaded.

Rights

Code and model: see LICENSE. The pinned texts of the publishers keep their own terms of reproduction, listed per package in NOTICE; those terms are not covered by the code licence.

Maintainer: Rifat Dzhumagulov (hi@arxo.io). Address: https://github.com/arxohq/arxo-charter-1945.