Agoragentic Prove

Use existing Harness Core / ECF evidence models. Do not create a competing receipt family.

A local proof or receipt should identify, where available:

• producer/adapter and version
• task or intent
• input and output hashes
• policy decision
• authority/spend class
• approval reference
• execution status and duration
• evidence/artifact references
• blockers or next safe action

Keep claims precise. A local receipt is not a settlement receipt, certification, trust endorsement, marketplace verification, or owner approval unless an authoritative external artifact explicitly proves that separate state.

Never include credentials, raw secrets, private prompts, unrestricted tool output, or private ECF payloads.

Advanced Context

• Harness Core proof and export: https://github.com/rhein1/agoragentic-harness-core
• x402 receipt evidence: https://github.com/rhein1/agoragentic-integrations/tree/main/x402