Computational package for: Mechanical Response Maps for Initial Incisor Proclination under Force and Displacement Normalization

Computational data and source code accompanying “Mechanical Response Maps for Initial Incisor Proclination under Force and Displacement Normalization”. Idealized Z-spring, 2×4 wire and clear-aligner models are coupled to a common rigid-root–periodontal ligament support. Paired normalizations use initial crown displacement of 0.0025 mm or labial force of 0.01 N. Analyses address morphology, material properties, geometry, mesh/formulation sensitivity, and layered bone with alveolar crest offsets. The original design contains 96 support configurations and 576 paired device-normalization rows. Separate formulation/geometry/modulus sensitivities add 348 coupled rows and a 24-row analytical pressure benchmark. Bone-support analyses add 216 core and 228 extension rows. Baseline and contact-height outputs are also included. These are numerical configurations, not patients or independent experimental replicates. The computational archive preserves 63 scientific CSV files, 484 NPZ archives and 22 Python source files from the final research package. It includes checksums, reproducibility instructions, verification reports and failure/precision diagnostics. Manuscript drafts, editorial checklists and document-layout records are excluded. All observations are simulation outputs. No patient-derived measurements or clinical observations are included. The models describe initial mechanical responses, not clinical tooth movement, treatment efficacy or safety thresholds. Computational verification does not establish experimental or clinical validation. OpenAI ChatGPT/Codex assisted implementation, computation, analysis and drafting; independent human scientific verification is not claimed. Licensing is file-specific, not a choice between alternative licenses: data, figures and documentation are CC BY-NC 4.0; original Python source files use the Mechanical Response Maps Noncommercial Research License v1.0. Commercial reuse requiring the licensor’s permission needs separate prior written permission from Enes Bardakçı, [e-mail]. See LICENSE_SCOPE.txt, LICENSE_DATA.txt and LICENSE_CODE.txt. Third-party dependencies retain their own licenses. The code is source-available, not OSI-approved open source. Zenodo metadata follows Zenodo’s separate metadata policy.