UDCT v7.11 — Post-registration Results: Constant-Anisotropy Jeans and Outer-Boundary Sensitivity in Hydrus I

79UDCT v7.11 — Post-registration Results Reserved Zenodo DOI:https://doi.org/10.5281/zenodo.23263099 GitHub repository:https://github.com/wspaik5/UDCT_v7.11_Postregistration_Results Preregistered protocol:https://doi.org/10.5281/zenodo.23244522 This record reports the completed preregistered test of constant velocity anisotropy and outer-boundary sensitivity in the radial Jeans analysis of Hydrus I, using the frozen GQUMOND implementation from UDCT v7.10. The registered experiment comprises 216 gravitational-field evaluations, 1,080 pressure records, and 180 case-level decisions. It includes tapered-cusp and Plummer stellar profiles, five screening functions, screening lengths of 1, 3, and 10 pc, three QUMOND controls, and five constant anisotropy values: beta = -1, -0.5, 0, 0.25, and 0.5. All 216 isotropic reproduction checks passed. Independent recomputation reproduced all 180 registered decisions: 78 negative, 58 positive, and 44 indeterminate. Excluding positive-beta Plummer cases from physical interpretation leaves 144 eligible cases: 74 negative, 26 positive, and 44 indeterminate. For the A-f1/2 screening function at 10 pc, negative radial Jeans pressure persists across all five tested anisotropy values in both stellar profiles. Other configurations produce positive or indeterminate outcomes. The QUMOND controls yield no negative classifications. The study also reports the nonnegative outer radial pressure required to remove sampled negative pressure and a finite-shell virial audit. These boundary-pressure values are numerical diagnostics; they do not establish a physical confinement mechanism. The conclusions apply to the tested constant-anisotropy models and frozen assumptions. They do not exclude MOND generally, establish a full three-dimensional equilibrium or a positive distribution function, fit observed stellar velocities, or validate a new UDCT gravitational theory. The accompanying report and reproducibility package document the registered code, complete results, independent audits, execution provenance, and checksums. An initially truncated JSON output is preserved, and the successful compressed-output rerun is documented separately.