The rapid adoption of generative AI in software development has exposed a structural weakness in the artifacts used to communicate engineering intent. Traditional specifications—such as Software Design Documents and informal design notes—were designed for human authorship and linear development processes. In AI-assisted environments, however, code generation is inference-driven, asynchronous, and repeated across many generation events. Prompts and conventional documents therefore fail to provide a persistent, auditable basis for governing how code is produced. This paper introduces Viewpoint-Structured Specification (VSS), a structural framework for representing Intent as a versioned, multi-viewpoint specification prior to AI-assisted code generation. VSS formalizes a specification as a structured artifact Specification=(V,E)Specification=(V,E) , where VV represents a set of declared Viewpoints and EE represents persistently addressable specification elements produced under those viewpoints. Each element satisfies three sufficiency conditions—Persistent Addressability, Explicit Scope, and Viewpoint Membership—enabling specifications to function as durable governance artifacts rather than transient documentation. From this structure, several capabilities emerge without additional mechanisms: Relation formation between elements, Semantic Conflict Detection across viewpoints, Traceability of generation decisions, and Boundary formation for selecting governing constraints during code generation. By decomposing intent into addressable units across multiple governing concerns, VSS enables latent conflicts in Intent to surface before code is generated and establishes a recoverable specification baseline that persists across system evolution. VSS does not replace existing requirements engineering or model-driven methods. Instead, it provides the structural conditions under which their outputs can function as machine-selectable, version-stable governing constraints in AI-assisted development. The framework therefore reframes specification not as static documentation but as a persistent, structured artifact that governs the legitimate basis for code generation in AI-driven software production.
Spark Tsai (Tue,) studied this question.