跳到正文
研踪PaperTrail

YOUR RESEARCH, IN SIGHT

让下一篇重要论文,不再错过。

覆盖计算机全学科,以 AI 为快捷入口。关注方向、作者和关键词,把发现变成持续的研究积累。

部分采集异常
正在读取账号与研究记录…

全站更新概况

+0新增论文
+0其中 AI 相关
+1已有论文修订
+100新增 AI 导读

arXiv 最近完成扫描:2026-11-08 01:59 · 全站最近入库:2026-11-07 17:43各信源进度 →

统计口径与数据新鲜度

统计 2026-11-07 02:56 — 2026-11-08 02:56(北京时间) · 点击数字查看对应简报;AI 相关包含在新增论文内。

最近完成检查:2026-11-08 01:59最近发现新增版本:2026-11-07 17:43库内论文最新更新时间:2026-11-06 02:59

每分钟刷新已保存的数据。空检查不代表采集异常;新收录可能包含历史论文。AI 导读按新增版本计数。

17,100 已收录论文14,661 AI 相关4,056 有修订112 HF 社区发现

浏览论文库

时间范围跟随排序:版本更新、本站收录或首次发表。最新收录可能包含历史论文。部分信源异常,查看状态 →

找到 2 篇论文 · 按版本更新时间排序上轮扫描起点 2026-11-08 01:57(北京时间)
版本更新 · v3arXiv:2603.14689

Less Is Harder Than More: Proving Unnecessary Complexity

Tristan Simas

原文摘要

When can a sensor, feature, or API field be removed without changing a fixed system's decisions? We require the remaining inputs to recover its complete optimal-action set, including ties, at every admitted state. Admitting every input combination guarantees one smallest preserving set. Yet checking one deletion is coNP-complete when circuits give utilities on Boolean products, even with two actions and at most two optimal-action sets. Missing combinations permit alternative preserving sets, so an auditor must choose inputs within budget and check the chosen set. Requiring every declared reading to have a positive-probability state adds a support check. We classify choosing and checking exactly for circuit-defined Boolean models, with and without the support requirement. A unique winner after averaging hidden states can still change the original decisions. Certifying such winners requires weighted score comparisons: finding inputs within budget is $\mathsf{NP}^{(\mathsf{NP}^{\mathsf{PP}})}$-complete even with two actions and independent uniform inputs. Explicit tables admit logarithmic approximation of the minimum preserving input count; succinct Boolean products admit no polynomial-time $o(Λ/\logΛ)$ approximation in total encoded length $Λ$, unless $\mathsf P=\mathsf{NP}$. Supplied decompositions and symmetry proofs can make audits polynomial-time; discovery and validation are additional work. For a frozen digit classifier, eleven blocks suffice on held-out rows but fifteen are needed on the full product; four conflicting pairs expose the gap. Building the required response from retained inputs establishes sufficiency, not minimality. Preserve the structure that makes the dependence checkable.

cs.CC

版本更新 · v7arXiv:2601.14252

Semantic Completeness for Correct Maintenance: A Strict Hierarchy of Typing and Inheritance

Tristan Simas

原文摘要

Removing nominal types or inheritance is defended as reducing burden; cited Java and Go rationales measure no comparison. Correct maintenance minimizes outside answers and repair obligations, preserving required answers and excluding invalid states. Answers identify meanings, memberships, and required implementations. Five capacities form a strict chain. With nominal identities fixed, only multiple contract and implementation parents attain the answer-and-repair optimum on every finite declared history. Incomplete mechanisms force slop: answers restated in code or tooling. In 20 pinned multiple-inheritance Python projects, recovered implementation-class pairs grouped by source class would need outside supply: 12,880 without inheritance, 8,792 under first parents, 739 under sound one-parent optima (checked), zero with multiple parents. With provider and state carriers fixed, state-bearing rows alone force 236 outside pairs. Java and C# interface defaults supply no instance state. At least 24 of 65 size-qualified wheels among the top 150 pure-Python downloads have positive recovered gap (36.9%, 34 unscored). For distinct, independently changing implementations, the ancestry gap is the exact outside-pair minimum with one parent supplying only required pairs, even with reparenting, infinite helpers, delegation, or generators. Zero gap and one-parent contract coverage hold iff class sets nest or are disjoint. Identical records with distinct answers need the confusability graph's chromatic number of keys. Every tree-shaped growth step inserting an off-path provider strictly between ancestors forces one-parent repair. Every snapshot in our constructed history has gap zero, yet repair obligations recur each step; multiple parents add one edge per step. At fixed design costs, bans never lower optima; savings imply suboptimal unrestricted choices.

cs.IT · cs.PL