What — Make the chosen ligand and receptor states and preparation decisions explicit in a docking run.
How — Record ligand chemical state and conformer, receptor state, pH and residue variants, retained waters/cofactors, and any transformation parameters; associate each result with those inputs.
Why — The Core MVP requires prepared states and backend representations to be traceable to source systems.
Record — devguide/pending_proposals/select_molecular_states_and_record_preparation_decisions_for_docking.md
Related — #3. DockingMT consumes MolSysMT state selection and preparation capabilities tracked in uibcdf/molsysmt#217, uibcdf/molsysmt#218, uibcdf/molsysmt#220, uibcdf/molsysmt#221, and uibcdf/molsysmt#222.
What — Make the chosen ligand and receptor states and preparation decisions explicit in a docking run.
How — Record ligand chemical state and conformer, receptor state, pH and residue variants, retained waters/cofactors, and any transformation parameters; associate each result with those inputs.
Why — The Core MVP requires prepared states and backend representations to be traceable to source systems.
Record — devguide/pending_proposals/select_molecular_states_and_record_preparation_decisions_for_docking.md
Related — #3. DockingMT consumes MolSysMT state selection and preparation capabilities tracked in uibcdf/molsysmt#217, uibcdf/molsysmt#218, uibcdf/molsysmt#220, uibcdf/molsysmt#221, and uibcdf/molsysmt#222.