A restrained field guide to reviewed launch surfaces, founder-owned materials, and 88CN profile flows.
Early AI project submissions work best when founders prepare clear source material, choose reviewed channels, and keep every public claim auditable. This report maps practical submission surfaces without treating distribution as a shortcut or a paid placement mechanism.
Maintain one canonical page that explains the product, audience, docs, pricing status, and public source links.
Owned pages should be factual. Avoid claims that depend on unverified adoption or external placement.
Use official docs, changelogs, examples, and repository metadata to help technical evaluators understand the project.
Development signals are useful context, not proof of commercial traction or future outcomes.
Submit to editorially reviewed lists or databases when the channel has clear inclusion criteria and update controls.
A reviewed listing should not be treated as distribution certainty. Keep the submitted facts auditable.
Announce meaningful launches, changelogs, or open calls in communities where the audience is already relevant.
Avoid generic repetition. Community posts should add context rather than repeat the same pitch.
Use 88CN to submit a project, check machine-readable basics, and later claim a reviewed public profile.
88CN review is editorial and signal-based. It does not promise external placement or business results.
Write one stable public page with product scope, target user, docs, source links, and founder-controlled update paths.
Run a deterministic audit for title, description, canonical, schema, Open Graph, robots, and sitemap signals.
Open flowSend a structured project submission for admin review. Submitted projects do not publish automatically.
Open flowIf a reviewed profile exists, founders can request claim, correction, or removal review from the public profile flow.
Open flowChannels are grouped by surface type rather than promotional value.
The page favors channels with clear review, source, and correction boundaries.
No third-party directory content, screenshots, logos, or descriptions are copied.
No automated posting workflow, public API exposure, payment path, or external service integration is introduced.