README.md

DMC Rengine Documentation

Start here

• Current project status
• Public DMC3 FAQ
• Public DMC3 HD file-format and archive index
• Public discovery strategy
• Public release readiness
• GDSpaces Layer 1 roadmap
• Project roadmap
• Architecture
• GDSpaces contract
• DMC3 HD format and resource-purpose catalog
• DMC3 HD machine-readable format-purpose registry
• DMC3 HD format presence census
• DMC3 HD machine-readable format presence census
• DMC3 HD format-purpose closure pass — 2026-08-27
• Format documentation index
• Status system
• Constitution
• Contributing

Current execution authority

The live execution program, canonical implementation base and current proof gates are recorded in Current project status. This documentation index intentionally does not duplicate a frozen status snapshot.

Completion remains gate-based, not percentage-based. Synthetic tests, structural parsing, resolver progress or individual format readers never override the applicable canonical acceptance gates.

Architecture and contracts

• Canonical decisions
• Deprecated architecture
• Architecture Decision Records
• Tool integration
• DMC3 reverse-data authority
• Reverse-engineering rules
• Clean-room policy

GDSpaces

• GDSpaces contract
• Canonical L1 roadmap
• Layer classification
• Reverse progress scale — planning aid only; roadmap gates control completion
• Resource classification
• Working copy
• Container tree reconciliation
• DMC3 runtime resource resolver
• DMC3 resource lookup policy
• DMC3 loose-container .lst materialization
• DMC3 layout-preserving relative-slot writer
• DMC3 runtime-synth relative-slot writer
• DMC3 nested relative-slot reintegration
• DMC3 NBZ STORE overlay writer
• DMC3 NBZ retail serialization preservation

Formats and resource semantics

• Public DMC3 HD file-format and archive index
• Format documentation index
• Canonical DMC3 HD format and resource-purpose catalog
• Machine-readable DMC3 HD format-purpose registry
• DMC3 HD format presence census
• Machine-readable DMC3 HD format presence census
• Direct format-purpose closure pass — 2026-08-27
• HITS collision resource
• PAC structural parser
• PNST structural parser
• Residual DMC3 format census — 2026-08-26

The format catalog is the canonical human-readable inventory of currently observed/named DMC3-HD resource families. The JSON purpose registry is its machine-readable semantic companion. The separate presence census records a different axis: whether real payload bytes are bound to a retail/corpus source, whether a family is currently known only from the EXE, whether a semantic working name rides over .bin/.ukn, or whether an identifier is capability-only. These axes must not be collapsed. Unknown semantics stay explicitly bounded; extensions and short ASCII hits are never promoted as semantic truth by themselves.

Stage and downstream tools

• Stage Ops owns product-side stage/scene assembly and orchestration over GDSpaces outputs.
• Stage Semantic Graph is a derived representation/index of Stage Ops state.
• ModViz consumes Stage Ops/Semantic Graph state and must not create a second resolver or scene truth.
• st001 is a regression/compatibility fixture, not the complete Stage architecture.

See Stage reconstruction plan for historical/current Stage evidence boundaries.

Evidence, executable and recovered source

• Public evidence registry
• Evidence Packets
• Strict Evidence JSON import
• PE Inspector
• Known executable targets
• Guarded patching

Recovered original-game functions/types/lifetime code belong to the Recovered Game Source Tree. EXE Editor is a frontend over exact binary/reconstruction authority; GDSpaces consumes confirmed behavior without owning original runtime code.

Binary Inspector

• Binary document model
• Web-to-C++20 cross-port plan

Public discovery and releases

• Public discovery strategy
• Public DMC3 FAQ
• Public release readiness

These documents improve onboarding and discoverability without changing technical truth. Release notes and public summaries must stay subordinate to current main, status and evidence authority.

Current status and planning

• Current status
• Public discovery strategy
• Public release readiness
• Canonical L1 roadmap
• Project roadmap
• Phase map
• Blockers
• Risk register
• Machine-readable status
• Weekly reports
• Specifications

Research and history

Research baselines and historical receipts remain useful evidence sources, but they do not override current main/roadmap authority without explicit promotion.

• DMC3 Format-Purpose Closure Pass — 2026-08-27
• DMC3 Vanilla Research Baseline
• DMC3 Vanilla Deep Research Wave 2
• Project timeline
• Migrated findings
• Artifact registry

Product ownership map

• GDSpaces — The Archive: only product resource resolver/materializer/provenance authority.
• Recovered Game Source Tree: original DMC3 reconstructed code/ABI/lifecycle authority.
• Reverse Core: generic evidence/reconstruction/claim/validation infrastructure.
• EXE Editor — The Scriptorium: executable/recovered-source editing and navigation frontend.
• Binary Inspector — The Reliquary: byte/structure/evidence inspection.
• Stage Ops — The Theatre: stage/scene assembly and operational workspace authority.
• Stage Semantic Graph: derived semantic/evidence representation of Stage Ops state.
• ModViz — The Observatory: editor/visualization consumer.
• Build & Test Lab — The Trial Chamber: reproducibility and behavioral validation.

Status language

• canonical / in main: reviewed promoted repository truth at the stated snapshot;
• implemented: code exists in the stated branch/revision;
• confirmed / high / bounded: reverse-evidence status, not subsystem completion;
• validated: only the named bounded test/receipt scope;
• open / research required: unresolved by direct evidence;
• superseded / historical: preserved for audit history but not current execution authority;
• complete: allowed only after the applicable formal completion gate passes.