Developers

The record

Every action in a project is written down in order, with who did it and when, and every result can tell how it was made. Your own server keeps it, and you can take it with you.

What the record holds

Each entry says what happened, who did it, on whose behalf and when. A result also names its method and version, the data it came from and the release that made it.

Your own server keeps the record beside the history of every change to your data.

For engineers: the record is the project’s lineage and provenance, and its download follows W3C PROV.

Take it with you

From code, you can download the record one page at a time as PROV-JSON, a format other tools already read.

Available Leave with what you export. Streaming past 32 MiB per representation is not yet qualified. How leaving works

The contracts it is written in

Each contract below is served by the release this page was checked against.

Contract	What it holds
The story of a result Technical details Schema `StoryNode` in the server’s OpenAPI document.	How one result was made: who made it, with which method and version, from which data, in which release.
The record of a project Technical details Schema `ActivityEvent` in the server’s OpenAPI document.	Every action in a project, in order, with who did it and when.
A check against a reference Technical details Registry contract `ophiolite.check/1`, listed by `GET /api/v1/contracts` on your own server.	A result compared with an independent calculation on named data, and the bound it was held to.
The list of contracts Technical details Registry contract `ophiolite.contracts-registry/1`, listed by `GET /api/v1/contracts` on your own server.	Every contract your server serves, with its version.