@agent-blueprint-protocol/verifier 1.0.1 → 1.1.0-rc.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (48) hide show
  1. package/CHANGELOG.md +226 -194
  2. package/README.md +36 -15
  3. package/dist/examples/echo-blueprint.json +1 -0
  4. package/dist/examples/echo-deployment.json +1 -0
  5. package/dist/examples/extension-blueprint.json +1 -0
  6. package/dist/examples/federation-envelope.json +1 -0
  7. package/dist/examples/signed-blueprint.json +1 -0
  8. package/dist/release-history.json +1 -1
  9. package/dist/release-metadata.json +1 -1
  10. package/dist/spec/FOUNDATION-TRANSITION.md +9 -17
  11. package/dist/spec/IPR.md +1 -1
  12. package/dist/spec/README.md +2 -2
  13. package/dist/spec/conformance/runner.md +2 -2
  14. package/dist/spec/errata.md +1 -1
  15. package/dist/spec/grammar/blueprint.cddl +1 -1
  16. package/dist/spec/grammar/deployment.cddl +5 -3
  17. package/dist/spec/grammar/derived/deployment.schema.json +34 -21
  18. package/dist/spec/grammar/taskenvelope.cddl +1 -1
  19. package/dist/spec/protocol.md +86 -93
  20. package/dist/verifier/b64url.js +1 -1
  21. package/dist/verifier/blueprint.d.ts +17 -0
  22. package/dist/verifier/blueprint.js +12 -4
  23. package/dist/verifier/bounds.js +1 -1
  24. package/dist/verifier/bounds_algebra.js +1 -1
  25. package/dist/verifier/canonical.js +3 -3
  26. package/dist/verifier/cli.js +5 -5
  27. package/dist/verifier/compatibility.js +2 -2
  28. package/dist/verifier/corpus.js +2 -2
  29. package/dist/verifier/decode.js +4 -4
  30. package/dist/verifier/deployment.d.ts +17 -0
  31. package/dist/verifier/deployment.js +12 -4
  32. package/dist/verifier/digest.js +1 -1
  33. package/dist/verifier/extension.js +2 -2
  34. package/dist/verifier/facade.d.ts +6 -0
  35. package/dist/verifier/facade.js +6 -0
  36. package/dist/verifier/federation.d.ts +17 -0
  37. package/dist/verifier/federation.js +11 -3
  38. package/dist/verifier/mapping.d.ts +10 -10
  39. package/dist/verifier/mapping.js +1 -1
  40. package/dist/verifier/negotiation.js +4 -4
  41. package/dist/verifier/portability.js +2 -2
  42. package/dist/verifier/registry.js +1 -1
  43. package/dist/verifier/report.js +1 -1
  44. package/dist/verifier/runner.js +2 -2
  45. package/dist/verifier/schema.js +4 -4
  46. package/dist/verifier/signature.js +6 -6
  47. package/dist/verifier/value.js +3 -3
  48. package/package.json +3 -2
package/CHANGELOG.md CHANGED
@@ -2,7 +2,65 @@
2
2
 
3
3
  All notable public changes to `agent_blueprint_protocol` are documented here.
4
4
 
5
- ## [1.0.1] — 2026-11-12
5
+ ## [1.1.0-rc.2] - 2026-11-15
6
+
7
+ ### Fixed
8
+
9
+ A release run now fails while a registry approval is pending. The npm live
10
+ check and the Hex live check each end the run with an error naming the
11
+ pending version, so Hex, the source release and the post-publication checks
12
+ never appear as skipped jobs under a green run. A rerun on the same tag after
13
+ approval resumes as before. The 1.1.0-rc.1 tag was never published; this
14
+ candidate supersedes it.
15
+
16
+ The release-candidate check confirms every replanted mutation's anchor before
17
+ it replants any, and names every stale anchor at once.
18
+
19
+ Library and verifier behavior, the protocol revision, the verification-semantics
20
+ version (3), the corpus, the registry and the specification are unchanged from
21
+ 1.1.0-rc.1. The corpus contains 626 cases, digest
22
+ `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`; the registry digest is
23
+ `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the specification digest
24
+ is `sha-256:GgsMn83Cm0ZjYecBGwiwUy4bqwcKW3zfDzkRQ87yHsw`.
25
+
26
+ ## [1.1.0-rc.1] - 2026-11-15
27
+
28
+ ### Added
29
+
30
+ Adds revision-specific member vocabularies for Blueprint Core (18), Deployment
31
+ Manifest (19), and Federation TaskEnvelope (23) in Elixir and TypeScript, read
32
+ from their decoder tables. Unsupported integer revisions and invalid types
33
+ return the same typed refusals in both implementations.
34
+
35
+ Examples ship as installed application resources. Notebooks, module doctests,
36
+ README and guide snippets, and npm examples run against real package archives
37
+ outside the checkout; every release run repeats those gates against the
38
+ published registry packages. Documentation links pin this release, HexDocs extras resolve
39
+ to rendered pages, and the public ExDoc footer remains enabled.
40
+
41
+ A shipped-text gate rejects em dashes and en dashes in packaged documents,
42
+ source inputs, generated kit text, site files, issue templates, and the
43
+ release title and notes.
44
+
45
+ New design records cover release publication, documentation executed from
46
+ the package, the runtime boundary, the single continuous integration
47
+ workflow, artifact portability, and extraction of the normative tree. The
48
+ producer surface record gains the member introspection amendment.
49
+
50
+ ### Changed
51
+
52
+ All dated changelog headings use `## [x.y.z] - YYYY-MM-DD`.
53
+
54
+ Security maintenance moves from 1.0.x to 1.1.x. Consumers on 1.0.x should upgrade to 1.1.x; the 0.8 transition line remains supported.
55
+
56
+ ### Compatibility
57
+
58
+ Protocol revision 1 and verification-semantics version 3 are unchanged. The corpus
59
+ contains 626 cases, digest `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`;
60
+ the registry digest is `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`.
61
+ Verification behavior is unchanged. Specification edits correct producer digest insertion instructions, clarify the two valid `as_of` policies, make the foundation inventory self-contained, and repair links and wording. The Deployment grammar and derived JSON Schema now accept exactly `none` with a null age or `required` with a positive integer age in milliseconds, matching both implementations.
62
+
63
+ ## [1.0.1] - 2026-11-12
6
64
 
7
65
  Promotes 1.0.1-rc.1 without changes. The specification's licensing note is
8
66
  simplified to the Apache-2.0 license, the Developer Certificate of Origin
@@ -13,7 +71,7 @@ contains 626 cases, digest `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`
13
71
  `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the specification digest is
14
72
  `sha-256:9hm2GIG5FVX4-gGMFeJpVJfK3GMTi1TeePRopSF0r7w`.
15
73
 
16
- ## [1.0.1-rc.1] — 2026-11-12
74
+ ## [1.0.1-rc.1] - 2026-11-12
17
75
 
18
76
  The specification's licensing note is simplified to the Apache-2.0 license, the Developer Certificate of Origin sign-off and copyright.
19
77
  The npm README now ships the installed-package walkthrough.
@@ -21,7 +79,7 @@ Library and verifier behavior are unchanged. The corpus contains 626 cases,
21
79
  digest `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`; the registry digest is `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`;
22
80
  the specification digest is `sha-256:9hm2GIG5FVX4-gGMFeJpVJfK3GMTi1TeePRopSF0r7w`.
23
81
 
24
- ## [1.0.0] — 2026-11-11
82
+ ## [1.0.0] - 2026-11-11
25
83
 
26
84
  The 1.0 release of the Agent Blueprint Protocol. It promotes 1.0.0-rc.3
27
85
  without changes: library and verifier behavior, the protocol revision,
@@ -31,7 +89,7 @@ digest `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`; the registry
31
89
  digest is `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the
32
90
  specification digest is `sha-256:jh2uy3FU7ApQmFtPHHK3YY041sDgWrICmS8Hz-LaAGE`.
33
91
 
34
- ## [1.0.0-rc.3] — 2026-11-11
92
+ ## [1.0.0-rc.3] - 2026-11-11
35
93
 
36
94
  The specification no longer names a candidate version in its text, so
37
95
  the 1.0 specification is final as written. A documentation test now
