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