Incoming requests at the Reception front desk - what someone asked for, waiting to be handled. About this list · Site contents
ContentType.IncomingRequest
Lineage: ContentType.Item -> ContentType.IncomingRequestNews to TikTok: a conveyor of building-block workflows!New... |
2026-10-02T16:38:16.4580452+00:00 | claude-code | An app that turns the latest news into short vertical videos for TikTok | Make an app that takes the latest news and turns it into short vertical videos for TikTok - a factory conveyor where each stage is a building-block workflow that can be reused, swapped or re-run on its own. The conveyor others built (scouted 2026-10-02): ingest (RSS, news APIs) -> dedupe and rank -> script (hook, story, call to action) -> fact-check against the sources -> voiceover (TTS) -> visuals (stock b-roll or stills with a slow pan; generated video drifts) -> captions (Whisper) -> assemble 9:16 (ffmpeg, MoviePy or Remotion) -> human review gate -> publish (TikTok Content Posting API). Open source to reuse rather than rebuild: MoneyPrinterTurbo, ShortGPT, gyoridavid/short-video-maker, the n8n faceless-video templates. Reuse first: Agency.Content already runs RT-NEWS-DIGEST (the news intake) and has the Studio crew (DeepResearch, DocAuthor, ImageGen); name what is reused and what is new. Acceptance criteria (the traps others fell into): 1. Facts only: never the article text; every video names its sources on screen and links them; a story needs two independent outlets. 2. Fact-check is a stage of its own, and a person approves every video before it is published - automated news channels are what moderators take down as misinformation farms. 3. Realistic generated people or scenes carry TikTok's AI-generated label (C2PA); no publisher footage or photos, stock or generated only. 4. Publish as Inbox drafts (Upload to Inbox needs no API audit) until the TikTok app audit passes; an unaudited client can only post SELF_ONLY. 5. Each stage is one workflow with its own output row, retried on its own; one measurable success criterion for the whole line. Deliverable now: the division/pipeline design as a proposal for the operator (stages, the workflow per stage, crew by role, reused parts, the success criterion) - not a build. Sources: https://github.com/harry0703/MoneyPrinterTurbo https://docs.shortgpt.ai/ https://n8n.io/workflows/6014-create-faceless-videos-with-gemini-elevenlabs-leonardo-ai-and-shotstack/ https://developers.tiktok.com/docs/en/content-posting-api-get-started https://www.outstand.so/blog/tiktok-content-posting-api https://newsroom.tiktok.com/en-us/partnering-with-our-industry-to-advance-ai-transparency-and-literacy https://www.newsguardtech.com/special-reports/tiktok-content-farms-use-ai-voiceovers-to-mass-produce-political-misinformation/ https://copyrightlately.com/court-rules-ai-news-summaries-may-infringe-copyright/ | Agency.Content | Dispatched | Whether to run a news-to-short-video production line, and how it is staffed and gated | Standard | 2026-10-02T16:38:20.5279912 | |||||
Research: how agent companies staff, hire and approve - what works and why!New... |
2026-10-02T16:02:47.5863802+00:00 | claude-code | Agent staffing, hiring and risk-based approval: what works | Question: what works in practice for an agent company to start with default staff, hire when needed and retire idle hires; to approve low-risk changes automatically and escalate the rest by risk and operating mode (startup vs live); to hand approvals to a live steward on another system; and to give each agent just-in-time context (progressive disclosure, not teaching what a model already knows). Compare Paperclip, CrewAI, AutoGen, LangGraph, Agent Skills, ITIL change management, Project Server resource pools. Not covered again: who is on a core team (report gov-core-team-frameworks-2026-09-30). Deliverable: a sourced ResearchReport with the ideas to adopt the SharePoint way. | Agency.Content | Dispatched | Deep research report | Standard | A sourced ResearchReport | 2026-10-02T16:02:50.6289100 |