logicspike/docs

Content Engine

Content Engine: Service Vision & Strategy

Last Updated: 2026-03-15 Service Status: 📋 Planning Phase

This document defines the vision, goals, and strategic direction of the Content Engine — LogicSpike's independent, standalone service for content scheduling, calendar-based planning, and automated social media publishing. This service has zero dependency on the Blog Engine or any other LogicSpike service — users can schedule any type of content (text, images, videos, links, stories) to social media directly.

1. Purpose (The "Why")

Modern agencies, creators, and businesses juggle dozens of tools to plan, create, schedule, and publish content across social platforms. They use Notion for planning, Buffer or Hootsuite for scheduling, Canva for design, and then manually coordinate publish times — often across multiple client workspaces.

The Content Engine eliminates this chaos by providing a unified content calendar with automated multi-platform publishing — all within the LogicSpike ecosystem. And with its MCP (Model Context Protocol) server, AI agents can autonomously operate the entire content pipeline — scheduling, publishing, and managing content without human intervention.

IMPORTANT

This is a fully independent service. It does NOT depend on the Blog Engine, Newsletter, or any other LogicSpike service to function. A tenant can activate the Content Engine and start scheduling social media posts immediately — whether they're promoting a blog, sharing a product photo, posting a motivational quote, or publishing a video reel. The Blog Engine integration is an optional cross-service bonus, not a requirement.

NOTE

This is not a content creation tool. It is a content scheduling and distribution engine. Users (or AI agents) bring their own captions, images, and videos — the Content Engine handles the when, where, and how of publishing.

2. Core Value Proposition

Problem Content Engine Solution
Scattered scheduling across 5+ tools Single calendar view for all platforms
Manual posting → missed deadlines Automated time-zone-aware publishing
No visibility across client workspaces Multi-tenant calendar with team collaboration
Expensive per-seat SaaS pricing Included in LogicSpike subscription
Need a separate tool for each content type Schedule any content — text, images, videos, stories, links
No integration with other business tools Optional deep integrations with Blog Engine, Newsletter & more

3. Core Features (MVP — Phase 1)

3.1 Content Calendar

  • Visual Calendar UI — Day, Week, and Month views with drag-and-drop scheduling
  • Timezone-Aware — All content slots honor the workspace's configured timezone
  • Content Slots — Each slot represents a single piece of content to be published
  • Labels & Categories — Organize content by campaign, type, or client
  • Recurring Schedules — Set up repeating content patterns (e.g., "Post every Monday at 9 AM")

3.2 Social Media Integration

  • Platform Connectors — OAuth-based connections to:
    • Twitter/X
    • Instagram (via Meta Graph API)
    • LinkedIn
    • Facebook Pages (via Meta Graph API)
    • YouTube (for video scheduling — future)
  • Multi-Account Support — Connect multiple accounts per platform per tenant
  • Platform-Specific Formatting — Auto-adapt content to each platform's requirements (character limits, media formats, hashtag best practices)

3.3 Automated Publishing

  • Scheduled Dispatch — Content is published at the exact scheduled time via a background job system
  • Queue-Based Architecture — Uses a reliable queue (Cloudflare Queues / Durable Objects) to guarantee delivery
  • Retry Logic — Failed posts are retried with exponential backoff
  • Publish Status Tracking — Real-time status: draft → scheduled → publishing → published → failed

3.4 Content Slot Management

  • Rich Media Attachments — Images, videos, carousels attached to each slot
  • Caption & Copy — Per-platform captions with variable support
  • Approval Workflow — Draft → Pending Review → Approved → Scheduled (for team environments)
  • Version History — Track edits to content before publishing

3.5 MCP Agent Control Layer

  • MCP Server — Full Model Context Protocol server exposing 15+ tools for AI agent control
  • Agent-Native Design — AI agents can schedule, reschedule, cancel, and monitor content programmatically
  • Bulk Operations — bulk_schedule and bulk_action tools optimized for agent workflows (plan an entire week in one call)
  • Calendar Resources — MCP resources provide read-only context (content://calendar/week, content://stats/overview) for agent awareness
  • Safety Guards — Rate limits, dryRun mode, and autoApprove: false by default prevent agent overreach
  • Audit Trail — Every agent action is logged with agentId for accountability
  • See full specification: mcp_server_spec.md

4. Cross-Service Integrations (Phase 2+)

NOTE

All integrations below are optional enhancements. The Content Engine works fully standalone without any of them.

Integration Description
Blog Engine (optional) "Publish blog post → auto-schedule social promotion" — Listens to blog.published event and auto-creates social slots
Communication Service (optional) Send notifications to team members about upcoming publishable content or failed posts
Media Service Store and serve all content media (images, videos) through the existing media pipeline
Billing Service Enforce plan limits (e.g., max social accounts connected, max scheduled posts/month)
Event Bus Publish events: content.scheduled, content.published, content.failed for downstream automation
MCP Protocol AI agents (Claude, Gemini, custom) control the Content Engine via MCP tools — schedule, publish, manage campaigns autonomously

5. Strategic Alignment

This service directly fulfills the "Content Automation Engine" item from LOGICSPIKE_VISION.md and serves as a critical building block toward Phase 3 — The Automation Engine, enabling cross-service workflows like:

"When a blog post is published → auto-generate social media copies → schedule them across 3 platforms → send a Slack notification to the team."

6. What This Service Is NOT

  • ❌ Not a content creation tool (no AI writing, no design editor)
  • ❌ Not a social media analytics dashboard (platform insights are out of scope for MVP)
  • ❌ Not a community management tool (no DM management, no comment moderation)
  • ❌ Not a newsletter service (separate future service)

7. Success Metrics (Post-Launch)

  • Adoption: 60%+ of active tenants connect at least 1 social account within 30 days
  • Reliability: 99.5%+ publish success rate
  • Engagement: Average 15+ content slots scheduled per tenant per month
  • Retention Impact: Tenants using Content Engine show 2x higher retention vs non-users
Content Engine