Software practitioners can make sub-optimal decisions concerning requirements during gathering, documenting, prioritizing, and implementing requirements as software features or architectural design decisions -- this is captured by the metaphor `Requirements Technical Debt (RTD).' In our prior work, we developed a conceptual model to understand the quantification of RTD and support its management. In this paper, we present our perspective and the vision to apply the lens of RTD to software requirements concerning veracity, i.e., requirements related to truth, trust, authenticity, and demonstrability in software-intensive systems. Our goal is to cultivate awareness of veracity as an important concern and eventually support the management of RTD for software requirements concerning veracity, what we term as `Veracity Debt,' through its quantification.

翻译：软件从业者在需求收集、文档化、优先级排序以及将需求实现为软件功能或架构设计决策的过程中，可能做出次优决策——这一现象被“需求技术债务（RTD）”这一隐喻所捕捉。在我们先前的工作中，我们开发了一个概念模型来理解RTD的量化并支持其管理。在本文中，我们提出我们的视角与愿景，即应用RTD的视角来审视与真实性相关的软件需求，即软件密集型系统中涉及真实性、可信性、真实性与可验证性的需求。我们的目标是提升对真实性作为一个重要关注点的认识，并最终通过量化来支持管理与真实性相关的软件需求所产生的RTD，我们将其称为“真实性债务”。