@@ -42,7 +100,7 @@ and the registry are unchanged from 1.0.0-rc.2. The corpus contains
42
100
  626 cases, digest `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`; the registry digest is `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the specification digest
43
101
  is `sha-256:jh2uy3FU7ApQmFtPHHK3YY041sDgWrICmS8Hz-LaAGE`.
44
102
 
45
- ## [1.0.0-rc.2] — 2026-11-11
103
+ ## [1.0.0-rc.2] - 2026-11-11
46
104
 
47
105
  Documentation corrections cover the README, npm package README, guides, Livebooks, and site. The npm package description states the verifier's checks.
48
106
  The unused TypeScript `Context` type is no longer exported; no exported function
@@ -75,10 +133,10 @@ The corpus contains 626 cases, including 22 new host lifecycle and schema-pin
75
133
  cases. Its digest is `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`;
76
134
  the registry digest is `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`.
77
135
 
78
- The obsolete `verifier/RUNNER.md` redirect is removed from the repository and
136
+ The obsolete verifier runner redirect is removed from the repository and
79
137
  the standalone archive. The runner contract is `spec/conformance/runner.md`.
80
138
 
81
- ## [1.0.0-rc.1] — 2026-11-11
139
+ ## [1.0.0-rc.1] - 2026-11-11
82
140
 
83
141
  ### Breaking
84
142
 
@@ -181,7 +239,7 @@ Prior released verdicts remain equivalent. The
181
239
  `negotiation-estate-contract-valid` case now projects the
182
240
  `extension_deprecated` notice for the legacy federation namespace.
183
241
 
184
- ## [0.8.4] — 2026-11-10
242
+ ## [0.8.4] - 2026-11-10
185
243
 
186
244
  ### Fixed
187
245
 
@@ -215,9 +273,9 @@ The corpus contains 199 cases, digest
215
273
  `sha-256:YfVuNANOdTyQD2rXtXPbonyguVQBCZQheb9WCv4DR8E`. Protocol revision and
216
274
  `verification_semantics_version` remain 1.
217
275
 
218
- ## [0.8.3] — 2026-11-10
276
+ ## [0.8.3] - 2026-11-10
219
277
 
220
- ### Fixed — security
278
+ ### Fixed: security
221
279
 
222
280
  - Hostile JSON containing lone surrogate escapes or malformed Unicode escapes
223
281
  could raise an exception in the Elixir decoder. Every decode surface now
@@ -242,9 +300,9 @@ The corpus contains 190 cases, digest
242
300
  `sha-256:UDRV0o-JUWvHBZPiODetlEQYHALStnIOlWI4qZKxUcc`. Protocol revision and
243
301
  `verification_semantics_version` remain 1.
244
302
 
245
- ## [0.8.2] — 2026-11-05
303
+ ## [0.8.2] - 2026-11-05
246
304
 
247
- ### Fixed — documentation
305
+ ### Fixed: documentation
248
306
 
249
307
  - Correction to an earlier entry: bare `npx agent-blueprint-protocol` and
250
308
  `npx verifier` work only where `@agent-blueprint-protocol/verifier` is
@@ -253,7 +311,7 @@ The corpus contains 190 cases, digest
253
311
  - The post-publish check runs `npx --no-install verifier`, so it can never
254
312
  fetch the unrelated npm package named `verifier`.
255
313
 
256
- ### Added — documentation
314
+ ### Added: documentation
257
315
 
258
316
  - A Livebook walkthrough, `docs/livebooks/abp-walkthrough.livemd`,
259
317
  shipped in the package and on HexDocs. It installs the package from
@@ -270,7 +328,7 @@ The corpus contains 190 cases, digest
270
328
  quality step, `mix typescript.guide`, which the doc-gates workflow also
271
329
  runs.
272
330
 
273
- ### Changed — documentation
331
+ ### Changed: documentation
274
332
 
275
333
  - The CI workflows' GitHub Action pins move with their dependabot bumps
276
334
  (`actions/setup-node` v7.1.0, `actions/upload-pages-artifact` v5.0.0,
@@ -323,7 +381,7 @@ coverage. Corpus: 129 cases, digest
323
381
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
324
382
  digest `sha-256:aBgeih79woOR7YmJ_OBhyFgKU0j2euO-eieJKxLVDeA`.
325
383
 
326
- ## [0.8.1] — 2026-10-14
384
+ ## [0.8.1] - 2026-10-14
327
385
 
328
386
  ### Fixed
329
387
 
@@ -346,12 +404,11 @@ digest `sha-256:aBgeih79woOR7YmJ_OBhyFgKU0j2euO-eieJKxLVDeA`.
346
404
  public key) is bounded at 256 entries, evicting the oldest; it grew
347
405
  without limit before.
348
406
  - The npm tarball no longer ships `dist/verifier/self_checks.*`: the
349
- repo-side self-check battery reads `verifier/testdata/`, which never
350
- shipped, so the packed copy could not run. The kit's documented
407
+ repository self-check battery reads test data that never shipped, so the packed copy could not run. The kit's documented
351
408
  commands (the bin over the embedded corpus, `--corpus`, `--artifact`,
352
409
  and the importable modules) are unchanged.
353
410
 
354
- ### Changed — corpus and specification
411
+ ### Changed: corpus and specification
355
412
 
356
413
  - The conformance corpus grows from 96 to 129 cases, all on
357
414
  `signature.verify`. Signature-rule cases: R = the identity with
@@ -392,21 +449,21 @@ tests (63 properties) at 100% coverage. Corpus: 129 cases, digest
392
449
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
393
450
  digest `sha-256:CsVC7jVvA2ZP0NA6D5_h94A_ryb6F795h7ZpSo66CBA`.
394
451
 
395
- ## [0.8.0] — 2026-09-24
452
+ ## [0.8.0] - 2026-09-24
396
453
 
397
- ### Added — the release-identity consumer contract
454
+ ### Added: the release-identity consumer contract
398
455
 
399
456
  - `priv/release-metadata.json` is now a versioned public contract
400
457
  (`manifest_version: 2`; additive-only within a version). New fields:
401
458
  the manifest version, `verification_semantics_version` (the
402
- semantics/census split — unchanged at 1), the `digest_identity` label
403
- (RFC 8785 JCS + SHA-256 + domain separation + unpadded base64url —
459
+ semantics/census split, unchanged at 1), the `digest_identity` label
460
+ (RFC 8785 JCS + SHA-256 + domain separation + unpadded base64url,
404
461
  unchanged across every release), `protocol_revisions_supported`, the
405
462
  certified compatibility matrix `prior_census_verdicts` (the prior
406
463
  census `sha-256:sg6Fo7…` is certified `equivalent` by replay), and
407
- the verifier-kit identity derived from `package.json`. The npm kit
464
+ the verifier-kit identity derived from the npm package metadata. The npm kit
408
465
  embeds the manifest byte-identically (agreement-gated).
409
- - `priv/release-history.json`: the append-only retroactive mapping —
466
+ - `priv/release-history.json`: the append-only retroactive mapping:
410
467
  one row per manifest-era release, every PRIOR release's row verified
411
468
  against derived state (the corpus digest recomputed from the loaded
412
469
  census bytes, the registry digest from the census index, the
@@ -418,10 +475,10 @@ digest `sha-256:CsVC7jVvA2ZP0NA6D5_h94A_ryb6F795h7ZpSo66CBA`.
418
475
  this release's gate re-establishes it mechanically on every run), so
419
476
  exact-pinned consumers upgrading between any of these releases keep
420
477
  historical replays green when they bind the semantics identity. The record also shows the specification
421
- digest moved at 0.4.0 and 0.4.1 — movement the changelog prose of
478
+ digest moved at 0.4.0 and 0.4.1: movement the changelog prose of
422
479
  those releases never stated.
423
480
  - `mix compatibility.replay` (quality battery): certifies the
424
- compatibility claims and the history from live repository state —
481
+ compatibility claims and the history from live repository state,
425
482
  every manifest-era census loads through the new prior-census loader
426
483
  mode and replays under the current Runner (each PRIOR census also
427
484
  through the TS verifier, byte-compared; the current census's TS
@@ -434,34 +491,32 @@ digest `sha-256:CsVC7jVvA2ZP0NA6D5_h94A_ryb6F795h7ZpSo66CBA`.
434
491
  a self-contradictory `not_equivalent` claim), a tampered census file,
435
492
  a tampered history row, and both tag-absent refusal arms. The prior-census loader mode
436
493
  (`Corpus.load_prior_census/1`, mirrored in the TS verifier's
437
- `--prior-corpus`) suspends exactly the two current-state couplings —
438
- the compiled registry digest and the compiled applicability floor —
494
+ `--prior-corpus`) suspends exactly the two current-state couplings
495
+ (the compiled registry digest and the compiled applicability floor)
439
496
  because a released census was certified against the registry and
440
497
  floor of its release; the ordinary loader's couplings are unchanged
441
498
  and correct for conformance runs.
442
499
  - The Evolution clause gains the normative semantics/census law and the
443
500
  immutability policy (released identities are never edited in place;
444
501
  corrections are new releases); the upgrading guide gains the
445
- exact-pinned consumer partition — replay identity versus provenance
446
- metadata — and the fail-closed enumeration guidance; the decision
502
+ exact-pinned consumer partition (replay identity versus provenance
503
+ metadata) and the fail-closed enumeration guidance; the decision
447
504
  record `docs/adr/release-identity-semantics.md` ships with the
448
505
  `no-versioning-rule` axis amendment (precedence: the wire revision,
449
506
  the semantics version, and the release identity are independent
450
507
  axes). Answering an inbound consumer request for input
451
508
  (an exact-pinned consumer, 2026-09-23) in full.
452
- - `docs/consumer-evidence.md` (repository-level, deliberately NOT
453
- shipped): the unverified third-party consumer-rehearsal lane, its
454
- first entry reserved for an exact-pinned consumer's rehearsal.
509
+ - Consumer-rehearsal evidence remains separate from implementation conformance; no independent consumer-rehearsal evidence is included in this release.
455
510
 
456
511
  The correction the record now states plainly: the 0.6.0 corpus change
457
- was not purely additive at the byte level — the golden vectors' fixture
512
+ was not purely additive at the byte level; the golden vectors' fixture
458
513
  signature rotated on unchanged covered bytes (`content_digest`
459
514
  identical), verdict-neutral and replay-proven, but the 0.6.0 entry's
460
515
  "grows 94 → 96" prose under-recorded it.
461
516
 
462
517
  The public-history privacy scan's budget grows with the repository
463
518
  (the scan is O(tracked files × commits)); its ceiling moves 960s →
464
- 1920s on the same evidence as every prior raise — a borderline clip on
519
+ 1920s on the same evidence as every prior raise, a borderline clip on
465
520
  this release's tree, a timeout there being a flake, never a privacy
466
521
  finding.
467
522
 
@@ -471,37 +526,37 @@ The test suite is 924 tests (59 properties) at 100% coverage. Corpus:
471
526
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
472
527
  digest `sha-256:yC0gV-zIn8J8bXI5gV0dQyPmgEQgVsH6k7YOlkis37Q`.
473
528
 
474
- ## [0.7.1] — 2026-09-16
529
+ ## [0.7.1] - 2026-09-16
475
530
 
476
- ### Changed — the toolchain enforces itself (hygiene release)
531
+ ### Changed: the toolchain enforces itself (hygiene release)
477
532
 
478
533
  - The declared Elixir requirement is a supported range (`~> 1.19`: the
479
534
  1.19 and 1.20 lines are admitted, and Mix refuses anything outside
480
- the range at compile), and `config/config.exs` refuses any Erlang/OTP
535
+ the range at compile), and the checkout configuration refuses any Erlang/OTP
481
536
  major outside the supported set (27/28/29) before anything compiles.
482
537
  The set was probed from the official precompiled build lists, not
483
538
  assumed; the decision record ships as
484
539
  `docs/adr/supported-otp-set.md`. The assert governs development and
485
- CI only — the Hex archive does not ship `config/`, so package
540
+ CI only; the Hex archive does not ship `config/`, so package
486
541
  consumers see no new requirement.
487
542
  - CI exercises every lane of the supported matrix: Elixir 1.19 on
488
543
  OTP 28, and Elixir 1.20 on OTP 27, 28, and 29 (the dev pin, mirrored
489
- in the new `.tool-versions`). The four toolchain declarations — the
490
- Elixir range, the supported-OTP set, the dev pin, and the CI lanes —
544
+ in the checkout's toolchain declaration). The four toolchain declarations (the
545
+ Elixir range, the supported-OTP set, the dev pin, and the CI lanes)
491
546
  move together in one commit.
492
547
  - A dependency-currency gate (`mix deps.currency`; decision record at
493
548
  `docs/adr/dependency-currency-gate.md`) reds the battery on any
494
549
  resolvable drift and never passes an unverified registry state.
495
550
  dialyxir rides at its latest resolvable release.
496
- - Clones are byte-identical on every platform: `.gitattributes`
497
- disables line-ending conversion regardless of a machine's autocrlf
551
+ - Clones are byte-identical on every platform: the repository's checkout attributes
552
+ disable line-ending conversion regardless of a machine's autocrlf
498
553
  settings (Git for Windows defaults to rewriting LF to CRLF, which
499
554
  would shift the byte-frozen digests). The repository tree was probed
500
555
  for Windows checkout obstacles (reserved device names, forbidden
501
556
  characters, case collisions, symlinks, path length): none found.
502
557
  - Development documentation re-trued to the enforced-range story
503
558
  (README, CONTRIBUTING, quickstart). No Livebooks ship in this
504
- repository (probed — no notebook files and no `Mix.install`
559
+ repository (probed; no notebook files and no `Mix.install`
505
560
  anywhere), so no notebook cells were in scope. The npm kit version
506
561
  moves with the Hex line under the version-sync gate; no kit behavior
507
562
  changed.
@@ -515,9 +570,9 @@ coverage. Corpus: 96 cases, digest
515
570
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
516
571
  digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
517
572
 
518
- ## [0.7.0] — 2026-09-14
573
+ ## [0.7.0] - 2026-09-14
519
574
 
520
- ### Changed — the npm kit moves to `@agent-blueprint-protocol/verifier`
575
+ ### Changed: the npm kit moves to `@agent-blueprint-protocol/verifier`
521
576
 
522
577
  - Portfolio naming consistency with the bounded-authority kit: the
523
578
  verifier publishes under a project-named npm organization with a
@@ -525,12 +580,12 @@ digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
525
580
  (`@rjpalermo/agent-blueprint-protocol`) is deprecated with a forward
526
581
  pointer. Version numbering continues the protocol's single release
527
582
  line (the version-sync gate binds npm semver == the Hex line).
528
- - The bin gains a `verifier` alias alongside `agent-blueprint-protocol`
529
- — `npx @agent-blueprint-protocol/verifier` and
583
+ - The bin gains a `verifier` alias alongside `agent-blueprint-protocol`:
584
+ `npx @agent-blueprint-protocol/verifier` and
530
585
  `npx agent-blueprint-protocol` both work after install.
531
586
  - The publish workflow is fully idempotent: registry-published
532
587
  versions skip loudly instead of erroring (re-runs, and releases
533
- bootstrapped by a local first publish — required for a brand-new
588
+ bootstrapped by a local first publish, required for a brand-new
534
589
  package, since a trusted publisher cannot be configured before the
535
590
  package exists), and the GitHub release step creates only when
536
591
  absent.
@@ -539,21 +594,21 @@ digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
539
594
  changelog's historical entries keep it, as records).
540
595
 
541
596
  The conformance corpus, registry, and test-suite counts are unchanged
542
- from 0.6.0; the specification digest moves with the deferred-work
543
- registry row naming the kit. The test suite is 917 tests (59
597
+ from 0.6.0; the specification digest moves with the capability-inventory
598
+ row naming the kit. The test suite is 917 tests (59
544
599
  properties) at 100% coverage. Corpus: 96 cases, digest
545
600
  `sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry
