🛺 Distribution Dashboard

5/10

broadcast channels live (excl. email + Postiz)

NO

autonomous loop running

1

email subscribers

1d ago

last post · 4-day streak

generated 2026-09-13 14:00 UTC · reconcile/main-trunk @ 07771bd71 · auto-rebuilds on repo change

🔁 THE AUTONOMY LOOP

NO — daily autonomous publishing is not running today.

The dry-screen fires daily and would post if the gate were open. Real cadence, honestly: Last post 1 day(s) ago · current streak 4 consecutive day(s) · 24 total publish day(s) ever.

✅ 1

Build the pipeline

daily_publish.py, distribution_loop.py, faceless_engine.py, faceless_publish_loop.py, publish_screen.py, publish_streak.py all exist and pass dry-runs. DONE.
⬜ 2

Connect the accounts

X + LinkedIn API keys (owned-channel expansion) · Postiz droplet resize + OAuth for YouTube/TikTok/Instagram/Threads/Facebook/Pinterest.
⬜ 3

Justin's go

Re-enable `F2F Daily Syndication` (or one-shot PUBLISH_GO=RESUME_SYNDICATION) for the 7 live owned channels. Separately, set POSTIZ_ALLOW_PUBLISH=I_UNDERSTAND once Postiz + accounts are live for the wider platform set.

TAP_QUEUE.md — tap ④, flip on the daily-reach loop →

📥 CONTENT PIPELINE

generation → queue → quality gate

🟡

Content generation surfaces

ReThink corpus (essays + policy briefs) is the source; 9 pieces have curated faceless-derivation specs, producing 45 rendered platform-native artifacts across 9 source pieces.

WHY Generation is real and running — it's the auto-publish leg that's gated, not the writing.
FACELESS_PUBLISH_POLICY.md →
🟡

Faceless engine (queue → render → verify)

9 source specs · 45 queued derived items (X threads, LinkedIn posts, quote cards, IG captions, short-video scripts, narrated audio). First real run landed field-notes-2026-09-13: see report.

WHY Even on a real run, everything lands as OFFLINE-PREVIEW, not a real post — Postiz isn't reachable (see Infra below), so nothing has gone out to any platform yet. The gate itself is proven: it correctly HELD items with unverified 'guarantee' language.
latest faceless publish report →
🟡

Owned-channel pillar screen (daily_publish.py)

Dry-lane runs daily 08:40 (F2F-DailyPublishDry) and screens Historical inventory counts are not current release evidence. Review each selected piece before authorized publication.

WHY The screen works and is live; current eligibility requires a fresh review record.
PROJECT_REGISTRY.md §3b →
🟢

Quality / verification gate

publish_screen.screen_piece (4-filter: TRUTH / LEGAL-FTC / ToS / WISDOM-discretion) + no-fabrication checks + Firstfruits warmth pass — fail-closed, no override path in autonomous runs.

WHY This is the one piece of the pipeline that's fully proven — it's what makes the rest safe to eventually turn on.
publish_screen.py →

🌐 OWNED CHANNELS

the site + the email list — the assets Dispatch fully controls

🟡

ReThink public hub (site-rethink)

pages.dev URL returns HTTP 200 (live-verified at build time); PRIVATE_PREVIEW=False (config says public); custom domain rethink.fast2future.com resolves.

WHY The site itself went public 2026-07-06 (config flipped, robots allow-all, sitemap references the real domain) — but the domain purchase/DNS step hasn't landed, so it's only reachable at the opaque pages.dev URL today.
open the live hub →
🟢

Email list — Buttondown (fast2future)

1 subscriber(s) (live from Buttondown). Capture embed is deployed and live (no API key required for the embed itself).

WHY Connected and capturing — the list is just tiny because reach is still ≈0, not because the mechanism is broken.
buttondown.com/fast2future →
🔴

Daily owned-channel drip (live posting)

The dry-screen runs daily; the actual posting task (`F2F Daily Syndication`, 09:30) is Disabled — paused by Justin's own 2026-06-18 decision, not a failure.

WHY This is a deliberate pause, not a broken loop. Re-enabling it is a one-word tap.
the exact re-enable command →

📱 SOCIAL CHANNELS

account-creation + OAuth are always Justin's tap

🟢

Already live & auto-postable (5 channels)

Bluesky, Mastodon, Nostr, Dev.to, WordPress

WHY These need no further taps — they post today when the daily drip (above) is re-enabled.
CHANNELS.md (auto-generated registry) →
🔴

X (Twitter)

🔴 NOT CONNECTED — handle: (unclaimed/unwired) · [link](https://x.com)

WHY Create an X developer app (account-creation) + generate 4 API keys → store in credentials.md. Own-timeline posting code isn't written yet either — both the account AND the poster are open.
CHANNELS.md — connect-taps →
🔴

LinkedIn

🔴 NOT CONNECTED — handle: (code-complete · awaiting OAuth cred) · [link](https://linkedin.com)

WHY Create a LinkedIn developer app + OAuth the company page → store linkedin_access_token. No small-dev API for hands-off posting even once connected — drafts would still be hand-pasted.
CHANNELS.md — connect-taps →
🔴

YouTube

Not tracked in CHANNELS.md — no account, no OAuth, no posting code yet.

WHY Not in the channel registry yet. Needs Postiz reachable (it's not, see Infra below) + a Google/YouTube OAuth connection through it. Faceless engine already stages short-video scripts + narrated audio waiting for this pipe.
CHANNELS.md — connect-taps →
🔴

TikTok

Not tracked in CHANNELS.md — no account, no OAuth, no posting code yet.

WHY Not connected. Same Postiz dependency as YouTube, PLUS TikTok's own extra wall: their Content Posting API requires an app-review audit before non-draft posting even once OAuth'd.
CHANNELS.md — connect-taps →
🔴

Instagram

Not tracked in CHANNELS.md — no account, no OAuth, no posting code yet.

WHY Not connected. Same Postiz + Meta-developer-app dependency as the other Postiz-backed platforms.
CHANNELS.md — connect-taps →

🔧 INFRA / PIPES

the plumbing everything above depends on

🔴

Postiz (multi-platform fan-out backend)

NOT running. Installed + secrets staged at /opt/postiz/ on the DO VPS, but the stack (8 containers incl. Temporal + Elasticsearch) needs ~4GB RAM; the VPS is 1GB and already hosts live Hermes.

WHY 💰-gated: resize the droplet (~$24/mo) or stand up a second ≥4GB host. This is the single biggest unlock — it's the pipe for YouTube/TikTok/Instagram/Threads/Facebook/Pinterest all at once.
POSTIZ_CONNECT_GUIDE.md →
🟡

Auto-publish loop — owned channels (distribution_loop.py)

Built, verified, currently paused (see Owned Channels above). 7 channels wired: Telegram, Bluesky, Mastodon, Nostr, Dev.to, WordPress, Buttondown.

WHY Working machinery, closed gate — the honest state is 'ready,' not 'broken.'
distribution_loop.py →
🟡

Auto-publish loop — faceless/wide platforms (faceless_publish_loop.py)

Built, staged, never run (0 reports). Depends on Postiz being reachable, which it isn't.

WHY Downstream of the Postiz blocker above — nothing to verify by running it until that pipe exists.
faceless_publish_loop.py →
🟡

Measurement / analytics (funnel_meter.py)

Email-capture stage is LIVE (Buttondown, real number above). Traffic/session stages (Cloudflare Web Analytics) and purchase stage (Gumroad) read 'no data yet' — the CF_ANALYTICS_TOKEN and gumroad_access_token secrets aren't set.

WHY This is TAP_QUEUE's own '#1, everything else depends on it' item — without it, every reach number below the email stage is a guess.
TAP_QUEUE.md — the measurement odometer tap →
🟢

Health monitor / silent-death watchdog

F2F-HealthWatchdog runs every 6h — checks heartbeat staleness + per-loop beats, digests to HEARTBEAT_LOG.md.

WHY Live and verified firing — this is the safety net that would catch a silently-dead publish loop.
PROJECT_REGISTRY.md §3c →