Sign in

ProductOperate

Evidence recordpreview

What was checked for each change, as a record; drafts, not yet signed

One record per change that anyone can check without trusting the model.

The evidence record is the last step of the loop: what a change claimed, who or what acted and under which permissions, what was measured before and after, and the verdict per dimension. It holds references and hashes, never your content. Today it is written as an unsigned draft, marked so; signing and storage come next.

See a real record

In early access. A 30-minute call is the way in; there is no SLA during early access.

0%
01The problem

When an auditor or a customer asks how a change was checked, the answer is spread over CI logs, chat and someone's memory. An agent saying it tested something proves nothing.

02How it works

A model saying it succeeded is never evidence. The record keeps what was measured, by what, and when.

How it works

01

Where it runs

Change verification writes one for each change it measures, as an unsigned draft today. Signing and append-only storage come next.
02

What it reads

References and hashes: the pull request, the bench run and the traces. Never your requests, responses or code.
03

What you approve

You decide what a verdict means. A draft is marked unsigned: draft, so it is never taken for signed evidence.
01The changeA pull request, by a person or an agent.live
02MeasuredBefore and after, by chaos verify.preview
03Draft recordWritten today, unsigned.preview
04Signed and storedNext.coming
From a change to a record anyone can check
03What you getpreview

Each line says how far it is built today. Live means anyone with an account uses it; preview means it runs in early access or as a pre-release; coming means it is written down and not built yet.

What you get

  • Claim, measurement, verdict

    The change and its claims, the measurements before and after, and the verdict per claim and per dimension, reported separately and never as one score.

    preview

  • References, never content

    As an unsigned draft in an open evidence-record format (in-toto), holding references and hashes: the bench run, the traces, the pull request. A draft is marked unsigned: draft so it never reads as evidence.

    preview

  • Signed and stored

    Signing, append-only storage and a verifier anyone can run. Not built yet.

    coming

  • Graded against known truth

    The ground truth a verdict was graded against (a planted regression, a check that must fail) kept in the record. Not built yet.

    coming
04The draft recordExample data

The shape chaos verify writes today: a short in-toto statement (an open format for build evidence) that says inside it that it is an unsigned draft.

The draft record

record.intoto.json, a draft

{
  "_type": "https://in-toto.io/Statement/v1",
  "subject": [{ "name": "example/checkout@3f9c2e1", "digest": { "gitCommit": "3f9c2e1" } }],
  "predicateType": "https://inorbit.hr/evidence/change/v1",
  "predicate": {
    "unsigned": "draft",
    "subject": { "pull_request": { "number": 517, "head": "3f9c2e1" } },
    "claim": [{ "id": "contract-1", "claim": { "kind": "contract", "change": "none" } }],
    "actor": { "kind": "person", "id": "github:janedoe" },
    "observations": [
      { "phase": "before", "measurement": "chaos validate, every check",
        "load": "none: read-only probes", "validate": { "passed": 41, "failed": 0 } },
      { "phase": "after", "measurement": "chaos validate, every check",
        "load": "none: read-only probes", "validate": { "passed": 41, "failed": 0 } }
    ],
    "ground_truth": { "kind": "none", "mode": "observed" },
    "verdict": {
      "overall": "pass",
      "claims": [{ "id": "contract-1", "kind": "contract", "outcome": "pass" }]
    }
  }
}

Shortened: the real draft also carries hashes, times and links. No signature yet: signing and storage are not built, so the draft says so in its first field.

Example data

The field names follow the code that writes the record. The pull request, commit, person and numbers are made up.

05Proof and links

Every claim on this page has its evidence: the documents that define it, the docs that say how to use it, and the API it runs on.

Proof and links

Documents

Docs

API

  • GitHubpreviewThe draft record is linked from the verdict on the pull request.
  • RESTcomingNo route until records are stored.

The evidence rule: a model saying it succeeded is never evidence. What counts is what was measured, by what, and when.

Your data, your call

A record holds references and hashes, never your requests, responses or code, so it can be shown to an auditor without showing your data.

Logs record who did what and the outcome, never content. The platform's own models are self-hosted; a third-party model provider is one you connect with your own key, and it bills you directly, with no line or markup from InOrbit. Separately, our own DPAs with model providers are in progress, none signed yet. InOrbit is not certified: no auditor has attested its controls yet, and the known gaps are listed.

The company's facts, controls and gaps →

06Questions

Questions, answered plainly

Is a draft record evidence?

It is what was measured, unsigned. It says unsigned: draft so nobody mistakes it for a signed record.

Why one record per change?

Because a change is what someone has to sign off on. The record is what they read before they do.

When is it signed?

When signing and storage are built. There is no date yet.

Next step

See it on your own system

Book 30 minutes with an engineer. We look at your system together and, where it fits, open early access for your team.

Every product, by category →