Galdex · Work fingerprints and save-location rules

Project overview · GalShelf · Galguard · Galdrive

Galdex is an internal maintainer tool for work fingerprints and save-location rules. It is not another metadata website or an extra library application for players. It organises file evidence into reviewed data that can be signed, published and verified by consumers.

Status: core development is substantially complete. This page is not an internal-tool download. Tool completion, production corpus coverage and consumer integration are separate states; availability follows the relevant data and client releases.

Identify existing collections by more than names#

Collections may have been renamed, moved or reorganised. A work may have several editions, translations and patches. Folder and EXE names alone can be ambiguous, incomplete or unrelated to a database title.

Galdex associates verified fingerprints with work identity. Known files provide content-based evidence to assist identification. Unknown, changed or ambiguous files must not be forced into a definitive match.

File evidence and the work index#

Identity uses VNDB work IDs, not another public numbering system. Galdex does not replace VNDB, NextMoe or other metadata sources.

Evidence includes SHA-256, exact file size and the file's game role. Maintainers distinguish useful game identity anchors from shared runtimes and helper programs, which must not become unique identifiers merely because several games include them.

Multiple records can identify one work without implying identical editions, translations or patches, or interchangeable saves.

Save-location rules#

Galdex also maintains rules and supporting evidence for where a game's saves may be found, assisting a client's save-directory selection.

A rule is a location proposal, not permission to manipulate files. The client still checks the actual directory, edition compatibility and authorisation. An identity match must not itself bind a path, upload, restore or widen write access.

Collection, review and signed publication#

Collect: bind work identity, collect fingerprints, attach verified save rules and evidence, and prepare candidate records.

Review: submission does not make a candidate trusted. Collection, review and publication have separate responsibilities, and production records require the appropriate review.

Publish: accepted records form a signed data set. Consumers check signatures, validity and compatibility. Failed verification or invalid data must not remain a trusted identity source.

The records describe fingerprints, rules and associations; they are not a distribution channel for game binaries, translation packages or players' saves.

Component relationships#

GalShelf can use identity evidence alongside import confirmation, library indexing and management.

Galguard can show verified identity as provenance while retaining independent integrity and scanning decisions. A match does not clear a threat or accept a new baseline.

Galdrive can use identity and save rules to organise backups and restoration. Actual paths, compatibility, conflicts and write authority remain responsibilities of the save workflow.

Identification is not proof of safety; a finished tool is not a complete catalogue. Coverage comes from reviewed, published records. Players do not need a maintainer workspace, review privileges or signing keys.