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

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.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,85 @@
2
2
 
3
3
  All notable public changes to `agent_blueprint_protocol` are documented here.
4
4
 
5
+ ## [1.1.0-rc.3] - 2026-11-16
6
+
7
+ ### Changed
8
+
9
+ The validity periods of the signing key and the signature are host-owned in
10
+ both verifiers. `signature_time_validity` now always appears in
11
+ `Evidence.not_verified`, after `signature_created_at` and `lifecycle_state`.
12
+ Reconcile never judges creation time, lifecycle state or validity periods; the
13
+ host does. Specification section 13 states this. The Elixir
14
+ `Evidence.host_owned` type names every host-owned fact, and the TypeScript
15
+ `KNOWN_EVIDENCE_SURFACES` gains `signature_time_validity`.
16
+
17
+ The three time facts are now host-owned in every evidence value, not only in
18
+ reconcile's. Evidence from Elixir `Evidence.build/1` and
19
+ `Compatibility.verify/2`, and from the TypeScript import verification, now lists
20
+ `signature_created_at`, `lifecycle_state` and `signature_time_validity` in
21
+ `not_verified`. A consumer that compares that evidence with 1.1.0-rc.2 output
22
+ sees these three additional entries.
23
+
24
+ Specification text that described repository process rather than the protocol
25
+ is removed: the foundation transition's trigger list and its list of
26
+ capabilities not included, the registration steps in the registry operations
27
+ guide, and the notes on repository checks in the three CDDL grammar headers.
28
+ The grammar rules are unchanged.
29
+
30
+ ### Added
31
+
32
+ Release verification replays every earlier release census and the signed 0.8.x
33
+ golden artifacts through the installed Hex and npm packages, so a published
34
+ package is checked against release history and not only against the source
35
+ tree. `scripts/verify_release_packages.exs` runs that replay with the package
36
+ gates from a tagged checkout. The Hex package's own
37
+ `scripts/consumer_examples.exs` runs the four package gates without a checkout.
38
+
39
+ The TypeScript verifier is checked against the pinned stock JOSE library for both
40
+ Ed25519 algorithm spellings, `EdDSA` and `Ed25519`.
41
+
42
+ The producer guide and the glossary gain JSON examples, which run as packaged
43
+ examples.
44
+
45
+ ### Fixed
46
+
47
+ Consumer package verification works on Windows. Package documents are found
48
+ with the package root as the lookup's working directory, so a temporary path's
49
+ backslashes are never read as glob syntax.
50
+
51
+ Post-publication verification checks out the calling ref. A release run uses
52
+ its tag's driver and replay. A manual run can verify any package that ships its
53
+ own consumer gates, and the driver names any gate a package lacks.
54
+
55
+ ### Compatibility
56
+
57
+ Protocol revision 1 is unchanged. The verification-semantics version moves from
58
+ 3 to 4: reconcile outputs certified under earlier censuses now carry
59
+ `signature_time_validity` in `not_verified`. The release claims the 1.1.0-rc.2
60
+ census (`sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`) and the
61
+ `sha-256:oYnkSmTkHGk4AmZ8Sul99_6KYJUIuj2SN2GZAiT1glw` census `not_equivalent`;
62
+ the earlier censuses remain `diverged_by_registry_census`. The corpus contains
63
+ 626 cases, digest `sha-256:uwbwaxugSBQKC_3Byy86_3N-Z6RBCBvW7rP79SGmSLE`; the
64
+ registry digest is unchanged at
65
+ `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the specification digest
66
+ is `sha-256:kr7Wtl2ZNdTpSBKqBk3xmE57saO9q_Y8T-kmn_S7PKc`.
67
+
68
+ ### Security
69
+
70
+ This project publishes one npm package, `@agent-blueprint-protocol/verifier`.
71
+ Install nothing under the unscoped name `agent-blueprint-protocol`: two
72
+ placeholder versions published there on 2026-11-03 contained no code and were
73
+ withdrawn the same day.
74
+
75
+ ## [1.1.0-rc.2] - 2026-11-15
76
+
77
+ Library and verifier behavior, the protocol revision, the verification-semantics
78
+ version (3), the corpus, the registry and the specification are unchanged from
79
+ 1.1.0-rc.1. The corpus contains 626 cases, digest
80
+ `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`; the registry digest is
81
+ `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the specification digest
82
+ is `sha-256:GgsMn83Cm0ZjYecBGwiwUy4bqwcKW3zfDzkRQ87yHsw`.
83
+
5
84
  ## [1.1.0-rc.1] - 2026-11-15
6
85
 
7
86
  ### Added
@@ -11,25 +90,12 @@ Manifest (19), and Federation TaskEnvelope (23) in Elixir and TypeScript, read
11
90
  from their decoder tables. Unsupported integer revisions and invalid types
12
91
  return the same typed refusals in both implementations.
13
92
 
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.
93
+ Examples ship as installed application resources. Documentation links pin this
94
+ release, HexDocs extras resolve to rendered pages, and the public ExDoc footer
95
+ remains enabled.
28
96
 
29
97
  ### Changed
30
98
 
31
- All dated changelog headings use `## [x.y.z] - YYYY-MM-DD`.
32
-
33
99
  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
100
 
35
101
  ### Compatibility
@@ -70,20 +136,17 @@ specification digest is `sha-256:jh2uy3FU7ApQmFtPHHK3YY041sDgWrICmS8Hz-LaAGE`.
70
136
 
71
137
  ## [1.0.0-rc.3] - 2026-11-11
72
138
 
73
- The specification no longer names a candidate version in its text, so
74
- the 1.0 specification is final as written. A documentation test now
75
- keeps any version of the current release line out of every file a final
76
- release must leave unchanged. Library and verifier behavior, the
77
- protocol revision, the verification-semantics version (3), the corpus
78
- and the registry are unchanged from 1.0.0-rc.2. The corpus contains
139
+ The specification no longer names a candidate version in its text. Library and
140
+ verifier behavior, the protocol revision, the verification-semantics version
141
+ (3), the corpus and the registry are unchanged from 1.0.0-rc.2. The corpus contains
79
142
  626 cases, digest `sha-256:0B_9tnAAo05n3bWVvnIPDxFeqEr2XhJoDdaxNJv0_9A`; the registry digest is `sha-256:hreDA2_XbV5J9geMJDDYG5BB42AGkh9jmQ9bqHe8kRk`; the specification digest
80
143
  is `sha-256:jh2uy3FU7ApQmFtPHHK3YY041sDgWrICmS8Hz-LaAGE`.
81
144
 
82
145
  ## [1.0.0-rc.2] - 2026-11-11
83
146
 
84
- Documentation corrections cover the README, npm package README, guides, Livebooks, and site. The npm package description states the verifier's checks.
85
- The unused TypeScript `Context` type is no longer exported; no exported function
86
- accepted it. Release tooling works for any candidate or final version.
147
+ Documentation corrections cover the README, npm package README, guides, Livebooks,
148
+ and site. The npm package description states the verifier checks. The unused
149
+ TypeScript `Context` type is no longer exported; no exported function accepted it.
87
150
 
88
151
  The shipped registry contains only the protocol's federation registrations:
89
152
  `io.github.baselabs/federation` (active) and `com.example/federation`
@@ -155,8 +218,6 @@ the standalone archive. The runner contract is `spec/conformance/runner.md`.
155
218
  - TypeScript output identifiers are open with known-value constants;
156
219
  packed declarations support TypeScript 5.0.2 and newer. Node 26 joins
157
220
  the platform matrix while Node 24 remains the runtime floor.
158
- - GitHub release publication waits for a live Hex version whose checksum
159
- matches the verified archive, including after staged approval.
160
221
 
161
222
  - The specification separates protocol requirements from implementation notes
162
223
  and states the byte, grammar, lattice, predicate and schema profiles with
@@ -182,18 +243,13 @@ the standalone archive. The runner contract is `spec/conformance/runner.md`.
182
243
  execution harness and adapters, and unsigned implementation claims.
