Files
the-nexus/concept-packs/genie-nano-banana/storage-policy.md
Alexander Whitestone 3367ce5438
Some checks failed
CI / test (pull_request) Failing after 11s
CI / validate (pull_request) Failing after 11s
Review Approval Gate / verify-review (pull_request) Failing after 3s
feat: Project Genie + Nano Banana concept pack for The Nexus (closes #680)
Complete concept generation pipeline:
- shot-list.yaml: 17 shots across 5 priorities (environments, portals, landmarks, skyboxes, textures)
- prompts/: 5 YAML prompt packs with 17 detailed generation prompts
- pipeline.md: Concept-to-Three.js translation workflow
- storage-policy.md: Repo vs local split for binary media
- references/palette.md: Canonical Nexus color/material/lighting spec

All prompts match existing Nexus visual language (Orbitron/JetBrains,
#4af0c0/#7b5cff/#ffd700 palette, cyberpunk cathedral mood).
Genie world prompts designed for explorable 3D prototyping.
Nano Banana prompts designed for concept art that translates to
specific Three.js geometry, materials, and post-processing.
2026-04-10 21:17:08 -04:00

2.6 KiB

Storage Policy — Repo vs. Local

What Goes In The Repo

These are lightweight, versionable, text-based artifacts:

Artifact Path Format
README concept-packs/genie-nano-banana/README.md Markdown
Shot list concept-packs/genie-nano-banana/shot-list.yaml YAML
Prompt packs concept-packs/genie-nano-banana/prompts/*.yaml YAML
Pipeline docs concept-packs/genie-nano-banana/pipeline.md Markdown
This policy concept-packs/genie-nano-banana/storage-policy.md Markdown
Palette reference concept-packs/genie-nano-banana/references/palette.md Markdown
Design notes concept-packs/genie-nano-banana/references/design-*.md Markdown
Selected thumbnails concept-packs/genie-nano-banana/references/*_thumb.jpg JPEG, max 200KB each

Thumbnails are low-res (max 480px wide, JPEG quality 60) versions of selected concept art — enough to show which image a design note references, not enough to serve as actual texture data.

What Stays Local (NOT in Repo)

These are binary, heavy, or ephemeral:

Artifact Local Path Reason
Nano Banana full-res PNGs ~/nexus-concepts/nano-banana/ Binary, 2-10MB each
Genie walkthrough videos ~/nexus-concepts/genie-worlds/ Binary, 50-500MB each
Genie full-res screenshots ~/nexus-concepts/genie-worlds/ Binary, 5-20MB each
Raw texture maps (PBR) ~/nexus-concepts/textures/ Binary, 2-8MB each
Cubemap face images ~/nexus-concepts/skyboxes/ Binary, 6x2-10MB

Why This Split

  1. Git is for text. Binary blobs bloat history, slow clones, and can't be diffed. The repo should remain fast to clone.

  2. Concepts are reference, not source. The actual Nexus lives in JavaScript code. Concept art informs the code but isn't shipped to users. Keeping it local avoids shipping a 500MB repo.

  3. Regeneration is cheap. If a local concept is lost, re-run the prompt. The prompt is in the repo; the output can be regenerated. The prompt is the durable artifact.

  4. Selected references survive. When a concept image directly informs a design decision, a low-res thumbnail and design note go into the repo — enough context to understand the decision, not enough to replace the original.

Thumbnail Generation

To create a repo-safe thumbnail from a concept image:

# macOS
sips -Z 480 -s format jpeg -s formatOptions 60 input.png --out output_thumb.jpg

# Linux (ImageMagick)
convert input.png -resize 480x -quality 60 output_thumb.jpg

Max 5 thumbnails per shot. Only commit the ones that are actively referenced in design notes.