Backend
AuditCoder: Process-Auditable Code Generation through Responsibility-Preserving Task Graphs
arXiv cs.SE0 views
arXiv:2607.29529v2 Announce Type: replace Abstract: Plans can guide code generation without record?ing which code implements each subproblem, leaving reviewers to reconstruct these links dur?ing handoff and maintenance. We present AU?DITCODER, a multi-agent system for process?auditable code generation that jointly con?structs a program and its responsibility record. A contract-annotated task graph assigns sta?ble IDs before implementation and preserves code ownership through generation and assem?bly. The same IDs connect each planning commitment to its code, versioned check results, and repair history, supporting human inspec?tion and automated checks of record complete?ness and repair decisions. When failure evidence supports a node or branch, bounded repair declares an editable scope, records any expansion, and leaves code outside the final scope unchanged. The system abstains when no boundary is supported. On a 200-task APPS sample and ClassEval, AUDITCODER remains competitive with CodeSim across two models under a one-round feedback limit. The DeepSeek-based system also remains compet?itive on 22 exploratory cross-domain tasks. An audit of the DeepSeek APPS run finds that, averaged across tasks, 97.25% of final leaf records retain nonempty code, contract, provenance, and check fields. All 44 repair attempts follow the recorded accept/rollback policy, and 30 pass held-out tests, with scopes averaging 22% of graph nodes. Anonymous repository: https://anonymous.4open.science/r/AuditCoder/.
Source:https://arxiv.org/abs/2607.29529PreviousNo Edges, No Verdict: A Large-Scale Empirical Study of Declared Dependency Graphs in 78K SBOMs in the WildNextPosterHarness: Turning Scientific Poster Generation into an Auditable Instruction-Following Benchmark
Related posts
I read all 308 open jobs at xAI: 54% are in its data center team, and most of them are in Memphis
0dev.to AI
Claude Code marketing analytics with an app-scoped key
0dev.to AI
I red-teamed my own support bot with 30 scenarios. It failed 7 — here's the harness.
0dev.to AI
The Log That Told Everyone the Password: Redacting Secrets in n8n Execution Logs
0dev.to WebDev
Your AI Portal Isn't Ready Until a Stranger Can Recover from Failure
0dev.to WebDev
API traffic monitoring: what to track, and how to set it up for a Node API
0dev.to Security