546
601
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
547
602
  digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
548
603
 
549
- ## [0.6.0] — 2026-09-14
604
+ ## [0.6.0] - 2026-09-14
550
605
 
551
- ### Added — the installable verifier (npm kit)
606
+ ### Added: the installable verifier (npm kit)
552
607
 
553
608
  - `@rjpalermo/agent-blueprint-protocol` on npm: the verifier compiled
554
609
  to `.js` + `.d.ts` (strict, declarations, zero runtime dependencies,
555
610
  Node >= 24), the conformance corpus embedded byte-identically to the
556
- release-certified copy, and a single bin — `npx` verifies out of the
611
+ release-certified copy, and a single bin: `npx` verifies out of the
557
612
  box. The verifier itself typechecks clean for the first time (66
558
613
  type-level fixes, byte-frozen against the strip-types baseline).
559
614
  - `--artifact <file>` single-artifact mode (kit-only by design; the
@@ -567,7 +622,7 @@ digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
567
622
  inverted-expectation seed. `kit.build` is a quality-alias step; CI
568
623
  builds the kit before the battery.
569
624
  - The TypeScript quickstart (`documentation/typescript.md`); the ARD
570
- mapping (`docs/ard-mapping.md` — sources pinned at exact commits,
625
+ mapping (`docs/ard-mapping.md`; sources pinned at exact commits,
571
626
  trust-manifest DNA shared, the capability layer instrument-verified
572
627
  absent); the EU AI Act evidence anchor
573
628
  (`documentation/evidence-commitments.md`); the blueprint-card
@@ -578,7 +633,7 @@ digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
578
633
  line).
579
634
  - Two new examples, both byte-exact corpus cases:
580
635
  `examples/signed-blueprint.json` (a producer-signed envelope over
581
- the golden digest — signing never changes the digest it covers) and
636
+ the golden digest; signing never changes the digest it covers) and
582
637
  `examples/extension-blueprint.json` (a registered optional
583
638
  namespace retained by a supporting host, quarantined byte-exactly
584
639
  by one without it).
@@ -590,7 +645,7 @@ digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
590
645
  claim re-tied.
591
646
  - The privacy history-scan budget grows with the repository (480s →
592
647
  960s; the scan is O(tracked files × commits) and clipped its old
593
- ceiling under full-suite load — a timeout there is a flake, never a
648
+ ceiling under full-suite load; a timeout there is a flake, never a
594
649
  privacy finding).
595
650
 
596
651
  The test suite is 917 tests (59 properties) at 100% coverage. The
@@ -599,39 +654,35 @@ conformance corpus is 96 cases, digest
599
654
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
600
655
  digest `sha-256:iBllJ-J8aoWUaYKI7VAqjIfXx9bqwNqWXFO4nxBTCfM`.
601
656
 
602
- ## [0.5.0] — 2026-09-12
657
+ ## [0.5.0] - 2026-09-12
603
658
 
604
- ### Fixed — the credibility floor
659
+ ### Fixed: the credibility floor
605
660
 
606
661
  - Dependency pull requests can go green again. The public-surface
607
662
  privacy history scan hard-requires the maintainer HMAC key, which
608
- GitHub never delivers to dependabot or fork runs — every dependency
663
+ GitHub never delivers to dependabot or fork runs; every dependency
609
664
  PR was structurally red. The gate now has exactly one relaxation:
610
665
  CI marks true fork pull requests `ABP_PRIVACY_SCAN=fork-skip`, where
611
666
  the scan skips LOUDLY (a greppable `[privacy-scan] SKIPPED` banner
612
- naming what did not run); every other mode value — including typos —
667
+ naming what did not run); every other mode value (including typos)
613
668
  fails closed exactly as before, and a fork run whose secret IS
614
- present still enforces. All three arms are red-proven in the
615
- requirement map; the dependabot green run is recorded as a green
616
- observation.
669
+ present still enforces. All three arms have regression tests; the dependency-update run passes.
617
670
  - The documentation-currency gate's shipped-file enumeration now globs
