evidence over claims in software delivery
Why delivery without defensible evidence is not “done” at UNX Code — and how the acceptance ladder replaces progress bars and status narratives.
- managed network
- no fabricated news
the done problem
In high-risk work, saying work is done differs from showing it. Status meetings invent confidence; evidence archives create accountability.
UNX Code treats evidence as part of the delivery path — not an optional final report bolted on after the invoice.
acceptance is a ladder
Ready-for-evidence is a rung — not the summit.
claim
Scoped description of what was delivered — tied to agreed work
evidence
Immutable versioned artifact — edits create a new version
review
Human QA with findings — developer portal does not issue final Accept
accept
Explicit event after checks — when upload and file-check integration is connected, files pass checks before preview
in practice at UNX Code
Deliverables are versioned; history is not silently rewritten
When file-check integration is connected: pending or unsafe checks block download
QA findings are logged as events members can see
Public claims about work require evidence and wording approval
Empty published-work indexes stay empty until gates pass
what evidence is not
you get
- Artifacts that survive review and handoff
- Acceptance criteria that can be checked
- Honest empty public surfaces
you do not get
- Free-form progress percentages as contractual truth
- “Almost OK” as a delivery state
- Invented metrics or logos to fill a case-study grid
Continue with quality, developers, organizations.