The problem
Founder-brand social publishing needed a repeatable pipeline that could take a content brief, attach real (non-AI-slop) photography, and never publish without a human sign-off, without manual folder shuffling between drafting and publishing.
My responsibility
Built the FastAPI webhook server, Unsplash sourcing integration, Founder OS folder-stage pipeline, Telegram approval gate, campaign API, and blog-indexed comment-link resolution.
System route
The architecture below is a readable abstraction of the documented workflow, not a simulated live execution.
- Receive a content brief via webhook from Hyperagent
- Source real editorial photography via the Unsplash API
- Stage the draft in a tracked Founder OS folder
- Send an interactive Telegram approval card to the founder
- Move the asset to the approved-for-publishing folder on approval
Reliability notes
- Publishing is explicitly gated on a human Telegram approval step before any asset is marked approved.
- Deployed configuration and public run history are still pending evidence capture.
Evidence currently available
- Architecture description
- Webhook payload schema
- Founder-approval-gated publishing flow
Technology used
Evidence still being recovered
Client-approved metrics, execution recordings, exact delivery dates, and sanitized implementation artifacts will be added only after verification. This dossier deliberately avoids unsupported impact claims.