pub struct CapsuleResolution {
pub name: String,
pub version: CapsuleVersion,
pub capsule_id: CapsuleId,
pub build_digest: String,
pub policy_version: Option<String>,
pub overlays: Option<Vec<String>>,
pub effective_grants: Option<BTreeSet<CapabilityGrant>>,
pub clamped_budget: Option<ResourceBudget>,
}Expand description
A journaled registry resolution (R0.9 wave 1): the answer to one
RunManifest capsule pin, recorded as the output of a
RunEventKind::CapsuleResolved
event at admission. This is the link that lets a checkpoint’s version
string pin reach the content address: header pin → journaled
resolution → receipt.
Wave 2 (Cedar, overlays, budget composition) extended the payload additively: the four optional fields are absent — on the wire and in old journals — whenever the admission ran without the policy plane (a build without the feature, a tenant with no active policy, no overlays, no budget bounds), which is exactly the wave-1 shape.
Fields§
§name: StringThe pin’s name (the RunManifest::capsules key — the capsule’s
identity name).
version: CapsuleVersionThe pinned version string.
capsule_id: CapsuleIdThe content address the registry resolved the pin to.
build_digest: StringThe build digest the resolved manifest declares — what the host will recompute against the artifact bytes before instantiating.
policy_version: Option<String>The Cedar policy version this admission was decided under (R0.9
wave 2): the tenant’s active policy version at resolve time,
pinned so a later audit can answer “which policy permitted this”
without reconstructing history. None when no policy was active.
overlays: Option<Vec<String>>The tenant overlays applied at admission (R0.9 wave 2), sorted by
name. None when none applied.
effective_grants: Option<BTreeSet<CapabilityGrant>>The effective grant set after overlay intersection (R0.9 wave 2)
— what the host may actually link, always a subset of the
manifest’s declared grants (intersect_grants). Present exactly
when an overlay applied.
clamped_budget: Option<ResourceBudget>The budget after clamping against the enclosing run’s bounds and the deployment’s tenant ceiling (R0.9 wave 2), present exactly when the clamp changed the declared budget — the journaled evidence of the wave’s budget composition.