Run receipts: what your coding agent actually did

When a coding agent stops, it writes a summary. The same model wrote the code. It grades its own work.

After the pull request is saved, Syndai can issue a signed delivery receipt. It links each checked condition to its check and the checked file tree.

What's in a receipt

When issued, the receipt lists each condition, result, check, and checked file tree. It also says how the team set the conditions. Syndai signs those fields. A reader can then see who made the record and if it changed.

When the run lacks a passing check for a condition, the receipt says so. It never turns a gap into a pass. The full table of what we may and may not claim is published at /claims.

Why it matters

Without a receipt, you must guess what the run checked. With one, you can read the condition, check, and file tree. Then you decide. A receipt also records the review lanes. Each diff clears them before its pull request opens.

A receipt is private at first. Its owner can publish a share link and revoke it later. A teammate with a live link sees the same signed record.

We wrote more in Welcome to Syndai. A condition with no check is not a pass. The receipt shows the gap.

Common questions

Is the receipt written by the model? No. Syndai makes it from saved delivery and check records, then signs it.

Does the signature mean the work was rerun elsewhere? No. The checks run in the authoring sandbox. An independent fresh-sandbox rerun is not live yet.

Can I share a receipt? If you own the run, you can publish a link. It is private by default. You can revoke the link at any time.