fix(artifacts): clarify provider privacy boundary - #399
Open
8Dionysus wants to merge 2 commits into
Open
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
8Dionysus
force-pushed
the
goal-01a02fec-machine-privacy-boundary-followup
branch
from
August 30, 2026 08:47
de3ad8d to
afdc9c3
Compare
Owner
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Already looking forward to the next diff. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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
1 participant
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
Validation
python -m pytest -q tests/public_smoke/test_artifact_bundle_verifier.py(253 passed)python scripts/ci_gate.py --mode release-artifactpython scripts/release_check.py --sdk-root .deps/aoa-sdk --receipt /srv/abyss-machine/tmp/ai/code-intelligence-goal-01a02fec-20260823/runtime-visible/machine-privacy-release-v2.json(full owner claim/evidence sufficient=true; exact CI pins aoa-sdk b73c8aca and aoa-stats fb984e66)Context / remaining proof
The previously produced code-intelligence provider artifact correctly failed closed at consumer admission because the old wording combined a publishable prefix with an ambiguous private-evidence phrase. This source correction does not retroactively admit that artifact. After landing, the Goal will produce, sign, promote, gate, and install a fresh artifact from the landed SHA. Runtime deployment and semantic acceptance remain separate downstream proof.