pilot-promotion-gate

A promotion gate evaluates cross-variant safety by synthesizing three-way compare outcomes, source-truth, and receipt verification from both variant A and variant B. It produces a PASS, WATCH, ASK, or BLOCK verdict based on deterministic, field-level evidence for your release decision.

A three-way compare in GitOps evaluates the live state, desired state, and target state for each variant to identify field-level diffs. The promotion gate uses this per-variant comparison alongside source-truth analysis to produce a deterministic cross-variant safety verdict.

Yes, a promotion gate applies to canary progression, blue-green flips, environment promotions, and cell-to-cell promotions. It evaluates cross-variant safety by synthesizing field-level diffs and attribution evidence across both variants to determine if the promotion target is safe.

BindingSource attribution detects upstream changes during a promotion by analyzing per-field bindingSource graph shifts in connected mode. This reveals whether the promotion alters what is ultimately sourced from upstream, adding attribution context to the safety verdict.

Chained receipts verify auditability by producing a promotion-target receipt that links variant A evidence into variant B verification. This input attestation chaining establishes an auditable gate input, ensuring the cross-variant safety verdict is rooted in deterministic evidence.