@agent-blueprint-protocol/verifier 0.7.0
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 +891 -0
- package/LICENSE +190 -0
- package/NOTICE +4 -0
- package/README.md +199 -0
- package/dist/corpus/cases/base64url-decode.json +1 -0
- package/dist/corpus/cases/blueprint-decode.json +1 -0
- package/dist/corpus/cases/bounds-new.json +1 -0
- package/dist/corpus/cases/bounds_algebra-intersect.json +1 -0
- package/dist/corpus/cases/canonicalization-encode.json +1 -0
- package/dist/corpus/cases/compatibility-verify.json +1 -0
- package/dist/corpus/cases/deployment-decode.json +1 -0
- package/dist/corpus/cases/digest-tagged.json +1 -0
- package/dist/corpus/cases/extension-resolve.json +1 -0
- package/dist/corpus/cases/federation-decode.json +1 -0
- package/dist/corpus/cases/federation-verify_commitment.json +1 -0
- package/dist/corpus/cases/json-decode.json +1 -0
- package/dist/corpus/cases/negotiation-negotiate.json +1 -0
- package/dist/corpus/cases/portability-scan.json +1 -0
- package/dist/corpus/cases/schema-validate_instance.json +1 -0
- package/dist/corpus/cases/signature-verify.json +1 -0
- package/dist/corpus/index.json +1 -0
- package/dist/corpus/schemas/estate-contract.schema.json +1 -0
- package/dist/corpus/schemas/object.schema.json +1 -0
- package/dist/corpus/vectors/blueprint-golden.json +1 -0
- package/dist/corpus/vectors/deployment-golden.json +1 -0
- package/dist/corpus/vectors/rfc8785-numbers.json +1 -0
- package/dist/kit/cli.mjs +24 -0
- package/dist/verifier/b64url.d.ts +16 -0
- package/dist/verifier/b64url.js +36 -0
- package/dist/verifier/blueprint.d.ts +56 -0
- package/dist/verifier/blueprint.js +795 -0
- package/dist/verifier/bounds.d.ts +19 -0
- package/dist/verifier/bounds.js +45 -0
- package/dist/verifier/bounds_algebra.d.ts +27 -0
- package/dist/verifier/bounds_algebra.js +282 -0
- package/dist/verifier/canonical.d.ts +17 -0
- package/dist/verifier/canonical.js +160 -0
- package/dist/verifier/cli.d.ts +1 -0
- package/dist/verifier/cli.js +149 -0
- package/dist/verifier/compatibility.d.ts +22 -0
- package/dist/verifier/compatibility.js +112 -0
- package/dist/verifier/corpus.d.ts +42 -0
- package/dist/verifier/corpus.js +672 -0
- package/dist/verifier/decode.d.ts +16 -0
- package/dist/verifier/decode.js +457 -0
- package/dist/verifier/deployment.d.ts +49 -0
- package/dist/verifier/deployment.js +830 -0
- package/dist/verifier/digest.d.ts +23 -0
- package/dist/verifier/digest.js +58 -0
- package/dist/verifier/extension.d.ts +11 -0
- package/dist/verifier/extension.js +75 -0
- package/dist/verifier/federation.d.ts +76 -0
- package/dist/verifier/federation.js +817 -0
- package/dist/verifier/negotiation.d.ts +29 -0
- package/dist/verifier/negotiation.js +324 -0
- package/dist/verifier/portability.d.ts +12 -0
- package/dist/verifier/portability.js +184 -0
- package/dist/verifier/predicate.d.ts +10 -0
- package/dist/verifier/predicate.js +172 -0
- package/dist/verifier/registry.d.ts +16 -0
- package/dist/verifier/registry.js +120 -0
- package/dist/verifier/registry_engine.d.ts +42 -0
- package/dist/verifier/registry_engine.js +220 -0
- package/dist/verifier/report.d.ts +13 -0
- package/dist/verifier/report.js +29 -0
- package/dist/verifier/run_corpus.d.ts +1 -0
- package/dist/verifier/run_corpus.js +81 -0
- package/dist/verifier/runner.d.ts +20 -0
- package/dist/verifier/runner.js +778 -0
- package/dist/verifier/schema.d.ts +20 -0
- package/dist/verifier/schema.js +623 -0
- package/dist/verifier/self_checks.d.ts +1 -0
- package/dist/verifier/self_checks.js +316 -0
- package/dist/verifier/signature.d.ts +23 -0
- package/dist/verifier/signature.js +226 -0
- package/dist/verifier/value.d.ts +44 -0
- package/dist/verifier/value.js +77 -0
- package/package.json +42 -0
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,891 @@
|
|
|
1
|
+
# Changelog
|
|
2
|
+
|
|
3
|
+
All notable public changes to `agent_blueprint_protocol` are documented here.
|
|
4
|
+
|
|
5
|
+
## [0.7.0] — 2026-09-14
|
|
6
|
+
|
|
7
|
+
### Changed — the npm kit moves to `@agent-blueprint-protocol/verifier`
|
|
8
|
+
|
|
9
|
+
- Portfolio naming consistency with the bounded-authority kit: the
|
|
10
|
+
verifier publishes under a project-named npm organization with a
|
|
11
|
+
role-named package. The 0.6.0 package
|
|
12
|
+
(`@rjpalermo/agent-blueprint-protocol`) is deprecated with a forward
|
|
13
|
+
pointer. Version numbering continues the protocol's single release
|
|
14
|
+
line (the version-sync gate binds npm semver == the Hex line).
|
|
15
|
+
- The bin gains a `verifier` alias alongside `agent-blueprint-protocol`
|
|
16
|
+
— `npx @agent-blueprint-protocol/verifier` and
|
|
17
|
+
`npx agent-blueprint-protocol` both work after install.
|
|
18
|
+
- The publish workflow is fully idempotent: registry-published
|
|
19
|
+
versions skip loudly instead of erroring (re-runs, and releases
|
|
20
|
+
bootstrapped by a local first publish — required for a brand-new
|
|
21
|
+
package, since a trusted publisher cannot be configured before the
|
|
22
|
+
package exists), and the GitHub release step creates only when
|
|
23
|
+
absent.
|
|
24
|
+
- The no-versioning-rule npm-axis amendment records the rename and its
|
|
25
|
+
history; every shipped mention of the old name is updated (the
|
|
26
|
+
changelog's historical entries keep it, as records).
|
|
27
|
+
|
|
28
|
+
The conformance corpus, registry, and test-suite counts are unchanged
|
|
29
|
+
from 0.6.0; the specification digest moves with the deferred-work
|
|
30
|
+
registry row naming the kit. The test suite is 917 tests (59
|
|
31
|
+
properties) at 100% coverage. Corpus: 96 cases, digest
|
|
32
|
+
`sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry
|
|
33
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
|
|
34
|
+
digest `sha-256:UkpTfB07D8H8xxtuqDysU-xIXFCKovkaUn7_aiR-tAs`.
|
|
35
|
+
|
|
36
|
+
## [0.6.0] — 2026-09-14
|
|
37
|
+
|
|
38
|
+
### Added — the installable verifier (npm kit)
|
|
39
|
+
|
|
40
|
+
- `@rjpalermo/agent-blueprint-protocol` on npm: the verifier compiled
|
|
41
|
+
to `.js` + `.d.ts` (strict, declarations, zero runtime dependencies,
|
|
42
|
+
Node >= 24), the conformance corpus embedded byte-identically to the
|
|
43
|
+
release-certified copy, and a single bin — `npx` verifies out of the
|
|
44
|
+
box. The verifier itself typechecks clean for the first time (66
|
|
45
|
+
type-level fixes, byte-frozen against the strip-types baseline).
|
|
46
|
+
- `--artifact <file>` single-artifact mode (kit-only by design; the
|
|
47
|
+
escript stays corpus-only): verifies one JSON file against all three
|
|
48
|
+
artifact kinds; a valid report names the kind, a denial names each
|
|
49
|
+
kind's typed code.
|
|
50
|
+
- The agreement gate proves the KIT, not just the tree: npm
|
|
51
|
+
version-sync with a one-side-bump seed, kit-vs-escript byte equality
|
|
52
|
+
over the embedded corpus, and a single-artifact sweep replaying
|
|
53
|
+
every text-only decode-surface corpus case with an
|
|
54
|
+
inverted-expectation seed. `kit.build` is a quality-alias step; CI
|
|
55
|
+
builds the kit before the battery.
|
|
56
|
+
- The TypeScript quickstart (`documentation/typescript.md`); the ARD
|
|
57
|
+
mapping (`docs/ard-mapping.md` — sources pinned at exact commits,
|
|
58
|
+
trust-manifest DNA shared, the capability layer instrument-verified
|
|
59
|
+
absent); the EU AI Act evidence anchor
|
|
60
|
+
(`documentation/evidence-commitments.md`); the blueprint-card
|
|
61
|
+
section in the specification (derived, non-normative, never
|
|
62
|
+
conforming on its own) with a mirror-tested derivation in the
|
|
63
|
+
concept guide; the no-versioning-rule npm-axis amendment (the npm
|
|
64
|
+
semver is the fifth permitted version axis, bound equal to the Hex
|
|
65
|
+
line).
|
|
66
|
+
- Two new examples, both byte-exact corpus cases:
|
|
67
|
+
`examples/signed-blueprint.json` (a producer-signed envelope over
|
|
68
|
+
the golden digest — signing never changes the digest it covers) and
|
|
69
|
+
`examples/extension-blueprint.json` (a registered optional
|
|
70
|
+
namespace retained by a supporting host, quarantined byte-exactly
|
|
71
|
+
by one without it).
|
|
72
|
+
|
|
73
|
+
### Changed
|
|
74
|
+
|
|
75
|
+
- The conformance corpus grows 94 → 96 cases (the two valid signed
|
|
76
|
+
and extension-bearing decode cases); every shipped count and digest
|
|
77
|
+
claim re-tied.
|
|
78
|
+
- The privacy history-scan budget grows with the repository (480s →
|
|
79
|
+
960s; the scan is O(tracked files × commits) and clipped its old
|
|
80
|
+
ceiling under full-suite load — a timeout there is a flake, never a
|
|
81
|
+
privacy finding).
|
|
82
|
+
|
|
83
|
+
The test suite is 917 tests (59 properties) at 100% coverage. The
|
|
84
|
+
conformance corpus is 96 cases, digest
|
|
85
|
+
`sha-256:vMyREM8ggUqVvGG0y2e4Gf-KmpksJjnx2eF8UjtpVP8`; registry digest
|
|
86
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
|
|
87
|
+
digest `sha-256:iBllJ-J8aoWUaYKI7VAqjIfXx9bqwNqWXFO4nxBTCfM`.
|
|
88
|
+
|
|
89
|
+
## [0.5.0] — 2026-09-12
|
|
90
|
+
|
|
91
|
+
### Fixed — the credibility floor
|
|
92
|
+
|
|
93
|
+
- Dependency pull requests can go green again. The public-surface
|
|
94
|
+
privacy history scan hard-requires the maintainer HMAC key, which
|
|
95
|
+
GitHub never delivers to dependabot or fork runs — every dependency
|
|
96
|
+
PR was structurally red. The gate now has exactly one relaxation:
|
|
97
|
+
CI marks true fork pull requests `ABP_PRIVACY_SCAN=fork-skip`, where
|
|
98
|
+
the scan skips LOUDLY (a greppable `[privacy-scan] SKIPPED` banner
|
|
99
|
+
naming what did not run); every other mode value — including typos —
|
|
100
|
+
fails closed exactly as before, and a fork run whose secret IS
|
|
101
|
+
present still enforces. All three arms are red-proven in the
|
|
102
|
+
requirement map; the dependabot green run is recorded as a green
|
|
103
|
+
observation.
|
|
104
|
+
- The documentation-currency gate's shipped-file enumeration now globs
|
|
105
|
+
DIRECTORY package entries: the original filter silently skipped
|
|
106
|
+
every guide inside `"documentation"`, and the onboarding install
|
|
107
|
+
pins had drifted into a line SECURITY.md marks unsupported (the
|
|
108
|
+
organic red is recorded in the requirement map).
|
|
109
|
+
- macOS Finder artifacts (`.DS_Store`, `._*`) are excluded from the
|
|
110
|
+
four digest/file-set walks (specification identity, both release
|
|
111
|
+
asset walks, the corpus directory walk): a stray `.DS_Store` inside
|
|
112
|
+
`spec/` shifted the specification digest and red the
|
|
113
|
+
release-candidate check on any Mac that had previewed the folder.
|
|
114
|
+
|
|
115
|
+
### Added — the adoption surface
|
|
116
|
+
|
|
117
|
+
- Community intake: bug-report and registry-request issue templates
|
|
118
|
+
(the registry template follows `spec/registry/OPERATIONS.md`),
|
|
119
|
+
GitHub Discussions, SUPPORT.md, and a how-to-propose-changes path in
|
|
120
|
+
CONTRIBUTING with the deferred-work registry surfaced as the public
|
|
121
|
+
roadmap.
|
|
122
|
+
- Onboarding reaches a green verification: the quickstart and getting-
|
|
123
|
+
started guides now decode the shipped echo example to `{:ok, _}` and
|
|
124
|
+
round-trip its canonical bytes byte-exactly (mirror-tested), state
|
|
125
|
+
the minimum Elixir version, and keep the typed-denial teaching
|
|
126
|
+
moment after the green path.
|
|
127
|
+
- The worked host integration: a full `reconcile/3` over the shipped
|
|
128
|
+
echo pair under the default `:deny` clamp posture (the typed
|
|
129
|
+
protected-clamp denial) and under `:acknowledge` (a green Evidence
|
|
130
|
+
record whose `not_verified` names the seven host-owned surfaces) —
|
|
131
|
+
mirror-tested line by line.
|
|
132
|
+
- The producer signing recipe: the detached-JWS Ed25519 envelope built
|
|
133
|
+
with `:crypto` over the RFC 7797 preimage and verified end-to-end
|
|
134
|
+
against the shipped verifier — mirror-tested. The package itself
|
|
135
|
+
remains verify-only.
|
|
136
|
+
- `examples/federation-envelope.json`: the 23-member federation
|
|
137
|
+
TaskEnvelope as a byte-exact conformance corpus case, documented in
|
|
138
|
+
the examples guide.
|
|
139
|
+
- The hexdocs sidebar groups the guides (getting started, concepts,
|
|
140
|
+
guides by role, reference, specification, design records,
|
|
141
|
+
governance).
|
|
142
|
+
- A CI compatibility job: the previous supported Elixir/OTP pair
|
|
143
|
+
(1.20.1 / 29.0.2) runs the test suite and the conformance corpus on
|
|
144
|
+
every push and pull request — the broadened-target receipt the
|
|
145
|
+
README's support claim now rests on.
|
|
146
|
+
|
|
147
|
+
The test suite is 917 tests (59 properties) at 100% coverage. The
|
|
148
|
+
conformance corpus is unchanged at 94 cases, digest
|
|
149
|
+
`sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
|
|
150
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
|
|
151
|
+
digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
|
|
152
|
+
|
|
153
|
+
## [0.4.1] — 2026-08-26
|
|
154
|
+
|
|
155
|
+
### Fixed — verification posture hardening
|
|
156
|
+
|
|
157
|
+
- CI green on the public repository (GitHub Actions is free for
|
|
158
|
+
public repos; the prior 'billing-blocked' posture was wrong and is
|
|
159
|
+
retired). The standing CI failures are fixed: a stale reprove copy
|
|
160
|
+
path (a pre-promotion directory that never exists in a fresh
|
|
161
|
+
checkout) crashed the release-candidate check.
|
|
162
|
+
- The README test-count claim is tied to the suite-REGISTERED count,
|
|
163
|
+
not just the source macro census: the release-candidate check
|
|
164
|
+
asserts macro census == registered count == README claim (both
|
|
165
|
+
divergence arms red-proven and replanted in the evidence map).
|
|
166
|
+
- The deferred-work registry (twelve named items, each with its
|
|
167
|
+
checkable reopen trigger) ships inside the specification tree's
|
|
168
|
+
FOUNDATION-TRANSITION document — the durable record no longer lives
|
|
169
|
+
only in planning artifacts.
|
|
170
|
+
|
|
171
|
+
The conformance corpus is unchanged at 94 cases, digest
|
|
172
|
+
`sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
|
|
173
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`; specification
|
|
174
|
+
digest `sha-256:LSSVPdBlOwb844Eg0NQ71ju-sCiBv2_wgRp9RV5Vf0U`.
|
|
175
|
+
|
|
176
|
+
## [0.4.0] — 2026-08-26
|
|
177
|
+
|
|
178
|
+
### Added — examples gallery + minutes-long quickstart
|
|
179
|
+
|
|
180
|
+
- `examples/`: complete, corpus-verified artifact pairs — byte-exact
|
|
181
|
+
conformance corpus cases (the gallery gate proves it against the
|
|
182
|
+
corpus on every build; a drifted example reds). The echo pair
|
|
183
|
+
(blueprint + deployment) is annotated member-by-member in the
|
|
184
|
+
examples guide.
|
|
185
|
+
- The quickstart (`documentation/quickstart.md`): from `mix deps.get`
|
|
186
|
+
to a green verification in `iex` — no heavyweight gates; its
|
|
187
|
+
result-claiming lines are mirror-tested like every guide example.
|
|
188
|
+
- The documentation corpus: 13 adopter guides (getting started, the
|
|
189
|
+
artifacts, extension authoring, host integration, producing,
|
|
190
|
+
portability, the full 74-code error guide, federation, registry,
|
|
191
|
+
upgrading, FAQ, operations), every file an ex_doc extra, every
|
|
192
|
+
result-claiming example executed against the real package by the
|
|
193
|
+
mirror gate; README as a decision document (when to use, when NOT
|
|
194
|
+
to use).
|
|
195
|
+
|
|
196
|
+
The conformance corpus is unchanged at 94 cases, digest
|
|
197
|
+
`sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
|
|
198
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
|
|
199
|
+
|
|
200
|
+
## [0.3.0] — 2026-08-26
|
|
201
|
+
|
|
202
|
+
### Added — the specification corpus (normative hardening + governance)
|
|
203
|
+
|
|
204
|
+
The normative specification is a specification in the standards sense:
|
|
205
|
+
|
|
206
|
+
- RFC 2119/8174 conformance language throughout (BCP 14 boilerplate,
|
|
207
|
+
MUST/MUST NOT/SHOULD/SHOULD NOT/MAY used where load-bearing), a
|
|
208
|
+
terminology section, and a normative Conformance clause (corpus
|
|
209
|
+
pass + byte-identical report agreement + release identity pinning;
|
|
210
|
+
partial conformance is not conformance).
|
|
211
|
+
- Member grammar for all three artifacts (18 Blueprint Core, 19
|
|
212
|
+
Deployment Manifest, 23 Federation TaskEnvelope members) with
|
|
213
|
+
cardinalities, types, constraints, and the pinned failure
|
|
214
|
+
precedence; the full 74-code error semantics table (raised when /
|
|
215
|
+
subject / host action).
|
|
216
|
+
- Security considerations with a corpus-traceable threat model; privacy
|
|
217
|
+
considerations as the data-minimization profile with honest limits;
|
|
218
|
+
the positioning boundary (AI Catalog owns discovery + identity +
|
|
219
|
+
attestation; this protocol owns the portable contract layer).
|
|
220
|
+
- Machine-readable grammar: CDDL (RFC 8610) normative under
|
|
221
|
+
spec/grammar/ with JSON Schema derived (never hand-edited) — bound
|
|
222
|
+
to the compiled tables and the corpus goldens by the
|
|
223
|
+
grammar-derivation gate.
|
|
224
|
+
- Registry data governance: spec/registry/registry.json as the
|
|
225
|
+
governance-canonical source, bound to both compiled twins and the
|
|
226
|
+
corpus index by the registry-equality gate (all four carriers
|
|
227
|
+
verified at sha-256:FG2f38K0…).
|
|
228
|
+
- Governance pack: spec-scoped IPR (Apache-2.0 + DCO, no CLA,
|
|
229
|
+
donation-ready), FOUNDATION-TRANSITION inventory, registry
|
|
230
|
+
operations process, errata policy; root CONTRIBUTING (the
|
|
231
|
+
verification battery published) and CODE_OF_CONDUCT. Steward: the
|
|
232
|
+
unincorporated BaseLabs org, Russ Palermo as named maintainer.
|
|
233
|
+
- The release identity chain: priv/release-metadata.json pins the
|
|
234
|
+
specification digest, package version, corpus and registry digests,
|
|
235
|
+
and the corpus index hash — asserted from live state on every run.
|
|
236
|
+
- Specification extraction is a tested proof (spec/ + the conformance
|
|
237
|
+
corpus extract self-contained; the CI job runs the literal
|
|
238
|
+
repository-filter extraction).
|
|
239
|
+
|
|
240
|
+
Every new gate carries a recorded red proof in the requirement map and
|
|
241
|
+
is replanted by the release-candidate reprove (74 plants).
|
|
242
|
+
|
|
243
|
+
The conformance corpus is unchanged at 94 cases, digest
|
|
244
|
+
`sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
|
|
245
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
|
|
246
|
+
|
|
247
|
+
## [0.2.1] — 2026-08-25
|
|
248
|
+
|
|
249
|
+
### Fixed — public documentation credibility
|
|
250
|
+
|
|
251
|
+
- README install pin corrected to the current release line (`~> 0.2.1`;
|
|
252
|
+
the previous `~> 0.1.0` excluded every 0.2.x release in Hex
|
|
253
|
+
requirement semantics).
|
|
254
|
+
- SECURITY.md's supported-version table names the 0.2.x line (0.1.x is
|
|
255
|
+
no longer supported — upgrade to the current line).
|
|
256
|
+
- Two changelog entries cited an internal working document by section
|
|
257
|
+
number (a document that ships nowhere); both are reworded to
|
|
258
|
+
self-contained prose, and a new document-citation gate (below) keeps
|
|
259
|
+
the class dead.
|
|
260
|
+
- `docs/protocol.md` states the producer surface explicitly in its
|
|
261
|
+
shipped-surface section (`Blueprint.from_value/2`,
|
|
262
|
+
`Deployment.from_value/2`, the per-artifact `content_digest/1` and
|
|
263
|
+
`canonical_bytes/1`), resolving the pointer the producer-surface ADR
|
|
264
|
+
relied on.
|
|
265
|
+
- The federation mapping's pinned sources now carry canonical
|
|
266
|
+
repository URLs, each pinned by plain SHA-1 of the served bytes
|
|
267
|
+
(A2A `lf.a2a.v1` line at commit `cfc9d34b`; the MCP Tasks extension
|
|
268
|
+
draft at commit `0d0a6bd4`).
|
|
269
|
+
- README rewritten for external readers: CI, Hex version, and license
|
|
270
|
+
badges; an outsider-readable status section; current test and corpus
|
|
271
|
+
counts.
|
|
272
|
+
|
|
273
|
+
### Added — documentation gates
|
|
274
|
+
|
|
275
|
+
- Documentation-currency gate
|
|
276
|
+
(`test/architecture/documentation_currency_test.exs`): README,
|
|
277
|
+
SECURITY.md, and CHANGELOG version claims, install pins, count
|
|
278
|
+
claims, and the current release's corpus identity (digest and case
|
|
279
|
+
total) are checked against the live project on every run.
|
|
280
|
+
- Document-citation gate
|
|
281
|
+
(`test/architecture/document_citation_gate_test.exs`): shipped
|
|
282
|
+
markdown documents may cite only documents that exist — a named
|
|
283
|
+
section citation must name a shipped document or a pinned external
|
|
284
|
+
standard, and every repository-relative link must resolve to a real
|
|
285
|
+
file.
|
|
286
|
+
|
|
287
|
+
The conformance corpus is unchanged at 94 cases, digest
|
|
288
|
+
`sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
|
|
289
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
|
|
290
|
+
|
|
291
|
+
## [0.2.0] — 2026-08-25
|
|
292
|
+
|
|
293
|
+
### Added — product-extension registration
|
|
294
|
+
|
|
295
|
+
- The extension registry registers `com.example.platform/estate-contract`
|
|
296
|
+
(owner `ExamplePlatform`, **critical**, active, never promoted) — the first
|
|
297
|
+
product-owned critical namespace with an authored schema digest pin, riding
|
|
298
|
+
the `:authored_extensions` validated channel: critical bodies validate
|
|
299
|
+
against a host-supplied schema whose `extension_schema` JCS digest matches
|
|
300
|
+
the registry pin, then thread into `from_value/2` as authored content. The
|
|
301
|
+
schema document covers the asset materialization window (`definition
|
|
302
|
+
{name, version}` + nullable `window_days`) and the objective condition AST
|
|
303
|
+
(leaves `materialization_present` / `materialization_stale` /
|
|
304
|
+
`materialization_count_within`; composites `and`/`or` n-ary, `not` unary),
|
|
305
|
+
hand-tiered as uniform-depth strict tiers because the bounded dialect denies
|
|
306
|
+
`$ref` cycles — portable condition depth is three composite tiers
|
|
307
|
+
(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`.
|
|
308
|
+
- The schema document ships as corpus data
|
|
309
|
+
(`priv/conformance/schemas/estate-contract.schema.json`); `lib/` records only
|
|
310
|
+
the digest pin, and a test binds the pin to the SHIPPED document (the corpus
|
|
311
|
+
index hashes raw file bytes, the pin hashes JCS of the parsed document — the
|
|
312
|
+
test is the bridge between the two domains).
|
|
313
|
+
- The conformance corpus grows 88 → 94 cases: the validated-channel cells
|
|
314
|
+
(valid attach with matching schema, schema absent, digest mismatch,
|
|
315
|
+
criticality conflict, the tier-bound deny) and the deprecated-optional
|
|
316
|
+
retention cell; two new applicability classes (`extension_schema_unavailable`,
|
|
317
|
+
`extension_deprecated_retained`); the floor is now 16 surfaces × 31 classes /
|
|
318
|
+
90 required cells. Corpus digest
|
|
319
|
+
`sha-256:sg6Fo7p8nZpJDzxFn4dXHBWgbGvEvtOk-7t3m7OT7Yo`; registry digest
|
|
320
|
+
`sha-256:FG2f38K0hba8tTP7iUaw7vHjgcnN_5F5Mp0v4G6UDVs`.
|
|
321
|
+
- `docs/adr/producer-surface.md` records the producer-surface disposition: the
|
|
322
|
+
documented per-artifact constructors ARE the intended producer surface for
|
|
323
|
+
hosts; the facade stays a verification facade.
|
|
324
|
+
|
|
325
|
+
### Deprecated
|
|
326
|
+
|
|
327
|
+
- `com.example.platform/estate` (the placeholder optional namespace) is
|
|
328
|
+
`deprecated`: its payload role — a condition body carried verbatim as a free
|
|
329
|
+
object — is superseded by the schema-validated channel. Optional bodies in
|
|
330
|
+
existing artifacts remain verifiable, retained with a typed
|
|
331
|
+
`extension_deprecated` notice.
|
|
332
|
+
|
|
333
|
+
### Fixed
|
|
334
|
+
|
|
335
|
+
- Cross-vendor review fix pass: the schema document bounds
|
|
336
|
+
`definition.name` with `maxLength: 128` (the free-form string in a body
|
|
337
|
+
that skips the portability value-shape heuristics — the schema is the
|
|
338
|
+
bound on that surface); the registry's closed-schema lens test now fails
|
|
339
|
+
loudly for any future pinned namespace without its own document binding;
|
|
340
|
+
stale 0.1.x release-line claims and the generator's section counts were
|
|
341
|
+
reconciled to 0.2.0.
|
|
342
|
+
- The second-language verifier's schema `items` evaluation had its schema and
|
|
343
|
+
instance arguments swapped, so no cross-language case had ever actually
|
|
344
|
+
validated array items (object-shaped items passed vacuously; scalar items
|
|
345
|
+
crashed the verifier). The estate-contract tier schemas are the first
|
|
346
|
+
corpus-bearing `items` user; the byte-identical agreement gate now proves
|
|
347
|
+
both languages validate items identically.
|
|
348
|
+
|
|
349
|
+
### Changed — from the unreleased queue
|
|
350
|
+
|
|
351
|
+
- The gitleaks secret-scan configuration was invalid TOML (a string
|
|
352
|
+
concatenation TOML does not support) and, independently, nothing executed
|
|
353
|
+
it — no CI job or alias ran gitleaks, so a committed credential would have
|
|
354
|
+
passed the complete quality gate. The config now parses (the corpus key
|
|
355
|
+
fragment is matched via a single-character class instead of concatenation),
|
|
356
|
+
the generated conformance corpus is allowlisted by path (per-value fragments
|
|
357
|
+
had rotted: the federation corpus keys were uncovered), and CI runs a
|
|
358
|
+
full-history gitleaks v8.30.1 scan as its own job, pinned to the release
|
|
359
|
+
commit. Red-proven against a staged canary secret; every finding the
|
|
360
|
+
allowlists suppress was adjudicated as deterministic public-by-construction
|
|
361
|
+
fixture material.
|
|
362
|
+
- GitHub CI now selects Node 24.19.0 through the immutable `setup-node` v7.0.0
|
|
363
|
+
commit before running the complete quality gate. This removes dependence on
|
|
364
|
+
the runner image's ambient Node release while preserving the verifier's
|
|
365
|
+
Node 24 minimum.
|
|
366
|
+
- The normative protocol header and README introduction were reconciled to the
|
|
367
|
+
live public 0.1.x package state (obsolete pre-publication/release-candidate
|
|
368
|
+
framing removed).
|
|
369
|
+
|
|
370
|
+
## [0.1.1] — 2026-08-23
|
|
371
|
+
|
|
372
|
+
### Changed — documentation packaging (no code change)
|
|
373
|
+
|
|
374
|
+
- The Hex archive and hexdocs now ship the seven architecture decision
|
|
375
|
+
records (`docs/adr/`), and `docs/federation-mapping.md` joins the
|
|
376
|
+
hexdocs extras — matching the house packaging convention of the
|
|
377
|
+
published `bounded_authority_protocol` package.
|
|
378
|
+
- The requirement map stays repository-side BY DESIGN (public in the
|
|
379
|
+
repository, not in the archive): its verbatim red receipts quote the
|
|
380
|
+
very internal tokens the publish guard bans from the archive, so
|
|
381
|
+
archiving it reds the guard — that red is now recorded in the map's
|
|
382
|
+
own publish-guard entry as the boundary's proof. An earlier draft of
|
|
383
|
+
this release stripped the map's receipt fences from the guard's scan
|
|
384
|
+
instead; cross-vendor review correctly blocked it as a guard blind
|
|
385
|
+
spot that would have shipped the banned tokens verbatim.
|
|
386
|
+
- README restructured to the house convention: Installation directly
|
|
387
|
+
after the introduction, a function-level "What it provides" section,
|
|
388
|
+
and the requirement map's boundary stated.
|
|
389
|
+
|
|
390
|
+
## [0.1.0] — 2026-08-23
|
|
391
|
+
|
|
392
|
+
Initial public release: the Agent Blueprint Protocol, its Elixir
|
|
393
|
+
reference implementation, the conformance corpus, and the
|
|
394
|
+
second-language verifier.
|
|
395
|
+
|
|
396
|
+
### Normative docs + release-candidate gates
|
|
397
|
+
|
|
398
|
+
- `docs/protocol.md`: the normative protocol document (ships in the Hex
|
|
399
|
+
archive) — artifacts and the closed member registries, bounded bytes
|
|
400
|
+
and the integer window, RFC 8785 canonicalization, domain-separated
|
|
401
|
+
digests, the detached-JWS envelope, evolution and extension rules, the
|
|
402
|
+
compiled registry's first-release entries, the bounds algebra laws,
|
|
403
|
+
the 74-code error vocabulary, the evidence contract, and the
|
|
404
|
+
conformance corpus identity (88 cases at the recorded digest).
|
|
405
|
+
- `docs/design/requirement-map.md` (repository-side, not in the Hex
|
|
406
|
+
archive): every build gate's recorded red
|
|
407
|
+
proof — each quality-alias step, every architecture-lane test case,
|
|
408
|
+
and the conformance lanes — re-derived live (plant → run → restore)
|
|
409
|
+
with verbatim failing output.
|
|
410
|
+
- `docs/adr/` (repository-side, slug-only filenames): the seven
|
|
411
|
+
decisions of record —
|
|
412
|
+
the non-authorizing boundary, the detached JWS envelope, the
|
|
413
|
+
two-consumer amendment, deny-default protected-bound clamps, the
|
|
414
|
+
compiled-in registry (closing the package-boundary contradiction of
|
|
415
|
+
record), the federation lanes, and the no-versioning rule.
|
|
416
|
+
- New architecture gates, both red-proven at birth:
|
|
417
|
+
- **publish guard** — no internal-planning reference, private-tool
|
|
418
|
+
path, or home-directory path in any archived file (byte patterns
|
|
419
|
+
plus word-bounded text patterns that cannot false-positive inside
|
|
420
|
+
base64url tokens; registry owner/namespace/URI data is published by
|
|
421
|
+
design and exempted on record);
|
|
422
|
+
- **spec coverage** — every public function carries a matching
|
|
423
|
+
`@spec` (default-arity rule recorded) and every shipped module's
|
|
424
|
+
moduledoc states the non-authorizing boundary (39 modules gained
|
|
425
|
+
an honest stance sentence; `ExtensionRegistry.federation_schema/0`
|
|
426
|
+
gained its missing `@spec`).
|
|
427
|
+
- `mix release.candidate` (also in `mix quality`): re-derives the
|
|
428
|
+
requirement map's completeness from live project state (every
|
|
429
|
+
architecture test case, every live quality-alias step), structure-
|
|
430
|
+
checks each entry's red fence, and couples `docs/protocol.md` to the
|
|
431
|
+
shipped implementation (facade functions, registry namespaces, corpus
|
|
432
|
+
digest and case total, the stance sentence).
|
|
433
|
+
- Internal-reference scrub of the shipped surface: tracker numerals,
|
|
434
|
+
internal design-shorthand citations, and a portfolio-terminology
|
|
435
|
+
section removed from `docs/federation-mapping.md`, README, CHANGELOG,
|
|
436
|
+
and `lib/` comments/`@doc`s (comments and docs only — zero behavior
|
|
437
|
+
change).
|
|
438
|
+
- README Status and Installation rewritten to the published 0.1.0
|
|
439
|
+
state.
|
|
440
|
+
|
|
441
|
+
### Second-language verifier + agreement gate
|
|
442
|
+
|
|
443
|
+
- `conformance/verifier/`: the repo-side TypeScript verifier (Node ≥ 24,
|
|
444
|
+
`node:` builtins only, zero npm runtime deps; never in the Hex archive) —
|
|
445
|
+
an independent recomputation of every corpus surface and integrity check,
|
|
446
|
+
with a CLI byte-compatible with the Elixir escript (`--corpus` required;
|
|
447
|
+
exit 0/1/2; report bytes on stdout, no trailing newline).
|
|
448
|
+
- `mix verifier.agreement` (in `mix quality`): byte-agrees the TS report
|
|
449
|
+
with the escript's over the repo corpus AND the built Hex archive's,
|
|
450
|
+
runs the self-check battery (RFC 8785 Appendix B three-way, the integer-window
|
|
451
|
+
matrix incl. the mis-round lexeme, Ed25519 key acceptance, stored
|
|
452
|
+
JOSE vectors), and proves three seeded reds fire (verdict inversion,
|
|
453
|
+
report member drift, window-check deletion) — with a calibration
|
|
454
|
+
self-proof of the raise path.
|
|
455
|
+
- `conformance/verifier/testdata/jose-vectors.json` +
|
|
456
|
+
`scripts/generate_jws_vectors.exs`: the stored detached-JWS vectors, KAT-
|
|
457
|
+
anchored to RFC 8032 §7.1 TEST 1, verified Elixir-signed → node-verified
|
|
458
|
+
in both detached and compact forms.
|
|
459
|
+
- `Signature`: small-order key rejection hardened — the identity (order 1)
|
|
460
|
+
and order-2 encodings no longer pass `usable_ed25519_key?` (found by the
|
|
461
|
+
mirror's torsion battery; latent on this OTP).
|
|
462
|
+
- `Federation.decode`: an empty claim value or compatibility identity now
|
|
463
|
+
denies `:invalid_constraint` instead of raising `FunctionClauseError`
|
|
464
|
+
(never-raising posture restored; found by the mirror's parity battery).
|
|
465
|
+
- `Conformance.Runner`: a malformed observed identity element denies typed
|
|
466
|
+
`:invalid_type` instead of raising (the prior-receipts pattern).
|
|
467
|
+
- Corpus regenerated to 88 cases (digest
|
|
468
|
+
`sha-256:QsRbWGreygTJ0m47csgfpwYtoNId3FbjNP49sK-X-MY`): two
|
|
469
|
+
obligation-varying intersect cases pin the protected-bound meet direction
|
|
470
|
+
inside corpus agreement (previously corpus-invisible; carried by the
|
|
471
|
+
verifier's vectors); the mutation gate gains an `obligation-meet-min`
|
|
472
|
+
entry (7 total). The real-escript end-to-end test covers the halt shim's
|
|
473
|
+
exit contract in-suite (the coverage-exclusion ack's substance).
|
|
474
|
+
|
|
475
|
+
### Conformance corpus subsystem
|
|
476
|
+
|
|
477
|
+
- `Conformance.{Corpus,Runner,Report,Cli}`: the portable conformance corpus —
|
|
478
|
+
pure loader with the 16×29 applicability floor compiled in, two-directional
|
|
479
|
+
integrity with typed errors (corpus-registry and corpus-digest bindings,
|
|
480
|
+
tamper verbatim-vs-derived audits, vacuous-green refusal), a code-level
|
|
481
|
+
shape-agnostic runner over all 16 surfaces, a JCS report bound to the corpus
|
|
482
|
+
identity, and an escript CLI (`--corpus` required; exit 0/1/2).
|
|
483
|
+
- `priv/conformance/`: 86 shipped cases, full-registry goldens (evidence
|
|
484
|
+
members included), RFC 8785 vectors, deterministic key fixtures.
|
|
485
|
+
- `mix conformance.verify` + `mix conformance.mutations` wired into
|
|
486
|
+
`mix quality` — five named implementation mutations each proven to redden
|
|
487
|
+
the corpus, plus a corpus-expectation-flip calibration entry.
|
|
488
|
+
- `ExtensionRegistry.digest/0` (+ the `:extension_registry` digest domain):
|
|
489
|
+
the corpus-registry binding.
|
|
490
|
+
- Facade: `canonical_bytes/1` (the named canonicalize gap) and typed
|
|
491
|
+
`negotiate`/`intersect` rims. Decode surfaces deny typed on non-binary
|
|
492
|
+
input (was a `FunctionClauseError` raise).
|
|
493
|
+
- Eight new error codes: the seven corpus integrity codes + the recorded
|
|
494
|
+
`:corpus_case_invalid` addition.
|
|
495
|
+
|
|
496
|
+
|
|
497
|
+
### Added
|
|
498
|
+
|
|
499
|
+
- Federation profile: `AgentBlueprintProtocol.Federation` with
|
|
500
|
+
the 23-member `TaskEnvelope` (one wire member per logical field of the
|
|
501
|
+
protocol's federation seam; decoded through the shared registry engine,
|
|
502
|
+
canonical-before-semantics, cross-field rules, and a per-member
|
|
503
|
+
portability pass where an authority-shaped identity claim denies
|
|
504
|
+
`:nonportable_content`); the lossy-aware A2A/MCP state codecs
|
|
505
|
+
(UNSPECIFIED denies at intake; crossing into MCP denies for
|
|
506
|
+
rejected/submitted/auth_required; cancellation is never a terminal
|
|
507
|
+
receipt); the carrier placement laws for both transports
|
|
508
|
+
(`Task.metadata[a2a_uri]` on A2A, `_meta[namespace]` on MCP — the
|
|
509
|
+
`_meta` key grammar forbids a URI key); `terminal_commitment/1` over
|
|
510
|
+
the seven commitment components; and `verify_commitment/2` with the signature
|
|
511
|
+
BINDING step (the signed content digest must name the receiving
|
|
512
|
+
envelope's covered bytes — an honestly-signed statement naming a
|
|
513
|
+
different digest is evidence over THAT digest), the
|
|
514
|
+
issuer/subject/audience comparison (`:audience_mismatch`), and
|
|
515
|
+
`:federation_terminal_conflict` on any divergence between receipts for
|
|
516
|
+
one task identity. Facade rows `decode_federation_envelope/2` and
|
|
517
|
+
`federation_mapping/0` (the 23-row mapping as data, bijective with the
|
|
518
|
+
envelope's members by an architecture gate). Published mapping doc
|
|
519
|
+
`docs/federation-mapping.md` with the pinned live sources, the A2A
|
|
520
|
+
primary / MCP draft-tracking flag and revisit trigger, and the
|
|
521
|
+
ttlMs-is-not-an-execution-bound, AUTH_REQUIRED-is-not-authorization,
|
|
522
|
+
and AgentCard protobuf pre-normalization notes.
|
|
523
|
+
- Federation hardening (independent review): a
|
|
524
|
+
signature whose signed `purpose` is not `federation-envelope` never
|
|
525
|
+
verifies a federation receipt (the symmetric cross-surface purpose gap, closed
|
|
526
|
+
on this surface — cross-surface signature lifting denied
|
|
527
|
+
`:invalid_constraint`); the receipt's `kid`/`key_id` positions are
|
|
528
|
+
portability-scanned strict (PEM/hex secrets deny
|
|
529
|
+
`:forbidden_portable_value`; the signature blob stays deliberately
|
|
530
|
+
opaque — every honest signature is entropy-dense and never survives
|
|
531
|
+
verification without the key); `terminal_commitment/1` and
|
|
532
|
+
`verify_commitment/2` are total over hand-built structs (typed denials
|
|
533
|
+
replace raises on absent/non-string members and malformed commitment
|
|
534
|
+
spellings); the carrier-reconstruction lane re-imposes the decoder's
|
|
535
|
+
member/item/node/string/depth ceilings and the UTF-8 gate on hand-built
|
|
536
|
+
carrier maps; duplicate regulated markers deny `:invalid_cardinality`.
|
|
537
|
+
Receiver posture documented (purpose pinning, key-ids-as-labels,
|
|
538
|
+
keys-are-not-issuers, replay-is-receiver-policy).
|
|
539
|
+
- Federation residual hardening: `Federation.Context` gains
|
|
540
|
+
`issuer_key_sets` — per-issuer key attribution where the receipt's
|
|
541
|
+
claimed (and binding-proven) `issuer` member selects the signature key
|
|
542
|
+
pool, with strictest-wins precedence over the flat pool and deny-all
|
|
543
|
+
for an empty map (cross-attribution now denies by mechanism) — and
|
|
544
|
+
`created_after`/`created_before` freshness pins over the SIGNED
|
|
545
|
+
`created_at` (receiver-supplied inclusive window, Z-form double-gated,
|
|
546
|
+
checked after conflict detection so equivocation still reports
|
|
547
|
+
`:federation_terminal_conflict`). Fixes a live crash the adversarial
|
|
548
|
+
pass reproduced: `verify_commitment` with the Context's `keys: nil`
|
|
549
|
+
default raised `FunctionClauseError` — nil/malformed pools now deny
|
|
550
|
+
`:invalid_type` typed. Attribution-miss denials name the issuer
|
|
551
|
+
subject; a value-free structural guard pins every federation denial's
|
|
552
|
+
subject to schema shape with nil detail. Signature-blob opacity ruled
|
|
553
|
+
irreducible in-package (honest signatures are entropy-dense); the
|
|
554
|
+
boundary is shape-checked, never echoed, and never survives
|
|
555
|
+
verification without the key.
|
|
556
|
+
- Error vocabulary: `:forbidden_portable_value` is now declared and
|
|
557
|
+
emitted through per-site literals (the per-site vocabulary walk could
|
|
558
|
+
not see the module-attribute-carried emission — a live closedness hole,
|
|
559
|
+
closed with a staged red); the federation codes
|
|
560
|
+
`:federation_state_unmappable`, `:federation_mapping_conflict`,
|
|
561
|
+
`:nonportable_content`, `:audience_mismatch`, and
|
|
562
|
+
`:federation_terminal_conflict` declared exactly as emitted.
|
|
563
|
+
|
|
564
|
+
- Reconcile hardening (independent review): the
|
|
565
|
+
composed pass gates non-object artifact roots at the canonical stage
|
|
566
|
+
(typed denial, never a raise); `Reconcile.Inputs` drops the unused
|
|
567
|
+
observed-identities field (the eight-stage pass performs no
|
|
568
|
+
compatibility verification — hosts call `verify_compatibility/2`;
|
|
569
|
+
recorded contract delta); the portability stage mirrors each
|
|
570
|
+
artifact's own per-position scan modes (authored schema documents and
|
|
571
|
+
predicate operands, the blueprint's five identifier member tables,
|
|
572
|
+
strict elsewhere) instead of strict-scanning everything; `Evidence
|
|
573
|
+
.build/1` validates every field's shape and denies struct inputs
|
|
574
|
+
typed; compatibility re-asserts the identity manifest's cardinality
|
|
575
|
+
and closed four-member entries, and case-folds range tags (LATEST
|
|
576
|
+
denies like latest); signatures checks carry the entry count as
|
|
577
|
+
detail; the two facade delegates deny typed on malformed
|
|
578
|
+
arguments; the vocabulary gate treats sigil-built code positions as
|
|
579
|
+
dynamic build failures, sees piped call sites, and fixes the
|
|
580
|
+
case/cond branch tag.
|
|
581
|
+
- Reconcile, compatibility, and the evidence record:
|
|
582
|
+
`AgentBlueprintProtocol.Reconcile.reconcile/3` — the one call per
|
|
583
|
+
import, running the pinned stage order canonical → digest →
|
|
584
|
+
negotiation → structure → portability → signatures → bind → bounds,
|
|
585
|
+
each stage reject-or-annotate, never repair, under host-supplied
|
|
586
|
+
`Reconcile.Inputs` (host policy bounds, negotiation support, trusted
|
|
587
|
+
public keys, observed build identities, the protected-clamp posture,
|
|
588
|
+
and the bind-time observations). The signature stage BINDS each
|
|
589
|
+
entry's signed `content_digest` to the artifact's recomputed digest —
|
|
590
|
+
an honestly-signed statement naming a different digest is evidence
|
|
591
|
+
over that digest, not this artifact (`:digest_mismatch`). The
|
|
592
|
+
portability stage runs the direct scans under the authored channel
|
|
593
|
+
re-derived from this import's negotiated critical extensions; the
|
|
594
|
+
structure stage is the registry validation, kept disjoint so both
|
|
595
|
+
guards are independently observable. Every clamp lands as
|
|
596
|
+
`Evidence.clamps` and as a per-bound `:bounds` check carrying the
|
|
597
|
+
`%ClampEvidence{}`. `AgentBlueprintProtocol.Compatibility.verify/2` —
|
|
598
|
+
identity-exact matching of manifest `build_identities` against
|
|
599
|
+
host-observed identities: ranges deny `:compatibility_identity_inexact`
|
|
600
|
+
on both sides, duplicate candidates (including byte-identical
|
|
601
|
+
observations) and duplicated manifest names deny
|
|
602
|
+
`:compatibility_duplicate_entry`, unmatched entries deny
|
|
603
|
+
`:compatibility_entry_missing`, extra observed identities are
|
|
604
|
+
evidence-neutral; `exact?/1` is the public exact-version predicate.
|
|
605
|
+
`AgentBlueprintProtocol.Evidence` — the non-authorizing verification
|
|
606
|
+
record whose `not_verified` is non-empty BY CONSTRUCTION: `build/1`
|
|
607
|
+
unions in the seven host-owned surfaces (tenancy, live_policy,
|
|
608
|
+
authority, effect_ownership, execution, billing, evaluation_truth),
|
|
609
|
+
never replacing them; callers may only add. The facade gains
|
|
610
|
+
`verify_compatibility/2` and `reconcile/3`, and `Error.code` widens
|
|
611
|
+
to carry the `{:ceiling, key}` family. All eight reconcile stage
|
|
612
|
+
guards and the Evidence constructor are mutation-redded (each guard's
|
|
613
|
+
removal fails its committed tamper or order test).
|
|
614
|
+
|
|
615
|
+
- Bounds-algebra hardening pass: classification comparison
|
|
616
|
+
moves to the PRODUCT order the meet computes in (ordinal ≤ AND markers
|
|
617
|
+
⊇) — a marker dropped at ANY ordinal is a widening (obligations are not
|
|
618
|
+
tradeable against scope), `widens?` becomes `¬(a ⪯ b)` and so
|
|
619
|
+
fail-closed on every incomparable pair (an independent review's
|
|
620
|
+
blocking finding: `{pci}` vs `{phi}` previously compared non-widening
|
|
621
|
+
in both directions), and `narrower` requires both components. The rim is now
|
|
622
|
+
deny-typed everywhere it previously raised on struct-bypass inputs:
|
|
623
|
+
hostile map keys and unknown/extra names deny `:bound_unknown` with the
|
|
624
|
+
CONTAINING surface as subject (never the attacker key — the echo
|
|
625
|
+
channel closes), plain-map markers and marker maps with extra keys deny
|
|
626
|
+
`:bound_value_invalid` at construction and again at `intersect`'s
|
|
627
|
+
revalidation, malformed lifter sub-shapes read as absent (total,
|
|
628
|
+
never-raising), off-lattice envelope strings deny with a constructible
|
|
629
|
+
subject (the error builder itself was a crash site), a string on a
|
|
630
|
+
numeric host bound denies `:invalid_type`, duplicate or extra members
|
|
631
|
+
in hand-built `host_bounds`/`ceilings` objects deny `:invalid_type`
|
|
632
|
+
(decode already enforced both), bound values above the parse profile's
|
|
633
|
+
declared integer magnitude deny, `widens?`/`narrower` never raise on
|
|
634
|
+
forged values (total predicates, fail-closed in the widening
|
|
635
|
+
direction), and `Result.t`'s clamps type resolves its module. Every
|
|
636
|
+
fix re-probed live against the finding's original probe input.
|
|
637
|
+
- Bounds algebra: `AgentBlueprintProtocol.BoundsAlgebra` —
|
|
638
|
+
the pointwise narrowest intersection of the Blueprint's declared
|
|
639
|
+
bounds, the Deployment's `host_bounds`, and the host's live policy over
|
|
640
|
+
the closed thirteen-bound vocabulary, with per-family direction
|
|
641
|
+
(scope families narrow at the low end; authority/approval/effect
|
|
642
|
+
narrow at the STRICT end; classification markers are
|
|
643
|
+
retained regulatory obligations whose effective set is the UNION of
|
|
644
|
+
the sources' sets — dropping one is the widening the mutation gate
|
|
645
|
+
names). Protected narrowings never happen silently: under the default
|
|
646
|
+
`:deny` posture they deny `:protected_bound_clamp_denied` carrying
|
|
647
|
+
the field/requested/effective triple; under `:acknowledge` they clamp
|
|
648
|
+
with `acknowledged: true` evidence ALWAYS. Operational narrowings
|
|
649
|
+
emit `ClampEvidence{field, class, unit, requested, effective, source,
|
|
650
|
+
acknowledged}` with `:host` attribution on ties and composites (the
|
|
651
|
+
live policy is the operative constraint), clamps ordered by the
|
|
652
|
+
name-sorted vocabulary. `max_cost` compares within one currency only
|
|
653
|
+
(`:bound_unit_mismatch`, order-free). All three sources must be total:
|
|
654
|
+
an operational absence denies `:missing_ceiling`, a protected absence
|
|
655
|
+
`:bound_source_missing`, under the pinned precedence (source order,
|
|
656
|
+
then numerics → cost → protected, each name-sorted). `widens?/2` is
|
|
657
|
+
fail-closed on incomparable pairs; `Bound.narrower/2` is
|
|
658
|
+
direction-encoded per family and function-total (marker-bearing
|
|
659
|
+
classification is a partial order — the lexicographic
|
|
660
|
+
ordinal-then-marker superset relation). The lifters derive the
|
|
661
|
+
Blueprint side totally (classification is the WIDEST across all five
|
|
662
|
+
declaration sites; approval/authority/impact are the strictest claims
|
|
663
|
+
across capabilities/effects with bottoms for empty arrays; disclosure
|
|
664
|
+
is the identity element `:full` — the Blueprint declares no
|
|
665
|
+
disclosure member) and lift the Deployment from `host_bounds` only
|
|
666
|
+
(`model_policy` and `data_bindings` are not intersection inputs).
|
|
667
|
+
The new `AgentBlueprintProtocol.Error{code, subject, detail}` record
|
|
668
|
+
(typed shape, string subject paths, `detail` only for the
|
|
669
|
+
protected deny) lands with the algebra surface; the facade gains
|
|
670
|
+
`intersect/1`. Property lane: idempotent/commutative/associative
|
|
671
|
+
(pinned fold encoding), `not widens?(effective, host)` universal,
|
|
672
|
+
clamp iff `effective ≠ requested`, marker-union law — with the
|
|
673
|
+
min→max, marker-intersection, direction-flip, struct-default, and
|
|
674
|
+
silent-path mutations each proven RED against them.
|
|
675
|
+
|
|
676
|
+
### Fixed
|
|
677
|
+
|
|
678
|
+
- The bounds-algebra rim's coverage claim was corrected to a true
|
|
679
|
+
100% (measured 2026-08-22: the then-committed suite reached only
|
|
680
|
+
97.7% — the deny-typed rim's catch-all clauses had no tests). The rim probes now ship as tests: struct-bypass forged
|
|
681
|
+
values through `widens?/2` and `Bound.narrower/2` for every family,
|
|
682
|
+
wrong-shape cost at construction, non-map `new/1`, absent-name
|
|
683
|
+
`fetch/2`, non-`Sources`/junk-posture/non-set-source `intersect/1`,
|
|
684
|
+
and the `host_bounds` lifter shape matrix (absent, malformed member,
|
|
685
|
+
malformed value, off-lattice ordinal, non-string on a protected
|
|
686
|
+
name), each asserting the typed denial or fail-closed verdict.
|
|
687
|
+
Eleven representative rim mutations each redded their test before
|
|
688
|
+
restore. Two provably unreachable arms were removed (the only
|
|
689
|
+
production change): `widens_value/3`'s unknown-name arm (its only
|
|
690
|
+
caller iterates `names/0`, always `@table` keys) and `member_of/2`'s
|
|
691
|
+
`{:object, _}` clause (no call site passes an object tuple).
|
|
692
|
+
An independent re-review of the follow-up range then found the rim's
|
|
693
|
+
one remaining hole: `widens?/2` matched any `%BoundSet{}` regardless
|
|
694
|
+
of `bounds`' type, so a struct-forged `%BoundSet{bounds: nil}` raised
|
|
695
|
+
`BadMapError` from either argument position instead of failing
|
|
696
|
+
closed (the head now guards `is_map` on both, dropping the forgery
|
|
697
|
+
to the fail-closed catch-all), plus its guard-family sibling
|
|
698
|
+
`BoundSet.to_map/1` (same forged shape raised; now deny-typed
|
|
699
|
+
`:invalid_type` with subject `["bound_set"]`). Both probed red
|
|
700
|
+
before the fix, green after.
|
|
701
|
+
`mix quality` has reported a true 100.00% since.
|
|
702
|
+
- A one-off suite flake, root-caused: the
|
|
703
|
+
"mutating the signatures member" test replaced the first `A` in the
|
|
704
|
+
base64url signature, which lands on the FINAL character ~7% of random
|
|
705
|
+
signatures — the one position whose value is canonicality-constrained
|
|
706
|
+
— producing a correctly-rejected non-canonical string
|
|
707
|
+
(`:signature_malformed`). The tamper now targets the first character
|
|
708
|
+
(a significant 6-bit position at every base64url length), making the
|
|
709
|
+
test deterministic for every key.
|
|
710
|
+
|
|
711
|
+
### Core surfaces
|
|
712
|
+
|
|
713
|
+
- Deployment Manifest + binding: the 19-member table
|
|
714
|
+
(re-derived against the protocol's Deployment Manifest definition) on the
|
|
715
|
+
SAME generic engine — `AgentBlueprintProtocol.Deployment` mirrors the
|
|
716
|
+
Blueprint pipeline stage-for-stage (canonical verify → registry
|
|
717
|
+
validation → portability scan → digest comparison) under the
|
|
718
|
+
`:deployment_content` domain, with only the table, the scan's open
|
|
719
|
+
regions (extension bodies, eligibility expressions), and the digest
|
|
720
|
+
domain as deltas. The binding surface: `binds?/2` (digest equality and
|
|
721
|
+
nothing else, against the paired Blueprint's recomputed digest,
|
|
722
|
+
constant-time, total over malformed deployment input) and the six-stage
|
|
723
|
+
`verify_binding/3` with a pinned order — release digest
|
|
724
|
+
(`:deployment_digest_mismatch`), release identity and tool-binding
|
|
725
|
+
completeness (`:binding_incomplete`), mutation/recovery
|
|
726
|
+
(`:no_authoritative_recovery`, the stricter of both operation sources),
|
|
727
|
+
attestation staleness (`:binding_attestation_stale`, future attestations
|
|
728
|
+
deny), and observed rug-pull (`:binding_descriptor_mismatch`); stages
|
|
729
|
+
carrying host observations skip exactly when their inputs are absent.
|
|
730
|
+
Table semantics: `blueprint_release` with a REQUIRED digest;
|
|
731
|
+
exact-only build identities (the range vocabulary — comparators,
|
|
732
|
+
wildcards, `latest`, range spans — denies
|
|
733
|
+
`:compatibility_identity_inexact`; prerelease/build suffixes are exact
|
|
734
|
+
pins); the `as_of` total rule; lifecycle temporal rules
|
|
735
|
+
(`:lifecycle_state_invalid`); `host_bounds` totality over the thirteen
|
|
736
|
+
bound names (structure only — the algebra surface owns the rest); empty
|
|
737
|
+
`allowed_model_roles` valid. Every `adapter_identity`/`profile_identity`
|
|
738
|
+
and every string nested in tool/data/build members is strict-scanned
|
|
739
|
+
(`:forbidden_portable_value` in deployment positions). A signature's
|
|
740
|
+
`purpose` is asserted per artifact (`deployment` here, `blueprint` in
|
|
741
|
+
`Blueprint` — the symmetric cross-surface gap this closes). The extension
|
|
742
|
+
envelope judgment is extracted to `AgentBlueprintProtocol.Extension` so
|
|
743
|
+
both tables carry one definition, and `Negotiation` resolves the
|
|
744
|
+
artifact kind from the digest member so each
|
|
745
|
+
artifact's `required_core_fields` check against its own vocabulary. The
|
|
746
|
+
facade gains `decode_deployment/2`, and a new architecture gate proves
|
|
747
|
+
the no-second-pipeline invariant (delegation to `Registry.validate` plus
|
|
748
|
+
no local stage definitions — planted-red proven, after the exports-only
|
|
749
|
+
form was found vacuous by the same mutation).
|
|
750
|
+
- Deployment hardening pass: `verify_binding/3` gains a
|
|
751
|
+
stage-0 shape totality — a non-object root, DUPLICATE root members, or a
|
|
752
|
+
malformed `tool_bindings` entry (shape, operands, digest) denies before
|
|
753
|
+
any cross-artifact judgment, and validated entries thread every later
|
|
754
|
+
stage (the blocking finding of an independent review: malformed
|
|
755
|
+
bindings were silently discarded, failing OPEN); negotiation restores revision-first
|
|
756
|
+
order ahead of the new artifact-kind resolution, which now requires a
|
|
757
|
+
well-formed string digest member (a malformed tag is machinery
|
|
758
|
+
`:invalid_type`); the exact-version detector becomes one total charset
|
|
759
|
+
rule (bare tilde, OR/comma/semicolon lists, and not-equal comparators
|
|
760
|
+
join the denied range vocabulary); `max_attestation_age_ms` is
|
|
761
|
+
shape-guarded (a non-integer bound silently failed to apply);
|
|
762
|
+
scheme-relative network-path references (`//authority/path`) deny in
|
|
763
|
+
every strict scan position; and the portability member-name denylist
|
|
764
|
+
folds kebab/SCREAMING/camel spellings onto one normalized form (the
|
|
765
|
+
normalization lesson swept across the guard family).
|
|
766
|
+
- Negotiation + compiled-in extension registry: the
|
|
767
|
+
evolution gate (`AgentBlueprintProtocol.Negotiation`) with the pinned
|
|
768
|
+
internal precedence (revision → required_core_fields → extensions) and
|
|
769
|
+
registry-consistent reason rules for malformed machinery; explicit revision
|
|
770
|
+
SET support (never ranges — a miss denies `:protocol_revision_unsupported`
|
|
771
|
+
in both directions); the three fail-closed required-core-field checks;
|
|
772
|
+
the positional extension state machine (unregistered critical denies,
|
|
773
|
+
unregistered optional QUARANTINES byte-exactly with a notice fact,
|
|
774
|
+
criticality conflict denies for live states before state handling,
|
|
775
|
+
deprecated/retired/reserved cells all decided); critical-body validation
|
|
776
|
+
only against digest-pinned host schemas (`:extension_schema_unavailable`
|
|
777
|
+
/ `:extension_schema_digest_mismatch`); and a reserved-semantics
|
|
778
|
+
denylist (bound-shaped member names, camelCase twins included) over ALL
|
|
779
|
+
extension bodies. The registry (`ExtensionRegistry`) is compiled-in
|
|
780
|
+
data — drift unrepresentable, backed by a new beam-census gate that
|
|
781
|
+
asserts no shipped module touches the filesystem (planted-red proven) —
|
|
782
|
+
carrying the five first-release entries with `com.example/federation`'s schema
|
|
783
|
+
authored in-repo under the new `:extension_schema` digest domain.
|
|
784
|
+
`Blueprint.from_value/2`'s `:authored_extensions` option opens the
|
|
785
|
+
encoded-content carriage channel: negotiation-validated critical bodies
|
|
786
|
+
skip the portability value-shape heuristics (their controls are the
|
|
787
|
+
schema pin and the denylist). The facade gains `negotiate/2`.
|
|
788
|
+
- Portability named-encoding closures: the raw-key floor
|
|
789
|
+
drops to 24 decoded bytes (catches AES-128-class hex keys) with hyphenated
|
|
790
|
+
UUIDs exempt by shape in every mode (the spec-pinned honest-limit
|
|
791
|
+
calibration); padded standard base32 (up to six pad chars) joins the
|
|
792
|
+
padded-base64 class; and a colon-chunked hex fingerprint class (the SSH
|
|
793
|
+
fingerprint / EUI form, 24+ decoded bytes) denies while the chunk grammar
|
|
794
|
+
spares tagged content addresses and MAC addresses.
|
|
795
|
+
- Blueprint artifact + generic registry engine: the ONE
|
|
796
|
+
table-driven decode/validate engine (`AgentBlueprintProtocol.Registry`)
|
|
797
|
+
parameterized by `AgentBlueprintProtocol.Blueprint.table/0`'s
|
|
798
|
+
18-member field registry (the closed-world Blueprint core member
|
|
799
|
+
table), with the pinned failure precedence
|
|
800
|
+
(unknown member → missing required → type → constraint → cardinality →
|
|
801
|
+
nested → cross-field hooks). `Blueprint.decode/2` runs the fail-closed
|
|
802
|
+
pipeline in order: canonical verify (`:non_canonical_bytes` before any
|
|
803
|
+
semantic read or digest work — the canonicality obligation, digests computed only
|
|
804
|
+
over exact received bytes), registry validation (closed world;
|
|
805
|
+
tag-strict integer typing so a float-tagged window value in an
|
|
806
|
+
integer-typed core field denies `:invalid_type` — the window-float obligation,
|
|
807
|
+
visible only at this layer), the portability scan, then the
|
|
808
|
+
content-digest comparison (`:digest_mismatch`). Also ships
|
|
809
|
+
`AgentBlueprintProtocol.Predicate` (the closed, order-independent
|
|
810
|
+
predicate algebra: grammar validation against declared ports, the
|
|
811
|
+
256-node ceiling, and error-dominant `evaluate/2`), and
|
|
812
|
+
`AgentBlueprintProtocol.Portability` (the never-portable structural
|
|
813
|
+
guard: the 34-name member denylist over the open regions and the
|
|
814
|
+
value-shape denylist — PEM armour, compact JWS, network-authority URIs,
|
|
815
|
+
≥32-byte clean base64url with the identifier-style exemption — over every
|
|
816
|
+
other string including signature `key_id`). The facade gains
|
|
817
|
+
`decode_blueprint/2`.
|
|
818
|
+
- Public Elixir package starter with zero third-party/Hex production
|
|
819
|
+
dependencies.
|
|
820
|
+
- Explicit non-authorizing product boundary and release-candidate posture.
|
|
821
|
+
- RFC 8785 JSON Canonicalization Scheme (`AgentBlueprintProtocol.Canonicalization`):
|
|
822
|
+
UTF-16 code-unit member sorting, §3.2.2.2 string escaping, hand-written
|
|
823
|
+
ECMA-262 §7.1.12.1 number serialization (byte-exact against every finite
|
|
824
|
+
RFC 8785 Appendix B vector), and `verify/2` decode→re-encode→byte-compare
|
|
825
|
+
interchange enforcement with fail-closed guards for duplicate names,
|
|
826
|
+
invalid UTF-8/lone surrogates, and out-of-bound integers on the encode path.
|
|
827
|
+
- Strict unpadded base64url codec (`AgentBlueprintProtocol.Base64Url`):
|
|
828
|
+
RFC 4648 §5 alphabet, RFC 7515 §2 padding-free wire form, and RFC 4648
|
|
829
|
+
§3.3/§3.5 canonicality — padded input, non-alphabet characters, and
|
|
830
|
+
non-canonical pad-bit spellings (which alias the same bytes) all reject
|
|
831
|
+
with value-free reasons.
|
|
832
|
+
- Tagged content digests (`AgentBlueprintProtocol.Digest`):
|
|
833
|
+
`"sha-256:<43-char unpadded base64url>"` wire strings over domain-separated
|
|
834
|
+
preimages (`SHA-256(separator || <<0>> || canonical JCS bytes)` under the
|
|
835
|
+
registered domain-separation separators), `from_tagged/1` fail-closed parsing
|
|
836
|
+
(unknown algorithm tag vs malformed body, wrong-length bodies included),
|
|
837
|
+
constant-time `equal?/2`, and `verify_content/3` (parse, then compare;
|
|
838
|
+
divergence denies `:digest_mismatch`). SHA-256 conformance is pinned to the
|
|
839
|
+
FIPS 180-4 known-answer vectors.
|
|
840
|
+
- Detached JWS signature envelope (`AgentBlueprintProtocol.Signature`):
|
|
841
|
+
RFC 7515 compact serialization with the RFC 7797 `b64=false` unencoded
|
|
842
|
+
detached payload — the signing input is
|
|
843
|
+
`BASE64URL(JCS(protected_header)) || "." || JCS(signed_attributes)` —
|
|
844
|
+
Ed25519 verified through `:crypto`, verify-only (an architecture gate
|
|
845
|
+
enforces no `:crypto.sign` call, no private-key parameters, and no
|
|
846
|
+
key-material shape anywhere in the shipped source). Host-supplied trusted
|
|
847
|
+
keys match by `key_id` (`:signature_key_unsupported` when absent,
|
|
848
|
+
`:signature_not_verified` on divergence — facts, never authorization).
|
|
849
|
+
The exact four-member protected header (`alg/crit/b64/kid`) and the five
|
|
850
|
+
signed attributes are closed-world with fail-closed, value-free denials;
|
|
851
|
+
`kid` must equal the signed `key_id`, which is dot-free so the unencoded
|
|
852
|
+
payload can never carry `.` (RFC 7797 §5.2). Compact rendering (`h..s`,
|
|
853
|
+
empty payload segment per RFC 7515 Appendix F) supports standard-tooling
|
|
854
|
+
cross-checks. RFC 8032 §7.1 TEST 1 is reproduced byte-exact. Attestations
|
|
855
|
+
share the envelope with a registered `kind` and `statement_digest`; the
|
|
856
|
+
kind registry is empty, so attestations deny `:attestation_malformed`
|
|
857
|
+
today (fail-closed until kinds become data).
|
|
858
|
+
|
|
859
|
+
### Changed
|
|
860
|
+
|
|
861
|
+
- Integer window decode rule (the amendment): a pure-digit number lexeme
|
|
862
|
+
above the I-JSON bound ±(2^53−1) now decodes as a float when it is exactly
|
|
863
|
+
that double's canonical ECMAScript serialization (e.g. the RFC 8785
|
|
864
|
+
Appendix B vectors `9007199254740992`, `295147905179352830000`), and
|
|
865
|
+
denies with the new `:number_not_double_expressible` reason otherwise
|
|
866
|
+
(retiring the interim `:integer_magnitude` decode reason). Canonical
|
|
867
|
+
pure-digit float output in [2^53, 10^21) now round-trips `verify/2`; the
|
|
868
|
+
encode/verify asymmetry previously documented here is closed.
|
|
869
|
+
- Bounded JSON Schema 2020-12 dialect + instance validator
|
|
870
|
+
(`AgentBlueprintProtocol.Schema`): the closed 16-keyword subset
|
|
871
|
+
(`type properties required items enum const minimum maximum minLength
|
|
872
|
+
maxLength minItems maxItems additionalProperties oneOf $defs` plus
|
|
873
|
+
document-local `$ref`) over the tagged algebra, with everything else —
|
|
874
|
+
`pattern`/`format`/`patternProperties`/`if-then-else`/`allOf`/remote
|
|
875
|
+
`$ref` and the rest of the 2020-12 keyword universe — denying
|
|
876
|
+
`:schema_keyword_not_allowed`. 2020-12 semantics read first-hand and
|
|
877
|
+
pinned: type-targeted assertions auto-pass other types, missing keywords
|
|
878
|
+
never fail, `oneOf` is exactly-one, boolean schemas are the substrate,
|
|
879
|
+
numbers compare by mathematical value across the integer/float tags
|
|
880
|
+
(tag-blind `type:"integer"` — the tags do not survive the wire), object
|
|
881
|
+
equality is order-blind, and string lengths count codepoints (not
|
|
882
|
+
graphemes, not UTF-16 units). Resource posture: complexity metered as
|
|
883
|
+
`nodes + keywords + Σ(branches) + depth × 4` against the 512 profile
|
|
884
|
+
ceiling; evaluation memoized on (schema node, instance location) —
|
|
885
|
+
closing the acyclic-`$ref`-DAG exponential blowup for passing AND failing
|
|
886
|
+
instances; document-local RFC 6901 pointers (split-then-unescape, `~1`
|
|
887
|
+
before `~0`) resolve at parse, and application-reachable reference cycles
|
|
888
|
+
deny while dead `$defs` self-references parse. Both `parse/2` and
|
|
889
|
+
`validate_instance/3` are total — malformed tagged shapes deny, never
|
|
890
|
+
raise. Multi-failure reasons follow a fixed canonical keyword order
|
|
891
|
+
(mirrored for the TS verifier).
|