183
244
  - A package-root TypeScript library with typed import evidence, exhaustive
184
245
  errors, isolated consumer declarations, and its own package README.
185
- - A stability and deprecation policy for both packages and three-platform
186
- contributor and published-package lanes on Linux, macOS, and Windows.
187
- - Candidate promotion checks preserve certified bytes; further publication
188
- waits for the staged npm version to be live and byte-verified.
246
+ - A stability and deprecation policy for both packages on Linux, macOS, and Windows.
189
247
 
190
248
  - Mixed-order Ed25519 vectors distinguish the required cofactorless equation
191
249
  from cofactored verification, without rejecting mixed-order points.
192
- - Deterministic test-only signing for new fixtures, preserving every existing
193
- fixture signature. Corpus cases pin algorithm spellings, duplicate signers,
194
- both federation namespaces, and effect impact as an obligation.
195
- - A public module and function declaration prevents silent API expansion.
196
- Error descriptions distinguish overlapping conditions; evidence explicitly
250
+ - Corpus cases cover algorithm spellings, duplicate signers, both federation
251
+ namespaces, and effect impact as an obligation.
252
+ - Error descriptions distinguish overlapping conditions; evidence explicitly
197
253
  names timestamp and lifecycle facts it does not establish.
198
254
 
199
255
  ### Documentation
@@ -239,12 +295,8 @@ Prior released verdicts remain equivalent. The
239
295
  - The installed CLI accepts relative and absolute corpus paths with trailing
240
296
  separators, reports help and version with exit 0, and keeps unknown arguments
241
297
  at exit 2. Importing the optional corpus entry performs no filesystem access.
242
- - Dependency installations use the lockfile with lifecycle scripts disabled.
243
- Only the npm staging job can request an identity token.
244
298
  - Malformed host arguments and hand-built values deny with the code of the
245
299
  first violated rule; no verdict for decoded bytes changes.
246
- - Publishing jobs consume the npm tarball and standalone kit produced by the
247
- verification job.
248
300
 
249
301
  The corpus contains 199 cases, digest
250
302
  `sha-256:305LYavPWYaZP_pYGcZBPploy27btWTyMhiKd7XiRb8`; registry
@@ -269,9 +321,6 @@ The corpus contains 199 cases, digest
269
321
  prototype-chain lookups. Input-keyed tables and dictionaries now use only
270
322
  their own properties, including predicate operators, transport states,
271
323
  bounds, recovery operations, extension support, and result comparisons.
272
- - The release workflow could publish after a failed check or npm staging
273
- failure. Each publishing step now requires all preceding steps to succeed;
274
- already-published versions still skip safely on reruns.
275
324
 
276
325
  The corpus contains 190 cases, digest
277
326
  `sha-256:SvJLvMwXdYQZBjOrklsQSHQRX8PhxPHOv23C2rmFazQ`; registry
@@ -287,57 +336,26 @@ The corpus contains 190 cases, digest
287
336
  `npx verifier` work only where `@agent-blueprint-protocol/verifier` is
288
337
  installed. Elsewhere, npx looks the bare name up on the public registry,
289
338
  where it is not this project's. Use `npx @agent-blueprint-protocol/verifier`.
290
- - The post-publish check runs `npx --no-install verifier`, so it can never
291
- fetch the unrelated npm package named `verifier`.
292
339
 
293
340
  ### Added: documentation
294
341
 
295
- - A Livebook walkthrough, `docs/livebooks/abp-walkthrough.livemd`,
296
- shipped in the package and on HexDocs. It installs the package from
297
- Hex, composes and signs a Blueprint, negotiates extensions, binds a
298
- Deployment Manifest, reconciles the pair, runs the shipped corpus, and
299
- shows each denial: a tampered signature, the wrong key, an unknown
300
- `key_id`, a small-order key, an edited member, non-canonical bytes,
301
- and the strict R and S rule. The test suite runs every cell in order
302
- and compares each result with the output printed in the notebook.
303
- - The README opens with a first-verification example, and the
304
- TypeScript guide with an import example; the README example runs in
305
- the guide mirror test, and the TypeScript one runs against the kit
306
- as npm packs it (installed from the `npm pack` tarball) in a new
307
- quality step, `mix typescript.guide`, which the doc-gates workflow also
308
- runs.
342
+ - A Livebook walkthrough, `docs/livebooks/abp-walkthrough.livemd`, ships in the
343
+ package and on HexDocs. It composes and signs a Blueprint, negotiates
344
+ extensions, binds a Deployment Manifest, reconciles the pair, runs the corpus,
345
+ and demonstrates signature, digest, key, and canonical-byte denials.
346
+ - The README opens with a first-verification example, and the TypeScript guide
347
+ with an import example.
309
348
 
310
349
  ### Changed: documentation
311
350
 
312
- - The CI workflows' GitHub Action pins move with their dependabot bumps
313
- (`actions/setup-node` v7.1.0, `actions/upload-pages-artifact` v5.0.0,
314
- `actions/deploy-pages` v5.0.1); the toolchain lockstep test's pinned
315
- setup-node identity moves with them. No workflow inputs changed.
316
- - npm kit commands in the README, the TypeScript guide, and the landing
317
- page stay unpinned, with a line saying npx runs the latest published
318
- kit and how to check its version (a kit release goes live after a
319
- maintainer approves its staged publish). The documentation-currency
320
- gate requires the README's npm commands to stay unpinned.
321
- - The document-citation gate now checks the guides under
322
- `documentation/` and the Livebook (it skipped directory entries
323
- before), and the version gate scans the Livebook.
324
- - Corrected guide statements: the Deployment binding check has six
325
- ordered stages, not three; the echo example has 16 members (the table
326
- has 18); the kit has four modes and two bin names; the error guide
327
- lists the `{:ceiling, key}` decoder-limit family; SECURITY.md names
328
- the Security tab's **Report a vulnerability** form; the battery lists
329
- in the README, CONTRIBUTING.md, and the operations guide name every
330
- step; the evidence-commitments guide cites the AI Act articles it
331
- relies on (12, 25(4), and 26) and points to Regulation (EU) 2026/1744,
332
- which moved the high-risk application dates.
333
- - The release-candidate reprove turns off git's automatic maintenance in
334
- its scratch repositories, as does the privacy gate's throwaway
335
- repository. From git 2.54, `git commit` starts a detached repack that
336
- keeps writing into `.git` after the command returns; on hosted CI
337
- (git 2.55) it raced the scratch cleanup and failed the check with
338
- `could not remove files and directories recursively ... file already
339
- exists`. A new architecture test requires every script or test that
340
- commits in a scratch repository to set `maintenance.auto` false.
351
+ - npm kit commands in the README, TypeScript guide, and landing page explain
352
+ how to inspect the published kit version.
353
+ - Corrected guides: the Deployment binding check has six ordered stages; the
354
+ echo example has 16 members; the kit has four modes and two bin names; the
355
+ error guide lists the `{:ceiling, key}` decoder-limit family; SECURITY.md
356
+ names the vulnerability-report form. The evidence-commitments guide cites
357
+ AI Act articles 12, 25(4), and 26 and Regulation (EU) 2026/1744, which moved
358
+ the high-risk application dates.
341
359
  - Removed duplicated sentences from eighteen module docs. The comments
342
360
  on small-order keys in `Signature` and the TypeScript verifier now say
343
361
  exactly what the backends accept: under the identity key, R = identity
@@ -346,7 +364,7 @@ The corpus contains 190 cases, digest
346
364
  - The errata table's release boundaries now name the recording date
