pask-wire 0.2.0

SCITT-style COSE receipt library for Physical-Site Engagement Receipts: supplied-key production and verification for the wilder.pser/0.5, 0.6 and 0.7 profiles, not complete conformance
Documentation
# pask-wire

Producer and verifier for Physical-Site Engagement Receipts: SCITT-style signed
statements that record work performed by an autonomous or human-directed actor at a
regulated physical site.

This crate is the reference implementation of the wire format. It builds a canonical
payload, signs it, and implements specified processing for supported profile
identifiers. This is not complete profile certification; conformance and
assurance gaps remain documented in the repository's KNOWN-LIMITATIONS.md.

## Names and versions

Pask is the software family for working with Physical-Site Engagement Receipts (PSER).
The `wilder.pser/<version>` identifier names the profile a receipt declares; the `pask-*`
names identify software packages. Package versions, profile versions, and Internet-Draft
revision numbers are three separate things and are versioned independently. Passing this
crate's checks does not establish complete profile conformance, and it does not establish
the truth of a physical-world claim.

## Supported profile versions

| Profile | Version constant | Content-type constant | Content type |
| --- | --- | --- | --- |
| `wilder.pser/0.5` | `SPEC_VERSION` | `CONTENT_TYPE` | `application/pser+json; profile=wilder.pser/0.5` |
| `wilder.pser/0.6` | `SPEC_VERSION_06` | `CONTENT_TYPE_06` | `application/pser+json; profile=wilder.pser/0.6` |
| `wilder.pser/0.7` | `SPEC_VERSION_07` | `CONTENT_TYPE_07` | `application/pser+json; profile=wilder.pser/0.7` |

All three identifiers are accepted by `is_supported_spec` and handled by the
implemented producer and verifier checks. Crate versions describe software releases
and compatibility; they are independent of profile versions because one software
release can support more than one profile.

What the implementation does differently under `wilder.pser/0.7`, as implemented in
this crate:

- `engagement.contentDigest` is required and must be either an explicit `null` or a
  `sha256:` digest of 64 lowercase hexadecimal digits. Under 0.5 and 0.6 the member
  is rejected. A digest value is a syntactic commitment to retained content; it is
  not evidence that the content exists, was retrieved, or was checked.
- The protected header's CWT `sub` claim is a text string under 0.7 and a byte string
  under 0.5 and 0.6. A verifier applies the typing of the declared profile.
- `canonical_example_07()` emits the deterministic 0.7 example with an explicit
  `null` `contentDigest`, alongside the unchanged `canonical_example()` (0.5) and
  `canonical_example_06()` emitters.

The 0.7 content-handling modules are published under their retained API names
`proposed_constraints`, `proposed_content`, `proposed_evidence`, `proposed_recipient`
and `proposed_replay`. The `proposed_` prefix is an identifier, kept so that existing
callers keep compiling; it is not a statement about the status of the profile text.

## Specification

The profile is specified in `draft-wilder-scitt-physical-site-engage-receipt`, an
Internet-Draft published through the IETF Datatracker:
<https://datatracker.ietf.org/doc/draft-wilder-scitt-physical-site-engage-receipt/>

An Internet-Draft is a work in progress. It is not a standard, and publication does not
imply IETF endorsement.

The posted -04 figure uses `pask_wire::canonical_example_06()`. The repository's
current draft revision carries the 0.7 figure generated by
`pask_wire::canonical_example_07()`, checked by a workspace document test that runs
from a repository checkout. `pask-wire-cli canonical-example` continues to emit the
legacy 0.5 generator's output; these are distinct tests and outputs.

## Releases and evaluation

`pask-wire` 0.1.0 is the historical first release on crates.io. It implements the
0.5 and 0.6 profiles only and is not evidence of 0.7 support.

This source is prepared as `pask-wire` 0.2.0, which adds the 0.7 processing described
above. Once that exact version has been published, it installs with:

```
cargo add pask-wire@0.2.0 --features alloc
```

From a checkout, run `cargo test --locked -p pask-wire --features alloc` to
exercise allocation-dependent functionality. Without `alloc`, Cargo skips
the targets that declare that prerequisite, and crate-gated test files
contain no tests. The two examples with fallback `main` functions retain
those fallbacks. Skipped or empty targets are not executions of the
allocation-dependent assertions. Local consumers can use a path dependency
with `features = ["alloc"]`.

`#![no_std]` with `default = []`, so the example above enables `alloc` for the
producer and verifier APIs. Use `std` for standard-library integration. ECDSA
P-256 signing and verification are optional and enabled by `es256`. The minimum
supported Rust version is 1.88.

## What a receipt does and does not establish

These are distinct operations, and passing one does not imply another:

- **Supplied-key signature verification** (`verify_ed25519`, `verify_es256`) is
  implemented. Success establishes that the statement verifies under the key the
  caller supplied and that the payload passes the implemented checks for its declared
  profile. It does not establish authenticated ownership of that key by a named
  organization or actor.
- **Retained-content checks** (`proposed_content`, `proposed_evidence`,
  `proposed_recipient`, `proposed_replay`) are implemented as bounded, offline
  operations over caller-presented bytes. The replay API provides both
  single-statement and bounded chain modes; neither establishes latest or
  complete history. A matched digest or root does not authenticate the origin
  of the content, the truth of a recorded value, or the party named as its source.
- **Registration verification** (`verify_scitt_receipt`, `verify_transparent_statement`
  and the inspection APIs) is implemented offline against caller-provisioned
  Transparency Service keys only. No receipt-controlled key discovery, retrieval, or
  live service interaction is performed, and the independence of a Transparency
  Service is not established here.
- **Hardware-evidence appraisal** is not implemented. Attestation members and
  evidence digests are carried and type-checked; no vendor evidence is parsed or
  appraised, and no hardware custody is established.
- **Full PSER or SCITT conformance** is not established by this crate. The
  implemented checks are the ones listed above; the remaining gaps are recorded in
  the repository's KNOWN-LIMITATIONS.md.

None of these establish that a described event physically happened.

## License

Apache-2.0. No commercial agreement is required to use, modify, or redistribute it.