Synchronization means information was exchanged. It does not prove that the record belongs to the correct client, represents the right work, uses the accepted commercial policy, or is authorized to change canonical state.
A practical example
A provider may contain two projects with similar names, a former employee, or an archived client that still appears in historical exports. Automatically treating every imported row as canonical can silently attach time, money, or responsibility to the wrong work.
Kernel therefore separates observation from acceptance. Confirmed bindings may safely automate later compatible records until they are revoked, contradicted, or fall below an integration’s confidence and policy threshold.
When someone says “sync,” the useful follow-up is: which records moved, in which direction, and did any canonical command run?