From f797231e04532440c8376f97fea405a579091512 Mon Sep 17 00:00:00 2001
From: Sarmad Tawfeek <125739417+SamCT86@users.noreply.github.com>
Date: Sat, 3 Oct 2026 17:37:23 +0200
Subject: [PATCH 1/2] docs: add buyer-first reliability context

---
 README.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/README.md b/README.md
index d41fe5e..8d4da6f 100644
--- a/README.md
+++ b/README.md
@@ -10,6 +10,20 @@ I use this public reference to make the safer pattern executable and easy to ins
 
 The production system remains private. This repository uses synthetic state only.
 
+## Why a buyer or CTO should care
+
+This is a small reliability proof for systems that let software agents or automation mutate something outside themselves. The risk is not theoretical: when transport acknowledgement is ambiguous, a blind retry can duplicate a payment, deployment, write, job, message or other side effect.
+
+The concrete pattern demonstrated here is:
+
+1. know the state the action was allowed to start from;
+2. bind evidence to the exact task + attempt;
+3. read the external state after an ambiguous result;
+4. keep `UNKNOWN` when reality is not yet established;
+5. retry only when the observed state makes retry safe.
+
+If you are evaluating whether this approach fits a real AI/automation workflow, inspect the tests first and then use the [portfolio](https://sarmadtawfeek.se) or [email](mailto:sarmadtawfeek@gmail.com) for a concrete technical discussion. This public reference is engineering evidence, not a claim of customer adoption or ROI.
+
 ## Try it
 
 ```bash

From e650d514d8f6dd4676d3b5a20c6da9a191a3c15b Mon Sep 17 00:00:00 2001
From: Sarmad Tawfeek <125739417+SamCT86@users.noreply.github.com>
Date: Sat, 3 Oct 2026 17:40:02 +0200
Subject: [PATCH 2/2] docs: tighten buyer risk claim

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 8d4da6f..118bf5f 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ The production system remains private. This repository uses synthetic state only
 
 ## Why a buyer or CTO should care
 
-This is a small reliability proof for systems that let software agents or automation mutate something outside themselves. The risk is not theoretical: when transport acknowledgement is ambiguous, a blind retry can duplicate a payment, deployment, write, job, message or other side effect.
+This is a small reliability proof for systems that let software agents or automation mutate something outside themselves. When a mutation can succeed before its acknowledgement returns, a blind retry can duplicate a payment, deployment, write, job, message or other side effect.
 
 The concrete pattern demonstrated here is: