PIDL v0.8.0 Release Notes¶
Release Date: 2026-10-19
This release turns a PIDL file into a walkthrough you can present. pidl generate -f viewer writes one self-contained HTML page that steps through each scenario one message at a time: the active roles and message are highlighted on the sequence diagram, a narrative explains the step, and the request and response appear beside it with their headers, bodies and decoded tokens. The page needs no server, so it can be shared as a file.
Highlights¶
- Walkthrough viewer for any PIDL protocol, with presentation controls and a 16:9 presentation mode
- Flow examples: illustrative requests, responses and decoded tokens, each citing its source
- A fully worked AAuth draft-11 example with narratives and consistent example values throughout
What's New¶
Walkthrough Viewer¶
| Area | Shows |
|---|---|
| Menu bar | Protocol name, scenario selector, theme, Present |
| Sequence card | Scenario introduction, the diagram with shared steps as labeled bands, the active step's narrative, and Overview, back, Step n / total and forward controls |
| Request and response cards | Request line, Host, headers and body; status, headers and body. Signed headers are marked; a Tokens tab decodes each token and highlights the claims the receiver checks |
Keys: → and ← step, Home and End jump, P presents on a 16:9 stage. The URL records the scenario and step. See the Walkthrough Viewer guide.
Flow Examples¶
A flow's example holds a request, a response and decoded tokens, with a source citation and a kind: draft (taken from the source, values aligned to the scenario) or derived (written from its normative text). See the specification.
Walkthrough Data¶
generate -f walkthrough-json writes the data the viewer renders: every scenario with fragments expanded, each step's example and narrative, and analyzer findings attached to the steps they concern. Use it to build other viewers.
AAuth Example¶
Every step of the five access modes and the agent token, person token and consent fragments has a narrative and an example. Values are shared throughout: one agent key whose thumbprint is the resource token's agent_jkt, one person, and one timeline within the draft's token lifetimes. The agent token step follows the web app pattern of the AAuth Bootstrap guidance.
Fixes¶
- For files with scenarios, analyzer findings from flow rules now point at the written scenario flow instead of an index into the flattened protocol.