Software development processes requires a thorough understanding of stakeholder objectives and requirements. Product-centrism is an insufficient stance from which to achieve greater efficiencies and reduce reengineering. Stakeholder requirement elicitation is thus worthy of formalization. A suite of tools, notably the i* model, provides a framework for early-phase requirements capture. These tools currently are at best only semiautomated and essentially consist of a notational glossary and sets of mark-up symbols. Increasing formalization may lead to greater automation of the process in the future, but currently there is a degree of flexibility that presents pitfalls for the unwary practitioner. A notion of contextual consistency would enhance the applicability such toolkits. Requirements generated from stakeholder objectives may suffer scoping errors, complicated by the complexity of practical examples. Hierarchical situations of contextual confusion are explored. A formalisation is offered of the constraints that circumscribe the set of valid decompositions.