arXiv:2606. 17099v1 Announce Type: cross Abstract: AI coding agents increasingly accept assigned software tasks, modify repositories under bounded authority, and return work packages for review.
The study investigates when work done with AI feels like one's own, using a qualitative survey where participants described tasks that felt owned versus not owned. Findings show that ownership depends on the collaboration process: people feel ownership when they lead, iterate, or rewrite, but disown work when merely approving AI suggestions. Ownership also extends to tasks where people set the vision but rely on AI for execution, yet loss of personal voice and lack of comprehension erode ownership, and willingness to disclose AI use is driven more by community norms than by pride.
arXiv:2606. 05770v1 Announce Type: cross Abstract: AI is changing how software engineers work, but it often comes with hidden burdens and costs.
arXiv:2607. 01087v1 Announce Type: cross Abstract: Generative AI is shifting software engineering from a practice organized around scarce implementation effort toward one organized around abundant, low-cost code production.
The article discusses how generative models increasingly act as builders, defenders, and breakers of software, challenging the assumption that full autonomy is the ultimate goal. It introduces a framework that defines measurable independence between lifecycle roles based on shared generative substrates, and proposes five autonomy levels, three human roles, and five decision criteria to guide oversight. The authors argue that human authority should focus on specification, accountability, and emergency intervention, and they outline testable hypotheses and protocols to evaluate independence and oversight effectiveness.
The paper investigates the reliability of software produced by agentic AI by comparing AI-generated versions of ten well-known Linux utilities to their human-written counterparts. Using fuzz testing (both black-box and coverage-guided AFL++), the authors find that AI-generated code is often as reliable or more reliable than the latest human versions, with fewer memory errors but a higher incidence of hangs. The study emphasizes that robust AI-generated software requires careful prompting, skilled human oversight, and that the AI workflow can serve as a cost-effective specification for sustainable code.
arXiv:2606. 13468v1 Announce Type: cross Abstract: AI coding agents are increasingly used to generate pull requests (PRs) that propose code fixes in software projects.
arXiv:2607. 28617v2 Announce Type: replace Abstract: System prompts are instructions configured by developers to govern the behaviors of foundation models in AI applications.
The paper discusses the EU AI Act’s requirement for generative AI providers to embed detectable watermarks in their outputs, noting that Anthropic’s Claude models and Google’s Gemini use SynthID‑Text by default. It critiques the lack of verifiability of claims about watermark quality, privacy, and robustness, and evaluates the open‑source SynthID‑Text implementation on two open‑weight models, finding minimal impact on prose and modest correctness loss on code. The authors argue that the real governance issue is the inability to verify these assertions and outline necessary steps—such as output release, configuration disclosure, accredited audits, shared evaluation protocols, and interoperable detection—to address the gaps.
The study investigates whether AI assistance leaves a temporal fingerprint in writing and programming tasks. By analyzing keystroke-level data from three corpora, the authors find that AI contributions appear in distinct bursts and that temporal patterns can almost perfectly distinguish wholesale delegation from authentic work, though ordinary collaboration remains hard to detect. The research suggests that process visibility could serve as a basis for academic integrity checks.
The paper argues that AI should be evaluated not only by principles but by concrete protocols that translate commitments into roles, requirements, records, oversight, and assessment. It introduces a rupture test linking institutional baselines to system evaluation, and distinguishes evidence‑bounded deployment from measurement‑bounded governance. The authors propose the RISE AI architecture to make bounded, evidence‑based claims about Responsibility, Inclusivity, Safety, and Empowerment, emphasizing the need for engineering, institutional repair, and ongoing moral judgment.
arXiv:2609.05677v1 Announce Type: cross Abstract: Lifelong LLM agents increasingly rely on external skill artifacts as one element for preserving and reusing capabilities over time. These skills (usu...