mlsanityData to 14 Oct 2026

SLEAN: Simple Lightweight Ensemble Analysis Network for Multi-Provider LLM Coordination: Design, Implementation, and Vibe Coding Bug Investigation Case Study

arXiv 2510.10010 ↗First posted 11 Oct 2025cs.SE cs.AIcited by 0

Not on the map. Why?

Abstract (arXiv)

We present SLEAN (Simple Lightweight Ensemble Analysis Network), a deterministic framework for coordinating multiple LLM providers through text-based prompt orchestration. Unlike complex multi-agent systems requiring specialized infrastructure, SLEAN operates as a simple prompt bridge between LLMs using .txt templates, requiring no deep technical knowledge for deployment. The three-phase protocol formed by independent analysis, cross-critique, and arbitration, filters harmful AI-generated code suggestions before production deployment, addressing how AI-assisted debugging increasingly produces modifications that introduce unnecessary complexity, break existing functionality, or address problems. Evaluating 15 software bugs, we analyzed 69 AI-generated fix propositions. SLEAN's filtering accepted 22 fixes (31.9%, 95% CI 20.9-42.9%) while rejecting 47 that would have been harmful if applied verbatim. The arbitration process reduced code change surface by 83-90% relative to raw AI outputs, enforcing minimal causal edits over scope-expanding modifications. Minimal Type 2 inputs proved more efficient than detailed Type 1 inputs, requiring 2.85 versus 3.56 propositions per accepted fix (35.1% versus 28.1% acceptance, about a 20% efficiency gain). Agreement between AI systems showed weak correlation with fix quality: high convergence (at least 80%) occurred in 4 of 15 cases and improved acceptance by only 2.4% points; arbitration appeared only at exactly 10% convergence in 2 of 15 cases, although low convergence alone did not necessitate arbitration. The file-driven, provider-agnostic architecture enables deployment without specialized coding expertise, making it applicable to security auditing, code review, document verification, and other domains requiring reliable multi-provider synthesis with end-to-end auditability.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 20 of its 34 references that are in the map. First posted on arXiv 11 Oct 2025.

Builds on

20 of 34 references.

References · 20

  1. 2016"Why Should I Trust You?": Explaining the Predictions of Any Classifiercited by 5,070
  2. 2023Voyager: An Open-Ended Embodied Agent with Large Language Modelscited by 2,191
  3. 2023AutoGen: Enabling Next-Gen LLM Applications via Multi-Agent Conversationcited by 1,988
  4. 2023MetaGPT: Meta Programming for A Multi-Agent Collaborative Frameworkcited by 1,808
  5. 2023CAMEL: Communicative Agents for "Mind" Exploration of Large Language Model Societycited by 1,395
  6. 2018Model Cards for Model Reportingcited by 1,080
  7. 2023ChatDev: Communicative Agents for Software Developmentcited by 919
  8. 2023Graph of Thoughts: Solving Elaborate Problems with Large Language Modelscited by 886
  9. 2024Large Language Model based Multi-Agents: A Survey of Progress and Challengescited by 769
  10. 2023AutoAgents: A Framework for Automatic Agent Generationcited by 216
  11. 2020Towards Accountability for Machine Learning Datasets: Practices from Software Engineering and Infrastructurecited by 138
  12. 2023Keep the Conversation Going: Fixing 162 out of 337 bugs for 0.42 each using ChatGPTcited by 125
8 more
  1. 2022Repair Is Nearly Generation: Multilingual Program Repair with LLMscited by 68
  2. 2025Interactive Debugging and Steering of Multi-Agent AI Systemscited by 68
  3. 2023Large Language Models for Test-Free Fault Localizationcited by 67
  4. 2024ThinkRepair: Self-Directed Automated Program Repaircited by 23
  5. 2023The Pipeline for the Continuous Development of Artificial Intelligence Models -- Current State of Research and Practicecited by 14
  6. 2025Accountability in Code Review: The Role of Intrinsic Drivers and the Impact of LLMscited by 8
  7. 2021Reproducible Builds: Increasing the Integrity of Software Supply Chainscited by 7
  8. 2020Provenance Graph Kernelcited by 1

Built on by

Not cited yet.