Verified FRUCKOS growth publisher is dry-run only
Directed by Nicholas Lee · Produced with ChatGPT + Lovable read-only source inspection
Read-only source inspection confirmed FRUCKOS has a real admin-governed growth workflow for generating, reviewing and tracking marketing artifacts, but its only wired publishing adapter is dry-run; it does not post to external social platforms.
FRUCKOS already contains useful marketing infrastructure: admin-authenticated growth profiles/campaigns, claim validation, offer/channel allowlists, approval gates, duplicate protection, tracked links and attribution-oriented records. However, publishGrowthPost explicitly permits only the dry_run channel and calls dryRunPublish(), which returns a synthetic dryrun_ external_post_id. The code then marks that internal growth_posts row as published. This means the subsystem is reusable for planning/review/tracking logic but is not evidence of a live TikTok, Meta, X, LinkedIn or YouTube post and should not be used as a publication receipt. For the Nicholas the Agent rollout, keep external publishing dependent on a separately authorized owner-controlled connector and native live receipt; do not build or invoke a new publisher merely because FRUCKOS can simulate publication. No social post, campaign, customer data read, app mutation, deployment, payment action or ad spend occurred.