Pre-launch gate and announcement plan — do not announce early

[eaitbrahim]

A project that attracts attention before it can absorb it dies of that attention. This issue is the gate: nothing is announced until every box below is ticked.

Pre-launch gate

• Phase 6 fully closed — licence detected by GitHub, description, topics, SECURITY.md, positioning statement
• Phase 7 fully closed — README, CONTRIBUTING.md, code of conduct, templates, Discussions live, 8–12 real good first issues
• Fiqh basis document published, scholarly-review stance decided and stated honestly
• CI green on main, and the code-quality scans actually configured — SONAR_TOKEN / SNYK_TOKEN still do not exist, so keel has never had static analysis or dependency scanning. Shipping a public financial tool without either is a bad first impression waiting to happen
• A maintainer response commitment that is honest for one person, stated in CONTRIBUTING.md

Where the audience actually is

Small, high-trust communities beat a broad launch. One credible post in the right place outperforms a Show HN:

• Islamic fintech communities and practitioner networks (IFN and similar)
• r/islamicfinance, Muslim developer Discord and Telegram groups
• Islamic finance programmes — IIUM, INCEIF, Durham
• Only then: Hacker News / Reddit / Lobsters

What the announcement must say

Lead with the compliance engine. State the measured result — 0 of 20 net-positive — in the post itself, not only in the repo. Being the one who says it first is the whole credibility play.

Explicit non-goal

Do not announce to get stars. Announce to find the handful of people who want an auditable Shariah screening engine and will help build one.

[eaitbrahim]

Resolving the open item in docs/launch.md's scans box, with evidence: the five packages/* Dependabot entries are live, not inert — the Dependabot log shows successful runs per entry (e.g. pip in /packages/keel-broker-coinbase - Update #1528373505 and github_actions in / - Update #1528373532, both success). The scheduled security workflow has also completed green on main at 18bc092 alongside CI, Code Quality, and Migrate. No collapse to the root entry needed; the note can be considered verified.