UNIDROIT Principles 2016 as executable rules: closed questions answered with grounds and source text
MCP Server: io.arxo/picc
The io.arxo/picc Model Context Protocol (MCP) server provides executable rules representation of the UNIDROIT Principles 2016. It focuses on closed questions and returns answers that include grounds and source text, aligning each response with the underlying referenced material.
🛠️ Key Features
Encodes UNIDROIT Principles 2016 as executable rules
Answers closed questions
Includes grounds with answers
Provides source text used in responses
🚀 Use Cases
Rule-based Q&A grounded in UNIDROIT Principles 2016
Generating responses for closed questions with supporting rationale
Returning answers together with the referenced source text
⚡ Developer Benefits
Structured outputs that pair answers with grounds and source text
Builds Q&A behavior directly from UNIDROIT Principles 2016 rules
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.
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.
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.