Styxis
Company
Knowledge

Check whether Iceberg WAP data is visible on main before approval

Actual branch visibility and the existence of the WAP snapshot define the approval boundary more clearly than a stage label.

Verify the approval boundary by reading

Writing, reviewing and publishing are separated by observed branch visibility, not by status names alone. Give Truthound observed row identities from main and stage rather than only WAP configuration. If main consumers can read an unapproved row, the review stage no longer provides the intended boundary. [1, 2, 3]

The report distinguishes two failure modes

The public Iceberg issue describes format-version 3 WAP with deletion vectors: staged appends can appear on main, while a WAP DELETE snapshot can be unavailable. Its version field and reproduction description name different versions, so the affected scope needs further confirmation. Do not turn that ambiguity into a blanket claim about an entire release. [1]

Visibility and snapshot existence are separate

Before permitting cherry-pick, check both main visibility of stage-marked rows and existence of the snapshot associated with wap.id. Append isolation does not establish availability of a delete approval target. Record the branch and workflow step of every observation. [1, 3]

An illustrative pre-publication condition

An illustrative policy requires 0 unapproved stage rows visible on main. Observing 0 unapproved stage rows on main preserves the publication boundary. Seeing 1 such row means a main consumer can read it before cherry-pick. Other approved rows on main are legitimate, so distinguish the marker and approval history instead of treating every visible row as an error. [1, 3]

The limits of the Truthound boundary

Truthound Core's ConditionalExpressionValidator can inspect a prepared visibility table for the forbidden combination of an unapproved marker and main exposure. It does not publish WAP atomically or implement branch isolation. A verified separate staging branch still requires an actual main-read check. An ambiguous source version is not proof that a deployed release is fixed. [1, 2, 3]

Application conditions

Collect branch, row_id, staged_marker and wap_snapshot_id from actual reads at the same approval stage, linking them with original approval history.

Alternatives

Use a separate stage branch in a verified format and branch combination, checking main visibility through actual reads.

Limitations

  • Truthound neither publishes WAP atomically nor provides branch isolation. The source’s inconsistent version descriptions remain unconfirmed scope.

Evidence

Event checked
Subject checked
Modified