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