SLSA Build Provenance attests that a build platform produced artifacts by running a build definition. The builder.id names the platform as the transitive closure of everything trusted to run the build and record provenance; the platform implementer should define a security model identifying the platform's boundaries, actors, interfaces and trusted control plane, and use it to set that closure. The buildType names the parameterised template that ran. externalParameters, the build's external interface, are untrusted and must be included in the provenance and verified downstream; internalParameters set by the platform are optional and need no downstream check. Everything fetched during the build is a dependency recorded, where known, in resolvedDependencies; communication with the control plane or caches should not change the build definition and, if it does, belongs in resolvedDependencies. The outputs are listed as the subject.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.