ALL-STAT1002 · temporal_coupling
Judge whether required operation order is explicit and justified.
This is a contextual rule for all languages. Read its implementation.
Definition
Section titled “Definition”Compare legal states, constructors, method order, hidden flags, failure modes, and possible designs that make invalid sequences unrepresentable.
Evidence
Section titled “Evidence”Findings cite state transitions, callers, ordering assumptions, failures, and alternatives.
Exceptions
Section titled “Exceptions”Stateful protocols may require order when the API represents each state clearly.
Examples
Section titled “Examples”Requiring configure before run while both methods remain callable is hidden. A session
object returned only after successful configuration makes the sequence explicit.
References
Section titled “References”- Cites “The Pragmatic Programmer”, temporal coupling
- Cites “Refactoring”, Mutable Data
- Cites “Domain-Driven Design”, making implicit concepts explicit