Day 9 of 1060 minShell Walker

Day 9: Capstone: One Case File, Three Media Types

Taught by Mr Elite Updated

By the end of today you can

  • Build a case folder that holds an image, a video and an audio clip with hashes and a custody log
  • Run the Day 1 to 7 methods on each file and save the outputs as evidence
  • Write a peer-readable report with evidence references, confidence levels and limits
  • Name sensible next steps for further study in detection, trust and safety, and legal evidence

Warm-up

Answer from memory first, then tap to check. Recalling yesterday is what makes it stick.

On Day 8, what three things did we say every confidence statement should carry?

The level on a fixed scale, the basis for it, and the limits of what the evidence shows.

Why do we build timelines in UTC and label each row as file, platform or claim?

UTC avoids time zone confusion, and the labels separate what a file says from what a platform recorded and what someone merely asserted.

Someone in finance forwards you three things in one email: a screenshot of a CEO at a product launch, a 20 second video clip of the same person apparently approving a payment, and a voice note saying the same thing. They want one answer by end of day: is any of this fake, and what should we do?

That is a real shape of case. Nobody hands you one clean file. Today you run the whole method on all three, and you write the answer so a colleague who was not there can check every claim. No new tools. This is the day you prove the ten days hang together.

The method in one page

Before we touch anything, let me lay out the whole course as a single workflow. If you can recite this, you can handle any file that lands on your desk.

Quick check

A file has no EXIF camera data at all. What does that tell you?

Set up the capstone case folder

No lab is listed today, so everything runs on your own machine. You need three files you are allowed to use: one image, one video with an audio track, and one audio clip. Use your own material from earlier days, files you made yourself, or clearly licensed samples. Ideally include one you have generated or edited yourself so you know the ground truth. Never use footage of a real person you have no right to analyse.

