Client-approved deliverables are the only source of truth.
NORMATIVE RULE
A deliverable is official only after client approval inside the portal. All other artifacts are non-authoritative drafts.
Failure mode
- Client-approved in Slack/email - non-binding
- Multiple versions - no version authority
- No proof of client approval - no system of record
How FinalMark enforces it
- Client approval irreversibly promotes a draft to an official record
- The client-approved version is locked and timestamped
- A certification payload provides cryptographic-grade evidence
Client-certified deliverable (system of record)
Reference implementation
SYSTEM OF RECORD — CLIENT-CERTIFIED ARTIFACT
Client-certified deliverable
Q1 Brand Launch Deck
Client-approved — Version 3
Client-approved on
January 12, 2026 - 2:14 PM ET
Client-approved by
C. Mason (Client Owner)
Evidence
Certification payloadEvaluate the protocol by inspecting a client-approved deliverable.