Published registry standards
Every production target must provide a repeatable submission path, useful public listings, a relevant audience, a genuine free route, reasonable ownership and privacy controls, and an outcome that can be detected without unsafe or prohibited actions.
Published standards
A target needs current observable evidence for every core standard. A copied directory list or owner claim does not replace the audit.
The directory must publish enough current product information to help a relevant audience understand or discover the listing.
The useful listing path cannot require payment, an undisclosed final-step fee, a website badge, or a reciprocal backlink.
The required account, fields, verification, legal confirmation, review, and result must be understandable without unsafe or unrelated data collection.
Manual review process
The reviewer follows the current public workflow and records what a campaign can safely do, not what the directory promises in a sales message.
Confirm that the route loads, accepts the stated products, and exposes the actual required fields and conditions.
Verify that the output is public, useful, relevant to the audience, and more than a private lead record.
Follow the route through the final step and disclose every fee, badge, reciprocal-link, or promotion condition.
Identify the operator, contact route, privacy terms, listing terms, and a way to claim, correct, or remove a listing.
Record account behavior, verification, required assets, legal steps, final submit action, and observable outcomes.
Approve as a candidate, request evidence, reject, or keep the target outside production until the current state is safe and repeatable.
Audit decisions
A candidate decision never skips the separate production-rule and signed-release process.
Audit state
Next action
Registry governance
The registry can respond when a directory changes after its original review.
An owner application or public discovery record cannot enter production automatically.
Audit dates, workflow rules, and eligibility metadata belong to a named release state.
Candidate approval remains distinct from release staging and real campaign inclusion.
A changed free path, workflow, ownership, audience, safety state, or result can remove a target.
The current submission URL must load, accept the directory’s stated product types, expose the required fields and assets, and lead to a result that can be manually verified. A broken, hidden, invitation-only, or misleading path cannot enter production.
The directory must publish product pages or records that are visible to the public and contain enough information to help the stated audience understand the listed product. A private database, lead form, or paid report is not a public listing.
The directory should have a clear category, audience, or discovery purpose that matches the product types it accepts. A broad claim that every product is eligible is not enough when the public listings and audience do not support that scope.
A builder must be able to request or create a useful listing without mandatory payment. Optional promotion may exist, but the free path cannot secretly become paid at the final step.
Approval is rejected when a listing requires automatic payment, a website badge, a reciprocal link, an unrelated marketing opt-in, or another condition that Vibe Launch Master is not authorized to place or accept.
The directory should identify the operator or a responsible contact route, explain its privacy and listing terms, and avoid requesting credentials, payment data, or identity documents that are unnecessary for a normal product listing.
A product owner needs a reasonable way to claim, correct, update, or request removal of a listing. A directory with no ownership or correction process creates avoidable accuracy and safety risk.
Reviewers must be able to inspect the current workflow, required fields, account behavior, verification messages, legal confirmations, final submit action, and expected result. A flow that cannot be repeated cannot be safely automated.
Directories are rejected when the apparent submission flow exists mainly to collect contact data, resell services, force irrelevant outreach, publish low-quality duplicate pages, or create a misleading appearance of product discovery.
Before applying
Include the submission URL, example public listings, accepted products, free-path details, ownership evidence, audience evidence, fee disclosure, and review process.