347
365
  instead of a concrete version ("every release published before
348
366
  2026-10-13 that ships this specification"), so each row stays true and
349
- gate-clean at every later release without rewording. The corrections'
367
+ accurate at later releases without rewording. The corrections'
350
368
  substance is unchanged; the specification digest moves with the
351
369
  rewording (the digest covers the whole extracted specification,
352
370
  errata included), which is recorded in the release history;
@@ -354,8 +372,7 @@ The corpus contains 190 cases, digest
354
372
 
355
373
  This is a documentation-only release; the public API, the registry, and
356
374
  the corpus are unchanged from 0.8.1, and `spec/protocol.md` is
357
- byte-identical. The test suite is 957 tests (63 properties) at 100%
358
- coverage. Corpus: 129 cases, digest
375
+ byte-identical. Corpus: 129 cases, digest
359
376
  `sha-256:WOZcBfvCW88L6TG_66vxG1fw0QN8cCXrJxveqHgI8a4`; registry
360
377
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
361
378
  digest `sha-256:aBgeih79woOR7YmJ_OBhyFgKU0j2euO-eieJKxLVDeA`.
@@ -420,86 +437,34 @@ digest `sha-256:aBgeih79woOR7YmJ_OBhyFgKU0j2euO-eieJKxLVDeA`.
420
437
  only for a `key_id` with no supplied key). Both corrections are
421
438
  recorded in `spec/errata.md`, as is the `spec/protocol.md` §5 separator table, which
422
439
  now lists the extension-schema and extension-registry separators. The conformance
423
- mutation gate breaks the implementation at seventeen named points.
440
+ specification describes these verification rules.
424
441
 
425
- The public API and the registry are unchanged. The test suite is 951
426
- tests (63 properties) at 100% coverage. Corpus: 129 cases, digest
442
+ The public API and the registry are unchanged. Corpus: 129 cases, digest
427
443
  `sha-256:WOZcBfvCW88L6TG_66vxG1fw0QN8cCXrJxveqHgI8a4`; registry
428
444
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
429
445
  digest `sha-256:CsVC7jVvA2ZP0NA6D5_h94A_ryb6F795h7ZpSo66CBA`.
430
446
 
431
447
  ## [0.8.0] - 2026-09-24
432
448
 