618
671
  DIRECTORY package entries: the original filter silently skipped
619
672
  every guide inside `"documentation"`, and the onboarding install
620
- pins had drifted into a line SECURITY.md marks unsupported (the
621
- organic red is recorded in the requirement map).
673
+ pins had drifted into a line SECURITY.md marks unsupported.
622
674
  - macOS Finder artifacts (`.DS_Store`, `._*`) are excluded from the
623
675
  four digest/file-set walks (specification identity, both release
624
676
  asset walks, the corpus directory walk): a stray `.DS_Store` inside
625
677
  `spec/` shifted the specification digest and red the
626
678
  release-candidate check on any Mac that had previewed the folder.
627
679
 
628
- ### Added — the adoption surface
680
+ ### Added: the adoption surface
629
681
 
630
682
  - Community intake: bug-report and registry-request issue templates
631
683
  (the registry template follows `spec/registry/OPERATIONS.md`),
632
684
  GitHub Discussions, SUPPORT.md, and a how-to-propose-changes path in
633
- CONTRIBUTING with the deferred-work registry surfaced as the public
634
- roadmap.
685
+ CONTRIBUTING, with the capability inventory explaining what is not included.
635
686
  - Onboarding reaches a green verification: the quickstart and getting-
636
687
  started guides now decode the shipped echo example to `{:ok, _}` and
637
688
  round-trip its canonical bytes byte-exactly (mirror-tested), state
@@ -640,11 +691,11 @@ digest `sha-256:iBllJ-J8aoWUaYKI7VAqjIfXx9bqwNqWXFO4nxBTCfM`.
640
691
  - The worked host integration: a full `reconcile/3` over the shipped
641
692
  echo pair under the default `:deny` clamp posture (the typed
642
693
  protected-clamp denial) and under `:acknowledge` (a green Evidence
643
- record whose `not_verified` names the seven host-owned surfaces) —
694
+ record whose `not_verified` names the seven host-owned surfaces),
644
695
  mirror-tested line by line.
645
696
  - The producer signing recipe: the detached-JWS Ed25519 envelope built
646
697
  with `:crypto` over the RFC 7797 preimage and verified end-to-end
647
- against the shipped verifier — mirror-tested. The package itself
698
+ against the shipped verifier, mirror-tested. The package itself
648
699
  remains verify-only.
649
700
  - `examples/federation-envelope.json`: the 23-member federation
650
701
  TaskEnvelope as a byte-exact conformance corpus case, documented in
@@ -654,8 +705,7 @@ digest `sha-256:iBllJ-J8aoWUaYKI7VAqjIfXx9bqwNqWXFO4nxBTCfM`.
654
705
  governance).
655
706
  - A CI compatibility job: the previous supported Elixir/OTP pair
656
707
  (1.20.1 / 29.0.2) runs the test suite and the conformance corpus on
657
- every push and pull request — the broadened-target receipt the
658
- README's support claim now rests on.
708
+ every push and pull request, checking the README's support claim.
659
709
 
660
710
  The test suite is 917 tests (59 properties) at 100% coverage. The
661
711
  conformance corpus is unchanged at 94 cases, digest
@@ -663,9 +713,9 @@ conformance corpus is unchanged at 94 cases, digest
663
713
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
664
714
  digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
665
715
 
666
- ## [0.4.1] — 2026-08-26
716
+ ## [0.4.1] - 2026-08-26
667
717
 
668
- ### Fixed — verification posture hardening
718
+ ### Fixed: verification posture hardening
669
719
 
670
720
  - CI green on the public repository (GitHub Actions is free for
671
721
  public repos; the prior 'billing-blocked' posture was wrong and is
@@ -675,28 +725,27 @@ digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
675
725
  - The README test-count claim is tied to the suite-REGISTERED count,
676
726
  not just the source macro census: the release-candidate check
677
727
  asserts macro census == registered count == README claim (both
678
- divergence arms red-proven and replanted in the evidence map).
679
- - The deferred-work registry (twelve named items, each with its
680
- checkable reopen trigger) ships inside the specification tree's
681
- FOUNDATION-TRANSITION document — the durable record no longer lives
682
- only in planning artifacts.
728
+ divergence arms tested against deliberately introduced faults).
729
+ - The capability inventory ships inside the specification tree's
730
+ FOUNDATION-TRANSITION document, with a condition for reconsidering
731
+ each capability not included in that release.
683
732
 
684
733
  The conformance corpus is unchanged at 94 cases, digest
685
734
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
686
735
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
687
736
  digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
688
737
 
689
- ## [0.4.0] — 2026-08-26
738
+ ## [0.4.0] - 2026-08-26
690
739
 
691
- ### Added — examples gallery + minutes-long quickstart
740
+ ### Added: examples gallery + minutes-long quickstart
692
741
 
693
- - `examples/`: complete, corpus-verified artifact pairs — byte-exact
742
+ - `examples/`: complete, corpus-verified artifact pairs, byte-exact
694
743
  conformance corpus cases (the gallery gate proves it against the
695
744
  corpus on every build; a drifted example reds). The echo pair
696
745
  (blueprint + deployment) is annotated member-by-member in the
697
746
  examples guide.
698
747
  - The quickstart (`documentation/quickstart.md`): from `mix deps.get`
699
- to a green verification in `iex` — no heavyweight gates; its
748
+ to a green verification in `iex`; no heavyweight gates; its
700
749
  result-claiming lines are mirror-tested like every guide example.
701
750
  - The documentation corpus: 13 adopter guides (getting started, the
702
751
  artifacts, extension authoring, host integration, producing,
@@ -710,9 +759,9 @@ The conformance corpus is unchanged at 94 cases, digest
710
759
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
711
760
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
712
761
 
713
- ## [0.3.0] — 2026-08-26
762
+ ## [0.3.0] - 2026-08-26
714
763
 
715
- ### Added — the specification corpus (normative hardening + governance)
764
+ ### Added: the specification corpus (normative hardening + governance)
716
765
 
717
766
  The normative specification is a specification in the standards sense:
718
767
 
@@ -731,7 +780,7 @@ The normative specification is a specification in the standards sense:
731
780
  the positioning boundary (AI Catalog owns discovery + identity +
732
781
  attestation; this protocol owns the portable contract layer).
733
782
  - Machine-readable grammar: CDDL (RFC 8610) normative under
734
- spec/grammar/ with JSON Schema derived (never hand-edited) — bound
783
+ spec/grammar/ with JSON Schema derived (never hand-edited); bound
735
784
  to the compiled tables and the corpus goldens by the
736
785
  grammar-derivation gate.
737
786
  - Registry data governance: spec/registry/registry.json as the
@@ -745,32 +794,31 @@ The normative specification is a specification in the standards sense:
745
794
  unincorporated BaseLabs org, Russ Palermo as named maintainer.
746
795
  - The release identity chain: priv/release-metadata.json pins the
747
796
  specification digest, package version, corpus and registry digests,
748
- and the corpus index hash — asserted from live state on every run.
797
+ and the corpus index hash, asserted from live state on every run.
749
798
  - Specification extraction is a tested proof (spec/ + the conformance
750
799
  corpus extract self-contained; the CI job runs the literal
751
800
  repository-filter extraction).
752
801
 
753
- Every new gate carries a recorded red proof in the requirement map and
754
- is replanted by the release-candidate reprove (74 plants).
802
+ Every new gate is tested against a deliberately introduced fault by the release-candidate check (74 faults).
755
803
 
756
804
  The conformance corpus is unchanged at 94 cases, digest
757
805
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
758
806
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
759
807
 
760
- ## [0.2.1] — 2026-08-25
808
+ ## [0.2.1] - 2026-08-25
761
809
 
762
- ### Fixed — public documentation credibility
810
+ ### Fixed: public documentation credibility
763
811
 
764
812
  - README install pin corrected to the current release line (`~> 0.2.1`;
765
813
  the previous `~> 0.1.0` excluded every 0.2.x release in Hex
766
814
  requirement semantics).
767
815
  - SECURITY.md's supported-version table names the 0.2.x line (0.1.x is
768
- no longer supported — upgrade to the current line).
816
+ no longer supported; upgrade to the current line).
769
817
  - Two changelog entries cited an internal working document by section
770
818
  number (a document that ships nowhere); both are reworded to
771
819
  self-contained prose, and a new document-citation gate (below) keeps
772
820
  the class dead.
773
- - `docs/protocol.md` states the producer surface explicitly in its
821
+ - `spec/protocol.md` states the producer surface explicitly in its
774
822
  shipped-surface section (`Blueprint.from_value/2`,
775
823
  `Deployment.from_value/2`, the per-artifact `content_digest/1` and
776
824
  `canonical_bytes/1`), resolving the pointer the producer-surface ADR
@@ -783,16 +831,14 @@ The conformance corpus is unchanged at 94 cases, digest
783
831
  badges; an outsider-readable status section; current test and corpus
784
832
  counts.
785
833
 
786
- ### Added — documentation gates
834
+ ### Added: documentation gates
787
835
 
788
- - Documentation-currency gate
789
- (`test/architecture/documentation_currency_test.exs`): README,
836
+ - Documentation-currency gate: README,
790
837
  SECURITY.md, and CHANGELOG version claims, install pins, count
791
838
  claims, and the current release's corpus identity (digest and case
792
839
  total) are checked against the live project on every run.
