Incremental delivery groups (2026-10-08)

Work in one or two coherent topics per GitHub PR. Commit remotely after each group. Never defer all write operations until after a large research session.

Group 1: scheduling capability truth

Align Threads native scheduling in both canonical and standalone Claude Code registries.
Add contract tests: native UI availability is not a ReachWeaver API integration.
Confirm current signed-in composer and eligibility before asserting any particular owner account can schedule.
Research remaining unverified Meta platform entries individually with first-party eligibility and format evidence.

Group 2: 22-platform priority rollout

Wave	Platforms	Purpose	Gate
1	Reddit, Hacker News, LinkedIn, YouTube Shorts, X, Bluesky, Mastodon, Product Hunt, DEV Community	Real developer interest, proof demos, releases, contributors	Human-only Hacker News text/submission, community-compliant Reddit, account-specific consent everywhere
2	Instagram Reels, TikTok, Threads, Facebook Groups	Native visual proof and discussion	Rights-cleared media, eligible accounts and group moderator rules
3	Discord, Telegram, Indie Hackers, Peerlist, Hashnode	Builder relationships, opt-in retention, tutorials	No unsolicited broadcasts or synthetic engagement
4	Bilibili, Zhihu, OSCHINA	Chinese developer reach	Human-reviewed localization and account eligibility

These are editorial groupings, not forecasts or permission to post. Start with two primary channels and one limited experiment. For restricted Reddit or Hacker News accounts, prioritize DEV, LinkedIn, YouTube and GitHub contributor onboarding without evading moderation.

Remaining independent groups

Source recency, official eligibility, evidence confidence and registry-documentation drift checks.
Evidence-bound project campaigns and truthful repurposing of already-public releases.
Real account insights, local IANA timezones and small matched-age timing experiments.
Permissioned, supervised native queues or API adapters with exact approval and remote receipts.
Qualified traffic and contributor attribution, moderation and safety review.

Per-channel evidence ledger: account identity and role; policy source/date; original claim and artifact; distinct angle/format; local time plus UTC; native UI versus ReachWeaver support; item approval; verified native permalink or not-published state; +24h and +7d metrics; referral/contributor results; unknowns and follow-up.

Existing authoritative documents

No real social account connection, remote schedule or live result is implied by this plan.