The Third Restructuring of Software Form: From the Three-Tier Architecture to Storage, Models, and Agents

Source

• Source name: arXiv
• Source kind: paper
• Authors / organization: Wei Lin, Tao Zhou, Zhaofei Xie, Changgui Hong
• Venue: arXiv: cs.AI
• Published: 2026-08-20
• Collected: 2026-08-21
• URL: http://arxiv.org/abs/2608.20201v1
• PDF: https://arxiv.org/pdf/2608.20201v1
• DOI: UNKNOWN
• Registry group: academic_apis_and_preprints
• Evidence role: canonical_academic_index
• Language: en
• Country / region: UNKNOWN

Plain-Language Brief

The paper suggests a third shift in software development, called Software 3.0, which focuses on context and reasoning determining behavior. The proposed terminal form includes a generalized database, a large model, and an agent. The authors argue that traditional three-tier architectures will be transformed with the user interface layer absorbed by the model's ability to generate interfaces, the business logic layer re-partitioned into model reasoning and storage constraints, and only the data layer remaining as persistent infrastructure.

What the Document Says

• The authors propose a third shift in software development called Software 3.0.
• Software 3.0 focuses on context and reasoning determining behavior.
• The terminal form of Software 3.0 consists of a generalized database, a large model, and an agent.
• In traditional three-tier architectures, the user interface layer will be absorbed by the model's ability to generate interfaces.
• The business logic layer will be re-partitioned into model reasoning and storage constraints.
• Only the data layer will remain as persistent infrastructure.

Key Concepts Mentioned

• Software form
• Software 3.0
• Three-tier architecture
• Generalized database
• Large model
• Agent

Claims Made by the Document

• A third shift in software development, Software 3.0, is underway.
• The terminal form of Software 3.0 converges to three elements: a generalized database, a large model, and an agent.

Evidence Used

• Formalization of the convergence thesis
• Presentation of a minimal reference architecture
• Reporting evidence from real prototypes and a live model

Methods / Approach

UNKNOWN

Limitations Stated by the Authors

UNKNOWN

Limitations Noted by the Agent

Agent interpretation — not from the source.

UNKNOWN

Open Questions

UNKNOWN

Notes for Future Q&A

May include interpretation. Labeled where it does.

UNKNOWN

Raw Abstract / Excerpt

Software form has undergone two paradigm shifts since its inception: Software 1.0, in which instructions determine behavior, and Software 2.0, in which data determines behavior (machine learning). This paper argues that a third shift - Software 3.0, in which context and reasoning determine behavior - is now underway, and contends that its terminal form converges to three elements: a generalized database (the unified abstraction of all persistent state and memory), a large model (the intelligence core that performs reasoning and generation), and an agent (the execution loop connecting the first two). The core argument is as follows: in the traditional three-tier architecture, the user-interface layer will be absorbed by the model's ability to generate interfaces on demand, the business-logic layer will be re-partitioned along 'expressibility x criticality' into model reasoning and storage constraints (with residual deterministic logic retained as tools), and only the data layer will be elevated into the sole persistent infrastructure. We formalize this convergence thesis, present a minimal reference architecture, report evidence from real prototypes and a live model, and systematically analyze both the conditions under which it holds and the boundaries where it fails - determinism, cost, security, and verifiability delimit the thesis's domain of applicability. We argue that the thesis holds in task domains that are expressible, verifiable, externally stateful, and tool-complete, and that it will reshape the roles of developers, the database industry, and the software-engineering discipline.