fix: disclose Cloudflare photo storage - #4
Merged
Conversation
calelamb
marked this pull request as ready for review
July 18, 2026 00:33
calelamb
added a commit
that referenced
this pull request
Jul 18, 2026
* docs(licensing): outreach drafts + demo-mode entry in data-licensing.md Demo-mode V1 (45 publicly-licensed orca individuals from HappyWhale + FinID-20) is shipping in fluke-model as a "useful, not authoritative" public engagement layer while Salish-Sea catalog licensing is in flight. This PR writes that down on the fluke side: - Update data-licensing.md outreach table: drafts ready for all four catalog orgs (CWR, Orca Network, Bay Cetology / Bigg's, Whale Museum) and two researcher partnerships (Bergler / FinID-20, Wild Me). - New docs/outreach/ directory with the six drafts, ready to read, personalize, and send. Each references a [DEMO_URL] placeholder so recipients can see a working thing rather than a description. - New "Demo-mode V1" section in data-licensing.md spelling out why the demo is policy-clean (both source datasets have explicit ML-permitting licenses) and the retirement plan for when real Salish-Sea catalogs come online. Drafts only — none are sent. User is in the loop on every send. * docs: define two-release launch design * docs: define standalone API extraction * docs: plan standalone API extraction * docs: fix API extraction task sequencing * docs: preserve submission contract behavior * docs: include standalone seed type repair * docs: align generated contracts with runtime * docs: correct API release workflow * refactor: move API to standalone repository * test: harden web repository boundaries * docs: plan release a launch * docs: fix release plan sequencing * test: codify release a boundaries * test: execute release boundary gates * feat: enforce browse-only web release * fix: close web release boundary gaps * ci: add release a web verification gates * test: cover critical web browse flows * chore: add contract fixture sync gate * fix: preflight contract fixture sync * docs: clarify cross-repo contract gate * ci: add cross-repo contract checkpoint * feat: consume paginated release a contracts * fix: bound web cursor pagination * feat: make web browse resilient * feat: prepare production web deployment * perf: eliminate landing hero load waterfall * feat: add launch privacy support and metadata * docs: record website launch verification * fix: align observer launch web contracts * fix: disclose Cloudflare photo storage (#4)
calelamb
added a commit
that referenced
this pull request
Jul 21, 2026
* docs(licensing): outreach drafts + demo-mode entry in data-licensing.md Demo-mode V1 (45 publicly-licensed orca individuals from HappyWhale + FinID-20) is shipping in fluke-model as a "useful, not authoritative" public engagement layer while Salish-Sea catalog licensing is in flight. This PR writes that down on the fluke side: - Update data-licensing.md outreach table: drafts ready for all four catalog orgs (CWR, Orca Network, Bay Cetology / Bigg's, Whale Museum) and two researcher partnerships (Bergler / FinID-20, Wild Me). - New docs/outreach/ directory with the six drafts, ready to read, personalize, and send. Each references a [DEMO_URL] placeholder so recipients can see a working thing rather than a description. - New "Demo-mode V1" section in data-licensing.md spelling out why the demo is policy-clean (both source datasets have explicit ML-permitting licenses) and the retirement plan for when real Salish-Sea catalogs come online. Drafts only — none are sent. User is in the loop on every send. * docs: define two-release launch design * docs: define standalone API extraction * docs: plan standalone API extraction * docs: fix API extraction task sequencing * docs: preserve submission contract behavior * docs: include standalone seed type repair * docs: align generated contracts with runtime * docs: correct API release workflow * refactor: move API to standalone repository * test: harden web repository boundaries * docs: plan release a launch * docs: fix release plan sequencing * test: codify release a boundaries * test: execute release boundary gates * feat: enforce browse-only web release * fix: close web release boundary gaps * ci: add release a web verification gates * test: cover critical web browse flows * chore: add contract fixture sync gate * fix: preflight contract fixture sync * docs: clarify cross-repo contract gate * ci: add cross-repo contract checkpoint * feat: consume paginated release a contracts * fix: bound web cursor pagination * feat: make web browse resilient * feat: prepare production web deployment * perf: eliminate landing hero load waterfall * feat: add launch privacy support and metadata * docs: record website launch verification * fix: align observer launch web contracts * fix: disclose Cloudflare photo storage (#4)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Photo submissions must not be enabled while the public notice still describes an unnamed provider. The selected production provider is Cloudflare R2.
Verification