Skip to main content
Case Study · PMOS (PIP)

Engineering an autonomous, platform-native content engine & media OS.

Social media schedulers treat content as interchangeable text blocks cross-posted identically across networks, alienating audiences and triggering algorithmic penalties. PMOS (Personal Intelligence Publisher) rethinks media distribution as an autonomous operating system: Claude-powered platform synthesis, BullMQ job queues, and an anti-vanity metric architecture.

Claude 3.5 Sonnet AdaptationBullMQ & Redis PipelinesHuman-in-the-Loop ReviewPlatform-Native AdaptersOAuth2 Token RotationAnti-Vanity Opportunity Tracking
01 — Problem

Cross-posting is dead. Nuance matters, but manual adaptation doesn't scale.

Founders and engineering leaders have high-value insights, but communicating them consistently across LinkedIn, X, and Threads requires hours of rewriting to match each platform's unique vernacular and character constraints.

The Cross-Post Trap

Posting the exact same text block to LinkedIn, X, and Threads looks lazy and performs poorly. X demands punchy thread cadence, LinkedIn requires structured professional storytelling, and Threads favors casual conversational starters.

Vanity Metrics Trap

Most tools celebrate likes and impressions. For a high-end engineering consultancy like WEBMUSE, 10,000 viral views that produce 0 inquiries is a failure; 300 views that produce 2 enterprise client contracts is a massive win.

The Automation Hazard

Fully autonomous AI posting without human sign-off leads to hallucinatory claims, embarrassing tone mismatches, and brand reputation damage.

02 — Thesis

One idea, platform-native execution, human-certified delivery.

PMOS is built on a constitutional mandate: the creator provides the genuine insight, AI models perform the stylistic translation, and the creator certifies the output. Every pipeline stage is auditable, and the queue enforces platform rate compliance.

Anti-Vanity North Star

The system optimizes for meaningful business outcomes (inbound client inquiries, partnership offers, podcast invitations) rather than vanity likes and impressions.

Platform-Native, Not Cross-Post

A single core concept is refactored by Claude into native conventions: narrative hook for LinkedIn, punchy thread for X, and conversational prompt for Threads.

Human Stays in Control

Zero blind auto-publishing. Every synthesized artifact passes through a strict approval state machine requiring human sign-off before entering the queue.

Resilient Distributed Workers

BullMQ and Redis handle transient platform outages and rate limits with jittered exponential backoff and dead-letter queue auditing.

03 — Architecture

The PIP Engine Architecture: Modular synthesis with BullMQ persistence.

Incoming concepts flow from the Idea Repository into the Claude Synthesizer, producing staged drafts. Upon approval, BullMQ workers manage delayed dispatch and token rotation.

  Creator Input (Voice note / Text bullet)
          │
          ▼
  [Idea Service] ─── Validated & Stored
          │
          ▼
  [Claude Synthesizer] ─── Platform-Specific Prompts
          │
          ├──> LinkedIn Draft (Long-form narrative + takeaways)
          ├──> X Thread Draft (Hook + numbered insights + CTA)
          └──> Threads Draft (Conversational question + brief context)
          │
          ▼
  [Human Review Gate] ─── Approved by Creator (100% Gated)
          │
          ▼
  [BullMQ Redis Queue] ─── Jittered Cadence & Rate Control
          │
          ├──> [LinkedIn Publisher] (OAuth2 + URN asset registration)
          ├──> [X Publisher] (OAuth2 + v2 tweets endpoint + pricing guard)
          └──> [Threads Publisher] (Meta Graph API container publishing)
          │
          ▼
  [Opportunity Tracker] ── Tracks Inbound Enquiries & Conversions
LayerTechnologyWhy it's there
Core BackendNode.js · Express · TypeScript (Strict)Event-driven modular monolith managing idea capture, prompt orchestration, and queue dispatching
AI Synthesis EngineAnthropic Claude 3.5 Sonnet · Prompt EngineeringTransforms a single raw thesis into platform-native drafts (X threads, LinkedIn long-form, Threads conversations)
Job Queue & SchedulingBullMQ · RedisPersistent, rate-limit-conscious publishing workers with exponential backoff and delayed execution
Platform AdaptersLinkedIn API v2 · X API v2 · Meta Threads GraphDecoupled OAuth2 authentication, token rotation, media upload chunking, and network-specific payload shaping
Cost & Quota GuardAPI Cost Tracker · Tiered Throttle RulesGuards against unexpected X (Twitter) API per-request paywalls and monitors monthly API expense limits
Human ReviewState Machine · Webhook NotificationsStrict human-in-the-loop gate: drafts remain in staged state until explicitly certified and scheduled by the creator
04 — Deep Dive

The 4-Stage Lifecycle: Eliminating accidental publishes.

Every piece of content traverses a rigid state machine. A draft in state STAGED cannot be picked up by publishing workers under any circumstances until transitioned to APPROVED by user authentication.

01. Capture

Raw Idea Ingestion

A voice note transcription, quick code observation, or architecture diagram is logged to the Idea Vault with key bullet points.

02. Synthesize

Multi-Platform Generator

Claude 3.5 Sonnet ingests the raw thought and executes platform-tailored prompts to produce 3 native formats simultaneously.

03. Gate

Human Review & Refine

The creator edits, approves, or rejects each platform draft via a clean terminal or web dashboard. The draft cannot publish without approval.

04. Dispatch

BullMQ Rate-Limited Queue

Approved drafts are scheduled into BullMQ queues calibrated to platform-specific posting cadences and API rate windows.

05 — By the numbers
3 networks
Native API adapters
100%
Human approval gate
0
Blind auto-publishes
3 formats
Generated per core idea
<2 sec
Multi-draft synthesis
0 drift
Platform token rotation
Building autonomous AI media systems or workflow engines? Let's talk.