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

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