Devil May Cry 3 HD Collection · Evidence-first C++20 research
GDSpaces — DMC Rengine Resource Architecture
Entry point into the canonical GDSpaces resource resolver/materializer/provenance architecture. The site does not recreate its contracts or state.
What GDSpaces connects
- GDSpaces is the resource architecture that carries provenance from archive source through member, container and slot layers toward a classified resource instead of flattening those steps into one extraction operation.
- Resolver, classifier, container expansion and resource-graph responsibilities are separated so a guessed filename or extension cannot silently override stronger structural evidence.
- The architecture lets Stage Ops, readers and future authoring workflows reuse one canonical materialization path instead of embedding format-specific extraction logic in each UI.
Questions this entry point helps answer
- How can a resource remain traceable back to the NBZ member, PAC or PNST slot and evidence that produced it?
- Where is the boundary between physical storage, materialized bytes, format classification and runtime resource resolution?
- Why does DMC Rengine centralize these contracts before adding higher-level browsing, editing or export workflows?
Evidence boundary
A parser is not automatically a writer. A successful writer is not automatically equivalent to Capcom's offline tools. Synthetic validation does not establish original-game behavioral equivalence.
Use the current status for promoted capabilities and open proof gates.