line

Use when responsibility, authority, or handoff is unclear between people, agents, or systems.

Use when choosing the smallest complete design that meets the real need.

Use when developers need a clearer path to understand, change, verify, or operate software.

Use when effects, dependencies, failures, resources, concurrency, or execution boundaries need explicit modeling.

Use when user-facing behavior exposes implementation detail, jargon, or technical showmanship.

Use when a project-specific coding pattern must be found, taught, applied, or maintained.

Use when one result crosses technical domains and needs integrated scope and proof.

Use when an unfamiliar, costly, or high-risk task needs evidence before a decision or change.

Use when data, runtime values, types, contracts, and allowed operations must stay aligned.

Use when product behavior, interface, or content must improve for the people using it.

Use when documentation or comments must explain current behavior to a specific reader.

Use for work with two or more independently owned workstreams that need coordinated integration.