Your Laptop as the Authorship Record

An authorship record is the set of traces a piece of work leaves behind as it is made: the versions a document passed through, the dates the files carry, the copies a backup drive kept along the way, and for a photograph, the data the camera wrote at the moment of capture. None of it is a certificate. Together it shows the shape of real work, which is a start, growth, revision and a finish, and that shape is very hard to invent after the fact.

A laptop keeps most of this without being asked. Cloud document editors record every save with a server-side time. Windows and macOS stamp every file with created and modified dates and, when a backup is switched on, copy the whole documents folder to a drive on a schedule. Cameras and some editing apps write a signed history into the image file. The record is already there; what people lack is the habit of switching on the parts that are optional, and the knowledge of how to read the parts that are not.

Read the guides in the order below. Start with keeping version history of your drafts, because it is the spine of the whole record and the one thing that has to be switched on before the work begins. Then read how to prove when a file was created, which explains what the created, modified and accessed dates on a file actually mean, why a copy or a cloud sync changes some of them, and which records corroborate the date that matters. Follow that with checking whether a file has been altered, which uses a hash to settle whether two copies are identical and a document compare to find out what changed when they are not.

The fourth guide moves off the document and onto the drive. Local backups as an authorship record shows how File History on Windows and Time Machine on a Mac keep dated snapshots of a project folder, how to read a snapshot's date, what retention setting to choose, and how to restore a version for a reviewer without disturbing the original. It sits in the laptop care section because the drive it needs is the same one every laptop should have for ordinary data loss.

Photographs have their own record. Checking a photo's metadata before sharing covers the EXIF data a camera writes, including the capture time and the software that last saved the file, and how to strip it when privacy matters more than provenance. Checking an image's Content Credentials covers the newer signed history that some cameras and apps attach, what a valid credential proves, and why a missing one proves nothing at all.

Two guides deal with the moment someone asks. Showing your writing process after an AI detector flag walks through gathering the history, the drafts and the notes and presenting them calmly. Disclosing AI writing help at school and work covers the other side of the same conversation: finding the policy that applies to you, saying plainly what help you used, and citing it where a citation is expected. A good record makes both easier, because there is something concrete to point at.

Three explainers give the background. How AI writing detectors work shows that a detector estimates how predictable a text is and turns that estimate into a score. AI text watermarking explained covers the separate idea of a statistical signal planted in generated text, what a watermark test can support, and why editing weakens it. Plagiarism checkers versus AI detectors explains why a similarity report and an AI score measure different things and why they so often disagree.

One principle runs through all of it. A detector score is never a verdict. It is an estimate produced by a tool with known error rates, and the fair response to one is to look at the record of how the work was made. Everything on this page exists so that when the question comes, the record is already there, on the laptop, in the order it happened.