Frontend
Architectural Debt Enforcement under Incomplete Observation: A Controlled Study of Ratchets and Evidence Qualification
arXiv cs.SE0 views
arXiv:2610.41276v1 Announce Type: new Abstract: Architectural debt gates must distinguish an allowed change from an incompletely observed one. We study a decision contract separating observation qualification, prohibited relation identity, inherited debt and authorized baseline updates. Across 240 fixed files from four repositories, the current observer and programmatic reference jointly qualify 166 files (69.17%), all with exact reference-relative edge agreement; 74 remain reference-UNKNOWN. Coverage varies from 13/60 to 59/60 by repository. On 480 constructed state scenarios sharing 60 source anchors, both the candidate ratchet and mature dependency-cruiser baseline match every expected outcome, whereas static and count-only baselines match 420 and 360. These results do not establish candidate superiority. Preserved failures include nine additional false-PASS probes and 120 unqualified full-tree timing attempts. A subsequent generic binding layer rejects 54 specified mismatches, accepts 54 current controls and permits legal repetition. Two bounded package scopes support 40 scenarios and 48 fresh-process functional checks; their costs remain tied to the measured implementations. Diagnostics explain residual uncertainty through type/runtime relations, installation context and generated-artifact provenance. TypeScript 5.9.3 and 6.0.2 yield identical outputs on ten paired emission witnesses, but neither that agreement nor verified release provenance changes the frozen UNKNOWN labels. The contribution is a controlled account of evidence-qualified enforcement and its limits, not language completeness, natural maintenance effectiveness or a new shrinking-baseline algorithm.
Source:https://arxiv.org/abs/2610.41276PreviousYesterday's Code, Today's Dependencies: How Dependency Selection Shapes PHP Migration BenchmarksNextWhat Does a Repair Agent Gain from Remembering Its Failure? An Exploratory Study on Real Python Bugs
Related posts
Trailing slashes in a static Astro site on Vercel: five layers and a check that never failed
0dev.to
Try four admin templates before you install one
0dev.to
I scanned the GitHub Actions setup of 139 popular JS/TS repos. Only 1 passed 3 basic checks.
0dev.to GitHub
Power BI for Beginners: 5 Essential Concepts You Should Know
0dev.to Data
Per-Author Comment Macros for Co-Authors in LaTeX
0dev.to Productivity
How Singers Use iPhone Notes to Track Vocal Development and Performance Insights
0dev.to Productivity