How it is built
One workbench runs the whole content operation: trending-list collection, forum thread classification, competitor-noise filtering, copywriting and image generation, browser session management. Collection belongs to the machine, judgement and publishing belong to the person.
Classification keys off the tone of a request for help rather than topic words — in one forum every thread mentions the same word, so keyword matching alone hits hundreds of noisy hits. Competitor noise is filtered by stable signals (short links, platform names, template copy); strip those out and what remains is worth reading.
Two hard gates are written into the code: a red-line scan (contact details, traffic-driving phrasing) and a localisation scan (regional words, cross-region promises). Nothing ships that fails them.
Browser sessions are separate profiles per platform, driven by Playwright. You click in and work by hand; the machine only patrols and fills in forms.
The boundary is deliberate: collection is fully automatic, but the final click of publishing and interaction must be made by a person. No third-party services, it all runs locally.
