The Aero family

What each one holds

Public

• aero-agent-skills

  The corpus of leaf skills, the published specification directory and the sealing code

• aero-agent-roles

  The engineering roles and the leaf skills each one binds

• aero-harness-records

  The calibration registry, the dated log of every proof, and the public evidence log

• ahcs-conformance

  The test suite that grades an implementation against the published specification

Private

• The runtime

  Private. Not published, and not linked from any public page.

  The runtime: the execution engine, the confinement, the reviewer and the issuance machinery

• The held-out negative controls

  Private. Not published, and not linked from any public page.

  The held-out negative controls, kept apart from the gates they grade

Outside

• European Space Agency requirement export

  The European Space Agency's published export mapping requirement identifiers to clauses. Not ours, never republished

• Time-stamp authorities

  Outside services that sign a statement that a digest existed at an instant, and the national trusted list that names the qualified ones

• The customer's matrix

  The applicability, compliance and verification matrices a customer already keeps. Not ours, and never held here

What connects them

In the order the runtime's own map keeps them.

• aero-agent-roles to aero-agent-skills public

  Each role's bound leaf skills

  Pinned by

  Slug resolution in the skills corpus

  Held red by

  gate-bindings

• aero-agent-skills to The runtime public to private

  The corpus, handed in by path at issue time

  Pinned by

  Content hash recorded in the record's corpora field

  Held red by

  determinism gate-isolation

• aero-agent-roles to The runtime public to private

  The roles and the tools they request

  Pinned by

  Reconciled to the smaller of the ceiling and the request

  Held red by

  gate-permissions

• aero-agent-skills to The runtime public to private

  The attestation format and the Ed25519 (Edwards-curve Digital Signature Algorithm using Curve25519) signing code

  Pinned by

  Handed in by path and never copied in; the verifier kit copies it at build time

  Held red by

  gate-spec

• The runtime to aero-agent-skills private to public

  The published specification directory: the specification, the specimen record and the trust anchor

  Pinned by

  Byte-for-byte copy with published SHA-256 (Secure Hash Algorithm 256-bit) sums

  Held red by

  gate-spec-mirror

• aero-agent-skills to ahcs-conformance public

  The published specification directory

  Pinned by

  SHA-256 sums; the suite pins the specification it grades

  Held red by

  conformance-suite-ci

• The held-out negative controls to The runtime private

  The held-out negative controls

  Pinned by

  One digest per gate target in contract/heldout.csv

  Held red by

  gate-heldout

• The runtime to aero-harness-records private to public

  The calibration registry, the dated proof log, the countermand policy and the public evidence log

  Pinned by

  Rebuilt from the tree; published SHA-256 sums

  Held red by

  gate-records-mirror records-verify-ci

• European Space Agency requirement export to The runtime from outside

  Requirement identifiers, never requirement text

  Pinned by

  The export's own SHA-256; each reader regenerates the index

  Held red by

  trace gate-claims

• Time-stamp authorities to The runtime from outside

  Time-stamp tokens, and qualified status read from a national trusted list

  Pinned by

  An anchor file of authority certificates; trusted-list units

  Held red by

  verify-timestamp tsa-probe

• The runtime to The customer's matrix per engagement

  The customer's own matrices, and the observation archive on exit

  Pinned by

  Published requirement identifiers; the exit formats the engagement terms document

  Held red by

  matrix

Terms

Ed25519

Edwards-curve Digital Signature Algorithm using Curve25519. The signature algorithm the issuing key uses.

SHA-256

Secure Hash Algorithm 256-bit. A function that turns any file into a 64-character fingerprint. Two different files practically never share one, so quoting the fingerprint pins the file.

Where this page comes from

Nothing on this page is typed by hand. It is built from family.json, which the runtime publishes in its public records repository, at commit d84f7ea8d16ec072fc7b0925f1bac9f634e90a11. The file's SHA-256 (Secure Hash Algorithm, 256-bit) digest is fa1b4dc227c5dbf73551caeac01c7ee8d10d1030e1f947016509a12c4436de51, and it matches the line for it in that commit's SHA256SUMS, which was checked before this page was built.