Use modules with explicit inputs
The factory mounts an image composer, diagram composer, photobooth, font builder, timeline, pet authoring, and pose atlas. Modules receive explicit mount points, runtime directories, public assets, and credentials where needed.
Those constructor inputs make dependencies visible. A diagram editor does not need to know how the platform authenticates users, and a pose tool does not need the rest of the toolkit's mutable files.
Keep documents separate from the release
Runtime files and binary chunks use the shared controller's scoped storage interface. A revision-checked manifest publishes changes, while the source package records immutable assets and source hashes. Existing local tools remain available independently.
The timeline adapter creates its own CSRF secret in runtime storage. Credential-dependent tools receive the hosted credential context rather than importing workstation configuration. Some native or provider-dependent behavior remains unavailable until suitable adapters exist.
The image composer receives a separate design-configuration path, while the pose atlas receives a prompt directory. Their distinct dependencies remain visible even within one category.
Make dependencies visible at composition time
The factory confirms which tools are mounted and what each receives. Individual readiness still depends on the module and any required provider adapter. This keeps a shared creative workspace from becoming an undifferentiated process with access to everything: composition is explicit, and each tool's data and integration needs remain inspectable.