433
- ### Added: the release-identity consumer contract
434
-
435
- - `priv/release-metadata.json` is now a versioned public contract
436
- (`manifest_version: 2`; additive-only within a version). New fields:
437
- the manifest version, `verification_semantics_version` (the
438
- semantics/census split, unchanged at 1), the `digest_identity` label
439
- (RFC 8785 JCS + SHA-256 + domain separation + unpadded base64url,
440
- unchanged across every release), `protocol_revisions_supported`, the
441
- certified compatibility matrix `prior_census_verdicts` (the prior
442
- census `sha-256:sg6Fo7…` is certified `equivalent` by replay), and
443
- the verifier-kit identity derived from the npm package metadata. The npm kit
444
- embeds the manifest byte-identically (agreement-gated).
445
- - `priv/release-history.json`: the append-only retroactive mapping:
446
- one row per manifest-era release, every PRIOR release's row verified
447
- against derived state (the corpus digest recomputed from the loaded
448
- census bytes, the registry digest from the census index, the
449
- specification digest recomputed over the tag's tree); the current
450
- release's row is asserted against the live manifest and gains its
451
- tag verification at the next release. Semantics version 1 spans the
452
- whole manifest era through this release: the prior census replays
453
- case-perfect (observed under the preceding package on 2026-09-23;
454
- this release's gate re-establishes it mechanically on every run), so
455
- exact-pinned consumers upgrading between any of these releases keep
456
- historical replays green when they bind the semantics identity. The record also shows the specification
457
- digest moved at 0.4.0 and 0.4.1: movement the changelog prose of
458
- those releases never stated.
459
- - `mix compatibility.replay` (quality battery): certifies the
460
- compatibility claims and the history from live repository state,
461
- every manifest-era census loads through the new prior-census loader
462
- mode and replays under the current Runner (each PRIOR census also
463
- through the TS verifier, byte-compared; the current census's TS
464
- agreement is the verifier.agreement gate's duty); an
465
- `equivalent` claim with any disagreement reds, a registry-explained
466
- divergence class is gated by the registry diff, an unclaimed census,
467
- stale claim, or tampered history row reds, and a tag-less checkout
468
- refuses (a named override exists and is never a green claim).
469
- Self-proving seeded reds fire every run: four claim flips (including
470
- a self-contradictory `not_equivalent` claim), a tampered census file,
471
- a tampered history row, and both tag-absent refusal arms. The prior-census loader mode
472
- (`Corpus.load_prior_census/1`, mirrored in the TS verifier's
473
- `--prior-corpus`) suspends exactly the two current-state couplings
474
- (the compiled registry digest and the compiled applicability floor)
475
- because a released census was certified against the registry and
476
- floor of its release; the ordinary loader's couplings are unchanged
477
- and correct for conformance runs.
478
- - The Evolution clause gains the normative semantics/census law and the
479
- immutability policy (released identities are never edited in place;
480
- corrections are new releases); the upgrading guide gains the
481
- exact-pinned consumer partition (replay identity versus provenance
482
- metadata) and the fail-closed enumeration guidance; the decision
483
- record `docs/adr/release-identity-semantics.md` ships with the
484
- `no-versioning-rule` axis amendment (precedence: the wire revision,
485
- the semantics version, and the release identity are independent
486
- axes). Answering an inbound consumer request for input
487
- (an exact-pinned consumer, 2026-09-23) in full.
488
- - Consumer-rehearsal evidence remains separate from implementation conformance; no independent consumer-rehearsal evidence is included in this release.
489
-
490
- The correction the record now states plainly: the 0.6.0 corpus change
491
- was not purely additive at the byte level; the golden vectors' fixture
492
- signature rotated on unchanged covered bytes (`content_digest`
493
- identical), verdict-neutral and replay-proven, but the 0.6.0 entry's
494
- "grows 94 → 96" prose under-recorded it.
495
-
496
- The public-history privacy scan's budget grows with the repository
497
- (the scan is O(tracked files × commits)); its ceiling moves 960s →
498
- 1920s on the same evidence as every prior raise, a borderline clip on
499
- this release's tree, a timeout there being a flake, never a privacy
500
- finding.
501
-
502
- The test suite is 924 tests (59 properties) at 100% coverage. Corpus:
449
+ ### Added
450
+
451
+ - The release manifest is a versioned public contract (`manifest_version: 2`),
452
+ with verification semantics, digest identity, supported revisions, prior
453
+ census verdicts, and the npm kit identity. The kit embeds the same manifest.
454
+ - `priv/release-history.json` maps each manifest-era release to its corpus,
455
+ registry, specification, and verification-semantics identities. Semantics
456
+ version 1 spans the manifest era through this release.
457
+ - `Corpus.load_prior_census/1` and TypeScript `--prior-corpus` load each released
458
+ census using its own integrity rules, independently of the current registry
459
+ and applicability floor. Ordinary conformance loading retains those bindings.
460
+ - The specification states the semantics/census law and released-identity
461
+ immutability. The upgrading guide separates replay identity from provenance
462
+ metadata. Wire revision, verification semantics, and release identity remain
463
+ independent axes.
464
+ - The 0.6.0 corpus change also rotated the golden fixture signature over
465
+ unchanged covered bytes. Its verdicts remain equivalent.
466
+
467
+ Corpus:
503
468
  96 cases, digest
504
469
  `sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry
505
470
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
@@ -507,187 +472,77 @@ digest `sha-256:yC0gV-zIn8J8bXI5gV0dQyPmgEQgVsH6k7YOlkis37Q`.
507
472
 
508
473
  ## [0.7.1] - 2026-09-16
509
474
 
510
- ### Changed: the toolchain enforces itself (hygiene release)
511
-
512
- - The declared Elixir requirement is a supported range (`~> 1.19`: the
513
- 1.19 and 1.20 lines are admitted, and Mix refuses anything outside
514
- the range at compile), and the checkout configuration refuses any Erlang/OTP
515
- major outside the supported set (27/28/29) before anything compiles.
516
- The set was probed from the official precompiled build lists, not
517
- assumed; the decision record ships as
518
- `docs/adr/supported-otp-set.md`. The assert governs development and
519
- CI only; the Hex archive does not ship `config/`, so package
520
- consumers see no new requirement.
521
- - CI exercises every lane of the supported matrix: Elixir 1.19 on
522
- OTP 28, and Elixir 1.20 on OTP 27, 28, and 29 (the dev pin, mirrored
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)
525
- move together in one commit.
526
- - A dependency-currency gate (`mix deps.currency`; decision record at
527
- `docs/adr/dependency-currency-gate.md`) reds the battery on any
528
- resolvable drift and never passes an unverified registry state.
529
- dialyxir rides at its latest resolvable release.
530
- - Clones are byte-identical on every platform: the repository's checkout attributes
531
- disable line-ending conversion regardless of a machine's autocrlf
532
- settings (Git for Windows defaults to rewriting LF to CRLF, which
533
- would shift the byte-frozen digests). The repository tree was probed
534
- for Windows checkout obstacles (reserved device names, forbidden
535
- characters, case collisions, symlinks, path length): none found.
536
- - Development documentation re-trued to the enforced-range story
537
- (README, CONTRIBUTING, quickstart). No Livebooks ship in this
538
- repository (probed; no notebook files and no `Mix.install`
539
- anywhere), so no notebook cells were in scope. The npm kit version
540
- moves with the Hex line under the version-sync gate; no kit behavior
541
- changed.
542
-
543
- For consumers nothing reachable changed: the library surface, the
544
- conformance corpus, the registry, and the specification are
545
- byte-identical to 0.7.0, and the Elixir floor widened (1.20 to 1.19),
546
- never narrowed. The test suite is 917 tests (59 properties) at 100%
547
- coverage. Corpus: 96 cases, digest
475
+ ### Changed
476
+
477
+ - The Elixir requirement widens from 1.20 to 1.19. The supported OTP set is
478
+ 27/28/29. The Hex package does not ship checkout configuration.
479
+
480
+ The library surface, conformance corpus, registry, and specification are
481
+ byte-identical to 0.7.0.
482
+
483
+ Corpus: 96 cases, digest
548
484
  `sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry
549
485
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
550
486
  digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
551
487
 
552
488
  ## [0.7.0] - 2026-09-14
553
489
 
554
- ### Changed: the npm kit moves to `@agent-blueprint-protocol/verifier`
555
-
556
- - Portfolio naming consistency with the bounded-authority kit: the
557
- verifier publishes under a project-named npm organization with a
558
- role-named package. The 0.6.0 package
559
- (`@rjpalermo/agent-blueprint-protocol`) is deprecated with a forward
560
- pointer. Version numbering continues the protocol's single release
561
- line (the version-sync gate binds npm semver == the Hex line).
562
- - The bin gains a `verifier` alias alongside `agent-blueprint-protocol`:
563
- `npx @agent-blueprint-protocol/verifier` and
564
- `npx agent-blueprint-protocol` both work after install.
565
- - The publish workflow is fully idempotent: registry-published
566
- versions skip loudly instead of erroring (re-runs, and releases
567
- bootstrapped by a local first publish, required for a brand-new
568
- package, since a trusted publisher cannot be configured before the
569
- package exists), and the GitHub release step creates only when
570
- absent.
571
- - The no-versioning-rule npm-axis amendment records the rename and its
572
- history; every shipped mention of the old name is updated (the
573
- changelog's historical entries keep it, as records).
574
-
575
- The conformance corpus, registry, and test-suite counts are unchanged
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
578
- properties) at 100% coverage. Corpus: 96 cases, digest
490
+ ### Changed
491
+
492
+ - The verifier publishes as `@agent-blueprint-protocol/verifier`. The 0.6.0
493
+ package name (`@rjpalermo/agent-blueprint-protocol`) is retired; npm no longer
494
+ serves it. npm and Hex retain the same version.
495
+ - The bin gains a `verifier` alias alongside `agent-blueprint-protocol`.
496
+
497
+ The corpus and registry are unchanged from 0.6.0; the specification digest
498
+ changes with the kit identity.
499
+
500
+ Corpus: 96 cases, digest
579
501
  `sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry
580
502
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
581
503
  digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
582
504
 
583
505
  ## [0.6.0] - 2026-09-14
584
506
 
585
- ### Added: the installable verifier (npm kit)
586
-
587
- - `@rjpalermo/agent-blueprint-protocol` on npm: the verifier compiled
588
- to `.js` + `.d.ts` (strict, declarations, zero runtime dependencies,
589
- Node >= 24), the conformance corpus embedded byte-identically to the
590
- release-certified copy, and a single bin: `npx` verifies out of the
591
- box. The verifier itself typechecks clean for the first time (66
592
- type-level fixes, byte-frozen against the strip-types baseline).
593
- - `--artifact <file>` single-artifact mode (kit-only by design; the
594
- escript stays corpus-only): verifies one JSON file against all three
595
- artifact kinds; a valid report names the kind, a denial names each
596
- kind's typed code.
597
- - The agreement gate proves the KIT, not just the tree: npm
598
- version-sync with a one-side-bump seed, kit-vs-escript byte equality
599
- over the embedded corpus, and a single-artifact sweep replaying
600
- every text-only decode-surface corpus case with an
601
- inverted-expectation seed. `kit.build` is a quality-alias step; CI
602
- builds the kit before the battery.
603
- - The TypeScript quickstart (`documentation/typescript.md`); the ARD
604
- mapping (`docs/ard-mapping.md`; sources pinned at exact commits,
605
- trust-manifest DNA shared, the capability layer instrument-verified
606
- absent); the EU AI Act evidence anchor
607
- (`documentation/evidence-commitments.md`); the blueprint-card
608
- section in the specification (derived, non-normative, never
609
- conforming on its own) with a mirror-tested derivation in the
610
- concept guide; the no-versioning-rule npm-axis amendment (the npm
611
- semver is the fifth permitted version axis, bound equal to the Hex
612
- line).
613
- - Two new examples, both byte-exact corpus cases:
614
- `examples/signed-blueprint.json` (a producer-signed envelope over
615
- the golden digest; signing never changes the digest it covers) and
616
- `examples/extension-blueprint.json` (a registered optional
617
- namespace retained by a supporting host, quarantined byte-exactly
618
- by one without it).
507
+ ### Added
508
+
509
+ - The npm verifier includes JavaScript, TypeScript declarations, an embedded
510
+ corpus, and a CLI, with zero runtime dependencies and Node.js 24 or newer.
511
+ - `--artifact <file>` verifies one JSON file against all three artifact kinds,
512
+ naming the valid kind or each kind's typed denial.
513
+ - Consumer guides cover TypeScript, ARD discovery mapping, EU AI Act evidence,
514
+ and derived Blueprint cards. The npm version matches the Hex release.
515
+ - Signed and extension-bearing Blueprint examples are byte-exact corpus cases.
619
516
 
620
517
  ### Changed
621
518
 
622
- - The conformance corpus grows 94 → 96 cases (the two valid signed
623
- and extension-bearing decode cases); every shipped count and digest
624
- claim re-tied.
625
- - The privacy history-scan budget grows with the repository (480s →
626
- 960s; the scan is O(tracked files × commits) and clipped its old
627
- ceiling under full-suite load; a timeout there is a flake, never a
628
- privacy finding).
519
+ - The corpus grows from 94 to 96 cases with signed and extension-bearing inputs.
629
520
 
630
- The test suite is 917 tests (59 properties) at 100% coverage. The
631
- conformance corpus is 96 cases, digest
521
+ The conformance corpus is 96 cases, digest
632
522
  `sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry digest
633
523
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
634
524
  digest `sha-256:iBllJ-J8aoWUaYKI7VAqjIfXx9bqwNqWXFO4nxBTCfM`.
635
525
 
636
526
  ## [0.5.0] - 2026-09-12
637
527
 
638
- ### Fixed: the credibility floor
639
-
640
- - Dependency pull requests can go green again. The public-surface
641
- privacy history scan hard-requires the maintainer HMAC key, which
642
- GitHub never delivers to dependabot or fork runs; every dependency
643
- PR was structurally red. The gate now has exactly one relaxation:
644
- CI marks true fork pull requests `ABP_PRIVACY_SCAN=fork-skip`, where
645
- the scan skips LOUDLY (a greppable `[privacy-scan] SKIPPED` banner
646
- naming what did not run); every other mode value (including typos)
647
- fails closed exactly as before, and a fork run whose secret IS
648
- present still enforces. All three arms have regression tests; the dependency-update run passes.
649
- - The documentation-currency gate's shipped-file enumeration now globs
650
- DIRECTORY package entries: the original filter silently skipped
651
- every guide inside `"documentation"`, and the onboarding install
652
- pins had drifted into a line SECURITY.md marks unsupported.
653
- - macOS Finder artifacts (`.DS_Store`, `._*`) are excluded from the
654
- four digest/file-set walks (specification identity, both release
655
- asset walks, the corpus directory walk): a stray `.DS_Store` inside
656
- `spec/` shifted the specification digest and red the
657
- release-candidate check on any Mac that had previewed the folder.
658
-
659
- ### Added: the adoption surface
660
-
661
- - Community intake: bug-report and registry-request issue templates
662
- (the registry template follows `spec/registry/OPERATIONS.md`),
663
- GitHub Discussions, SUPPORT.md, and a how-to-propose-changes path in
664
- CONTRIBUTING, with the capability inventory explaining what is not included.
665
- - Onboarding reaches a green verification: the quickstart and getting-
666
- started guides now decode the shipped echo example to `{:ok, _}` and
667
- round-trip its canonical bytes byte-exactly (mirror-tested), state
668
- the minimum Elixir version, and keep the typed-denial teaching
669
- moment after the green path.
670
- - The worked host integration: a full `reconcile/3` over the shipped
671
- echo pair under the default `:deny` clamp posture (the typed
672
- protected-clamp denial) and under `:acknowledge` (a green Evidence
673
- record whose `not_verified` names the seven host-owned surfaces),
674
- mirror-tested line by line.
675
- - The producer signing recipe: the detached-JWS Ed25519 envelope built
676
- with `:crypto` over the RFC 7797 preimage and verified end-to-end
677
- against the shipped verifier, mirror-tested. The package itself
678
- remains verify-only.
679
- - `examples/federation-envelope.json`: the 23-member federation
680
- TaskEnvelope as a byte-exact conformance corpus case, documented in
681
- the examples guide.
682
- - The hexdocs sidebar groups the guides (getting started, concepts,
683
- guides by role, reference, specification, design records,
684
- governance).
685
- - A CI compatibility job: the previous supported Elixir/OTP pair
686
- (1.20.1 / 29.0.2) runs the test suite and the conformance corpus on
687
- every push and pull request, checking the README's support claim.
688
-
689
- The test suite is 917 tests (59 properties) at 100% coverage. The
690
- conformance corpus is unchanged at 94 cases, digest
528
+ ### Fixed
529
+
530
+ - Corrected onboarding install pins that named an unsupported release line.
531
+ - macOS Finder artifacts are excluded from specification and corpus identity
532
+ walks, preserving identities across platforms.
533
+
534
+ ### Added
535
+
536
+ - Community support includes issue templates, GitHub Discussions, SUPPORT.md,
537
+ and contribution guidance.
538
+ - Quickstart examples decode the shipped echo artifact and round-trip its
539
+ canonical bytes before demonstrating typed denials.
540
+ - Host integration examples show protected-clamp denial and acknowledged
541
+ evidence from `reconcile/3`.
542
+ - A host-side detached-JWS Ed25519 signing recipe; the package remains verify-only.
543
+ - The federation-envelope example and grouped documentation sidebar.
544
+
545
+ The conformance corpus is unchanged at 94 cases, digest
691
546
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
692
547
  `sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
693
548
  digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
@@ -696,18 +551,7 @@ digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
696
551
 
697
552
  ### Fixed: verification posture hardening
698
553
 
699
- - CI green on the public repository (GitHub Actions is free for
700
- public repos; the prior 'billing-blocked' posture was wrong and is
701
- retired). The standing CI failures are fixed: a stale reprove copy
702
- path (a pre-promotion directory that never exists in a fresh
703
- checkout) crashed the release-candidate check.
704
- - The README test-count claim is tied to the suite-REGISTERED count,
705
- not just the source macro census: the release-candidate check
706
- asserts macro census == registered count == README claim (both
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.
554
+ - The specification includes a foundation-transition asset inventory.
711
555
 
712
556
  The conformance corpus is unchanged at 94 cases, digest
713
557
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
@@ -718,21 +562,10 @@ digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
718
562
 
719
563
  ### Added: examples gallery + minutes-long quickstart
720
564
 
721
- - `examples/`: complete, corpus-verified artifact pairs, byte-exact
722
- conformance corpus cases (the gallery gate proves it against the
723
- corpus on every build; a drifted example reds). The echo pair
724
- (blueprint + deployment) is annotated member-by-member in the
725
- examples guide.
726
- - The quickstart (`documentation/quickstart.md`): from `mix deps.get`
727
- to a green verification in `iex`; no heavyweight gates; its
728
- result-claiming lines are mirror-tested like every guide example.
729
- - The documentation corpus: 13 adopter guides (getting started, the
730
- artifacts, extension authoring, host integration, producing,
731
- portability, the full 74-code error guide, federation, registry,
732
- upgrading, FAQ, operations), every file an ex_doc extra, every
733
- result-claiming example executed against the real package by the
734
- mirror gate; README as a decision document (when to use, when NOT
735
- to use).
565
+ - Complete, byte-exact example artifact pairs with member-by-member annotations.
566
+ - A quickstart from dependency setup to verification in `iex`.
567
+ - Thirteen adopter guides cover artifacts, extensions, host integration,
568
+ producing, portability, errors, federation, upgrading, and common questions.
736
569
 
737
570
  The conformance corpus is unchanged at 94 cases, digest
738
571
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
@@ -758,27 +591,13 @@ The normative specification is a specification in the standards sense:
758
591
  considerations as the data-minimization profile with honest limits;
759
592
  the positioning boundary (AI Catalog owns discovery + identity +
760
593
  attestation; this protocol owns the portable contract layer).
761
- - Machine-readable grammar: CDDL (RFC 8610) normative under
762
- spec/grammar/ with JSON Schema derived (never hand-edited); bound
763
- to the compiled tables and the corpus goldens by the
764
- grammar-derivation gate.
765
- - Registry data governance: spec/registry/registry.json as the
766
- governance-canonical source, bound to both compiled twins and the
767
- corpus index by the registry-equality gate (all four carriers
768
- verified at sha-256:FG2f38K0…).
769
- - Governance pack: spec-scoped IPR (Apache-2.0 + DCO, no CLA,
770
- donation-ready), FOUNDATION-TRANSITION inventory, registry
771
- operations process, errata policy; root CONTRIBUTING (the
772
- verification battery published) and CODE_OF_CONDUCT. Steward: the
773
- unincorporated BaseLabs org, Russ Palermo as named maintainer.
774
- - The release identity chain: priv/release-metadata.json pins the
775
- specification digest, package version, corpus and registry digests,
776
- and the corpus index hash, asserted from live state on every run.
777
- - Specification extraction is a tested proof (spec/ + the conformance
778
- corpus extract self-contained; the CI job runs the literal
779
- repository-filter extraction).
780
-
781
- Every new gate is tested against a deliberately introduced fault by the release-candidate check (74 faults).
594
+ - Normative RFC 8610 CDDL grammars with derived JSON Schemas.
595
+ - `spec/registry/registry.json` is the canonical registry source.
596
+ - Governance documents cover Apache-2.0 licensing, DCO sign-off, foundation
597
+ transition, registry operations, and errata.
598
+ - `priv/release-metadata.json` identifies the specification, package, corpus,
599
+ registry, and corpus index.
600
+ - The specification and corpus form a self-contained normative tree.
782
601
 
783
602
  The conformance corpus is unchanged at 94 cases, digest
784
603
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
@@ -793,10 +612,7 @@ The conformance corpus is unchanged at 94 cases, digest
793
612
  requirement semantics).
794
613
  - SECURITY.md's supported-version table names the 0.2.x line (0.1.x is
795
614
  no longer supported; upgrade to the current line).
796
- - Two changelog entries cited an internal working document by section
797
- number (a document that ships nowhere); both are reworded to
798
- self-contained prose, and a new document-citation gate (below) keeps
799
- the class dead.
615
+ - Changelog citations now use self-contained prose.
800
616
  - `spec/protocol.md` states the producer surface explicitly in its
801
617
  shipped-surface section (`Blueprint.from_value/2`,
802
618
  `Deployment.from_value/2`, the per-artifact `content_digest/1` and
@@ -806,21 +622,7 @@ The conformance corpus is unchanged at 94 cases, digest
806
622
  repository URLs, each pinned by plain SHA-1 of the served bytes
807
623
  (A2A `lf.a2a.v1` line at commit `cfc9d34b`; the MCP Tasks extension
808
624
  draft at commit `0d0a6bd4`).
809
- - README rewritten for external readers: CI, Hex version, and license
810
- badges; an outsider-readable status section; current test and corpus
811
- counts.
812
-
813
- ### Added: documentation gates
814
-
815
- - Documentation-currency gate: README,
816
- SECURITY.md, and CHANGELOG version claims, install pins, count
817
- claims, and the current release's corpus identity (digest and case
818
- total) are checked against the live project on every run.
819
- - Document-citation gate: shipped
820
- markdown documents may cite only documents that exist; a named
821
- section citation must name a shipped document or a pinned external
822
- standard, and every repository-relative link must resolve to a real
823
- file.
625
+ - README install and status guidance is written for external readers.
824
626
 
825
627
  The conformance corpus is unchanged at 94 cases, digest
826
628
  `sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
@@ -843,11 +645,8 @@ The conformance corpus is unchanged at 94 cases, digest
843
645
  hand-tiered as uniform-depth strict tiers because the bounded dialect denies
844
646
  `$ref` cycles; portable condition depth is three composite tiers
845
647
  (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`.
846
- - The schema document ships as corpus data
847
- for that release; the library records only
848
- the digest pin, and a test binds the pin to the SHIPPED document (the corpus
849
- index hashes raw file bytes, the pin hashes JCS of the parsed document; the
850
- test is the bridge between the two domains).
648
+ - The schema document ships as corpus data; the library records its canonical
649
+ schema digest pin.
851
650
  - The conformance corpus grows 88 → 94 cases: the validated-channel cells
852
651
  (valid attach with matching schema, schema absent, digest mismatch,
853
652
  criticality conflict, the tier-bound deny) and the deprecated-optional
@@ -870,37 +669,13 @@ The conformance corpus is unchanged at 94 cases, digest
870
669
 
871
670
  ### Fixed
872
671
 
873
- - Cross-vendor review fix pass: the schema document bounds
874
- `definition.name` with `maxLength: 128` (the free-form string in a body
875
- that skips the portability value-shape heuristics; the schema is the
876
- bound on that surface); the registry's closed-schema lens test now fails
877
- loudly for any future pinned namespace without its own document binding;
878
- stale 0.1.x release-line claims and the generator's section counts were
879
- reconciled to 0.2.0.
880
- - The second-language verifier's schema `items` evaluation had its schema and
881
- instance arguments swapped, so no cross-language case had ever actually
882
- validated array items (object-shaped items passed vacuously; scalar items
883
- crashed the verifier). The estate-contract tier schemas are the first
884
- corpus-bearing `items` user; the byte-identical agreement gate now proves
885
- both languages validate items identically.
672
+ - The schema bounds `definition.name` to 128 bytes, including bodies validated
673
+ through the authored-extension channel.
674
+ - The TypeScript schema validator now evaluates array `items` with the correct
675
+ schema and instance arguments, matching the Elixir implementation.
886
676
 
887
677
  ### Changed
888
678
 
889
- - The gitleaks secret-scan configuration was invalid TOML (a string
890
- concatenation TOML does not support) and, independently, nothing executed
891
- it; no CI job or alias ran gitleaks, so a committed credential would have
892
- passed the complete quality gate. The config now parses (the corpus key
893
- fragment is matched via a single-character class instead of concatenation),
894
- the generated conformance corpus is allowlisted by path (per-value fragments
895
- had rotted: the federation corpus keys were uncovered), and CI runs a
896
- full-history gitleaks v8.30.1 scan as its own job, pinned to the release
897
- commit. Red-proven against a staged canary secret; every finding the
898
- allowlists suppress was adjudicated as deterministic public-by-construction
899
- fixture material.
900
- - GitHub CI now selects Node 24.19.0 through the immutable `setup-node` v7.0.0
901
- commit before running the complete quality gate. This removes dependence on
902
- the runner image's ambient Node release while preserving the verifier's
903
- Node 24 minimum.
904
679
  - The normative protocol header and README introduction were reconciled to the
905
680
  live public 0.1.x package state (obsolete pre-publication/release-candidate
906
681
  framing removed).
@@ -913,7 +688,6 @@ The conformance corpus is unchanged at 94 cases, digest
913
688
  records (`docs/adr/`), and `docs/federation-mapping.md` joins the
914
689
  hexdocs extras, matching the house packaging convention of the
915
690
  published `bounded_authority_protocol` package.
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.
917
691
  - README restructured to the house convention: Installation directly
918
692
  after the introduction, a function-level "What it provides" section,
919
693
  and the documentation packaging boundary stated.
@@ -924,7 +698,7 @@ Initial public release: the Agent Blueprint Protocol, its Elixir
924
698
  reference implementation, the conformance corpus, and the
925
699
  second-language verifier.
926
700
 
927
- ### Normative docs + release-candidate gates
701
+ ### Normative documentation
928
702
 
929
703
  - `spec/protocol.md`: the normative protocol document (ships in the Hex
930
704
  archive): artifacts and the closed member registries, bounded bytes
@@ -933,68 +707,35 @@ second-language verifier.
933
707
  compiled registry's first-release entries, the bounds algebra laws,
934
708
  the 74-code error vocabulary, the evidence contract, and the
935
709
  conformance corpus identity (88 cases at the recorded digest).
936
- - Build-verification records stay in the repository. Every quality step, architecture test, and conformance check is tested against a deliberately introduced fault.
937
710
  - `docs/adr/` (repository-side, slug-only filenames): the seven
938
711
  decisions of record:
939
712
  the non-authorizing boundary, the detached JWS envelope, the
940
713
  two-consumer amendment, deny-default protected-bound clamps, the
941
714
  compiled-in registry (closing the package-boundary contradiction of
942
715
  record), the federation lanes, and the no-versioning rule.
943
- - New architecture gates, both red-proven at birth:
944
- - **publish guard**: no internal-planning reference, private-tool
945
- path, or home-directory path in any archived file (byte patterns
946
- plus word-bounded text patterns that cannot false-positive inside
947
- base64url tokens; registry owner/namespace/URI data is published by
948
- design and exempted on record);
949
- - **spec coverage**: every public function carries a matching
950
- `@spec` (default-arity rule recorded) and every shipped module's
951
- moduledoc states the non-authorizing boundary (39 modules gained
952
- an honest stance sentence; `ExtensionRegistry.federation_schema/0`
953
- gained its missing `@spec`).
954
- - `mix release.candidate` (also in `mix quality`): re-derives 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
956
- shipped implementation (facade functions, registry namespaces, corpus
957
- digest and case total, the stance sentence).
958
- - Internal-reference scrub of the shipped surface: tracker numerals,
959
- internal design-shorthand citations, and a portfolio-terminology
960
- section removed from `docs/federation-mapping.md`, README, CHANGELOG,
961
- and `lib/` comments/`@doc`s (comments and docs only; zero behavior
962
- change).
963
716
  - README Status and Installation rewritten to the published 0.1.0
964
717
  state.
965
718
 
966
- ### Second-language verifier + agreement gate
719
+ ### Second-language verifier
967
720
 
968
721
  - `conformance/verifier/`: the repo-side TypeScript verifier (Node ≥ 24,
969
722
  `node:` builtins only, zero npm runtime deps; never in the Hex archive):
970
723
  an independent recomputation of every corpus surface and integrity check,
971
724
  with a CLI byte-compatible with the Elixir escript (`--corpus` required;
972
725
  exit 0/1/2; report bytes on stdout, no trailing newline).
973
- - `mix verifier.agreement` (in `mix quality`): byte-agrees the TS report
974
- with the escript's over the repo corpus AND the built Hex archive's,
975
- runs the self-check battery (RFC 8785 Appendix B three-way, the integer-window
976
- matrix incl. the mis-round lexeme, Ed25519 key acceptance, stored
977
- JOSE vectors), and proves three seeded reds fire (verdict inversion,
978
- report member drift, window-check deletion), with a calibration
979
- self-proof of the raise path.
980
726
  - The stored detached-JWS vectors are KAT-
981
727
  anchored to RFC 8032 §7.1 TEST 1, verified Elixir-signed → node-verified
982
728
  in both detached and compact forms.
983
729
  - `Signature`: small-order key rejection hardened: the identity (order 1)
984
- and order-2 encodings no longer pass `usable_ed25519_key?` (found by the
985
- mirror's torsion battery; latent on this OTP).
730
+ and order-2 encodings no longer pass `usable_ed25519_key?`.
986
731
  - `Federation.decode`: an empty claim value or compatibility identity now
987
732
  denies `:invalid_constraint` instead of raising `FunctionClauseError`
988
- (never-raising posture restored; found by the mirror's parity battery).
733
+ (typed denial replaces the exception).
989
734
  - `Conformance.Runner`: a malformed observed identity element denies typed
990
- `:invalid_type` instead of raising (the prior-receipts pattern).
735
+ `:invalid_type` instead of raising.
991
736
  - Corpus regenerated to 88 cases (digest
992
- `sha-256:QsRbWGreygTJ0m47csgfpwYtoNId3FbjNP49sK-X-MY`): two
993
- obligation-varying intersect cases pin the protected-bound meet direction
994
- inside corpus agreement (previously corpus-invisible; carried by the
995
- verifier's vectors); the mutation gate gains an `obligation-meet-min`
996
- entry (7 total). The real-escript end-to-end test covers the halt shim's
997
- exit contract in-suite (the coverage-exclusion ack's substance).
737
+ `sha-256:QsRbWGreygTJ0m47csgfpwYtoNId3FbjNP49sK-X-MY`), including two
738
+ obligation-varying intersection cases.
998
739
 
999
740
  ### Conformance corpus subsystem
1000
741
 
@@ -1006,9 +747,6 @@ second-language verifier.
1006
747
  identity, and an escript CLI (`--corpus` required; exit 0/1/2).
1007
748
  - `priv/conformance/`: 86 shipped cases, full-registry goldens (evidence
1008
749
  members included), RFC 8785 vectors, deterministic key fixtures.
1009
- - `mix conformance.verify` + `mix conformance.mutations` wired into
1010
- `mix quality`, five named implementation mutations each proven to redden
1011
- the corpus, plus a corpus-expectation-flip calibration entry.
1012
750
  - `ExtensionRegistry.digest/0` (+ the `:extension_registry` digest domain):
1013
751
  the corpus-registry binding.
1014
752
  - Facade: `canonical_bytes/1` (the named canonicalize gap) and typed
@@ -1017,7 +755,6 @@ second-language verifier.
1017
755
  - Eight new error codes: the seven corpus integrity codes + the recorded
1018
756
  `:corpus_case_invalid` addition.
1019
757
 
1020
-
1021
758
  ### Added
1022
759
 
1023
760
  - Federation profile: `AgentBlueprintProtocol.Federation` with
@@ -1039,12 +776,12 @@ second-language verifier.
1039
776
  `:federation_terminal_conflict` on any divergence between receipts for
1040
777
  one task identity. Facade rows `decode_federation_envelope/2` and
1041
778
  `federation_mapping/0` (the 23-row mapping as data, bijective with the
1042
- envelope's members by an architecture gate). Published mapping doc
779
+ envelope's members). Published mapping doc
1043
780
  `docs/federation-mapping.md` with the pinned live sources, the A2A
1044
781
  primary / MCP draft-tracking flag and revisit trigger, and the
1045
782
  ttlMs-is-not-an-execution-bound, AUTH_REQUIRED-is-not-authorization,
1046
783
  and AgentCard protobuf pre-normalization notes.
1047
- - Federation hardening (independent review): a
784
+ - Federation hardening: a
1048
785
  signature whose signed `purpose` is not `federation-envelope` never
1049
786
  verifies a federation receipt (the symmetric cross-surface purpose gap, closed
1050
787
  on this surface; cross-surface signature lifting denied
@@ -1078,19 +815,17 @@ second-language verifier.
1078
815
  boundary is shape-checked, never echoed, and never survives
1079
816
  verification without the key.
1080
817
  - Error vocabulary: `:forbidden_portable_value` is now declared and
1081
- emitted through per-site literals (the per-site vocabulary walk could
1082
- not see the module-attribute-carried emission: a live closedness hole,
1083
- closed with a staged red); the federation codes
818
+ emitted through per-site literals; the federation codes
1084
819
  `:federation_state_unmappable`, `:federation_mapping_conflict`,
1085
820
  `:nonportable_content`, `:audience_mismatch`, and
1086
821
  `:federation_terminal_conflict` declared exactly as emitted.
1087
822
 
1088
- - Reconcile hardening (independent review): the
823
+ - Reconcile hardening: the
1089
824
  composed pass gates non-object artifact roots at the canonical stage
1090
825
  (typed denial, never a raise); `Reconcile.Inputs` drops the unused
1091
826
  observed-identities field (the eight-stage pass performs no
1092
827
  compatibility verification; hosts call `verify_compatibility/2`;
1093
- recorded contract delta); the portability stage mirrors each
828
+ explicit contract change); the portability stage mirrors each
1094
829
  artifact's own per-position scan modes (authored schema documents and
1095
830
  predicate operands, the blueprint's five identifier member tables,
1096
831
  strict elsewhere) instead of strict-scanning everything; `Evidence
@@ -1099,9 +834,7 @@ second-language verifier.
1099
834
  and closed four-member entries, and case-folds range tags (LATEST
1100
835
  denies like latest); signatures checks carry the entry count as
1101
836
  detail; the two facade delegates deny typed on malformed
1102
- arguments; the vocabulary gate treats sigil-built code positions as
1103
- dynamic build failures, sees piped call sites, and fixes the
1104
- case/cond branch tag.
837
+ arguments.
1105
838
  - Reconcile, compatibility, and the evidence record:
1106
839
  `AgentBlueprintProtocol.Reconcile.reconcile/3`, the one call per
1107
840
  import, running the pinned stage order canonical → digest →
@@ -1132,17 +865,14 @@ second-language verifier.
1132
865
  authority, effect_ownership, execution, billing, evaluation_truth),
1133
866
  never replacing them; callers may only add. The facade gains
1134
867
  `verify_compatibility/2` and `reconcile/3`, and `Error.code` widens
1135
- to carry the `{:ceiling, key}` family. All eight reconcile stage
1136
- guards and the Evidence constructor are mutation-redded (each guard's
1137
- removal fails its committed tamper or order test).
868
+ to carry the `{:ceiling, key}` family.
1138
869
 
1139
870
  - Bounds-algebra hardening pass: classification comparison
1140
871
  moves to the PRODUCT order the meet computes in (ordinal ≤ AND markers
1141
872
  ⊇); a marker dropped at ANY ordinal is a widening (obligations are not
1142
873
  tradeable against scope), `widens?` becomes `¬(a ⪯ b)` and so
1143
- fail-closed on every incomparable pair (an independent review's
1144
- blocking finding: `{pci}` vs `{phi}` previously compared non-widening
1145
- in both directions), and `narrower` requires both components. The rim is now
874
+ fail-closed on every incomparable pair (`{pci}` vs `{phi}` previously
875
+ compared non-widening in both directions), and `narrower` requires both components. The rim is now
1146
876
  deny-typed everywhere it previously raised on struct-bypass inputs:
1147
877
  hostile map keys and unknown/extra names deny `:bound_unknown` with the
1148
878
  CONTAINING surface as subject (never the attacker key; the echo
@@ -1156,8 +886,7 @@ second-language verifier.
1156
886
  (decode already enforced both), bound values above the parse profile's
1157
887
  declared integer magnitude deny, `widens?`/`narrower` never raise on
1158
888
  forged values (total predicates, fail-closed in the widening
1159
- direction), and `Result.t`'s clamps type resolves its module. Every
1160
- fix re-probed live against the finding's original probe input.
889
+ direction), and `Result.t`'s clamps type resolves its module.
1161
890
  - Bounds algebra: `AgentBlueprintProtocol.BoundsAlgebra`:
1162
891
  the pointwise narrowest intersection of the Blueprint's declared
1163
892
  bounds, the Deployment's `host_bounds`, and the host's live policy over
@@ -1165,8 +894,7 @@ second-language verifier.
1165
894
  (scope families narrow at the low end; authority/approval/effect
1166
895
  narrow at the STRICT end; classification markers are
1167
896
  retained regulatory obligations whose effective set is the UNION of
1168
- the sources' sets; dropping one is the widening the mutation gate
1169
- names). Protected narrowings never happen silently: under the default
897
+ the sources' sets; dropping one is a widening). Protected narrowings never happen silently: under the default
1170
898
  `:deny` posture they deny `:protected_bound_clamp_denied` carrying
1171
899
  the field/requested/effective triple; under `:acknowledge` they clamp
1172
900
  with `acknowledged: true` evidence ALWAYS. Operational narrowings
@@ -1191,46 +919,7 @@ second-language verifier.
1191
919
  The new `AgentBlueprintProtocol.Error{code, subject, detail}` record
1192
920
  (typed shape, string subject paths, `detail` only for the
1193
921
  protected deny) lands with the algebra surface; the facade gains
1194
- `intersect/1`. Property lane: idempotent/commutative/associative
1195
- (pinned fold encoding), `not widens?(effective, host)` universal,
1196
- clamp iff `effective ≠ requested`, marker-union law, with the
1197
- min→max, marker-intersection, direction-flip, struct-default, and
1198
- silent-path mutations each proven RED against them.
1199
-
1200
- ### Fixed
1201
-
1202
- - The bounds-algebra rim's coverage claim was corrected to a true
1203
- 100% (measured 2026-08-22: the then-committed suite reached only
1204
- 97.7%; the deny-typed rim's catch-all clauses had no tests). The rim probes now ship as tests: struct-bypass forged
1205
- values through `widens?/2` and `Bound.narrower/2` for every family,
1206
- wrong-shape cost at construction, non-map `new/1`, absent-name
1207
- `fetch/2`, non-`Sources`/junk-posture/non-set-source `intersect/1`,
1208
- and the `host_bounds` lifter shape matrix (absent, malformed member,
1209
- malformed value, off-lattice ordinal, non-string on a protected
1210
- name), each asserting the typed denial or fail-closed verdict.
1211
- Eleven representative rim mutations each redded their test before
1212
- restore. Two provably unreachable arms were removed (the only
1213
- production change): `widens_value/3`'s unknown-name arm (its only
1214
- caller iterates `names/0`, always `@table` keys) and `member_of/2`'s
1215
- `{:object, _}` clause (no call site passes an object tuple).
1216
- An independent re-review of the follow-up range then found the rim's
1217
- one remaining hole: `widens?/2` matched any `%BoundSet{}` regardless
1218
- of `bounds`' type, so a struct-forged `%BoundSet{bounds: nil}` raised
1219
- `BadMapError` from either argument position instead of failing
1220
- closed (the head now guards `is_map` on both, dropping the forgery
1221
- to the fail-closed catch-all), plus its guard-family sibling
1222
- `BoundSet.to_map/1` (same forged shape raised; now deny-typed
1223
- `:invalid_type` with subject `["bound_set"]`). Both probed red
1224
- before the fix, green after.
1225
- `mix quality` has reported a true 100.00% since.
1226
- - A one-off suite flake, root-caused: the
1227
- "mutating the signatures member" test replaced the first `A` in the
1228
- base64url signature, which lands on the FINAL character ~7% of random
1229
- signatures (the one position whose value is canonicality-constrained)
1230
- producing a correctly-rejected non-canonical string
1231
- (`:signature_malformed`). The tamper now targets the first character
1232
- (a significant 6-bit position at every base64url length), making the
1233
- test deterministic for every key.
922
+ `intersect/1`.
1234
923
 
1235
924
  ### Core surfaces
1236
925
 
@@ -1267,16 +956,12 @@ second-language verifier.
1267
956
  both tables carry one definition, and `Negotiation` resolves the
1268
957
  artifact kind from the digest member so each
1269
958
  artifact's `required_core_fields` check against its own vocabulary. The
1270
- facade gains `decode_deployment/2`, and a new architecture gate proves
1271
- the no-second-pipeline invariant (delegation to `Registry.validate` plus
1272
- no local stage definitions; planted-red proven, after the exports-only
1273
- form was found vacuous by the same mutation).
959
+ facade gains `decode_deployment/2`.
1274
960
  - Deployment hardening pass: `verify_binding/3` gains a
1275
961
  stage-0 shape totality: a non-object root, DUPLICATE root members, or a
1276
962
  malformed `tool_bindings` entry (shape, operands, digest) denies before
1277
963
  any cross-artifact judgment, and validated entries thread every later
1278
- stage (the blocking finding of an independent review: malformed
1279
- bindings were silently discarded, failing OPEN); negotiation restores revision-first
964
+ stage (malformed bindings were silently discarded); negotiation restores revision-first
1280
965
  order ahead of the new artifact-kind resolution, which now requires a
1281
966
  well-formed string digest member (a malformed tag is machinery
1282
967
  `:invalid_type`); the exact-version detector becomes one total charset
@@ -1301,8 +986,7 @@ second-language verifier.
1301
986
  / `:extension_schema_digest_mismatch`); and a reserved-semantics
1302
987
  denylist (bound-shaped member names, camelCase twins included) over ALL
1303
988
  extension bodies. The registry (`ExtensionRegistry`) is compiled-in
1304
- data (drift unrepresentable, backed by a new beam-census gate that
1305
- asserts no shipped module touches the filesystem (planted-red proven)),
989
+ data that requires no filesystem access,
1306
990
  carrying the five first-release entries with `com.example/federation`'s schema
1307
991
  authored in-repo under the new `:extension_schema` digest domain.
1308
992
  `Blueprint.from_value/2`'s `:authored_extensions` option opens the
@@ -1365,9 +1049,8 @@ second-language verifier.
1365
1049
  RFC 7515 compact serialization with the RFC 7797 `b64=false` unencoded
1366
1050
  detached payload: the signing input is
1367
1051
  `BASE64URL(JCS(protected_header)) || "." || JCS(signed_attributes)`,
1368
- Ed25519 verified through `:crypto`, verify-only (an architecture gate
1369
- enforces no `:crypto.sign` call, no private-key parameters, and no
1370
- key-material shape anywhere in the shipped source). Host-supplied trusted
1052
+ Ed25519 verified through `:crypto`, with no signing or private-key inputs.
1053
+ Host-supplied trusted
1371
1054
  keys match by `key_id` (`:signature_key_unsupported` when absent,
1372
1055
  `:signature_not_verified` on divergence; facts, never authorization).
1373
1056
  The exact four-member protected header (`alg/crit/b64/kid`) and the five