From 551669fe17a088cbd715d70fefe4822d0fb099e3 Mon Sep 17 00:00:00 2001
From: Yuqiang Wang <10815391+schchit@users.noreply.github.com>
Date: Sat, 26 Sep 2026 20:17:02 -0500
Subject: [PATCH] docs: Align acceptance documentation with Core 0.7 behavior

---
 CONTRIBUTING.md | 2 +-
 HARDENING.md    | 6 +++++-
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5ef5d6e..10c9477 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -16,6 +16,6 @@ python -m pytest -q
 jep --help
 ```
 
-Keep each pull request focused. Test changed behavior and update CLI documentation. The command is `jep`; `jep-agent` and `jep-runtime` belong to separate packages. Protocol requirements stay in [Core](https://github.com/hjs-spec/jep-core).
+Keep each pull request focused. Test changed behavior and update CLI documentation. The command is `jep`; `jep-agent` belongs to the separate local Agent SDK. `jep-runtime` is a retired experiment, retained for historical reproduction. Follow the [repository directory](https://github.com/hjs-spec/.github/blob/main/PROJECTS.md) for maintenance ownership. Protocol requirements stay in [Core](https://github.com/hjs-spec/jep-core).
 
 Contact: signal@humanjudgment.org.
diff --git a/HARDENING.md b/HARDENING.md
index 7906354..0abe1f4 100644
--- a/HARDENING.md
+++ b/HARDENING.md
@@ -1,3 +1,7 @@
 # Acceptance context and exit status
 
-`jep verify --mode acceptance` requires `--expected-audience`. The value is forwarded to the API and negative verification exits with status 2. Malformed input/transport errors exit with status 1. `--ref` accepts either a digest or a JSON reference descriptor. All verification assurance comes from the configured API; the CLI does not perform local cryptographic verification.
+Current Core 0.7 verification forwards `--mode archival` or `--mode acceptance` to the API. `--expected-audience` and `--max-age-seconds` are optional profile checks; acceptance alone does not require them or a Core nonce. The API owns idempotent acceptance by Event Identity `(who,id)`.
+
+Verification exits with status 0 only when the API reports `status: valid`; invalid or indeterminate results exit with status 2. Input/transport errors handled by the CLI exit with status 1. `--ref` accepts either a digest or a JSON reference descriptor. All verification assurance comes from the configured API; the CLI does not perform local cryptographic verification.
+
+`--legacy` selects the historical verifier explicitly and uses its `valid` result. It is an archival compatibility path, not a fallback after current validation fails. See [current commands](README.md#verify).