UN Charter 1945
UN Charter (1945, as amended) as an executable model with worked cases; not UN-affiliated
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
| Package | Version | Scenarios | Dependencies |
|---|---|---|---|
doctrine.iura_humana | 0.1.0 | 1 | 0 |
un.charter | 0.1.0 | 169 | 1 |
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.
Installation
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @arxo/mcp-charterSet up in your AI client
Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-arxo-charter": {
"command": "npx",
"args": [
"-y",
"@arxo/mcp-charter"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencePackage
Compatible MCP Clients
UN Charter 1945 works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
- Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect. - Cursor
~/.cursor/mcp.jsonRestart Cursor for changes to take effect. - VS Code
.vscode/mcp.jsonReload VS Code window for changes to take effect. - Windsurf
~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect. - Claude Code
.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.