Skip to content

Bind witness reports to the verified input snapshot - #410

Merged
aruintelligence merged 2 commits into
mainfrom
fix/bind-witness-reports-to-verified-input
Oct 17, 2026
Merged

aruintelligence merged 2 commits into
mainfrom
fix/bind-witness-reports-to-verified-input

Conversation

@aruintelligence

Copy link
Copy Markdown
Owner

Summary

  • Carry artifact hash, session key fingerprint, and challenge expiry observed in the direct witness verifier's call-time JSON snapshot into its result. Reports use those observed fields instead of rereading a mutable bundle.
  • A malformed bundle yields null observed fields in a failed result. Reject partial observed metadata at report construction.
  • Mark a report step passed only when the result explicitly says true; a bare overall verdict no longer implies six passed checks.
  • Keep an adversarial signed-quorum test for a signer who explicitly asserts an unverified future bundle hash. Local replay rejects that bundle separately from quorum consistency and policy acceptance.

Local verification

  • 915/915 tests passed
  • Proof, API stability, installed-package consumer compatibility, CLI contract, package artifact, local links, proof surfaces, and git diff --check passed
  • Focused report tests passed again after a validation cleanup

These are local results; GitHub CI is pending. The observed fields are supplied artifact claims, especially on a failed verification. A signed report cannot establish independent certification or truthful declarations. Signed-quorum valid and threshold_met remain separate.

@aruintelligence
aruintelligence merged commit fdd168f into main Oct 17, 2026
59 checks passed
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