Four Modes of Software Evolution for AI Assisted Development

This paper proposes a four-mode framework for AI-assisted software evolution: Creation, Repair, Change, and Refactoring. Each mode is defined by its objective, reference baseline, preservation obligations, execution strategy, and acceptance evidence. Creation establishes new capabilities; Repair corrects deviations from accepted requirements; Change revises required behavior or constraints; and Refactoring improves internal structure while preserving declared observable behavior. The four modes are recurring development activities rather than mandatory stages in a fixed sequence. Execution, evaluation, and feedback connect them into an ongoing software evolution process. Evaluation determines whether to accept a result, continue within the current mode, gather additional evidence, transition to another mode, or stop. The paper describes a minimal work record, a transition protocol, an illustrative development episode, and a proposed longitudinal evaluation design. The framework separates development strategies from organizational roles and is applicable to both single-agent and multi-agent systems. This work is a conceptual proposal. No empirical evaluation is reported, and no improvements in reliability, efficiency, or maintainability are claimed as demonstrated results.

Authors

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2026-11-03
DOI
https://doi.org/10.5281/zenodo.23918972
Primary Topic
Software Engineering Research
Type
preprint
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
preprint

Four Modes of Software Evolution for AI Assisted Development

Zhongren Wang
Zenodo (CERN European Organization for Nuclear Research)
Software Engineering Research
preprint

Four Modes of Software Evolution for AI Assisted Development

Zhongren Wang
preprint en

Abstract

This paper proposes a four-mode framework for AI-assisted software evolution: Creation, Repair, Change, and Refactoring. Each mode is defined by its objective, reference baseline, preservation obligations, execution strategy, and acceptance evidence. Creation establishes new capabilities; Repair corrects deviations from accepted requirements; Change revises required behavior or constraints; and Refactoring improves internal structure while preserving declared observable behavior. The four modes are recurring development activities rather than mandatory stages in a fixed sequence. Execution, evaluation, and feedback connect them into an ongoing software evolution process. Evaluation determines whether to accept a result, continue within the current mode, gather additional evidence, transition to another mode, or stop. The paper describes a minimal work record, a transition protocol, an illustrative development episode, and a proposed longitudinal evaluation design. The framework separates development strategies from organizational roles and is applicable to both single-agent and multi-agent systems. This work is a conceptual proposal. No empirical evaluation is reported, and no improvements in reliability, efficiency, or maintainability are claimed as demonstrated results.

Zenodo (CERN European Organization for Nuclear Research)
Software Engineering Research
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon