What you can actually see
A post the owner can see exists only when a public permalink on a gaze network opens in the official app. Telegram, Discord, and generic webhooks are operator rails — they do not count.
Autoviralizer is not publishing to Facebook/X/TikTok/Instagram. It is armed only on operator rails: telegram, discord, webhook. Those are not the apps you open. Put FACEBOOK_PAGE_TOKEN, X user-context keys, INSTAGRAM_ACCESS_TOKEN, TIKTOK_ACCESS_TOKEN in GitHub Actions secrets (sync-all-secrets writes /etc/zeusai/social.env) or POST them to /api/visible-social/arm.
Operator rails armed (not gaze): telegram, discord, webhook
| Gaze network | Public permalink | Why dark |
|---|---|---|
| none | missing FACEBOOK_PAGE_TOKEN (and PAGE_ID if Graph /me cannot complete it) in social.env / GitHub secrets | |
| x | none | missing X_BEARER_TOKEN or X user-context keys in GitHub secrets → sync-all-secrets → /etc/zeusai/social.env → PM2 |
| none | missing INSTAGRAM_ACCESS_TOKEN (+ USER_ID, completable via Graph /me) | |
| tiktok | none | missing TIKTOK_ACCESS_TOKEN; even armed, organic publish needs a video file |
| threads | none | missing THREADS_ACCESS_TOKEN + THREADS_USER_ID |
| none | missing LINKEDIN_ACCESS_TOKEN + LINKEDIN_AUTHOR_URN (or LINKEDIN_ORG_ID) |
Arm path: GitHub Actions secrets named FACEBOOK_PAGE_TOKEN, FACEBOOK_PAGE_ID, X_API_KEY, X_API_SECRET, X_ACCESS_TOKEN, X_ACCESS_SECRET, INSTAGRAM_ACCESS_TOKEN → workflow sync-all-secrets writes /etc/zeusai/social.env. Same keys can be POSTed to /api/visible-social/arm (x-admin-token). Tokenless one-tap is /share. Ads keys do not publish posts. This process cannot mint Meta/X tokens.
visible-social.json · arm inventory · social-gravity.json · viral-unification.json · /share