793
- - Document-citation gate
794
- (`test/architecture/document_citation_gate_test.exs`): shipped
795
- markdown documents may cite only documents that exist — a named
840
+ - Document-citation gate: shipped
841
+ markdown documents may cite only documents that exist; a named
796
842
  section citation must name a shipped document or a pinned external
797
843
  standard, and every repository-relative link must resolve to a real
798
844
  file.
@@ -801,12 +847,12 @@ The conformance corpus is unchanged at 94 cases, digest
801
847
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
802
848
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
803
849
 
804
- ## [0.2.0] — 2026-08-25
850
+ ## [0.2.0] - 2026-08-25
805
851
 
806
- ### Added — product-extension registration
852
+ ### Added: product-extension registration
807
853
 
808
854
  - The extension registry registers `com.example.platform/estate-contract`
809
- (owner `ExamplePlatform`, **critical**, active, never promoted) — the first
855
+ (owner `ExamplePlatform`, **critical**, active, never promoted), the first
810
856
  product-owned critical namespace with an authored schema digest pin, riding
811
857
  the `:authored_extensions` validated channel: critical bodies validate
812
858
  against a host-supplied schema whose `extension_schema` JCS digest matches
@@ -816,12 +862,12 @@ The conformance corpus is unchanged at 94 cases, digest
816
862
  (leaves `materialization_present` / `materialization_stale` /
817
863
  `materialization_count_within`; composites `and`/`or` n-ary, `not` unary),
818
864
  hand-tiered as uniform-depth strict tiers because the bounded dialect denies
