Two entities, one contractor
One registration, two provable contracts — and privacy roles kept out of the contract.
A group pays freelancers from two entities, in Ireland and Hong Kong. Moving a project from one entity to the other meant re-signing contracts, and it blurred which company controls the contractor's data.
Double Acceptance: registration creates two separately provable framework agreements. Each Order names exactly one customer entity. An existing Order moves only by a three-party instrument — never by automatic novation. Accepting the contract is kept separate from privacy consent and from controller roles.
Architecture in use; current revision in legal review.
Facts before labels — the contract and the privacy role are two different questions.
Text description
Mini schematic: a contractor registers once with a group of two entities; Double Acceptance creates two framework agreements and binds each Order to one customer; out come provable Orders and privacy roles kept apart from the contract