hygiene: finalize GeoIntel public release
Managed validation / Managed repository validation (pull_request) Successful in 1m54s
GeoIntel release gates / Compile, test, contracts and builds (pull_request) Successful in 1m53s
GeoIntel release gates / Python and npm vulnerability policy (pull_request) Failing after 20s
GeoIntel release gates / Production AI image, SBOM and container scan (pull_request) Failing after 12m1s
GeoIntel release gates / Deploy exact gated revision to Unraid (pull_request) Skipped

This commit is contained in:
NuklearRabbit
2026-09-02 23:43:03 +02:00
parent faeb58ef6d
commit 3969a35d7a
7 changed files with 58 additions and 4 deletions
+32
View File
@@ -0,0 +1,32 @@
# Asset provenance and redistribution
The visual files distributed with GeoIntel were created for this project and
are released by the repository owner with the source under Apache-2.0. They do
not include private operator data, proprietary model weights, unpublished
imagery, or a bundled third-party geospatial dataset.
## Project artwork
The original PNG masters in `frontend/design-assets/portfolio/` and their
optimized WebP derivatives in `frontend/public/portfolio/` are project artwork.
The WebP files are mechanical resizes of the corresponding masters; the
reproduction command is documented in `frontend/design-assets/README.md`.
## Product captures and generated documents
Files in `docs/assets/portfolio/` are captures or diagrams of the GeoIntel
public-demo interface using synthetic/public demonstration content. The case
study at `output/pdf/geointel-case-study.pdf` is generated from repository
sources by `scripts/create_portfolio_case_study.py`.
Any provider name, logo, map attribution, or dataset title visible inside a
capture remains the property of its respective owner and is included only to
identify the source or reproduce the application's attribution UI. This
repository does not relicense or redistribute the underlying provider data.
## Integrity
Release review verifies these paths through the repository's normal Git object
hashes and the public-release gate. Regenerated derivatives must come from a
tracked master or reproducible repository source; do not replace them with
unlicensed stock material, private screenshots, or local operator exports.