Struct LinkEvidence 

pub struct LinkEvidence {
    pub semantic_id: String,
    pub strength: String,
    pub why_finding_can_fire: String,
}

Concrete evidence justifying one finding↔semantic link.

Under the v2 “forced per-candidate emit” contract (plan_link.md §6.1), the agent must emit one LinkEvidence per candidate semantic shown, each tagged with a strength label from {High, Medium, Low}.

Fields

semantic_id: String

Candidate ID (e.g. sem-12) from the prompt’s “Candidate Semantics” section.

strength: String

Strength tier for this link, drawn from {High, Medium, Low}. Parsed via LinkStrength::parse; unknown values are rejected by the tool handler so the agent can retry. Per-tier evidence length floors: High/Medium >= 40 chars, Low >= 15 chars.

why_finding_can_fire: String

One- or two-sentence concrete justification: cite a specific behaviour from the semantic’s description (state mutation, call ordering, external boundary, invariant) that matches the finding’s pattern/exploit prerequisites. Generic theme overlap (“both involve deposit”) is not sufficient — name the specific shared behaviour.

Trait Implementations

impl Clone for LinkEvidence

fn clone(&self) -> LinkEvidence

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for LinkEvidence

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for LinkEvidence

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for LinkEvidence

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.