Scope of authorship concerns who can shape a specification and where they can contribute. When intent is kept in an engineer-authored repository or expressed in rigid, code-like structures, non-engineering stakeholders may find it harder to participate. section 3.6.1
Compare the trade-offs:
- Repository-centered specifications can suit developer-led workflows. section 3.6.1
- Separating business intent from technical detail, or collaborating in places such as a product backlog, can make it easier for non-engineering stakeholders to contribute. section 3.6.1
Figure 3.6 Taxonomy of specification styles based on structure, location, granularity, and organization

Use the taxonomy to compare specification location and structure alongside other tool-choice trade-offs. section 3.6.1