bash
mkdir -p case09/{evidence,work,outputs}
cp ~/samples/suspect.jpg ~/samples/clip.mp4 ~/samples/voice.wav case09/evidence/
chmod a-w case09/evidence/*
ls -l case09/evidence
Builds the case folder, copies the three files in and makes the originals read-only. ls -l should show permissions like -r--r--r--.

Watch me do it: hash, log and examine

Now I work the case the way I want you to. I explain each step, run it, then say what the output means. Substitute your own file names throughout.

bash
cd case09
sha256sum evidence/* | tee outputs/hashes.txt
date -u +"%Y-%m-%dT%H:%M:%SZ" >> outputs/custody.log
echo "Received 3 files, hashed, originals read-only. Analyst: YOURNAME" >> outputs/custody.log
Hashes the originals, saves the list, and writes a UTC timestamped custody entry. Replace YOURNAME with your own.
bash
cp evidence/* work/
(cd work && sha256sum *) | sed 's#  #  evidence/#' | diff - outputs/hashes.txt && echo COPIES MATCH
Copies the files for analysis, hashes the copies and compares them with the original list. You should see COPIES MATCH.
bash
exiftool work/suspect.jpg > outputs/image_exif.txt
ffprobe -hide_banner work/clip.mp4 2> outputs/video_ffprobe.txt
exiftool work/voice.wav > outputs/audio_exif.txt
c2patool work/suspect.jpg > outputs/image_c2pa.txt 2>&1
cat outputs/image_c2pa.txt
Saves metadata and stream details as evidence files. ffprobe writes to stderr, hence 2>. The last line shows the provenance result.

Content analysis: your turn on each file

Now you apply the type-specific methods. For each file, produce at least one saved output and one written observation. Rate every signal weak, moderate or strong, and say why.

bash
mkdir -p work/frames
ffmpeg -hide_banner -i work/clip.mp4 -vf fps=2 work/frames/f_%03d.png
ls work/frames | head
Pulls two frames per second into PNG files. For a 20 second clip you should see about 40 files named f_001.png onwards.

Quick check

Your spectrogram looks suspicious, but the image and video show nothing unusual and metadata is stripped. What is the sensible wording?

Write the report a peer can check

The report is the product. A good one lets a colleague repeat your work from the hashes and output files alone. Keep it short and plain. Evidence references mean each claim names the file in outputs that supports it.

markdown
# Case 09 Report
## Scope
Question: are the image, video and voice note authentic?
Out of scope: who made them.
## Evidence
| File | SHA-256 (first 12) | Ref |
|---|---|---|
| suspect.jpg | 3f2a... | outputs/hashes.txt |
## Findings
### Image
- No C2PA manifest (outputs/image_c2pa.txt). Weak signal alone.
- Inconsistent shadow on left hand (outputs/img_notes.md). Moderate.
**Confidence: Low-moderate that it is synthetic.**
Basis: two signals. Limits: image was resized.
## Cross-file
## Recommended action
## What this does not show
A skeleton for report.md. Fill each finding with a reference, a rating, a confidence level, the basis and the limits.
Evidence reference
A pointer from a claim in the report to the saved output that supports it.
Chain of custody
The written record of who held the evidence, when, and what was done to it.
Confidence level
Your stated certainty on a fixed scale, always paired with its basis and limits.

For the recommended action, match the strength of evidence. Low confidence suggests hold the payment and verify through a known phone number. Strong, multi-signal evidence supports escalating to fraud and legal teams and preserving platform copies.

Where to go next

Ten days gets you a defensible method, not mastery. Three directions are worth choosing between.

If it did not work

Analysing the original files directly

Check the originals are read-only and work only in the work folder. Re-hash if you are unsure anything changed.

Treating missing metadata or a missing C2PA credential as proof of fakery

Write it as a weak signal with innocent explanations, and look for independent evidence.

Claiming who made the media

Keep attribution out of scope unless you have non-media evidence. Say the media alone does not show it.

A report with no evidence references

Attach a file name from outputs to every finding so a peer can verify it.

Recap

  • One workflow covers every file type: intake, hash, copy, examine, provenance, report
  • Originals stay read-only and every claim points to a saved output
  • Rate each signal, then combine independent signals into a stated confidence
  • Absence of metadata or credentials is weak evidence on its own
  • The recommendation must match the strength of the evidence
  • Next study paths: detection research, platform trust and safety, legal evidence standards

Cheat sheet

sha256sum evidence/*
Fingerprint every original
chmod a-w evidence/*
Make originals read-only
exiftool file
Dump metadata
ffprobe -hide_banner file
List streams, codecs and durations
ffmpeg -i clip.mp4 -vf fps=2 f_%03d.png
Extract two frames per second
c2patool file
Read C2PA content credentials
date -u +%Y-%m-%dT%H:%M:%SZ
UTC timestamp for logs

Before the next day

Mission: Final capstone report

Investigate your three-file case from start to finish and submit a final report. This is the evidence that you can deliver a defensible answer, so take care over wording and references rather than speed.

About 45 min

You are done when: A case09 folder with hashes.txt, custody.log, timeline.md, saved outputs and a completed report.md.

Want more? Add a ground-truth appendix: state which file you knew was synthetic or edited, and say honestly which of your signals caught it and which missed it.

Quiz

4 questions. Your score is saved with your progress.

1. Why do you hash the originals before doing any analysis?

2. c2patool reports no manifest on the image. What is the most defensible statement?

3. Two weak signals and one moderate signal point to synthetic audio, but you have no reference voice. What should the report say?

4. Which recommended action fits low-confidence findings on a payment request?

Finish the day

Mark the day complete to save your progress.

Go to Day 10

Next: Day 10 is the final apply-it day: a video with audio as one mixed case, a review of the earlier methods, and an honest look at how detectors can be evaded and why that limits every conclusion you write.

Tell someone you are doing this:WhatsAppXLinkedIn

Your notes

Private to this device. Write what you want to remember from today.