Skip to content

Align acceptance documentation with Core 0.7 behavior #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
schchit merged 1 commit into from
Sep 27, 2026
Merged

Align acceptance documentation with Core 0.7 behavior #6

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
6 changes: 5 additions & 1 deletion HARDENING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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).
Loading