UNIDROIT Principles of International Commercial Contracts 2016 · CISG 1980EN · FR · RU · Arxo Law

The UNIDROIT Principles, running

UNIDROIT Principles 2016 (PICC) as an executable model: every answer names the article, the facts, and what stays with the tribunal.

Start hereSame Facts, Two Instruments

Ask in your own words

Four of the recorded conversations below, one question each: the model reads it and chooses where to look in the instrument.

Answers come from the model of the instrument, not legal advice.

Change one fact, watch the answer

Worked cases. Every position of a switch is a registered case answered by two independent evaluators.

Same Facts, Two InstrumentsOne sales contract answered by the Vienna Convention and by the Principles. Where the Convention is silent the Principles answer — if the case chooses to read article 7(2) that way. Battle of Forms: What Survives?Two printed forms that disagree. What they share is the contract; what differs knocks itself out; a surprising term is for the tribunal. Limitation: Dates and EffectsThe period begins on the day after. What an acknowledgement restarts, what arbitration suspends, and what expiry does not do until it is asserted. Defects of ConsentA mistake can be lost to the mistaken party's own negligence; fraud cannot. The derivation names the rule that was defeated and the one that defeated it. AssignmentA non-assignment clause does not stop a claim for money. Then: whom must the debtor pay, before and after notice?

See every remedy at once

Chapter 7 as a map, not a column of cards. Each scenario is a registered case; each branch is an answer of the engine.

Remedy NavigatorWithhold, cure, require performance, terminate, damages, cover. Open, defeated, or left to the tribunal — on one screen.

One crisis, two tracks

Hardship keeps the contract standing. Force majeure excuses a non-performance. Each scenario is a registered case; each branch is an answer of the engine.

Hardship vs Force MajeureCost explosion still being performed, or an embargo that stops delivery. Which track opens, which stays silent, and which finding the tribunal has not yet supplied.

Ask in plain words

Recorded conversations. The model reads the question and chooses where to look; every answer, every refusal and every hash came from the engine — and the build repeats each call before the page goes out.

Recorded dialoguesFive conversations with the Principles: hardship from a question in plain words, the engine refusing the model, an evaluative element left to the tribunal, a rule without a number, and the same answer twice.

Bring your own dates

Nothing here was prepared in advance: the engine runs in your browser on the facts you enter.

Limitation CalculatorEnter the day the obligee knew and the day the right could be exercised; get the days the periods end, with the articles behind them.

Check an answer you were given

Verifiability as something you do, not something you are told.

VerifyLoad a saved answer. The engine repeats the computation in your browser and reports whether it reproduces byte for byte.

Read the text with the model beside it

For those whose question is whether the model is faithful to the text, and where that shows.

ReaderThe pinned black-letter text, article by article. Highlighted passages are the norms of the model; click one to see how it reads and the code behind it.

Run it yourself

Hosted or local, the answer is the same document: the same rules, the same hashes. mcp/pin.json records what either one must answer from.

From your MCP clientClaude, Cursor, anything that speaks MCP. Requests are evaluated on Arxo machines.
On your own machineThe same slice and the same engine over stdio; nothing leaves the laptop. linux-x64 today — elsewhere the launcher names the hosted endpoint.
Or the image, pinned by digest, from the repository below: docker compose -f mcp/compose.yml up
The packages themselvesThe canon, the worked cases and the pin: the canon profile hash, the package hashes and the image digest.