Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions gallery_matches_report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# Gallery Matches Report

## Executive Summary

An investigation was conducted across four provided photo gallery URLs from St John's College Ball / Commemoration Ball 2026 to locate photos matching specific target subjects: **a group of young men in tuxedos (black tie attire), featuring an individual wearing an orange/white Aperol Spritz bucket hat and holding an orange Aperol fan**.

Exact matches were found in the **Adobe Lightroom Shared Gallery**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: The core claims — "Exact matches were found" and each gallery's accessibility status — are asserted with no evidence, timestamp, or method, so they can't be audited from the repo. CI won't catch drift either: make lint_links runs pytest-check-links over every *.md including this file, but these URLs are wrapped in backticks so they're not extracted as links and never validated. Add provenance (investigation date, who/what was compared, evidence such as screenshots or crop references) or convert the URLs to real links so the checker verifies reachability.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At gallery_matches_report.md, line 7:

<comment>The core claims — "Exact matches were found" and each gallery's accessibility status — are asserted with no evidence, timestamp, or method, so they can't be audited from the repo. CI won't catch drift either: `make lint_links` runs pytest-check-links over every `*.md` including this file, but these URLs are wrapped in backticks so they're not extracted as links and never validated. Add provenance (investigation date, who/what was compared, evidence such as screenshots or crop references) or convert the URLs to real links so the checker verifies reachability.</comment>

<file context>
@@ -0,0 +1,39 @@
+
+An investigation was conducted across four provided photo gallery URLs from St John's College Ball / Commemoration Ball 2026 to locate photos matching specific target subjects: **a group of young men in tuxedos (black tie attire), featuring an individual wearing an orange/white Aperol Spritz bucket hat and holding an orange Aperol fan**.
+
+Exact matches were found in the **Adobe Lightroom Shared Gallery**.
+
+---
</file context>


---

## Matches Found

### 1. Adobe Lightroom Share
* **Gallery URL:** `https://lightroom.adobe.com/shares/d1a15922bffe4671a329b2d23208c683`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3: Each gallery URL is wrapped in backticks, so it renders as plain inline code and cannot be clicked from the report. Use markdown links instead so readers can open the galleries directly. Note make lint_links (pytest-check-links) will then validate them in CI.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At gallery_matches_report.md, line 14:

<comment>Each gallery URL is wrapped in backticks, so it renders as plain inline code and cannot be clicked from the report. Use markdown links instead so readers can open the galleries directly. Note `make lint_links` (pytest-check-links) will then validate them in CI.</comment>

<file context>
@@ -0,0 +1,39 @@
+## Matches Found
+
+### 1. Adobe Lightroom Share
+* **Gallery URL:** `https://lightroom.adobe.com/shares/d1a15922bffe4671a329b2d23208c683`
+* **Status:** Publicly Accessible
+* **Matched Images:**
</file context>
Suggested change
* **Gallery URL:** `https://lightroom.adobe.com/shares/d1a15922bffe4671a329b2d23208c683`
* **Gallery URL:** <https://lightroom.adobe.com/shares/d1a15922bffe4671a329b2d23208c683>

* **Status:** Publicly Accessible
* **Matched Images:**
1. **`img_0015.jpg`**
* **Description:** Group photo of six young men in tuxedos outdoors at night. The man second from the right is wearing a distinct white and orange "Aperol Spritz" branded bucket hat and holding an open orange Aperol fan across his chest.
2. **`img_0016.jpg`**
* **Description:** A sequential pose/variation of the same six young men in tuxedos in the same outdoor night setting, featuring the Aperol Spritz bucket hat and orange fan.

---

## Status of Other Provided Links

### 2. Google Drive Folder
* **URL:** `https://drive.google.com/drive/folders/16tceJfDqNEmn-XxVA5GK6nmJ-apIKbZY`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Committing this report records a non-public Google Drive folder's full URL/ID and fine-grained descriptions of identifiable individuals in git history. The Drive folder's own status is "Access Restricted / Requires Permission", yet its ID is now permanent repo history, and the matches section describes six people ("The man second from the right is wearing...") linked to a photo gallery. Unless this repository is private, redact the folder ID and the individual descriptions, or confirm repo visibility before merging.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At gallery_matches_report.md, line 27:

<comment>Committing this report records a non-public Google Drive folder's full URL/ID and fine-grained descriptions of identifiable individuals in git history. The Drive folder's own status is "Access Restricted / Requires Permission", yet its ID is now permanent repo history, and the matches section describes six people ("The man second from the right is wearing...") linked to a photo gallery. Unless this repository is private, redact the folder ID and the individual descriptions, or confirm repo visibility before merging.</comment>

<file context>
@@ -0,0 +1,39 @@
+## Status of Other Provided Links
+
+### 2. Google Drive Folder
+* **URL:** `https://drive.google.com/drive/folders/16tceJfDqNEmn-XxVA5GK6nmJ-apIKbZY`
+* **Status:** Access Restricted / Requires Permission
+* **Details:** The link directs to Google Drive authentication/request access page. No public photos were accessible without login/permission.
</file context>

* **Status:** Access Restricted / Requires Permission
* **Details:** The link directs to Google Drive authentication/request access page. No public photos were accessible without login/permission.

### 3. Christie's Client Gallery
* **URL:** `https://christie-s.client-gallery.com/gallery/st-johns-college-ball-2026`
* **Status:** Password Protected
* **Details:** The gallery requires a password to enter and view the photo set.

### 4. Pixieset Gallery
* **URL:** `https://hubertcecilphotography.pixieset.com/stjohnscollegecommemorationball2026/`
* **Status:** Password / PIN Protected
* **Details:** The landing page requires a PIN/password to access the image collection.
4 changes: 0 additions & 4 deletions uv.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading