From 6e77972df0748f9e5af97847eb065b4077d4d9a0 Mon Sep 17 00:00:00 2001
From: Yuqiang Wang <10815391+schchit@users.noreply.github.com>
Date: Wed, 30 Sep 2026 18:08:29 -0500
Subject: [PATCH] docs: simplify current usage and make examples easier to
 follow

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

diff --git a/README.md b/README.md
index a1c05ab..cf2329e 100644
--- a/README.md
+++ b/README.md
@@ -3,17 +3,6 @@
 Command-line client for creating and verifying current JEP Core 0.7 events
 through the JEP API.
 
-Default endpoints:
-
-```text
-POST /v0.7/events/create
-POST /v0.7/events/verify
-GET  /health
-```
-
-Historical pre-0.7 handling is explicit through `--legacy`; the CLI never
-retries a failed 0.7 event with a legacy decoder.
-
 ## Status
 
 Experimental HTTP client. Event creation and verification run on the configured
@@ -41,9 +30,12 @@ Judgment:
 jep create \
   --verb J \
   --who did:example:agent-789 \
-  --what '{"claim":"approve","subject":"demo"}'
+  --what '{"claim":"approve","subject":"demo"}' > response.json
+jep extract-event response.json > event.json
 ```
 
+`event.json` contains the signed event used by the verification command below.
+
 Delegation:
 
 ```bash
@@ -63,8 +55,8 @@ Pass a typed reference as JSON when the target is another JEP event.
 jep verify event.json --mode archival
 ```
 
-0.7 validation returns `status` plus independent `checks`, not a cumulative
-Validation Level.
+Validation returns `status` and independent `checks`. Look for `status: "valid"`
+and `checks.cryptographic: "pass"` for the sample event.
 
 ## Explicit legacy verification