UNIDROIT Principles 2016
UNIDROIT Principles 2016 as executable rules: closed questions answered with grounds and source text
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http unidroit-principles-2016 'https://mcp.arxo.io/mcp/picc'
{
"mcpServers": {
"unidroit-principles-2016": {
"type": "http",
"url": "https://mcp.arxo.io/mcp/picc"
}
}
}
@arxo/mcp-piccclaude mcp add unidroit-principles-2016 -- npx -y @arxo/mcp-picc@0.3.11
{
"mcpServers": {
"unidroit-principles-2016": {
"command": "npx",
"args": [
"-y",
"@arxo/mcp-picc@0.3.11"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
arxo-unidroit-picc
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 |
|---|---|---|---|
unidroit.picc | 0.1.0 | 5 | 0 |
unidroit.picc_formation | 0.1.0 | 4 | 1 |
unidroit.picc_limitation | 0.1.0 | 3 | 1 |
unidroit.picc_non_performance | 0.1.0 | 4 | 1 |
unidroit.picc_obligations | 0.1.0 | 4 | 1 |
unidroit.picc_performance | 0.1.0 | 4 | 1 |
unidroit.picc_validity | 0.1.0 | 4 | 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.
Asking these packages
Two ways, the same slice of the canon and the same engine; the difference is whose machine evaluates.
- Hosted:
https://mcp.arxo.io/mcp/picc— requests are evaluated on Arxo infrastructure. - Local:
docker compose -f mcp/compose.yml up— nothing leaves the machine.
mcp/pin.json records what either one must answer from: the
content hash of the canon profile, the pinned packages, the ABI
version of the engine and the availability of the hosted endpoint.
An answer that cannot be traced to that pin is not this repository's
answer.
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-unidroit-picc.
Questions fréquentes
Qu'est-ce que UNIDROIT Principles 2016 ?
UNIDROIT Principles 2016 as executable rules: closed questions answered with grounds and source text
Comment installer UNIDROIT Principles 2016 ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http unidroit-principles-2016 'https://mcp.arxo.io/mcp/picc'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour UNIDROIT Principles 2016 ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
UNIDROIT Principles 2016 est-il open source ?
Oui. Son code est sur GitHub sous licence Apache-2.0.
Qui maintient UNIDROIT Principles 2016 ?
Il est publié par arxohq. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.