Repository navigation
Add offline Codex capture analysis - #46
Merged
Merged
Conversation
Triad: SHIP 2026-09-20
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.
Provider captures currently prove provenance without exposing usable turn or request observations. Add an offline
provider_evidence.py --analyze-codex --capture-root PATH --capture-id IDcommand that verifies one pinned Codex capture and emits deterministic JSON with synthetic identities, turn boundaries, request open/resolved events, and thread-state observations.Complete observations exit 0; partial observations retain unresolved requests and exit 2. Malformed, conflicting, stale, tampered, or ineligible input exits 1 without publishing a report. Parsing and output are bounded, and private text and actual provider identifiers are excluded.
Reports remain explicitly unqualified, with task binding and source health unknown. The collector pin, public capability matrix, and production CLI stay unchanged. This adds offline evidence tooling; current-provider repinning and live qualification remain follow-up work.
Validation: 22 disposable scenario groups, 793 malformed-input mutations, capture/receipt integrity and file-boundary checks, hash-seed determinism, finite decimal payloads and nonfinite rejection, 1,200 JSON nesting depths on CPython 3.9.6 and 3.14.7, 122 existing tests, and the 24-cell artifact check. Repository tests are unchanged.