Skip to content

feat(guard): add typed execution-assurance receipt - #2002

Open
kantorcodes wants to merge 4 commits into
release/3.1from
feat/eai-w2-receipts
Open

feat(guard): add typed execution-assurance receipt#2002
kantorcodes wants to merge 4 commits into
release/3.1from
feat/eai-w2-receipts

Conversation

@kantorcodes

Copy link
Copy Markdown
Member

Purpose

Wave-two slice: receipt schema extension with typed assurance fields.

Changes

  • runtime/execution_assurance_receipt.py — frozen ExecutionAssuranceReceipt extending the existing receipt model with achieved_boundary, attestation_trust, enforced/absent guarantee kinds, execution-context and terminal-statement digests. receipt_assurance_payload produces privacy-safe fields (no command/path/secret); validate_assurance_receipt_schema_version pins the alpha schema version. Composes alongside store_receipts.py/models.py without editing them (2.x compatibility preserved).

Verification

28 tests pass, including privacy assertions that no secret/path leaks into receipt fields; basedpyright 0 errors/0 warnings; ruff clean. No release or deployment authorized.

…fields

- Add ExecutionAssuranceReceipt dataclass with frozen/slots schema
- Add achieved_boundary and attestation_trust typed fields
- Add enforced/absent guarantee kind lists with deduplication
- Add execution_context_digest and optional terminal_statement_digest
- Add proof_lines bounded at 64 lines of <=256 chars, total <=16384 chars
- to_receipt_fields() excludes proof_lines for privacy safety
- receipt_assurance_payload() and validate_assurance_receipt_schema_version() helpers
- 28 tests covering schema validation, typed fields, privacy, immutability

Signed-off-by: Michael Kantor <6068672+kantorcodes@users.noreply.github.com>
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@kantorcodes, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: f9d044db-b029-415f-a929-fc709a800e09

📥 Commits

Reviewing files that changed from the base of the PR and between 7c72877 and d2e2303.

📒 Files selected for processing (3)
  • src/codex_plugin_scanner/guard/runtime/execution_assurance_receipt.py
  • tests/fixtures/guard-command-corpus/decision-diff-report.json
  • tests/test_guard_execution_assurance_receipt.py

Comment @coderabbitai help to get the list of available commands.

@capy-ai capy-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added 1 comment

Signed-off-by: Michael Kantor <6068672+kantorcodes@users.noreply.github.com>
Signed-off-by: Michael Kantor <6068672+kantorcodes@users.noreply.github.com>
Signed-off-by: Michael Kantor <6068672+kantorcodes@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant