Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
10 changes: 10 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,16 @@ All notable changes to this specification are documented here.

The spec document follows [Semantic Versioning](https://semver.org/). Wire formats (Permit `v1`, `closure_v1`, `closure_v2`, chain entry `v1`) version independently and are not bumped by spec-document revisions.

## [1.4.1] — 2026-05-22

Promotes the Step 4 verifier adjudication corpus into the canonical public
verifier-claims corpus. Permit wire format `v1`, closure formats, chain entry
`v1`, claim registry `v0`, and pinned semantic artifacts are unchanged.

- Add 17 Step 4 permit-claim corpus fixtures covering signed permit-decision negatives, signed permit-revocation negatives, and scope-faithful absence adjudication negatives/edges for post-revocation dispatch initiation.
- Record dependency verdicts for bridge-record and missing-artifact absence cases so the public corpus captures both the target permit claim result and the supporting scope-state/export-scope adjudication result.
- Keep doctrine language on scope-faithful absence adjudication and avoid native non-membership overclaims.

## [1.4.0] — 2026-05-21

Adds Step 4 claim contracts for signed permit decisions, signed permit
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[![License](https://img.shields.io/github/license/keelapi/keel-permit)](LICENSE)
[![Latest release](https://img.shields.io/github/v/release/keelapi/keel-permit?label=release)](https://github.com/keelapi/keel-permit/releases)
![Spec version](https://img.shields.io/badge/spec-1.4.0-blue)
![Spec version](https://img.shields.io/badge/spec-1.4.1-blue)

A pre-execution decision record for AI agent systems. A Permit records that an action was evaluated and decided, and, for dispatched allow executions, can be bound to the final provider or tool request. A Permit JSON object alone is not self-authenticating; verification is performed from signed export artifacts and the relevant public keys or key manifest. Those artifacts are verifiable without contacting the issuer when the verifier has the signed export artifacts and relevant public keys/key manifest.

Expand All @@ -12,7 +12,7 @@ This repository contains the wire-format specification, JSON schemas, and verifi

| | |
|---|---|
| Spec document version | 1.4.0 |
| Spec document version | 1.4.1 |
| Permit wire format | `v1` |
| Closure record format | `closure_v1`, `closure_v2` |
| Chain entry hash format | `v1` |
Expand Down
Loading
Loading