Make the expectation explicit
Prioritize tests around those outcomes. Cover the most important journey first and include the failure paths that could block a user or lose work.
Put it into practice
Start a AuraCheck evaluation with one meaningful requirement. Review the case, run the journey, and inspect the evidence. Expand coverage because of risk, not because a test count looks impressive.
Try this on your next release
Choose one journey, define the expected result, and inspect the evidence from a completed run. Expand the suite after the first test is useful.