Settle revenue share for verified paid skill use #91

Outcome

Pay a skill contributor when a paid workflow uses the exact registered skill version and reaches a verified accepted outcome.

Current behavior

The proposed skill registry can attribute usage, but no contract connects a paid buyer, immutable skill version, accepted outcome, revenue-share terms, and self-custodial payout.

Source: docs/episode-triage.md, episodes 206, 238, and 269.

Contract

• Bind revenue-share terms to the exact skill version before dispatch.
• Record buyer payment, admitted invocation, accepted outcome, gross amount, fees, contributor share, and payout destination.
• Pay only for verified paid use; free, failed, canceled, duplicate, or unaccepted runs earn no royalty.
• Use idempotent settlement and self-custodial destinations.
• Define refunds, disputes, version removal, license expiry, and multi-skill attribution.
• Publish bounded totals and receipts under transparency policy.
• Start with one skill and one low-value paid canary after forge bounty settlement succeeds.

Acceptance criteria

• One paid accepted outcome produces one contributor payout tied to an exact skill digest.
• Retrying, replaying, or reusing a receipt cannot pay twice.
• A failed verifier, refund, stale version, or changed terms blocks settlement.
• The buyer and contributor can export receipts and reconcile the calculation.
• The platform never takes custody of a contributor's long-term balance.

Verification

Fault-test duplicate requests, lost acknowledgement, refund, dispute, multi-skill attribution, stale terms, and privacy. Run one low-value production canary after all gates pass.

Dependencies

Depends on the typed skill registry and successful completion of the project 8 verified bounty canary.