Bounded reobservation for disappearing atomic staging files

When a source inventory races with atomic evidence publication, an exact protocol-owned staging name can justify another complete observation; it cannot justify skipping an unseen entry or inferring its former type. Keep transient-publication and ordinary-source retry budgets separate so publisher churn cannot replenish tolerance for ordinary changes. Recheck the Git inventory, file types and content on every attempt, and preserve unknown on exhaustion or unsupported inputs.

Validate the mechanism with real publishers and controlled cleanup scheduling, then challenge tracked names, symlinks, special replacements, malformed names, refreshed source changes and exhausted mixed schedules. A deterministic matching mechanism supports a narrow correction even when CI omitted the low-level record; label the original CI explanation as inference. A later RED replay verifies old behavior but is not preimplementation evidence. This method does not prove continuous immutability or unconditional concurrency success.

Applies when: content-bound verification enumerates files while several writers publish evidence atomically. Keywords: atomic publication staging inventory fingerprint race bounded retry evidence source binding