Brief / Operations
Synthetic case: the unapproved upload that must not govern
An earlier, entirely synthetic demonstration: an unapproved newer file stays visible and never becomes governing evidence.
Case boundary: entirely synthetic
A newer file no one approved must stay in view but not govern. This entirely synthetic case, from an earlier demonstration, shows why: every drawing, person, asset, date, and outcome was invented, and nothing describes a customer deployment.
The question was narrow: when a released drawing and a newer unapproved field upload disagree, which record controls the bounded installation, what changed, and who approved the exception?
The evidence conflict
The controlled record set contained an approved parent drawing, an approved site-specific revision, a superseded revision, and a newer field upload. Because the upload carried no approval block or document-control release, its newer timestamp did not make it controlling.
A bounded site exception remained tied to its decision record, approving role, concurrence, and applicability. The control was not “find the newest file.” It was “show the conflict, preserve the rejected evidence, and identify the governing authority.”
What this proves, and what it does not
The earlier demonstration showed a control contract: governing evidence, a rejected newer file, revision lineage, applicability, decision ownership, and a plain-language confidence boundary.
The current public chain is Veldarium → VeldBuild → VS-001 → WP-019. Its deterministic proof tests whether work-package readiness can be established from controlled build state. Neither proof demonstrates a live shipyard connector, automated approval, production readiness, or a customer result.