feat(capsule-emit): lift bundle+disclosure block, per-item bundle disclosure - #56
Open
StevenMih wants to merge 2 commits into
Open
feat(capsule-emit): lift bundle+disclosure block, per-item bundle disclosure#56StevenMih wants to merge 2 commits into
StevenMih wants to merge 2 commits into
Conversation
…closure
scitt-cose#30 (merged + deployed) fixes the viewer's array-fragment bundle
path to unwrap a Disclosure Envelope before checking capsule_id/chain, so
the vacuous-Integrity-pass bug that motivated the producer-side
PermalinkError refusal no longer exists. build_url() now accepts
bundle=True + disclosures={capsule_id: {field: payload}} for per-item
disclosure; the CLI's --reveal takes SELECTOR:FIELD=payload.json for
bundles (1-based record number or capsule_id prefix). Per-item digest
mismatch still refuses the whole URL. Added a fragment-size warning at
~16KB.
Same frozen goose demo run (leaves 267/268/269), no re-anchor — built and
browser-confirmed the fully disclosed bundle permalink against the
deployed viewer.
Signed-off-by: stevenmih <stevenmih88-3@gmail.com>
StevenMih
force-pushed
the
capsule-emit-lift-bundle-disclosure-block
branch
from
August 11, 2026 05:50
85be7b9 to
b0b4cd1
Compare
capsule_ids are hex, so an all-digit >=8-char prefix is legal (~2.3% of capsules). selector.isdigit() alone misread such a prefix as a record index -- either an out-of-range error on a valid prefix, or silently resolving the wrong record when the prefix happened to also look like a valid index. Only treat the selector as an index when it's short enough that the two spaces can't overlap: len(selector) < 8. Signed-off-by: stevenmih <stevenmih88-3@gmail.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 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
capsule_id/chain, so the vacuous-Integrity-pass bug that motivatedcapsule_emit/permalink.py's producer-sidePermalinkErrorrefusal (bundle=True+disclosures=) no longer exists. That block is lifted.build_url()now acceptsbundle=True+disclosures={capsule_id: {field: payload}}for per-item bundle disclosure; single-capsuledisclosures={field: payload}is unchanged.--revealacceptsSELECTOR:FIELD=payload.jsonfor bundles (SELECTOR= 1-based record number or an>=8-charcapsule_idprefix); the old unqualifiedFIELD=payload.jsonform still works for a genuine single capsule and is refused (not silently misapplied) when more than one capsule is in scope.REVEALED · ✓ match, Regulatory context panel detectshuman-oversight-recordon an enveloped bundle item.Test plan
python3 -m pytest -q --ignore=tests/test_agentgateway.py— 461 passed (test_agentgateway.py's collection failure is a pre-existing local protobuf version mismatch, unrelated to this change)ruff check— cleanverify.agentactioncapsule.orgviewerexamples/goose-capsule/evidence/run-transcript.mdandREADME.mdupdated with the fully disclosed bundle permalink and browser-confirmation details🤖 Generated with Claude Code