Evidence

Takes one governed run out of the audit trail and writes a package that says what ran, under which policy, and who approved it. The package is signed, and a reader on another machine can check it without holding any key.

What you can do

Find a run. Every capability call carries the run it belongs to, so the panel lists runs rather than calls. A run that ended moments ago appears too, marked for the records that have not reached disk yet.

Read the package before it exists. The panel shows the exact bytes that will be written and signed. Nothing is written until you confirm them.

Write it in the format you need. JSON for a machine, Markdown for a person. Both carry the same content and both are signed.

Verify a package from anywhere. Verification needs no key, so a package produced on a colleague's machine, or a year ago, checks here.

The five questions, and what this version answers

A package answers five questions about a run: which data, which code, which environment, which gates, who approved. It states a status for each rather than a value, because none of them can be answered from one source in every run.

Question	What you get
Which data	Every file, model, prompt and dataset the run's calls named, with the capabilities that named nothing listed beside them.
Which code	The commit the workspace was on, with its refs and author.
Which environment	The interpreter, version and whether it is externally managed.
Which gates	Every gate call the run made and what each gate answered — passed, failed or skipped, with the reason. The numeric score behind a verdict is kept off the audit record, so a reader can check which gates passed and not by how much.
Who approved	Every call that needed a person, joined to the grant that covered it, kept separate from the calls a policy rule allowed with nobody asked.

A package that quietly dropped the rows it cannot fill would be making the overclaim an auditor finds first. These say so instead.

What a signature proves

A reader can check the package was not altered since it was signed. A reader cannot check which organisation produced it: the machine that makes a package is the machine that signs it, and nothing vouches for its key. Every package states this limit on its own face.

Getting started

1. Open Evidence from the activity bar.
2. Pick a run. The panel lists the runs the audit trail still holds.
3. Read what the package will claim, then choose JSON or Markdown.
4. Press Review and write. The files land in .punica/evidence/<run id>/.

To check a package, paste its directory into the verify field. That works on a package this machine never produced.

What it needs

The desktop app, version 1.0.7 or newer. The signing key belongs to the host and is never handed to an extension, which is what makes the signature worth anything.

What it reaches

It reads the audit trail, the loaded policy, the commit graph and the active Python environment, and it writes into the workspace. It reaches no network at all.