fix(akroasis): correct Pinax authority boundary - #476
Merged
Conversation
Keep the reference-library application unnamed, reserve Pinax for the standalone relational engine, and remove the unused Sphragis staging dependency. Reframe the storage and encryption contracts around producer-owned Pinax page encryption and Akroasis domain envelopes.
Uh oh!
There was an error while loading. Please reload this page.
forkwright added a commit
that referenced
this pull request
Aug 26, 2026
## Summary - follow up merged #476 with the exact-head review corrections for its remaining Sphragis boundary drift - state that Akroasis has no adopted Sphragis dependency; any preview use stays default-off and pins an immutable producer revision - limit KAT evidence to conformance, keep `hazmat` prohibited, and assign qualified review/release promotion to `forkwright/sphragis#43` while #395 owns the exact consumer handoff - move the preview test command into an exact-revision Sphragis checkout or its matching CI context - replace false “reviewed profile” claims with accurate versioned, unaudited, default-inert wording - classify both maintained boundary documents as authored SSOTs instead of false frozen decision records ## Tracker disposition - References #395 without closing it. - `forkwright/sphragis#43` remains open and owns qualified cryptographic review and reviewed release promotion. - #131 remains closed historical design context, not a live promotion owner. - This PR neither implies nor records a favorable cryptographic review. ## Verification - `cargo fmt --all -- --check` - `git diff --check origin/main..HEAD` - Kanon deterministic lint and writing checks over the changed documentation - no build, test, or full gate command was run, per operator direction ## Base and collision check - based on live `main` at `0a6cc2316fede4fff1a19662ebeda00c43743920`, the merge commit for #476 - release PR #465 head `3a75328aeda6a8d0fe44af722068995953a0d8de` changes only `.release-please-manifest.json`, `CHANGELOG.md`, `Cargo.lock`, and `Cargo.toml`; it does not overlap this four-doc patch Co-authored-by: forkwright <cody@forkwright.com>
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 freeto 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.
Summary
Cargo.locknever contained Sphragisakroasis knowplaceholder agree; explicitly forbid a localcrates/pinaxidentityTracker reconciliation
hazmatprohibition.ARCH/substrate-dead-deprow, moving the measured baseline from 24 entries to 23; it does not weaken or complete that issue.Verification
cargo fmt --allcargo fmt --all -- --checkgit diff --checkgit diff --exit-code -- Cargo.lockcrates/pinaxdoes not exist.kanon-lint-baseline.tomlcontains 23 entriesCollision and residual gates
Cargo.toml; it was inspected and left untouched. This branch is based on livemainatd4ac3c5f24121ac3aeef0aca5b6baabf82f51f03.