The visual source archive for Warpkeep: buildings, characters, landscapes, identity and sound, preserved with dated provenance, release manifests and verification tools.
Find source material here, then follow the game repository for runtime selection and integration. A source deposit, a runtime candidate and a playable feature are different stages of the work.
City Mill source preview from the August 2026 library. Gallery · Provenance.
Collections · Historical galleries · Licensing · Verification · Contributor guide · Security policy
Warpkeep 0.4 is being developed around gather → choose → build → benefit → return. The Verdant Citadel direction combines pale masonry, dark timber, teal roofs and layered natural surroundings in a readable keep diorama. This archive supplies preserved material for that work; composition, gameplay, mobile performance and release acceptance belong to the game.
Follow the 0.4 development source for current progress. An asset publication does not mean 0.4 has shipped. Reused material keeps its original authorship, provenance and terms.
Choose by purpose. The linked catalog keeps the dated galleries, exact downloads, package quantities, manifests and provenance together.
| Collection | What to find | Catalog and source records |
|---|---|---|
| Keep and settlement | Buildings, town props, palisades, ruins, banners and castle foundations. | Library and gallery · Earlier castle deposits |
| Citizens | Keep services, civic orders and mounted inhabitants. | Citizen collection |
| Unit corps | Infantry, ranged and cavalry models with their recorded rigs and actions. | Unit collection |
| Forests | Tree sources and runtime bundles for natural framing. | Tree bundle · Library trees |
| Gathering destinations | Windmill, logging camp, quarry and gold-mine deposits. | Food · Wood · Stone · Gold |
| Wildlife | Rabbit models, animation and UI material with the recorded validation limits. | Rabbit bundle |
| Identity and titles | The Core crest, Hegemony emblem, stone-letter title and historical Mark artwork. | The Core · Identity releases |
| Workers and supply | Wagon references, modeled supply wagons and the supplied worker source set. | Source releases |
| Sound | The supplied Hegemony admission-request button sound. | Audio record |
The historical catalog preserves the
publication record, including supplied QA statements and integration limits.
All release manifests remain in releases/; the
asset ledger links each set to its terms.
This is a mixed-license archive. Public download does not itself grant adaptation or redistribution rights. Read the root licensing map, the per-set ledger and the affected provenance record.
Project-authored verification software uses Apache 2.0. The stone-letter title set and Hegemony Mark artwork are expressly covered by CC BY 4.0. Other deposits retain their archive-only, original or unresolved terms; these grants do not extend across the collection. Repository prose follows the scope in the licensing map.
The game's licensing policy and runtime asset inventory record how integrated material is treated.
Most assets in this archive were substantially authored, prepared, or refined with Codex using OpenAI's GPT-5.6 Sol model at Ultra reasoning effort, under human direction and review. Some individual assets also use other tools or generation services; each set's dated provenance record remains the source of truth for its specific production history. This disclosure describes the creation process only. It does not change any license, ownership, attribution, or trademark boundary.
From the repository root, download all attachments for the chosen release into one directory, then verify them against its manifest:
python3 scripts/verify_release.py \
--manifest releases/title-stone-letters-2026-07-12/manifest.json \
--asset-dir /path/to/downloadsUse a manifest from a trusted repository commit. If its SHA-256 came through a
separate trusted channel, pin it with --manifest-sha256. Checksums establish
byte integrity against that manifest, not supplier identity or permission to reuse.
The verifier requires the release checksum sidecar. It rejects wrong bytes,
unsupported media, non-regular files, malformed PNG/GLB/Blender containers,
unsafe or unexpected archive paths, duplicates and excessive decompression.
Zstandard-compressed .blend and .blend1 verification requires the zstd CLI;
input, output and runtime are bounded, and a missing tool fails closed.
Rerun the manifest's pinned glTF semantic validation before deriving new runtime assets.
| Location | Responsibility |
|---|---|
releases/ |
Attachment manifests and checksum sidecars |
manifests/ |
Source inventories and preparation records |
provenance/ |
Authorization, production history and license boundaries |
previews/ |
Lightweight visual catalogs |
scripts/ and tests/ |
Release verification and regression checks |
| Historical catalog | Dated showcases, package details and original release links |
The July 2026 security and quality review has its own manifest and sanitized provenance. It is a dated technical snapshot; raw private evidence is excluded.
- Preserve exact release tags, attachment names, byte counts and SHA-256 values in downstream preparation records.
- Keep large masters in the established release-attachment archive and lightweight documentation and previews in Git.
- Deliver optimized runtime files through the game; release downloads are not a runtime CDN.
- Preserve source attribution and exact permissions through every derivative. Filenames, generation tools and repository presence do not establish ownership.