Examples

False success, made visible.

These examples start where people already feel the problem: delivered, resolved, refund issued, confirmed, approved, safe to proceed, AI handled this.

Delivery

Delivered Is Not Proof

Signal: Delivered
Relied-upon promise: The package reached a customer-accessible place.
Missing proof: Reliable evidence that the package reached the correct place.
Betrayal: The system marks delivery complete while the customer cannot access the package.
Praxis question: What reliable capability keeps or protects the delivery promise under real conditions?

Read teardown

Support

Resolved Is Not Repaired

Signal: Resolved
Relied-upon promise: The customer's problem was fixed or honestly remains open.
Missing proof: Customer-visible evidence that the original problem no longer persists.
Betrayal: The workflow closes cleanly while the customer still has the same problem.
Praxis question: What proves repair rather than merely proving that the ticket moved states?

Read teardown

Refund approval visual used to examine money movement and proof.

Refunds

Refund Issued Is Not Refund Received

Signal: Refund issued
Relied-upon promise: The customer's money is actually moving back to an account they can use.
Missing proof: Evidence that the refund reached the customer-facing financial state.
Betrayal: Internal completion is treated as customer repair before the money arrives.
Praxis question: What keeps or protects the refund promise across every carrier in the chain?

Read teardown

Appointment confirmation visual used to examine reserved capacity.

Appointments

Confirmed Is Not Reserved

Signal: Confirmed
Relied-upon promise: A real appointment slot was held for the relying person.
Missing proof: Evidence that the slot was actually reserved in the operating system.
Betrayal: The customer organizes around a confirmation that does not survive operational reality.
Praxis question: What capability protects the reservation promise after the confirmation is sent?

Read teardown

Product promise visual used to examine AI as carrier of a promise.

AI Answered Is Not AI Resolved

Signal: AI answered
Relied-upon promise: The user received a trustworthy answer, action, escalation, or refusal.
Missing proof: Evidence that the answer was true, sufficient, owned, or escalated.
Betrayal: A fluent response carries authority before it can carry the promise.
Praxis question: What must remain evidenced, human, accountable, escalated, or repairable?

Read teardown

Operational boundary visual used to examine ownership and refusal.

Operations

Escalated Is Not Owned

Signal: Escalated
Relied-upon promise: A capable owner is now responsible for the unresolved state.
Missing proof: Evidence that a receiving owner accepted responsibility and next action.
Betrayal: The process records motion while the relying person experiences abandonment.
Praxis question: What proves that escalation became owned work rather than displaced work?

Read teardown

Authority

Approved Is Not Authorized

Signal: Approved
Relied-upon promise: Someone with the right authority accepted the request and can make the next state real.
Missing proof: Evidence that the approving carrier had authority and that downstream execution is accepted.
Betrayal: The workflow says approved while the real authority boundary has not been crossed.
Praxis question: What proves that approval became authorized action rather than a label?

Read teardown

Safety

Safe To Proceed Is Not Evidenced

Signal: Safe to proceed
Relied-upon promise: The relying person can proceed without accepting hidden, unreviewed risk.
Missing proof: Traceable evidence that the relevant checks were performed and still apply.
Betrayal: The product presents safety while the evidence state remains incomplete or stale.
Praxis question: What evidence must exist before the product may say safe to proceed?

Read teardown

Product promise visual used to examine AI ownership.

AI Handled This Is Not Owned

Signal: AI handled this
Relied-upon promise: The request was resolved, refused, escalated, or left in an owned unresolved state.
Missing proof: Evidence that the answer, action, or handoff was owned and repairable.
Betrayal: Automation records handling while the relying person is left without accountable repair.
Praxis question: What proves AI handling became accountable resolution, valid refusal, or owned escalation?

Read teardown

Run the 2-minute review Use it with a team

Apply it

Run the same diagnostic on your own signal.

Start with the label your product shows. Then ask what promise someone relied on, what evidence would matter, and what would make the product look successful while the promise failed.

Start with one signal Open the older case library