Loading evidence…
Reading the recorded public case pack.
Evidence timeline
- Authenticating local case shape…
An agent claims the tests passed. But which commit did CI test, and did source change afterward? Follow real GitHub Actions records and a recorded Kiro coding session.
Evidence scope. The first three cases use hypothetical claims with real public GitHub run metadata. Case four uses a genuine Kiro CLI claim and self-recorded local test/edit receipts. Local logs are editable, not independently attested. No case proves code correctness. Read the boundaries.
Choose an exhibit. Inspect the evidence. Reveal the verdict.
Reading the recorded public case pack.
Each outcome is an assertion about the supplied evidence artifact. None certifies that the coding agent fixed a vulnerability or implemented correct behavior.
A green run on SHA A cannot stand in for a claim made about SHA B. The Git graph decides whether the cited result is ancestral.
GitHub run links identify provider records; the local Kiro case has no public transcript URL. Both recorded snapshots and editable local logs lack signed independent attestation.
Three examples use real workflow records with hypothetical claims. The fourth draws from an authentic Kiro session; no post-edit rerun was seen in that saved session. Outside evidence remains unknown.