Repository navigation
render-vocab hashes the artifact (RFC 0010); guardrails coordinate re-blessed at @com::squillo/aph_guardrails@0.1.0 - #8
Merged
Conversation
added 4 commits
November 8, 2026 16:39
aae8ad3 deleted snapp/aph_guardrails@0.1.0-alpha.1.json and renamed aph@0.1.0-alpha.1.json to aph@0.1.0.json. Two aph-cli tests include_str!'d the deleted file, so the test binary stopped compiling (Rust interpreter workflow red on main); the conformance freshness weld still anchored the protocol bundle at the old name, a failure only a host with nlang sees. - aph-cli publish.rs: both pins read snapp/aph_guardrails@0.1.0.json, and the record's `n=` tag is checked against the bundle's own @snapp.name (now `@com::squillo/aph_guardrails`) instead of a remembered literal — the test's stated intent is to read rather than remember. - aph-conformance snapp_freshness_test.rs: the protocol-bundle weld is anchored at aph@0.1.0.json, the file the export actually writes. - aph-conformance nlang_snapp_test.rs: optionality is read in both toolchain spellings — abi 40 (nlang 0.1.0) puts `optional: true` on the prop, abi 33 wrapped it in `@attrs`; the abi-40 bundle made four optional props look like unexercised requirements. - README: the three bundle paths follow the rename. No blessing text, digest, or DNS record is changed here; the vocabulary coordinate question raised by the re-emit is a separate ruling.
…-blessed at @com::squillo/aph_guardrails@0.1.0 The §8.5.1 `h` tag was rendered from the bundle's internal @snapp.integrity string. RFC 0010 (v0.3 delta §2) rules that out: a file cannot carry its own hash, so a carried string is over something other than the fetched bytes and §8.5.3's byte check can never pass against it. Executing against the live record confirmed it — the 2026-08-31 digest matched no committed revision of the bundle. - aph-core: `discovery::publish::vocabulary_digest(&[u8])` — SHA-256 over the artifact bytes, `sha256-<base64>` (SRI-style). `render_vocab_record` takes that digest; its doc no longer claims all three inputs come from `@snapp`. sha2 joins aph-core's dependencies from the workspace table (it was already in the lockfile via ed25519-dalek). - aph-cli: `render-vocab` reads the file as bytes, hashes them, and parses the same bytes for name and version; `vocabulary_record` takes the digest. Tests pin that the rendered `h` is the artifact digest and is NOT the carried integrity string. - Guardrails README, README, CHANGELOG: the blessed citation is `@com::squillo/aph_guardrails` 0.1.0, `sha256-mhSlBjnzsw25+HiXcIJkijKokYkdf0CnUTj4xT0oWJc=` over snapp/aph_guardrails@0.1.0.json (re-ruled 2026-11-08 after the PRD-887 W4 re-emit). Earlier coordinates are retired; the alpha.1 bundle left the tree with W4 (one name, one manifest). The live `_aph._vocab.squillo.com` record was updated to this value on 2026-11-08 and `aph render-vocab snapp/aph_guardrails@0.1.0.json` renders it byte for byte.
The public repository's sanitization check forbids citations to internal numbering schemes; the Guardrails README and CHANGELOG bullet carried one.
…abulary-digest change The byte-diff job fails by design on any aph-core change and uploads the runner's build as the rebuilt-aph-wasm artifact; this is that artifact, from the run that failed on 8efc3e9.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacks on #7 (its commit appears here until #7 merges).
render-vocabrendered the §8.5.1htag from the bundle's internal@snapp.integrity. RFC 0010 (v0.3 delta §2) rules that out: a file cannot carry its own hash, so a carried string is over something other than the fetched bytes and §8.5.3's byte check can never pass against it. Executing against the live record confirmed it: the 2026-08-31 digest matched no committed revision of the bundle.discovery::publish::vocabulary_digest(&[u8]) -> String, SHA-256 over the artifact bytes assha256-<base64>(SRI-style).render_vocab_recordtakes that digest.sha2joins aph-core's dependencies from the workspace table (already in the lockfile via ed25519-dalek; no new lock edge).render-vocabreads the file as bytes, hashes them, and parses the same bytes for name and version. Tests pin thathis the artifact digest and is NOT the carried integrity string.@com::squillo/aph_guardrails0.1.0,sha256-mhSlBjnzsw25+HiXcIJkijKokYkdf0CnUTj4xT0oWJc=oversnapp/aph_guardrails@0.1.0.json, re-ruled 2026-11-08 after the scoped re-emit. Earlier coordinates are retired; the alpha.1 bundle left the tree with that re-emit (one name, one manifest).Live state:
_aph._vocab.squillo.comwas updated to this value on 2026-11-08 (authoritative + 1.1.1.1 verified), andaph render-vocab snapp/aph_guardrails@0.1.0.jsonrenders it byte for byte.Gate: clean
git archiveexport plus these changes, full default-membercargo test --no-fail-fast: 653 passed, 0 failed.