Dodgy Dave puts illegal waste disposal in the shared calendar¶
Dave charges businesses for compliant waste disposal, then sends selected loads to quiet patches of countryside. He keeps customer paperwork, route sheets and photographs in cloud folder F-7740, shared with driver Mo Reed. Dave calls this efficient logistics. The countryside would probably choose a different phrase.
Dave offers the respectable service¶
Customers upload collection details and receive certificates saying their waste reached an authorised facility. Dave stores the working files under cloud tenant D-44018. Each job receives an object and reference; the official destination appears in the customer copy.
D-44018 stored this job and declared destinationStill open who planned or carried out the actual disposalDave creates the driver's version¶
Dave edits OBJ-7712, replaces the destination with Gate 4 · Old Quarry Road and adds “after 23:00”. Version history retains both versions and records the account and session responsible for the change.
Cloud ownership still does not prove authorship. Dave's account could be shared or compromised. But the save event gives a precise action to compare with messages, devices and later conduct rather than leaving investigators with two contradictory spreadsheets and a shrug.
C-88410 saved the changed destination as version V-04.Dave shares only what Mo needs¶
Dave grants Mo's account C-55210 editor access to folder F-7740. Mo views the changed route, uploads a photograph from the disposal location and marks the job complete. The shared-folder record identifies the permission; provider events distinguish viewing, editing and uploading.
The sequence does not by itself settle what Mo knew, but it is a strong route to testing participation. The cloud account record and session that changed the route give the propositions to compare with devices and communications. A driver who received the changed destination, attended it and uploaded the completion image has rather more to explain than someone whose name merely appeared on a rota.
Synchronisation distributes Dave's paperwork¶
The synchronised folder places route versions and certificates onto Dave's laptop and Mo's phone. Some files arrive automatically, so presence alone is not proof of reading. The sync databases also retain the tenant, account, object and version relationships, while recent-access records show which route each device opened.
Dave likes the fact that the files follow the business everywhere. The files have taken the instruction literally.
Dave empties the folder¶
After a disposal site is found, Dave deletes the route sheets and removes Mo's permission. Cloud deletion changes what users see, but provider audit events, recoverable versions and synchronised copies may remain. A timely preservation request can protect that history before retention rules or further account activity alter it.
