Beyond the Agent Harness: Boundary Criteria for Software-Factory Orchestration - A Single-Operator Case Study
cs.SE
Submitted: 2026-11-03
Updated: 2026-11-03
Code: https://github.com/strongdm/attractor
Terminology
Sources
- What makes a harness a harness: necessary and sufficient conditions for an agent harness
- Proof-or-Stop: Don't Trust the Agent, Trust the Evidence -- Loop Engineering for Verifiable Evidence-Gated Lifecycle Control
- ReAct: Synergizing Reasoning and Acting in Language Models
- SWE-agent: Agent-Computer Interfaces Enable Automated Software Engineering
- SWE-bench: Can Language Models Resolve Real-World GitHub Issues?
- OpenHands: An Open Platform for AI Software Developers as Generalist Agents
- From Failed Trajectories to Reliable LLM Agents: Diagnosing and Repairing Harness Flaws
- Judging LLM-as-a-Judge with MT-Bench and Chatbot Arena
- Harness-of-Harness: Multi-Day Autonomous Software Development with Continual Improvement
- Meta-Engineering Harnesses for AI-Native Software Production: A Contract-Driven Adversarial Verification Architecture with Early Deployment Report
Related papers
- ArkEval: Benchmarking and Evaluating Automated CodeRepair for ArkTS
- TestPrism: Rethinking Test Evaluation Beyond a Single Reference
- Mining Workflow Graphs for Black-Box Boundary Testing of Conversational LLM Agents
- Falsification-Based Verification of LLM-Generated Optimization Models: Sound Test Batteries and Their Detection Limits
- GitSkills: A Dataset of Agent Skills on GitHub
- For Coding Agents, the Repository Matters