Paths, Formats and Provenance
What this concept is
A path names a location. A format describes how data is organized. An extension is a naming convention that helps applications choose an interpretation; renaming an extension does not convert the underlying content. Provenance records where a file came from and what you changed.
Why it matters here
Tool installation and Git practice depend on acting on the intended file. A reliable learner can distinguish two same-named copies, keep an untouched source and explain how a result was produced.
Concrete example
In a disposable folder create originals and working. Copy a plain-text plan.txt from the first to the second, then edit only the working copy. Both files have the same name but different locations and content. A search result showing only the filename is insufficient evidence of which one you opened.
Imagine renaming a picture from photo.png to photo.txt: an editor may display unreadable content because the bytes remain an image. No real rename is needed for this thought experiment.
Common confusion / misconception
“Newest” can mean last downloaded, last modified or last edited by a collaborator. Timestamps alone do not prove correctness or authorship. A link to a shared document may point to changing content rather than a fixed version.
How to use it
Keep source, working and submitted copies distinguishable. Record source URL or creator, access date and meaningful changes. Show extensions where your system permits. Before replacing a file, confirm the full destination and retain a recoverable version.
Check yourself
Two files have the same name and size. Are they identical? Not necessarily. For a tiny text artifact, compare all content; later modules introduce byte fingerprints and their limits.
Mini drill or application
Write a three-line provenance note for your practice plan: origin, current location and edit. Move the working folder, reopen the correct file and update the location note. Explain why an old shortcut may fail.
Read this only if stuck
Return to computer basics repair if file navigation itself is still difficult. Then return here for identity, provenance and state reasoning.
For a broader file/storage model, consult the hardware material in the CS50 technology archive; the archive is not current product guidance.