Purpose
This issue provides public maintainer notice for a focused discoverability program on the collaboration branch codex/discoverability-growth.
Planned scope
- Establish version-controlled SEO, AI-answer, autonomous-agent, analytics, and distribution baselines.
- Repair the measurement path required to calculate mature 28-day Activated Discovery Users without fabricating unavailable historical data.
- Fix rejected competition analytics events and add privacy-safe autonomous-agent attribution.
- Consolidate internal homepage links onto the declared root canonical and strengthen contextual links to priority content.
- Prepare accurate submissions for eligible agent and MCP directories.
- Prepare three substantive DEV articles for separate action-time publication approval.
- Diagnose the current production API deployment failure and improve deployment evidence where needed.
Baseline evidence
Search Console for July 13–August 9, 2026 reports:
- 0 clicks
- 83 impressions
- 0% CTR
- average position 9.8
- 2 of 16 distinct sitemap canonical groups indexed
Analytics collection began July 19, 2026. The earliest fully mature 28-day acquisition cohort with a seven-day activation window can be measured on August 24, 2026. The current aggregate endpoint cannot validly calculate that cohort because it lacks the required first-acquisition-to-activation join and reliable exclusion controls.
The inventory verification guard currently reports zero verified claimable bounties because the observed candidates do not have executable verification paths. BountyScout has discovered recent GitHub issues, but those listings do not independently prove eligibility or payment.
Boundaries
- No unsupported earnings claims, fabricated metrics, misleading metadata, automated community spam, or paid-link schemes.
- No A2A promotion until the implementation conforms to the current specification.
- No OpenAI directory submission while the bounty/crypto workflow conflicts with current commerce policy.
- Third-party publications, submissions, outreach, and indexing requests will receive separate action-time confirmation.
BountySettled remains the payout-proof authority; external listings are discovery evidence only.
Coordination
Known overlap will be coordinated with PRs #904, #892, #906, #889/#885, and #799. Changes will use focused commits and the repository’s required review, merge, deployment, and verification workflow.
Purpose
This issue provides public maintainer notice for a focused discoverability program on the collaboration branch
codex/discoverability-growth.Planned scope
Baseline evidence
Search Console for July 13–August 9, 2026 reports:
Analytics collection began July 19, 2026. The earliest fully mature 28-day acquisition cohort with a seven-day activation window can be measured on August 24, 2026. The current aggregate endpoint cannot validly calculate that cohort because it lacks the required first-acquisition-to-activation join and reliable exclusion controls.
The inventory verification guard currently reports zero verified claimable bounties because the observed candidates do not have executable verification paths. BountyScout has discovered recent GitHub issues, but those listings do not independently prove eligibility or payment.
Boundaries
BountySettledremains the payout-proof authority; external listings are discovery evidence only.Coordination
Known overlap will be coordinated with PRs #904, #892, #906, #889/#885, and #799. Changes will use focused commits and the repository’s required review, merge, deployment, and verification workflow.