Brief / AI-native shipbuilding
Authority beats recency: the rule operators already know
A newer timestamp does not make an unapproved upload the controlling record. An AI-native operating system has to encode that rule.
The field upload trap
Someone uploads a marked-up drawing from a phone. It is newer. It may even capture a real field condition. It is still not automatically the controlling configuration.
Document control already knows this. Generative demos often forget it, because recency is easy to rank and approval state is harder to model.
The operating rule
In an earlier synthetic evidence-control proof, an unapproved upload was shown and rejected as non-governing while the approved revision pair remained controlling. The useful part was not the answer itself. It was that the reason stayed inspectable.
In shipbuilding, the same rule has to propagate beyond the document into material, work packages, inspection, and downstream configuration.
How to test the control layer
Bring a question where two records disagree and only one should govern. If the system cannot keep the disagreement and the downstream consequence inspectable, it should fail the evaluation. That is the bar.