Sbachmei/mic 6427/split manager and interface modules (#667)

Author: stevebachmeier

CHANGELOG.rst

@@ -1,3 +1,7 @@
+**3.5.6 - 10/23/25**
+
+  - Split Interfaces and their respective Managers into different modules
+
 **3.5.5 - 10/14/25**
 
   - Update simulation step log message to info level

docs/source/api_reference/framework/artifact/interface.rst

@@ -0,0 +1 @@
+.. automodule:: vivarium.framework.artifact.interface

docs/source/api_reference/framework/components/interface.rst

@@ -0,0 +1 @@
+.. automodule:: vivarium.framework.components.interface

docs/source/api_reference/framework/logging/interface.rst

@@ -0,0 +1 @@
+.. automodule:: vivarium.framework.logging.interface

docs/source/api_reference/framework/lookup/interface.rst

@@ -0,0 +1 @@
+.. automodule:: vivarium.framework.lookup.interface

docs/source/api_reference/framework/randomness/interface.rst

@@ -0,0 +1 @@
+.. automodule:: vivarium.framework.randomness.interface

docs/source/api_reference/framework/resource/interface.rst

@@ -0,0 +1 @@
+.. automodule:: vivarium.framework.resource.interface

docs/source/concepts/crn.rst

@@ -154,7 +154,7 @@ Registering simulants
 ++++++++++++++++++++++
 
 Let's start with registering simulants. The randomness system provides the
-aptly named :func:`register_simulants <vivarium.framework.randomness.manager.RandomnessInterface.register_simulants>`,
+aptly named :func:`register_simulants <vivarium.framework.randomness.interface.RandomnessInterface.register_simulants>`,
 which handles the mapping process we looked at above where simulants'
 chosen characteristics are used to map them to a specific location in the
 **randomness index**. This should be used in initializing simulants.
@@ -178,7 +178,7 @@ RandomnessStreams
 
 More commonly, you may want to get and use RandomnessStreams for specific
 **decision points**. The randomness system provides the
-:func:`get_stream <vivarium.framework.randomness.manager.RandomnessInterface.get_stream>` to do this. Let's
+:func:`get_stream <vivarium.framework.randomness.interface.RandomnessInterface.get_stream>` to do this. Let's
 look at a quick example of how we'd use this. Say we want a component that will
 move simulants one position left every time step with probability 0.5. We should
 use a :class:`RandomnessStreams <vivarium.framework.randomness.stream.RandomnessStream>`

docs/source/tutorials/disease_model.rst

@@ -185,7 +185,7 @@ Line 2 simply grabs a copy of the simulation
 a dictionary that supports ``.``-access notation.
 
 Lines 4-18 interact with Vivarium's
-:class:`randomness system <vivarium.framework.randomness.manager.RandomnessInterface>`.
+:class:`randomness system <vivarium.framework.randomness.interface.RandomnessInterface>`.
 Several things are happening here.
 
 Lines 4-13 deal with the topic of :doc:`Common Random Numbers </concepts/crn>`,

src/vivarium/framework/artifact/__init__.py

@@ -1,7 +1,7 @@
 from vivarium.framework.artifact.artifact import Artifact, ArtifactException
 from vivarium.framework.artifact.hdf import EntityKey
+from vivarium.framework.artifact.interface import ArtifactInterface
 from vivarium.framework.artifact.manager import (
-    ArtifactInterface,
     ArtifactManager,
     filter_data,
     parse_artifact_path_config,