Describe a release

Tell Tarnbrook Financial Group what the software is. It decides whether the software should exist here, and then Raidiam Connect issues it an identity.

Two decisions follow this form, and different parties take them. Tarnbrook Financial Group decides whether to accept the software. Only then does Raidiam Connect create the identity, and the Tarnbrook Financial Group authority decides what that identity may do. Nothing below crosses to Connect until the first decision passes.

The software Catalogue identifier The short name the software is filed under. This demonstration can drive a real deployment for records-assistant, balance-monitor, batch-reviewer, analyst-companion. Name What a person calls it. Version The version of the build being described. PurposeWhat the software is for, in one sentence. Release record URL Where the publisher publishes the signed record of this build. This catalogue fetches it and checks its signature. Artefact digest The SHA-256 fingerprint of the built software, so the record names one exact build.

Who is accountable Organisation The organisation that answers for this agent. Unit The team inside it. Accountable owner The named person who answers for it.

Where it runs Platform The platform it calls. Hosting Who runs the copies: Raidiam Connect, this catalogue, a workload host, or a workstation. Attester The service each running copy proves itself to. A running copy has no address, so it is attested instead.

What it may ask for Roles requested from the authority One or more role names, separated by a space. This is a request. The authority may refuse any of them.

Evidence Repository Where the source is. SBOM The software bill of materials: the list of everything the build contains.

Submitted by Who is asking. Change reference The change record this request belongs to.

A control on this screen that writes changes a real record in Raidiam Connect.

Requests already decided

Open one to see what each decision looked like.