pub struct ConfigResolution {
pub surface: SurfaceKey,
pub tag: Option<EnvironmentTag>,
pub candidate_id: CandidateId,
pub pointer: PointerBinding,
pub digest: String,
pub model: Option<String>,
pub layers: Option<Vec<String>>,
}Expand description
A journaled admission resolution (R0.11 wave 2): the answer to one
named registry artifact a run declared at submission, recorded as the
output of a
RunEventKind::ConfigResolved
event at admission. This is the link that lets a manifest’s content
digest pin reach the version it resolved from — the
CapsuleResolution precedent
(version string → content address) applied to configuration
(content digest → candidate).
The walk it closes: the run’s signed receipt commits the manifest
digest; the manifest pins digest; this event names the surface,
tag, and candidate_id the digest resolved from; the candidate
carries its author, evaluation, and promotion approver. Every hop is
signature-covered — the resolution event sits inside the journal the
receipt’s head signs.
Fields§
§surface: SurfaceKeyThe artifact resolved: its registry key, the untagged surface
(prompt:system). The tag travels separately so the two facts —
which artifact, which environment — read without string surgery.
tag: Option<EnvironmentTag>The environment tag the run resolved under (prompt:system@prod).
Absent when the run resolved the untagged surface — either it
declared no environment and the deployment declares no default
tag, or (deliberately) the artifact is governed untagged. Absent
is a fact, never a guess: the deployment’s declared default tag is
configuration, not something the run invents.
candidate_id: CandidateIdThe candidate the pointer bound — the exact version the run pinned, reproducible at audit from this id alone (candidates are content-addressed: the id is the integrity check).
pointer: PointerBindingWhich pointer slot admitted the candidate.
digest: StringThe content digest the run’s manifest pins for this artifact —
exactly what RunManifest::pin_prompt (SHA-256 of the prompt
text), pin_tool_schema (canonical-JSON digest of the schema),
or pin_model (canonical-JSON digest of the parameters) records.
The digest ↔ version join, journaled: equal digests under
different candidate ids cannot exist (content addressing), so
this field is the receipt walk’s hinge.
model: Option<String>The model identifier the manifest pins alongside the parameters
digest — present exactly for model_settings resolutions (the
manifest’s model slot is an identifier, not a digest, and the
walk is incomplete without it).
layers: Option<Vec<String>>The resolved layer order — present exactly for
middleware_composition resolutions (R0.11 wave 4): the layer
names in the order the run’s chain instantiated them. Ordering is
registry-aware in both directions — the artifact declares the
order, and this is the journaled evidence of the order that
actually served.