TrustNeutrality and limits

Neutral by design, and plain about its limits

Coriolis One works out how a limited resource could be shared between the parties who claim it. That is only useful if nobody can lean on the answer. This page sets out how we keep it that way, and what the engine is not.

Neutrality

The same method for every zone

One method, published

Every zone in every domain is solved by the same engine with the same published method. Nothing is tuned for a zone, a party or a client.

Six domains, equal

Carbon, fisheries, forests, freshwater, mining and orbital are listed alphabetically everywhere, so no domain or party comes first by design.

Money never buys an answer

When paid plans come, they will change the depth of access and the data you can add. They never change the method or a result.

The method in brief

How a zone is solved

The full working, with the formulas, is on the method page.

  1. Set the ceiling

    The most that can be taken or used without breaking the limit the zone has, such as a scientific catch advice, a legal cap or an export quota.

  2. Weigh every claim

    Each party's claim is weighed on the same factors, with any floor the law already guarantees it.

  3. Solve it the same way

    A weighted linear program shares the ceiling. No party can take more than 40% unless the zone's own framework switches that cap off, and each share says what limited it.

Inputs

Modelled and sourced, marked apart

Most inputs are modelled, not measured. We never present a modelled figure as a sourced one.

Sourced

Taken from a named source

A figure from a law, an official dataset or a scientific body, cited on the zone where it is used. The sources page lists every source and its licence.

Modelled

Set by the model, shown in violet

A figure we could not source yet, set so the zone can run. Results built on modelled inputs are modelled scenarios, and we label them that way.

What it is not

Not a regulator, and not the real parties

Not a regulator

Coriolis One sets and enforces nothing. Every result is a modelled scenario, not a binding determination, and no one is obliged to follow it.

Simulated parties

In Negotiate, each party is a simulated AI agent. They are not the real governments, companies or communities and do not speak for them. A referee checks every proposal against the zone's hard limits.

A watcher that only flags

News about each zone is read for you. Anything that states a new figure is marked "Needs review" for a person to check. The watcher never changes a figure itself.

Paid work

Commissioned zones are disclosed

An organisation can pay to have its own resource built as a zone. When it does, these rules hold.

Labelled where it appears

Outside the client's own Hive, the zone carries the label: "Commissioned zone. Built under a paid engagement, with the same method as every public zone. Money never buys a different answer."

Same engine, no promises

We never agree in advance what a zone will show. A result the client did not hope for stays as the engine produced it.

Client data labelled

Figures the client supplies are labelled "client-supplied", so readers can tell them from sourced figures.

Security and privacy

What we do with your data

The short version. The privacy policy is the full and binding text, and the subprocessors page lists every provider that handles data for us.

Browse without an account

Every public zone is open without signing in. We count page views on our own server, store no IP address and use no third-party analytics or advertising trackers.

Cards never touch us

Card numbers go straight to our payment processor. We never see or store them.

Your inputs stay yours

We do not sell personal information, and we do not use it or the positions and scenarios you enter to train AI models.

Signed in safely

Sign-in uses single-use links. We keep only a keyed hash of each sign-in and session token, never the token itself.

Encrypted in transit

Every connection uses HTTPS, and secret keys live in environment settings, never in the code.

Delete when you want

You can export your data from your account page, or ask us to correct or delete it at any time.

Corrections

Every change is logged

Every change to a published figure, unit, legal citation or claim is logged with its date and what it affects, and the zone's figures are regenerated from the engine. When a correction changes a result, the result changes everywhere it appears, in the public zones and in the Hive alike.

A public version of that change log will sit on this page. [Publish date to be set]

Found something wrong? Tell us through the contact page. A person reads every message.