Publish a verified trace and dataset listing surface #85

Outcome

Publish a read-only-first listing surface for opt-in traces and datasets with provenance, coverage, license, buyer, and delivery evidence.

Current behavior

The former NIP-DS data market shipped thinly and was abandoned. The forge now has a plausible buyer in training and evaluation work, but it has no listing or delivery surface tied to current authority and visibility rules.

Source: docs/episode-triage.md, episodes 215 and 266 and the recruitment station.

Contract

• Build on the normal authenticated OpenAgents API and runnable operator software; do not revive NIP-90 DVMs.
• List artifact digest, owner-safe description, schema, size, coverage, redaction, provenance, license, price when applicable, named buyer class, and evidence freshness.
• Require the opt-in licensing contract before publication.
• Keep source artifacts inaccessible until an admitted delivery or evaluation flow authorizes access.
• Record offer, acceptance, delivery, verification, and settlement references without moving money through the listing service.
• Start with OpenAgents-owned demand and a read-only catalog before opening third-party offers.
• Support export and removal without breaking immutable transaction receipts.

Acceptance criteria

• A caller can discover compatible licensed datasets without learning private source metadata.
• Every listing binds to exact content and provenance digests.
• Delivery of another digest cannot satisfy an accepted listing.
• Removing a listing blocks new transactions while preserving prior bounded receipts.
• The first production listing names its buyer and verification policy.

Verification

Test listing, search, authorization, digest binding, removal, redaction, delivery mismatch, and stale license. Qualify one low-risk listing end to end on staging.

Dependencies

Depends on the licensing-contract issue and project 3 coverage and receipt work.