Market & viral shifts — the outward-looking advisorOWNER: ENGINE — growth (market-watch-engine), Folo-first (Mav’s map, 2026-08-09). This watches the outside world — the sibling of AI insights, which watches our own behaviour. Per brand: Folo runs the full monitor set (the reference implementation); Fanogram consumes cross-product pushes from the same engine; Receipt doesn’t mount it. AUTO lane rule (Growth-engine rails): auto-actions are reversible, internal and contact-free — AUTO never contacts a person; anything outward is human-gated. folo.link scope (§17): this page READS the engine’s alert board — every alert is tagged ALL or with the product dots it targets; the only write this surface makes is the engine’s own push into each product’s admin board, and monitor toggles route to the engine’s Folo-side config — folo.link changes no product state directly.
Eight monitored categories, two lanes: what the engine did on its own (reversible, internal) and what waits for a human.
Demo dataLive on Folo
Active alerts
35
across 8 categories
DEMO DATA · source: market-watchHigh severity
8
pending human decisions first
DEMO DATA · source: market-watchAuto-actioned
11
reversible · internal · contact-free
DEMO DATA · source: auto lane logCross-product
21
pushed to sibling admins
DEMO DATA · source: push logAUTO-actions log 11 · reversibleAUTO = inbound-triggered OR reversible-internal-and-contact-free, with confidence ≥0.85 and mandatory evidence. AUTO never contacts a person — every entry here is an internal, reversible adjustment, logged with its trigger.
What the engine did on its own — internal only, each entry reversible. Each entry is tagged with WHERE it acted: product dots for a targeted adjustment, ENGINE for a change inside the engine itself.
⚙
Raised fraud-watch level on iDEAL top-upspayment-fraud ecosystem · conf 0.92 · 2h ago · acted on the shared payments engine
⚙
Re-weighted discovery for short-clip formatsfeature releases going viral · conf 0.88 · 6h ago · Folo discovery only
⚙
Flagged 3 geo rows for age-rules re-reviewregulatory & legal · conf 0.90 · yesterday · shared age-rules system
⚙
Widened competitor price-scrape windowcompetitor platform moves · conf 0.86 · yesterday · engine-internal, touches no product
Pending review 17 · human-gatedPROPOSE lane: approving a card visibly creates a job for a human owner — it sends nothing. Anything touching a person, a price or an outward message lives here, never in AUTO.
Waiting on a human — approve creates a job card, sends nothing. Each alert is tagged sector-wide (ALL) or with the product dots it targets — the job card files to that product’s (or each tagged product’s) human owner.
◭
New EU age-verification guidance draft publishedregulatory & legal · high · conf 0.94
◭
Competitor launched creator-referral bonusescompetitor platform moves · high · conf 0.83 · affects creator acquisition on both
◭
Chargeback-farm pattern seen on a sibling platformpayment-fraud ecosystem · high · conf 0.89 · Receipt’s Stripe store included
◭
Vertical-video export tool trending with creatorscreator-side trends · medium · conf 0.78 · creator tooling is FG’s lane
✋
sends nothing · human-gated — the approve flow logs an approved-intent row and creates a job card for a named human owner (Growth-engine rail, load-bearing wording).
Monitored categories 8 · each with cadence + on/offOwner + write path (§17-2): the monitor set is the Folo-first market-watch engine’s config — a toggle writes that engine config via the Folo admin API and audits there; on folo.link and the FG skin the same toggle ROUTES to that one config (no per-product copy exists to flip). Effect (§17-3): off = the category stops scanning at its next cadence tick; existing alerts stay on the board tagged "monitor off"; on = scanning resumes next tick, no back-fill of the gap.
The full monitor set as it runs on Folo — toggles are per-category and audited; a toggled-off category renders as OFF, never as silence. Owner: the Folo-first engine — one config, every skin routes to it (ⓘ above for the write path + effect).
Competitor platform moves
every 6hReferral-bonus launch0.83
Pricing page reshuffle0.71
sources: site diffs · app-store notesNew platform launches
dailyInvite-only fan app in beta0.66
sources: press · registriesFeature releases going viral
every 6hShort-clip remix format0.88
Voice-note paywalls0.62
sources: social feeds · changelogsRegulatory & legal shifts
dailyEU age-verification draft0.94
1 source unavailable — regulator RSS (see feed bar)Payment-fraud ecosystem
hourlyChargeback-farm pattern0.89
iDEAL top-up probing0.92
sources: PSP advisories · internal signalsCreator-side trends
dailyVertical-video export tool0.78
sources: creator forums · socialTech-model shifts
weeklyCheaper long-context tier0.81
sources: provider changelogsMacro signals
weekly · OFFMonitor off — renders as OFF, never as silence
sources: macro feedsCross-product pushes 21 this monthOne engine, many mounts: an alert tagged cross-product is pushed into each affected product’s admin with its evidence attached. FG’s mount of this page is largely this stream; Folo’s is the full monitor set.
⇄
Write path (§17-2): the push is market-watch-engine → each tagged product’s admin board, via that product’s admin API, with the evidence attached — the ONLY write this surface triggers, and it lands as a board card, never as a user-facing change. Replay-safe source ids on every pushed alert (wave-1 rule) — a re-run of the feed never double-pushes the same alert into a product admin.