Working definition
What is decision debt in software engineering?
Decision debt is the accumulated cost of engineering decisions that cannot be reliably reconstructed, connected to implementation or verified against the release they shaped.
Technical debt affects the system. Decision debt affects the explanation.
Technical debt usually describes the future cost created by shortcuts, complexity or deferred maintenance in software. Decision debt is different. It appears when a team loses the evidence required to explain what was decided, who authorized it, what was built and why a release was accepted.
The system may continue to work while the ability to explain and verify it steadily disappears.
How decision debt accumulates.
Requirements separate from delivery
The requirement changes, but the implementation record does not show which version governed the work.
Decisions remain conversational
The final choice exists in meetings or messages without an explicit owner, boundary or rationale.
Evidence loses its subject
Tests pass, but the result is no longer bound to the exact change and release it is supposed to support.
The questions a healthy record should answer.
- What requirement governed the change?
- Which technical decision was selected?
- Who had authority to approve it?
- What implementation fulfilled the decision?
- Which evidence verified the result?
- Why was the release accepted or rejected?
Reducing decision debt requires connection, not more documents.
A new document does not solve the problem if it becomes another detached artifact. The useful unit is a connected engineering record: requirements, decisions, human authorization, implementation and verification evidence preserved as one inspectable chain.
VESOS is being developed around that chain. The current work tests whether a bounded change can remain explainable from initial framing to publication decision without overstating the maturity of the wider platform.