loading…
Definition of done, evidence gates, QA loop, change control, and risk ownership — quality that can be defended in a record, not asserted in a status meeting.
Feeling done is not a gate.
At UNX Code, “done” means evidence exists, review happened, and acceptance is explicit — not that a progress bar moved.
Public claims about work ship only after evidence, privacy, and wording gates. Marketing pages do not invent completion rates.
Task readiness before execution — unclear work does not start quietly
When upload and file-check integration is connected: files pass checks before preview or download
QA review with logged findings — accept or reject as events
Clear acceptance criteria — “almost OK” is not a state
Change requests with reason and approval before scope shifts
Capability checks on every sensitive action — unknown = deny
Delivery description tied to scoped work — not a free-form percentage
Versioned artifact — immutable; edits create a new version
Human review path — developer portal does not issue final Accept/Reject
Finding, accept, or reject with record visible as events
After gates — ready-for-evidence ≠ final acceptance
Scope changes use formal requests, reason, and impact assessment. Silent edits via task fields are not a product path.
Evidence history stays intact. New versions carry the change forward instead of rewriting the past.
Early risk notes name dependencies and sensitive points — without fabricated probability scores.
If disruption hits, continuity desk owns replacement and handoff with logged events. Quality includes the ability to continue.
Evidence and QA are desks on the path — not a slide at the end.