SPECTERAUDITAGENT ALIBI INVESTIGATOR / V2
RECORDED CI + LOCAL KIRO EVIDENCE
FOLLOW THE TEST. THEN FOLLOW THE SOURCE EDITS.

Every agent has an alibi.
Follow the commit.

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.

Inspect the real Kiro case Analyze your own session 4 CASES · NO SIGN-UP · RECORDED EVIDENCE

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.

01 / OPEN THE CASE FILE

The investigation chamber

Choose an exhibit. Inspect the evidence. Reveal the verdict.

Loading recorded case files…
CASE ARCHIVE4 EXHIBITS

No account, code execution, or credentials needed. The real Kiro exhibit shows scrubbed, local self-reported tool receipts; raw logs are not published.

CAPTURED AT—DATA ORIGINRecorded GitHub Actions + self-recorded Kiro CLI (separate evidence types)
CASE 01 / RECONSTRUCTIONRECORDED RUN · HYPOTHETICAL CLAIM

Loading evidence…

Recorded evidence only · not proof of correctness

Reading the recorded public case pack.

THE CLAIMED REVISION—Target commit SHA
CITED CI REVISION—Source selected from record
RECONSTRUCTED CHAIN OF CUSTODY

Evidence timeline

EARLIEST → LATEST
  1. Authenticating local case shape…
02 / INTERROGATEDoes the evidence match the claim?
02 / EVIDENCE, NOT THEATER

How to read the verdict

Each outcome is an assertion about the supplied evidence artifact. None certifies that the coding agent fixed a vulnerability or implemented correct behavior.

01

Exact commit binding

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.

02

Provider-reported only

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.

03

No synthetic failure

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.