# Evidence Receipt Generation

> Generate portable evidence receipts from run artifacts. Use when users ask for ticket-ready proof, receipt footers, or integrity-backed handoff metadata. Use when this capability is needed.

- Skill: `tomevault-io/evidence-receipt-generation` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/evidence-receipt-generation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/evidence-receipt-generation/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/evidence-receipt-generation

---


# Evidence Receipt Generation

Use this skill to generate integrity-backed receipts that are portable across CI, tickets, and audit handoff.

## Gait Context

Gait is an offline-first runtime for AI agents that enforces tool-boundary policy, emits signed and verifiable evidence artifacts, and supports deterministic regressions.

Use this skill when:
- incident triage needs portable receipt handoff proof
- CI gate failures require receipt/evidence attachment
- evidence outputs must be generated from Gait artifacts

Do not use this skill when:
- Gait CLI is unavailable in the environment
- no Gait run/pack artifact or run identifier is available as input

## Required Inputs

- `source`: run id, runpack path, or pack path.
- `out_path` (optional): destination file for JSON receipt output.

## Workflow

1. Verify integrity before receipt generation:
   - `gait verify <source> --json`
2. Generate receipt from source artifact:
   - when `out_path` is provided: `gait run receipt --from <source> --json > <out_path>`
   - when `out_path` is omitted: `gait run receipt --from <source> --json`
3. Parse receipt fields for handoff from `out_path` (if set) or stdout:
   - `ok`, `run_id`, `manifest_digest`, `ticket_footer`, `bundle`
4. Return concise evidence block containing:
   - source identifier
   - manifest digest
   - ticket footer text
   - verification status

## Safety And Portability Rules

- Never invent digests, run ids, or receipt text.
- Treat failed verification as a blocking state for receipt publication.
- Keep receipt output machine-readable and transportable.
- Avoid environment-specific absolute paths in final handoff.

## Usage Example

```bash
gait demo --json
mkdir -p ./artifacts
gait verify run_demo --json
gait run receipt --from run_demo --json > ./artifacts/receipt.json
```

Expected result:
- verify returns `ok=true` for intact artifacts
- receipt file contains a non-empty `ticket_footer` suitable for issue or PR evidence

## Validation Example

```bash
gait demo --json
mkdir -p ./artifacts
gait run receipt --from run_demo --json > ./artifacts/receipt.json
python3 - <<'PY'
import json
from pathlib import Path
p = json.loads(Path('./artifacts/receipt.json').read_text(encoding='utf-8'))
assert p.get('ok') is True
assert str(p.get('ticket_footer', '')).strip()
print('validated receipt footer present')
PY
```

Expected result:
- script prints `validated receipt footer present`

## Provider Notes (OpenAI Codex)

- Invoke explicitly as `$evidence-receipt-generation` when asking Codex to run this workflow.
- Keep outputs grounded in command results and `--json` payload fields.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/clyra-ai) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->