CONTENT PATTERNS / LIVE COPY

Words for systems that might be wrong.

Extracted from the running portfolio and interface lab. Each pattern reduces ambiguity at a specific moment.

01 / Action
Review the work

Starts with a verb and names the value, not the UI object.

02 / Progress
Retrieving evidence · 2.4s

Names what is happening and exposes elapsed time.

03 / Source
Source attached · native case study

Keeps provenance beside the claim.

04 / Limit
Published case-study claim; not independently verified.

States the exact boundary without legal padding.

05 / Approval
Approve with label

Says what approval changes.

06 / Failure
No matching command

Plain empty state; no blame.

07 / Escalation
Stop before action

Makes the safe boundary explicit.

08 / Recovery
Show the unresolved choice to a person with the evidence already gathered.

Preserves work and names the next move.

09 / Privacy
Nothing here is inferred about you beyond this link.

Explains personalization at the moment it matters.

WRITING RULES

Name the action, not the button.

Put the source beside the claim.

Say what is uncertain and what happens next.

Use a number only when its provenance is visible.

Never make the interface sound more capable than the system.

End when the user can act.