screen-inventory

To map UI read-paths for Bounded Context screens, you compile a Screen Inventory detailing each screen's data needs and actions. This aligns Inbound Commands and Exposed Queries to ensure traceable cross-BC data dependencies.

A screen inventory lists each Bounded Context's contributed screens, user-facing routes, required data, and available actions. You need it when ensuring UI-bearing BCs have explicit, navigable read paths mapped to Exposed Queries.

You align Inbound Commands with screen-level read paths by documenting cross-BC data dependencies and cross-checking screen definitions with Exposed Queries. This reduces missed data requirements during design and implementation.

Yes, you can cross-check screen definitions with Exposed Queries from aggregate-designer. This validation ensures that every UI read-path has traceable data requirements and actions mapped to the correct Bounded Context.

The best way to document cross-BC data dependencies is enumerating each BC's screens, then mapping each screen to its required data and actions. This exposes navigable read paths and aligns Inbound Queries across contexts.