This document defines public-facing product, community, lore, and subsystem names for DMC Rengine C++.
Expanded name: Devil May Cry 3: Special Edition – HD Collection Decompilation & Recompilation Engine.
Positioning: An open-source C++20 research, decompilation, editing, and recompilation framework for Devil May Cry 3 HD.
Primary line: Reverse the engine. Rebuild the possibilities.
Technical line: Evidence-backed reverse engineering from resource identity to recompilable systems.
Lore line: Descend to the bytes. Return with the source.
Community authorship line: Built by the Sect of Neuroslop and the Monks of Binary Code.
The Sect of Neuroslop (Секта Нейрошлаку) is the public community identity of DMC Rengine.
It includes users, researchers, modders, programmers, artists, testers, writers, supporters, and contributors gathered around the project.
It is not an AI-only wing, a permission system, a verification tier, or a second hidden organization.
The Monks of Binary Code (Монахи Бінарного Коду) are the creators and evidence-backed core contributors of DMC Rengine.
The title is derived from accepted contribution records and does not itself grant repository, release, signing, moderation, or administration rights.
The Order of the Inverted Triangle is a lore-facing alias for the core DMC Rengine Team.
It is not the whole community. The wider community is the Sect of Neuroslop.
The Monastery of Binary Code is the lore-facing name for the DMC Rengine Core Development Hub.
It is a presentation alias for the core team's development workspace, not a separate Team or authority domain.
The single resource access API and virtual resource space.
Responsibilities include source mounting, game-folder scanning, NBZ/AFS/PAC/PNST expansion, path normalization, resource identity, classification, graph construction, diagnostics, evidence context, typed bundles, working copies, and future safe write policy.
The visual hub connecting tools, resources, evidence, scenes, executable findings, specifications, and project memory.
The executable research and source-recovery environment.
It owns PE analysis, disassembly evidence, recovered C/C++, function and data annotations, RVA/VA mapping, guarded patch plans, and the future compile/rebuild pipeline.
The evidence-oriented binary structure environment.
It owns byte regions, structure trees, ownership maps, field inspection, diffs, unknown regions, annotations, and diagnostics. It does not independently resolve game sources.
The stage and scene operations workspace.
It receives typed GDStageBundle objects and coordinates stage scripts, models, cameras, lighting, effects, collision, sound, events, positions, and unknown resources.
The visual editing and reconstruction environment.
Top-level modes:
- Scene/Model Editor — 3D scene, model, transform, hierarchy, and resource visualization.
- Menu Editor — HUD, menu, digit meshes, icon slots, screen-space layout, UV regions, draw order, and runtime-value preview.
The typed item-authoring workspace for ITM resources, item libraries, runtime-linked limits, guarded EXE changes, validation, and mod packaging.
The controlled environment for builds, patch validation, fixture tests, runtime tests, regression checks, reproducibility, and artifact reports.
These platform aliases are Chambers of the Monastery. They are not Teams, Orders, ranks, or independent sources of truth.
The versioned body of accepted, corrected, rejected, and research-required project knowledge.
The index connecting claims to hashes, offsets, bytes, traces, tests, recovered symbols, runtime observations, and supersession records.
The provenance path from Artifact → Hash → Evidence → Finding → Code → Test → Build.
A public/read-model view over corrected and rejected findings, failed experiments, and superseded assumptions.
A curated public explanation of major technical corrections.
A presentation badge that displays an exact underlying Evidence status and artifact scope. It never creates a new confirmation level.
Long-term AI-assisted project memory.
Human-readable project notes, journals, architecture pages, and research narratives.
Machine-usable relationships between resources, formats, executable functions, tools, specifications, evidence, and decisions.
The collection of controlled software design specifications, proposals, acceptance criteria, and compilation packets.
The append-only record of decisions, corrections, migrations, tests, and architecture changes.
The overall reverse-engineering and source-recovery journey:
Surface → Behavior → Resources → Structures → Ownership → Functions → Source → The Return.
Production read-only container and archive research.
Stage identity, StageBundle, stage behavior, and scene reconstruction work.
SCM, MOD, HITS, collision, mesh, and geometric-format research.
Save, persistence, state, and memory-card architecture.
EXE analysis, recovered types, ABI, ownership, functions, and source units.
HUD, Menu Editor, atlas, digit-mesh, and runtime counter work.
Source modification, integration, custom builds, behavioral comparison, and recompilation milestones.
Campaign names are labels over existing Projects, roadmaps, or publication series. They do not create new authority or workflow state.
These are optional presentation aliases for existing workflows:
- The Descent — opening a bounded research question;
- The Witnessing — capturing artifacts, bytes, traces, and observations;
- The Binding — linking findings to Evidence, code, graph, ownership, and tests;
- The Trial — CI, malformed-input, differential, runtime, or release validation;
- The Promotion — moving a finding into reviewed implementation and Canon;
- The Reconciliation — synchronizing implementation, research, docs, issues, and receipts;
- The Closure — recording exit criteria and residual gaps;
- The Return — behavior-tested recovered source entering a controlled build.
Professional workflow names remain canonical in APIs and stored records.
- Product names describe responsibilities, not file extensions.
- Container names never become top-level architecture names.
- The Sect names the community; it is not an AI-only subgroup.
- Monk of Binary Code is evidence-backed contributor recognition, not a permission role.
- The Order of the Inverted Triangle names the core Team, not the entire community.
- Tool aliases are Chambers, not additional Orders or authorities.
- Marketing aliases may appear beside technical names, never instead of them in API contracts.
- One subsystem has one canonical professional name.
- Experimental names must be labeled experimental.
- Legal, security, moderation, recovery, payment, and destructive-operation language remains direct and professional.
- Old PAC Editor/PAC Manager terminology is retained only in historical migration documents.
- Public lore must remain self-contained and must not imply technical claims beyond the available evidence.