ITB and SEMIC evidence
This page summarizes selected external validation evidence for Registry Manifest. It is not a certification statement, and it does not claim every generated artifact or every runtime deployment has been tested.
Registry Relay and Evidence Gateway have no external ITB or SEMIC evidence recorded.
Evidence status
Section titled “Evidence status”Registry Manifest includes a reproducible driver for selected JSON Schema, DCAT-AP, and BRegDCAT-AP checks. This repository does not currently pin immutable sanitized validator reports for the historical result counts, so those counts are not presented as current evidence.
Source links
Section titled “Source links”What is not covered
Section titled “What is not covered”- No maintained runtime has been validated by a GITB scenario suite.
- Exact historical success, error, and warning counts are not retained as immutable release evidence in this repository.
- The evidence applies to selected fixtures and profiles, not to every possible operator manifest or deployment.
Evidence required for exact result counts
Section titled “Evidence required for exact result counts”Exact public result claims require sanitized request and response reports with the
validator profile, source and artifact digests, execution date, and warning count under an immutable
release tag. The current smoke script writes reports under target/ and enforces zero errors, but it
does not publish those reports.
- Review the standards register for the broader claim-level model.
- Review the contracts register for machine-readable surfaces and their owning repos.