qsdsan-exposan-architecture

What problem does it solve?

It prevents breaking changes when evolving the paired QSDsan (engine) and EXPOsan (systems) repositories by documenting the required boundaries, naming conventions, dependency policy, and documentation standards.

Core Features & Use Cases

• Change management rules: Clear guidance on when to put modeling capabilities in QSDsan versus keeping case-study/system specifics in EXPOsan.
• Public namespace conventions: Canonical unit and process namespaces (unit_operations and process_models) and how to classify units into bst/static/dynamic.
• LCA and flowsheet isolation patterns: Correct per-flowsheet registry behavior, including the recommended context manager and removal of deprecated clearing patterns.
• Documentation authoring conventions: A strict notebook structure and style rules to keep tutorial artifacts consistent and buildable.

Quick Start

Ask the assistant to review your proposed QSDsan/EXPOsan change against the package map, namespace rules, and the release/checklist guidance, then recommend exactly what to update in each repo and what tests and docs to adjust.