RunOnProofDocs
Evidence firstScoped decisions
Integration · Relevance AI

Relevance AI Marketplace submission guide

This guide prepares a future decision. It does not authorize public sharing, acceptance of new terms, or submission.

Current state

This public repository does not represent a Marketplace submission or listing. Record the external state as NOT_SUBMITTED unless separate evidence proves a later state.

Before deciding to submit

Confirm:

  • current Relevance AI Marketplace eligibility and terms from official sources;
  • whether a Tool, agent, or both can be listed;
  • review requirements, pricing, support, privacy, and data-processing obligations;
  • whether legal terms require acceptance by Ricardo or the company;
  • whether a public listing needs a public production call path;
  • ownership of support, updates, incident response, and deprecation.

Stop for human action if login, MFA, new terms, identity documents, legal declarations, fees, or public-publishing confirmation are required.

Submission package to prepare

  • truthful title and short description;
  • public case and screenshots using synthetic data;
  • installation and everyday-use guide;
  • exact inputs and outputs;
  • current capabilities and limitations;
  • security and privacy summary;
  • cost/HTTP 402 explanation;
  • support and troubleshooting route;
  • version, repository SHA, and validation evidence;
  • statement that RunOnProof is not claiming a partnership.

Pre-submission gates

  • Public docs routes are live and coherent with GitHub.
  • Tool and agent pass all synthetic workspace cases or the listing precisely states which tests were run.
  • Current product, price, coverage, and source health are verified.
  • Automatic payment remains off unless separately designed and authorized.
  • No secrets or real personal data exist in examples or screenshots.
  • Rollback and support ownership are active.
  • Legal/terms acceptance is recorded by an authorized human.
  • The listing does not promise unsupported capabilities.

Possible external states

Record one exact state:

  • NOT_SUBMITTED
  • SUBMITTED_EXTERNAL_REVIEW
  • CHANGES_REQUESTED
  • APPROVED_NOT_LISTED
  • PUBLISHED_DISCOVERABLE_CERTIFIED
  • REJECTED

Never describe submission as approval or internal publication as public listing.

After a future submission

Preserve the submitted version and evidence. Track review feedback without weakening safety. Re-run synthetic certification for every requested technical change. Publish the final public URL only after independently confirming discoverability and installation behavior.

RunOnProof public documentationExplicit coverage · scoped claims · evidence first