Build an arrangement.
Inspect the dependency.
Select the parts in a small conceptual system. The example shows how a missing responsibility affects the arrangement.
A three-part example.
Local demonstration / Fictional systemEntry screen
Included
Record collection
Included
Role rules
Included
The selected parts form a connected example. Entry and role rules both have a record collection to refer to.
Parts: Entry screen, Record collection, Role rules Connections: Entry → Records; Roles → Records
What the arrangement means.
In this fictional example, the entry screen sends information to the record collection, and the role rules apply to actions on that collection. Removing the record collection leaves the other selected parts without their agreed dependency.
The rule is deliberately simple. A real application may have a different arrangement, and a diagram alone does not establish that the implementation is complete. The value is the discussion about responsibility: which part owns the information, which part provides an interaction, and which part makes a decision.
What the workbench does.
The controls update the diagram and outline in the current page. The copy action uses the clipboard when available or selects the outline for manual copying. Reloading the page restores the default arrangement.
This workbench does not create software, store records, or evaluate actual access permissions. It is an explanatory tool using predefined relationships. A project-specific component map would need agreed responsibilities, contracts, and implementation review.