Directory application promise

Free application, no paid acceleration, human review, and a public-listing requirement.

The application process evaluates current evidence. It is not a sales queue and does not sell registry access.

Free application

There is no fee to apply for a manual directory review.

No paid acceleration

Payment cannot purchase faster review, priority, approval, or production inclusion.

Manual review

Every application is checked against the published public-value, free-path, relevance, and safety standards.

Public listing required

The directory must create a useful publicly accessible product result.

Evidence before submission

Show the audience, complete free path, ownership, and repeatable workflow.

The review needs observable current facts rather than a marketing pitch or an unsupported traffic claim.

Audience and value

Show who uses the directory and what the listing helps them discover.

Provide the accepted product types, audience purpose, example public listings, and evidence that the directory creates more than a private lead record.

Free path

Show the complete route to a useful listing without mandatory payment.

Disclose every fee, optional promotion, final-step condition, reciprocal-link request, badge requirement, and review stage.

Ownership and workflow

Show that the operator and submission process can be verified.

Provide ownership evidence, current URLs, required fields, account behavior, verification messages, review process, and correction route.

What the review needs

Every requested field maps to a specific audit decision.

The form avoids collecting unrelated information and explains how each evidence group supports a manual review.

Application evidence

The evidence supplied by the directory owner.

Review purpose

The audit question that evidence must answer.

Field Application evidence Review purpose
Identity Directory name, public URL, operator, work email, and ownership evidence. Confirm who is responsible for the application and current workflow.
Audience Accepted products, audience purpose, example listings, and audience evidence. Evaluate public value and product relevance.
Free path Submission URL, complete free route, fee disclosure, and optional promotion. Verify that payment is not required for a useful listing.
Workflow Required fields, account behavior, review process, result state, and correction route. Assess repeatability, safety, and result detection.
Status Verified work email and durable application receipt. Enter manual review without implying approval or release timing.

Production application workflow

Submit, verify, enter manual review, and receive a signed status result.

An application is a candidate record. Approval, release staging, and production inclusion remain separate decisions.

  1. Submit one atomic application

    The server validates the complete application, duplicate state, abuse controls, and idempotency in one write operation.

  2. Verify the work email

    A signed verification link confirms that the applicant can receive status and evidence requests.

  3. Receive a durable receipt

    The applicant receives an opaque reference without exposing internal registry or review identifiers.

  4. Enter manual evidence review

    A reviewer checks ownership, public value, audience, free path, workflow, safety, and expected result.

  5. Provide more evidence when requested

    Missing or conflicting facts return as an evidence request rather than an automatic rejection or approval.

  6. Receive a signed status result

    Approval remains separate from host-rule verification, release staging, and production registry publication.

Application evidence

Show how the listing works.

The review needs ownership, audience, free-path, example-listing, fee, and workflow evidence. Approval cannot be purchased and an application does not create a production target automatically.

Development preview: the application API, email verification, evidence upload, and signed status route are not connected yet. This form does not send or store data.

Required production behavior: one atomic server submission, email verification, durable receipt, rate limit, bot control, RLS deny by default, and signed evidence upload URLs.

Production applications require email verification.

Explain where the free path begins and what public result it can produce.