# 04E Vocabulary in Context

The initial release must be compliant with the agreed requirements, including any explicit limit on automated actions.
An auto mode may sound convenient, but users must understand which actions are automated and which require a decision.
We considered a different implementation, but the selected approach covers the core requirement with less complexity.
Before we implement an option, we should consider its effect on the whole workflow rather than one attractive feature.
The system allows users to set a target, and it must clearly explain what happens when they reach it.
A bounded task has an explicit limit, while an undefined task may expand in an unintended direction.
A non-unique name is allowed here, but this field requires a unique identifier for each record.
We rejected several fancy additions because the basic product did not depend on them.