titan-workflow-architecture

To choose the right Titan workflow architecture, apply decision rules that identify the smallest correct structure for your domain, preventing both under-design and over-design while ensuring scalable, maintainable code layout.

In Titan workflow architecture, decision rules differentiate project steps, command steps, operations, clients, and services to help you place code correctly and enforce strict architecture boundaries for your specific plugin or project scenario.

Use a plugin-like project layout in Titan when you need to register plugin components, and use a vanilla project layout for simpler domains by applying the architecture boundaries and decision rules provided to determine the correct structure.

Whether to place workflow code under .titan or within a plugin package depends on the architecture decision rules, which evaluate your project domain boundaries to determine if a plugin registration layout is required for your components.

The best way to avoid over-designing a Titan workflow is to identify the smallest correct architecture by following the provided references, templates, and decision boundaries that match your specific project or plugin domain requirements.