liveBook · Manning

Scope of authorship

As explained in Spec-Driven Development

Scope of authorship is the set of participants, roles, and locations permitted to create or contribute to a specification.

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

How Spec-Driven Development covers it

How deep it goes
Contrasts engineer-centered repositories with stakeholder-accessible collaboration locations, without prescribing a universal authorship model.
Examples
Contrasts engineer-authored repository specifications with business-intent contributions in stakeholder collaboration systems such as product backlogs.
What you can do after
Evaluate whether a specification workflow lets relevant stakeholders contribute intent before implementation begins.
How it connects
Connects specification structure and location to stakeholder participation, intent preservation, and verification feedback loops.

This explainer was generated by Manning's knowledge graph from the text of Spec-Driven Development. The section links point to the parts of the book it draws on.