819
- `$ref` cycles — portable condition depth is three composite tiers
820
- (metered complexity 417/512; the single free-form string — `definition.name` — is bounded to 128 bytes by the schema itself, the bound on the authored channel's unscanned surface). See `docs/adr/product-extension-registration.md`.
865
+ `$ref` cycles; portable condition depth is three composite tiers
866
+ (metered complexity 417/512; the single free-form string (`definition.name`) is bounded to 128 bytes by the schema itself, the bound on the authored channel's unscanned surface). See `docs/adr/product-extension-registration.md`.
821
867
  - The schema document ships as corpus data
822
- (`priv/conformance/schemas/estate-contract.schema.json`); `lib/` records only
868
+ for that release; the library records only
823
869
  the digest pin, and a test binds the pin to the SHIPPED document (the corpus
824
- index hashes raw file bytes, the pin hashes JCS of the parsed document — the
870
+ index hashes raw file bytes, the pin hashes JCS of the parsed document; the
825
871
  test is the bridge between the two domains).
826
872
  - The conformance corpus grows 88 → 94 cases: the validated-channel cells
827
873
  (valid attach with matching schema, schema absent, digest mismatch,
@@ -838,8 +884,8 @@ The conformance corpus is unchanged at 94 cases, digest
838
884
  ### Deprecated
839
885
 
840
886
  - `com.example.platform/estate` (the placeholder optional namespace) is
841
- `deprecated`: its payload role — a condition body carried verbatim as a free
842
- object — is superseded by the schema-validated channel. Optional bodies in
887
+ `deprecated`: its payload role (a condition body carried verbatim as a free
888
+ object) is superseded by the schema-validated channel. Optional bodies in
843
889
  existing artifacts remain verifiable, retained with a typed
844
890
  `extension_deprecated` notice.
845
891
 
@@ -847,7 +893,7 @@ The conformance corpus is unchanged at 94 cases, digest
847
893
 
848
894
  - Cross-vendor review fix pass: the schema document bounds
849
895
  `definition.name` with `maxLength: 128` (the free-form string in a body
850
- that skips the portability value-shape heuristics — the schema is the
896
+ that skips the portability value-shape heuristics; the schema is the
851
897
  bound on that surface); the registry's closed-schema lens test now fails
852
898
  loudly for any future pinned namespace without its own document binding;
853
899
  stale 0.1.x release-line claims and the generator's section counts were
@@ -859,11 +905,11 @@ The conformance corpus is unchanged at 94 cases, digest
859
905
  corpus-bearing `items` user; the byte-identical agreement gate now proves
860
906
  both languages validate items identically.
861
907
 
862
- ### Changed — from the unreleased queue
908
+ ### Changed
863
909
 
864
910
  - The gitleaks secret-scan configuration was invalid TOML (a string
865
911
  concatenation TOML does not support) and, independently, nothing executed
866
- it — no CI job or alias ran gitleaks, so a committed credential would have
912
+ it; no CI job or alias ran gitleaks, so a committed credential would have
867
913
  passed the complete quality gate. The config now parses (the corpus key
868
914
  fragment is matched via a single-character class instead of concatenation),
869
915
  the generated conformance corpus is allowlisted by path (per-value fragments
@@ -880,27 +926,20 @@ The conformance corpus is unchanged at 94 cases, digest
880
926
  live public 0.1.x package state (obsolete pre-publication/release-candidate
881
927
  framing removed).
882
928
 
883
- ## [0.1.1] — 2026-08-23
929
+ ## [0.1.1] - 2026-08-23
884
930
 
885
- ### Changed — documentation packaging (no code change)
931
+ ### Changed: documentation packaging (no code change)
886
932
 
887
933
  - The Hex archive and hexdocs now ship the seven architecture decision
888
934
  records (`docs/adr/`), and `docs/federation-mapping.md` joins the
889
- hexdocs extras — matching the house packaging convention of the
935
+ hexdocs extras, matching the house packaging convention of the
890
936
  published `bounded_authority_protocol` package.
891
- - The requirement map stays repository-side BY DESIGN (public in the
892
- repository, not in the archive): its verbatim red receipts quote the
893
- very internal tokens the publish guard bans from the archive, so
894
- archiving it reds the guard — that red is now recorded in the map's
895
- own publish-guard entry as the boundary's proof. An earlier draft of
896
- this release stripped the map's receipt fences from the guard's scan
897
- instead; cross-vendor review correctly blocked it as a guard blind
898
- spot that would have shipped the banned tokens verbatim.
937
+ - Build-verification records remain in the repository and are excluded from the archive. The publication guard rejects those records if they are included, because their intentionally failing examples contain prohibited text.
899
938
  - README restructured to the house convention: Installation directly
900
939
  after the introduction, a function-level "What it provides" section,
901
- and the requirement map's boundary stated.
940
+ and the documentation packaging boundary stated.
902
941
 
903
- ## [0.1.0] — 2026-08-23
942
+ ## [0.1.0] - 2026-08-23
904
943
 
905
944
  Initial public release: the Agent Blueprint Protocol, its Elixir
906
945
  reference implementation, the conformance corpus, and the
@@ -908,45 +947,39 @@ second-language verifier.
908
947
 
909
948
  ### Normative docs + release-candidate gates
910
949
 
911
- - `docs/protocol.md`: the normative protocol document (ships in the Hex
912
- archive) — artifacts and the closed member registries, bounded bytes
950
+ - `spec/protocol.md`: the normative protocol document (ships in the Hex
951
+ archive): artifacts and the closed member registries, bounded bytes
913
952
  and the integer window, RFC 8785 canonicalization, domain-separated
914
953
  digests, the detached-JWS envelope, evolution and extension rules, the
915
954
  compiled registry's first-release entries, the bounds algebra laws,
916
955
  the 74-code error vocabulary, the evidence contract, and the
917
956
  conformance corpus identity (88 cases at the recorded digest).
918
- - `docs/design/requirement-map.md` (repository-side, not in the Hex
919
- archive): every build gate's recorded red
920
- proof — each quality-alias step, every architecture-lane test case,
921
- and the conformance lanes — re-derived live (plant → run → restore)
922
- with verbatim failing output.
957
+ - Build-verification records stay in the repository. Every quality step, architecture test, and conformance check is tested against a deliberately introduced fault.
923
958
  - `docs/adr/` (repository-side, slug-only filenames): the seven
924
- decisions of record —
959
+ decisions of record:
925
960
  the non-authorizing boundary, the detached JWS envelope, the
926
961
  two-consumer amendment, deny-default protected-bound clamps, the
927
962
  compiled-in registry (closing the package-boundary contradiction of
928
963
  record), the federation lanes, and the no-versioning rule.
929
964
  - New architecture gates, both red-proven at birth:
930
- - **publish guard** — no internal-planning reference, private-tool
965
+ - **publish guard**: no internal-planning reference, private-tool
931
966
  path, or home-directory path in any archived file (byte patterns
932
967
  plus word-bounded text patterns that cannot false-positive inside
933
968
  base64url tokens; registry owner/namespace/URI data is published by
934
969
  design and exempted on record);
935
- - **spec coverage** — every public function carries a matching
970
+ - **spec coverage**: every public function carries a matching
936
971
  `@spec` (default-arity rule recorded) and every shipped module's
937
972
  moduledoc states the non-authorizing boundary (39 modules gained
938
973
  an honest stance sentence; `ExtensionRegistry.federation_schema/0`
939
974
  gained its missing `@spec`).
940
975
  - `mix release.candidate` (also in `mix quality`): re-derives the
941
- requirement map's completeness from live project state (every
942
- architecture test case, every live quality-alias step), structure-
943
- checks each entry's red fence, and couples `docs/protocol.md` to the
976
+ verification-record completeness from live project state (every architecture test case and quality-alias step), checks recorded failures, and couples `spec/protocol.md` to the
944
977
  shipped implementation (facade functions, registry namespaces, corpus
945
978
  digest and case total, the stance sentence).
946
979
  - Internal-reference scrub of the shipped surface: tracker numerals,
947
980
  internal design-shorthand citations, and a portfolio-terminology
948
981
  section removed from `docs/federation-mapping.md`, README, CHANGELOG,
949
- and `lib/` comments/`@doc`s (comments and docs only — zero behavior
982
+ and `lib/` comments/`@doc`s (comments and docs only; zero behavior
950
983
  change).
951
984
  - README Status and Installation rewritten to the published 0.1.0
952
985
  state.
@@ -954,7 +987,7 @@ second-language verifier.
954
987
  ### Second-language verifier + agreement gate
955
988
 
956
989
  - `conformance/verifier/`: the repo-side TypeScript verifier (Node ≥ 24,
957
- `node:` builtins only, zero npm runtime deps; never in the Hex archive) —
990
+ `node:` builtins only, zero npm runtime deps; never in the Hex archive):
958
991
  an independent recomputation of every corpus surface and integrity check,
959
992
  with a CLI byte-compatible with the Elixir escript (`--corpus` required;
960
993
  exit 0/1/2; report bytes on stdout, no trailing newline).
@@ -963,13 +996,12 @@ second-language verifier.
963
996
  runs the self-check battery (RFC 8785 Appendix B three-way, the integer-window
964
997
  matrix incl. the mis-round lexeme, Ed25519 key acceptance, stored
965
998
  JOSE vectors), and proves three seeded reds fire (verdict inversion,
966
- report member drift, window-check deletion) — with a calibration
999
+ report member drift, window-check deletion), with a calibration
967
1000
  self-proof of the raise path.
968
- - `conformance/verifier/testdata/jose-vectors.json` +
969
- `scripts/generate_jws_vectors.exs`: the stored detached-JWS vectors, KAT-
1001
+ - The stored detached-JWS vectors are KAT-
970
1002
  anchored to RFC 8032 §7.1 TEST 1, verified Elixir-signed → node-verified
971
1003
  in both detached and compact forms.
972
- - `Signature`: small-order key rejection hardened — the identity (order 1)
1004
+ - `Signature`: small-order key rejection hardened: the identity (order 1)
973
1005
  and order-2 encodings no longer pass `usable_ed25519_key?` (found by the
974
1006
  mirror's torsion battery; latent on this OTP).
975
1007
  - `Federation.decode`: an empty claim value or compatibility identity now
@@ -987,7 +1019,7 @@ second-language verifier.
987
1019
 
988
1020
  ### Conformance corpus subsystem
989
1021
 
990
- - `Conformance.{Corpus,Runner,Report,Cli}`: the portable conformance corpus —
1022
+ - `Conformance.{Corpus,Runner,Report,Cli}`: the portable conformance corpus:
991
1023
  pure loader with the 16×29 applicability floor compiled in, two-directional
992
1024
  integrity with typed errors (corpus-registry and corpus-digest bindings,
993
1025
  tamper verbatim-vs-derived audits, vacuous-green refusal), a code-level
@@ -996,7 +1028,7 @@ second-language verifier.
996
1028
  - `priv/conformance/`: 86 shipped cases, full-registry goldens (evidence
997
1029
  members included), RFC 8785 vectors, deterministic key fixtures.
998
1030
  - `mix conformance.verify` + `mix conformance.mutations` wired into
999
- `mix quality` — five named implementation mutations each proven to redden
1031
+ `mix quality`, five named implementation mutations each proven to redden
1000
1032
  the corpus, plus a corpus-expectation-flip calibration entry.
1001
1033
  - `ExtensionRegistry.digest/0` (+ the `:extension_registry` digest domain):
1002
1034
  the corpus-registry binding.
@@ -1018,11 +1050,11 @@ second-language verifier.
1018
1050
  (UNSPECIFIED denies at intake; crossing into MCP denies for
1019
1051
  rejected/submitted/auth_required; cancellation is never a terminal
1020
1052
  receipt); the carrier placement laws for both transports
1021
- (`Task.metadata[a2a_uri]` on A2A, `_meta[namespace]` on MCP — the
1053
+ (`Task.metadata[a2a_uri]` on A2A, `_meta[namespace]` on MCP; the
1022
1054
  `_meta` key grammar forbids a URI key); `terminal_commitment/1` over
1023
1055
  the seven commitment components; and `verify_commitment/2` with the signature
1024
1056
  BINDING step (the signed content digest must name the receiving
1025
- envelope's covered bytes — an honestly-signed statement naming a
1057
+ envelope's covered bytes: an honestly-signed statement naming a
1026
1058
  different digest is evidence over THAT digest), the
1027
1059
  issuer/subject/audience comparison (`:audience_mismatch`), and
1028
1060
  `:federation_terminal_conflict` on any divergence between receipts for
@@ -1036,11 +1068,11 @@ second-language verifier.
1036
1068
  - Federation hardening (independent review): a
1037
1069
  signature whose signed `purpose` is not `federation-envelope` never
1038
1070
  verifies a federation receipt (the symmetric cross-surface purpose gap, closed
1039
- on this surface — cross-surface signature lifting denied
1071
+ on this surface; cross-surface signature lifting denied
1040
1072
  `:invalid_constraint`); the receipt's `kid`/`key_id` positions are
1041
1073
  portability-scanned strict (PEM/hex secrets deny
1042
1074
  `:forbidden_portable_value`; the signature blob stays deliberately
1043
- opaque — every honest signature is entropy-dense and never survives
1075
+ opaque; every honest signature is entropy-dense and never survives
1044
1076
  verification without the key); `terminal_commitment/1` and
1045
1077
  `verify_commitment/2` are total over hand-built structs (typed denials
1046
1078
  replace raises on absent/non-string members and malformed commitment
@@ -1050,16 +1082,16 @@ second-language verifier.
1050
1082
  Receiver posture documented (purpose pinning, key-ids-as-labels,
1051
1083
  keys-are-not-issuers, replay-is-receiver-policy).
1052
1084
  - Federation residual hardening: `Federation.Context` gains
1053
- `issuer_key_sets` — per-issuer key attribution where the receipt's
1085
+ `issuer_key_sets`: per-issuer key attribution where the receipt's
1054
1086
  claimed (and binding-proven) `issuer` member selects the signature key
1055
1087
  pool, with strictest-wins precedence over the flat pool and deny-all
1056
- for an empty map (cross-attribution now denies by mechanism) — and
1088
+ for an empty map (cross-attribution now denies by mechanism), and
1057
1089
  `created_after`/`created_before` freshness pins over the SIGNED
1058
1090
  `created_at` (receiver-supplied inclusive window, Z-form double-gated,
1059
1091
  checked after conflict detection so equivocation still reports
1060
1092
  `:federation_terminal_conflict`). Fixes a live crash the adversarial
1061
1093
  pass reproduced: `verify_commitment` with the Context's `keys: nil`
1062
- default raised `FunctionClauseError` — nil/malformed pools now deny
1094
+ default raised `FunctionClauseError`; nil/malformed pools now deny
1063
1095
  `:invalid_type` typed. Attribution-miss denials name the issuer
1064
1096
  subject; a value-free structural guard pins every federation denial's
1065
1097
  subject to schema shape with nil detail. Signature-blob opacity ruled
@@ -1068,7 +1100,7 @@ second-language verifier.
1068
1100
  verification without the key.
1069
1101
  - Error vocabulary: `:forbidden_portable_value` is now declared and
1070
1102
  emitted through per-site literals (the per-site vocabulary walk could
1071
- not see the module-attribute-carried emission — a live closedness hole,
1103
+ not see the module-attribute-carried emission: a live closedness hole,
1072
1104
  closed with a staged red); the federation codes
1073
1105
  `:federation_state_unmappable`, `:federation_mapping_conflict`,
1074
1106
  `:nonportable_content`, `:audience_mismatch`, and
@@ -1078,7 +1110,7 @@ second-language verifier.
1078
1110
  composed pass gates non-object artifact roots at the canonical stage
1079
1111
  (typed denial, never a raise); `Reconcile.Inputs` drops the unused
1080
1112
  observed-identities field (the eight-stage pass performs no
1081
- compatibility verification — hosts call `verify_compatibility/2`;
1113
+ compatibility verification; hosts call `verify_compatibility/2`;
1082
1114
  recorded contract delta); the portability stage mirrors each
1083
1115
  artifact's own per-position scan modes (authored schema documents and
1084
1116
  predicate operands, the blueprint's five identifier member tables,
@@ -1092,14 +1124,14 @@ second-language verifier.
1092
1124
  dynamic build failures, sees piped call sites, and fixes the
1093
1125
  case/cond branch tag.
1094
1126
  - Reconcile, compatibility, and the evidence record:
1095
- `AgentBlueprintProtocol.Reconcile.reconcile/3` — the one call per
1127
+ `AgentBlueprintProtocol.Reconcile.reconcile/3`, the one call per
1096
1128
  import, running the pinned stage order canonical → digest →
1097
1129
  negotiation → structure → portability → signatures → bind → bounds,
1098
1130
  each stage reject-or-annotate, never repair, under host-supplied
1099
1131
  `Reconcile.Inputs` (host policy bounds, negotiation support, trusted
1100
1132
  public keys, observed build identities, the protected-clamp posture,
1101
1133
  and the bind-time observations). The signature stage BINDS each
1102
- entry's signed `content_digest` to the artifact's recomputed digest —
1134
+ entry's signed `content_digest` to the artifact's recomputed digest,
1103
1135
  an honestly-signed statement naming a different digest is evidence
1104
1136
  over that digest, not this artifact (`:digest_mismatch`). The
1105
1137
  portability stage runs the direct scans under the authored channel
@@ -1107,7 +1139,7 @@ second-language verifier.
1107
1139
  structure stage is the registry validation, kept disjoint so both
1108
1140
  guards are independently observable. Every clamp lands as
1109
1141
  `Evidence.clamps` and as a per-bound `:bounds` check carrying the
1110
- `%ClampEvidence{}`. `AgentBlueprintProtocol.Compatibility.verify/2` —
1142
+ `%ClampEvidence{}`. `AgentBlueprintProtocol.Compatibility.verify/2`:
1111
1143
  identity-exact matching of manifest `build_identities` against
1112
1144
  host-observed identities: ranges deny `:compatibility_identity_inexact`
1113
1145
  on both sides, duplicate candidates (including byte-identical
@@ -1115,7 +1147,7 @@ second-language verifier.
1115
1147
  `:compatibility_duplicate_entry`, unmatched entries deny
1116
1148
  `:compatibility_entry_missing`, extra observed identities are
1117
1149
  evidence-neutral; `exact?/1` is the public exact-version predicate.
1118
- `AgentBlueprintProtocol.Evidence` — the non-authorizing verification
1150
+ `AgentBlueprintProtocol.Evidence`, the non-authorizing verification
1119
1151
  record whose `not_verified` is non-empty BY CONSTRUCTION: `build/1`
1120
1152
  unions in the seven host-owned surfaces (tenancy, live_policy,
1121
1153
  authority, effect_ownership, execution, billing, evaluation_truth),
@@ -1127,14 +1159,14 @@ second-language verifier.
1127
1159
 
1128
1160
  - Bounds-algebra hardening pass: classification comparison
1129
1161
  moves to the PRODUCT order the meet computes in (ordinal ≤ AND markers
1130
- ⊇) — a marker dropped at ANY ordinal is a widening (obligations are not
1162
+ ⊇); a marker dropped at ANY ordinal is a widening (obligations are not
1131
1163
  tradeable against scope), `widens?` becomes `¬(a ⪯ b)` and so
1132
1164
  fail-closed on every incomparable pair (an independent review's
1133
1165
  blocking finding: `{pci}` vs `{phi}` previously compared non-widening
1134
1166
  in both directions), and `narrower` requires both components. The rim is now
1135
1167
  deny-typed everywhere it previously raised on struct-bypass inputs:
1136
1168
  hostile map keys and unknown/extra names deny `:bound_unknown` with the
1137
- CONTAINING surface as subject (never the attacker key — the echo
1169
+ CONTAINING surface as subject (never the attacker key; the echo
1138
1170
  channel closes), plain-map markers and marker maps with extra keys deny
1139
1171
  `:bound_value_invalid` at construction and again at `intersect`'s
1140
1172
  revalidation, malformed lifter sub-shapes read as absent (total,
@@ -1147,14 +1179,14 @@ second-language verifier.
1147
1179
  forged values (total predicates, fail-closed in the widening
1148
1180
  direction), and `Result.t`'s clamps type resolves its module. Every
1149
1181
  fix re-probed live against the finding's original probe input.
1150
- - Bounds algebra: `AgentBlueprintProtocol.BoundsAlgebra` —
1182
+ - Bounds algebra: `AgentBlueprintProtocol.BoundsAlgebra`:
1151
1183
  the pointwise narrowest intersection of the Blueprint's declared
1152
1184
  bounds, the Deployment's `host_bounds`, and the host's live policy over
1153
1185
  the closed thirteen-bound vocabulary, with per-family direction
1154
1186
  (scope families narrow at the low end; authority/approval/effect
1155
1187
  narrow at the STRICT end; classification markers are
1156
1188
  retained regulatory obligations whose effective set is the UNION of
1157
- the sources' sets — dropping one is the widening the mutation gate
1189
+ the sources' sets; dropping one is the widening the mutation gate
1158
1190
  names). Protected narrowings never happen silently: under the default
1159
1191
  `:deny` posture they deny `:protected_bound_clamp_denied` carrying
1160
1192
  the field/requested/effective triple; under `:acknowledge` they clamp
@@ -1169,12 +1201,12 @@ second-language verifier.
1169
1201
  then numerics → cost → protected, each name-sorted). `widens?/2` is
1170
1202
  fail-closed on incomparable pairs; `Bound.narrower/2` is
1171
1203
  direction-encoded per family and function-total (marker-bearing
1172
- classification is a partial order — the lexicographic
1204
+ classification is a partial order; the lexicographic
1173
1205
  ordinal-then-marker superset relation). The lifters derive the
1174
1206
  Blueprint side totally (classification is the WIDEST across all five
1175
1207
  declaration sites; approval/authority/impact are the strictest claims
1176
1208
  across capabilities/effects with bottoms for empty arrays; disclosure
1177
- is the identity element `:full` — the Blueprint declares no
1209
+ is the identity element `:full`; the Blueprint declares no
1178
1210
  disclosure member) and lift the Deployment from `host_bounds` only
1179
1211
  (`model_policy` and `data_bindings` are not intersection inputs).
1180
1212
  The new `AgentBlueprintProtocol.Error{code, subject, detail}` record
@@ -1182,7 +1214,7 @@ second-language verifier.
1182
1214
  protected deny) lands with the algebra surface; the facade gains
1183
1215
  `intersect/1`. Property lane: idempotent/commutative/associative
1184
1216
  (pinned fold encoding), `not widens?(effective, host)` universal,
1185
- clamp iff `effective ≠ requested`, marker-union law — with the
1217
+ clamp iff `effective ≠ requested`, marker-union law, with the
1186
1218
  min→max, marker-intersection, direction-flip, struct-default, and
1187
1219
  silent-path mutations each proven RED against them.
1188
1220
 
@@ -1190,7 +1222,7 @@ second-language verifier.
1190
1222
 
1191
1223
  - The bounds-algebra rim's coverage claim was corrected to a true
1192
1224
  100% (measured 2026-08-22: the then-committed suite reached only
1193
- 97.7% — the deny-typed rim's catch-all clauses had no tests). The rim probes now ship as tests: struct-bypass forged
1225
+ 97.7%; the deny-typed rim's catch-all clauses had no tests). The rim probes now ship as tests: struct-bypass forged
1194
1226
  values through `widens?/2` and `Bound.narrower/2` for every family,
1195
1227
  wrong-shape cost at construction, non-map `new/1`, absent-name
1196
1228
  `fetch/2`, non-`Sources`/junk-posture/non-set-source `intersect/1`,
@@ -1215,8 +1247,8 @@ second-language verifier.
1215
1247
  - A one-off suite flake, root-caused: the
1216
1248
  "mutating the signatures member" test replaced the first `A` in the
1217
1249
  base64url signature, which lands on the FINAL character ~7% of random
1218
- signatures — the one position whose value is canonicality-constrained
1219
- — producing a correctly-rejected non-canonical string
1250
+ signatures (the one position whose value is canonicality-constrained)
1251
+ producing a correctly-rejected non-canonical string
1220
1252
  (`:signature_malformed`). The tamper now targets the first character
1221
1253
  (a significant 6-bit position at every base64url length), making the
1222
1254
  test deterministic for every key.
@@ -1225,7 +1257,7 @@ second-language verifier.
1225
1257
 
1226
1258
  - Deployment Manifest + binding: the 19-member table
1227
1259
  (re-derived against the protocol's Deployment Manifest definition) on the
1228
- SAME generic engine — `AgentBlueprintProtocol.Deployment` mirrors the
1260
+ SAME generic engine; `AgentBlueprintProtocol.Deployment` mirrors the
1229
1261
  Blueprint pipeline stage-for-stage (canonical verify → registry
1230
1262
  validation → portability scan → digest comparison) under the
1231
1263
  `:deployment_content` domain, with only the table, the scan's open
@@ -1233,7 +1265,7 @@ second-language verifier.
1233
1265
  domain as deltas. The binding surface: `binds?/2` (digest equality and
1234
1266
  nothing else, against the paired Blueprint's recomputed digest,
1235
1267
  constant-time, total over malformed deployment input) and the six-stage
1236
- `verify_binding/3` with a pinned order — release digest
1268
+ `verify_binding/3` with a pinned order: release digest
1237
1269
  (`:deployment_digest_mismatch`), release identity and tool-binding
1238
1270
  completeness (`:binding_incomplete`), mutation/recovery
1239
1271
  (`:no_authoritative_recovery`, the stricter of both operation sources),
@@ -1241,27 +1273,27 @@ second-language verifier.
1241
1273
  deny), and observed rug-pull (`:binding_descriptor_mismatch`); stages
1242
1274
  carrying host observations skip exactly when their inputs are absent.
1243
1275
  Table semantics: `blueprint_release` with a REQUIRED digest;
1244
- exact-only build identities (the range vocabulary — comparators,
1245
- wildcards, `latest`, range spans — denies
1276
+ exact-only build identities (the range vocabulary, comparators,
1277
+ wildcards, `latest`, range spans, denies
1246
1278
  `:compatibility_identity_inexact`; prerelease/build suffixes are exact
1247
1279
  pins); the `as_of` total rule; lifecycle temporal rules
1248
1280
  (`:lifecycle_state_invalid`); `host_bounds` totality over the thirteen
1249
- bound names (structure only — the algebra surface owns the rest); empty
1281
+ bound names (structure only; the algebra surface owns the rest); empty
1250
1282
  `allowed_model_roles` valid. Every `adapter_identity`/`profile_identity`
1251
1283
  and every string nested in tool/data/build members is strict-scanned
1252
1284
  (`:forbidden_portable_value` in deployment positions). A signature's
1253
1285
  `purpose` is asserted per artifact (`deployment` here, `blueprint` in
1254
- `Blueprint` — the symmetric cross-surface gap this closes). The extension
1286
+ `Blueprint`; the symmetric cross-surface gap this closes). The extension
1255
1287
  envelope judgment is extracted to `AgentBlueprintProtocol.Extension` so
1256
1288
  both tables carry one definition, and `Negotiation` resolves the
1257
1289
  artifact kind from the digest member so each
1258
1290
  artifact's `required_core_fields` check against its own vocabulary. The
1259
1291
  facade gains `decode_deployment/2`, and a new architecture gate proves
1260
1292
  the no-second-pipeline invariant (delegation to `Registry.validate` plus
1261
- no local stage definitions — planted-red proven, after the exports-only
1293
+ no local stage definitions; planted-red proven, after the exports-only
1262
1294
  form was found vacuous by the same mutation).
1263
1295
  - Deployment hardening pass: `verify_binding/3` gains a
1264
- stage-0 shape totality — a non-object root, DUPLICATE root members, or a
1296
+ stage-0 shape totality: a non-object root, DUPLICATE root members, or a
1265
1297
  malformed `tool_bindings` entry (shape, operands, digest) denies before
1266
1298
  any cross-artifact judgment, and validated entries thread every later
1267
1299
  stage (the blocking finding of an independent review: malformed
@@ -1280,7 +1312,7 @@ second-language verifier.
1280
1312
  evolution gate (`AgentBlueprintProtocol.Negotiation`) with the pinned
1281
1313
  internal precedence (revision → required_core_fields → extensions) and
1282
1314
  registry-consistent reason rules for malformed machinery; explicit revision
1283
- SET support (never ranges — a miss denies `:protocol_revision_unsupported`
1315
+ SET support (never ranges; a miss denies `:protocol_revision_unsupported`
1284
1316
  in both directions); the three fail-closed required-core-field checks;
1285
1317
  the positional extension state machine (unregistered critical denies,
1286
1318
  unregistered optional QUARANTINES byte-exactly with a notice fact,
@@ -1290,8 +1322,8 @@ second-language verifier.
1290
1322
  / `:extension_schema_digest_mismatch`); and a reserved-semantics
1291
1323
  denylist (bound-shaped member names, camelCase twins included) over ALL
1292
1324
  extension bodies. The registry (`ExtensionRegistry`) is compiled-in
1293
- data — drift unrepresentable, backed by a new beam-census gate that
1294
- asserts no shipped module touches the filesystem (planted-red proven) —
1325
+ data (drift unrepresentable, backed by a new beam-census gate that
1326
+ asserts no shipped module touches the filesystem (planted-red proven)),
1295
1327
  carrying the five first-release entries with `com.example/federation`'s schema
1296
1328
  authored in-repo under the new `:extension_schema` digest domain.
1297
1329
  `Blueprint.from_value/2`'s `:authored_extensions` option opens the
@@ -1313,10 +1345,10 @@ second-language verifier.
1313
1345
  (unknown member → missing required → type → constraint → cardinality →
1314
1346
  nested → cross-field hooks). `Blueprint.decode/2` runs the fail-closed
1315
1347
  pipeline in order: canonical verify (`:non_canonical_bytes` before any
1316
- semantic read or digest work — the canonicality obligation, digests computed only
1348
+ semantic read or digest work: the canonicality obligation, digests computed only
1317
1349
  over exact received bytes), registry validation (closed world;
1318
1350
  tag-strict integer typing so a float-tagged window value in an
1319
- integer-typed core field denies `:invalid_type` — the window-float obligation,
1351
+ integer-typed core field denies `:invalid_type`; the window-float obligation,
1320
1352
  visible only at this layer), the portability scan, then the
1321
1353
  content-digest comparison (`:digest_mismatch`). Also ships
1322
1354
  `AgentBlueprintProtocol.Predicate` (the closed, order-independent
@@ -1324,8 +1356,8 @@ second-language verifier.
1324
1356
  256-node ceiling, and error-dominant `evaluate/2`), and
1325
1357
  `AgentBlueprintProtocol.Portability` (the never-portable structural
1326
1358
  guard: the 34-name member denylist over the open regions and the
1327
- value-shape denylist — PEM armour, compact JWS, network-authority URIs,
1328
- ≥32-byte clean base64url with the identifier-style exemption — over every
1359
+ value-shape denylist (PEM armour, compact JWS, network-authority URIs,
1360
+ ≥32-byte clean base64url with the identifier-style exemption) over every
1329
1361
  other string including signature `key_id`). The facade gains
1330
1362
  `decode_blueprint/2`.
1331
1363
  - Public Elixir package starter with zero third-party/Hex production
@@ -1339,7 +1371,7 @@ second-language verifier.
1339
1371
  invalid UTF-8/lone surrogates, and out-of-bound integers on the encode path.
1340
1372
  - Strict unpadded base64url codec (`AgentBlueprintProtocol.Base64Url`):
1341
1373
  RFC 4648 §5 alphabet, RFC 7515 §2 padding-free wire form, and RFC 4648
1342
- §3.3/§3.5 canonicality — padded input, non-alphabet characters, and
1374
+ §3.3/§3.5 canonicality: padded input, non-alphabet characters, and
1343
1375
  non-canonical pad-bit spellings (which alias the same bytes) all reject
1344
1376
  with value-free reasons.
1345
1377
  - Tagged content digests (`AgentBlueprintProtocol.Digest`):
@@ -1352,13 +1384,13 @@ second-language verifier.
1352
1384
  FIPS 180-4 known-answer vectors.
1353
1385
  - Detached JWS signature envelope (`AgentBlueprintProtocol.Signature`):
1354
1386
  RFC 7515 compact serialization with the RFC 7797 `b64=false` unencoded
1355
- detached payload — the signing input is
1356
- `BASE64URL(JCS(protected_header)) || "." || JCS(signed_attributes)` —
1387
+ detached payload: the signing input is
1388
+ `BASE64URL(JCS(protected_header)) || "." || JCS(signed_attributes)`,
1357
1389
  Ed25519 verified through `:crypto`, verify-only (an architecture gate
1358
1390
  enforces no `:crypto.sign` call, no private-key parameters, and no
1359
1391
  key-material shape anywhere in the shipped source). Host-supplied trusted
1360
1392
  keys match by `key_id` (`:signature_key_unsupported` when absent,
1361
- `:signature_not_verified` on divergence — facts, never authorization).
1393
+ `:signature_not_verified` on divergence; facts, never authorization).
1362
1394
  The exact four-member protected header (`alg/crit/b64/kid`) and the five
1363
1395
  signed attributes are closed-world with fail-closed, value-free denials;
1364
1396
  `kid` must equal the signed `key_id`, which is dot-free so the unencoded
@@ -1383,22 +1415,22 @@ second-language verifier.
1383
1415
  (`AgentBlueprintProtocol.Schema`): the closed 16-keyword subset
1384
1416
  (`type properties required items enum const minimum maximum minLength
1385
1417
  maxLength minItems maxItems additionalProperties oneOf $defs` plus
1386
- document-local `$ref`) over the tagged algebra, with everything else —
1387
- `pattern`/`format`/`patternProperties`/`if-then-else`/`allOf`/remote
1388
- `$ref` and the rest of the 2020-12 keyword universe — denying
1418
+ document-local `$ref`) over the tagged algebra, with everything else
1419
+ (`pattern`/`format`/`patternProperties`/`if-then-else`/`allOf`/remote
1420
+ `$ref` and the rest of the 2020-12 keyword universe) denying
1389
1421
  `:schema_keyword_not_allowed`. 2020-12 semantics read first-hand and
1390
1422
  pinned: type-targeted assertions auto-pass other types, missing keywords
1391
1423
  never fail, `oneOf` is exactly-one, boolean schemas are the substrate,
1392
1424
  numbers compare by mathematical value across the integer/float tags
1393
- (tag-blind `type:"integer"` — the tags do not survive the wire), object
1425
+ (tag-blind `type:"integer"`; the tags do not survive the wire), object
1394
1426
  equality is order-blind, and string lengths count codepoints (not
1395
1427
  graphemes, not UTF-16 units). Resource posture: complexity metered as
1396
1428
  `nodes + keywords + Σ(branches) + depth × 4` against the 512 profile
1397
- ceiling; evaluation memoized on (schema node, instance location) —
1429
+ ceiling; evaluation memoized on (schema node, instance location),
1398
1430
  closing the acyclic-`$ref`-DAG exponential blowup for passing AND failing
1399
1431
  instances; document-local RFC 6901 pointers (split-then-unescape, `~1`
1400
1432
  before `~0`) resolve at parse, and application-reachable reference cycles
1401
1433
  deny while dead `$defs` self-references parse. Both `parse/2` and
1402
- `validate_instance/3` are total — malformed tagged shapes deny, never
1434
+ `validate_instance/3` are total; malformed tagged shapes deny, never
1403
1435
  raise. Multi-failure reasons follow a fixed canonical keyword order
1404
1436
  (mirrored for the TS verifier).