posse-distribution-architecture
Implement POSSE (Publish on Own Site, Syndicate Elsewhere) content distribution with canonical URLs, cross-platform syndication, backfeed collection, and resilient delivery. Covers multi-platform publishing automation and IndieWeb patterns. Triggers on POSSE implementation, content syndication architecture, or IndieWeb publishing requests.
What this skill does
# POSSE Distribution Architecture
Publish on your own site first, then syndicate everywhere else — with resilience.
## POSSE Principle
```
Your Site (canonical) ──→ Platform A (syndicated copy)
│ ├─→ Platform B (syndicated copy)
│ ├─→ Platform C (syndicated copy)
│ └─→ Newsletter (syndicated copy)
│
←── Backfeed (likes, comments, reshares from platforms)
```
**Why POSSE over platform-first:**
- Own your canonical URL and content
- Platform changes don't destroy your archive
- Canonical URL gets SEO benefit
- Single source of truth for corrections
## Architecture
### Core Components
```python
from dataclasses import dataclass, field
from datetime import datetime
from enum import Enum
class SyndicationStatus(str, Enum):
PENDING = "pending"
PUBLISHED = "published"
FAILED = "failed"
RETRYING = "retrying"
@dataclass
class CanonicalContent:
id: str
title: str
body: str
canonical_url: str
published_at: datetime
content_type: str # "essay", "note", "photo", "event"
tags: list[str] = field(default_factory=list)
syndications: dict[str, SyndicationStatus] = field(default_factory=dict)
@dataclass
class SyndicationTarget:
platform: str
adapter: "PlatformAdapter"
enabled: bool = True
format_rules: dict = field(default_factory=dict)
```
### Distribution Pipeline
```python
class POSSEDistributor:
def __init__(self, targets: list[SyndicationTarget]):
self.targets = {t.platform: t for t in targets if t.enabled}
async def distribute(self, content: CanonicalContent) -> dict[str, str]:
results = {}
for platform, target in self.targets.items():
try:
adapted = target.adapter.adapt(content)
syndication_url = await target.adapter.publish(adapted)
content.syndications[platform] = SyndicationStatus.PUBLISHED
results[platform] = syndication_url
except RateLimitError:
content.syndications[platform] = SyndicationStatus.RETRYING
await self.queue_retry(platform, content)
except Exception as e:
content.syndications[platform] = SyndicationStatus.FAILED
results[platform] = f"FAILED: {e}"
return results
```
### Content Adaptation
```python
from abc import ABC, abstractmethod
class PlatformAdapter(ABC):
@abstractmethod
def adapt(self, content: CanonicalContent) -> dict:
"""Transform content for platform constraints."""
@abstractmethod
async def publish(self, adapted: dict) -> str:
"""Publish and return syndication URL."""
class BlueskyAdapter(PlatformAdapter):
MAX_LENGTH = 300
def adapt(self, content: CanonicalContent) -> dict:
if content.content_type == "essay":
text = f"{content.title}\n\n{content.body[:200]}...\n\n{content.canonical_url}"
else:
text = content.body[:self.MAX_LENGTH - len(content.canonical_url) - 2]
text = f"{text}\n\n{content.canonical_url}"
return {"text": text[:self.MAX_LENGTH], "tags": content.tags[:8]}
class NewsletterAdapter(PlatformAdapter):
def adapt(self, content: CanonicalContent) -> dict:
return {
"subject": content.title,
"html": render_email_template(content),
"canonical_url": content.canonical_url,
}
class DevToAdapter(PlatformAdapter):
def adapt(self, content: CanonicalContent) -> dict:
return {
"title": content.title,
"body_markdown": content.body,
"canonical_url": content.canonical_url,
"tags": content.tags[:4],
"published": True,
}
```
## Resilient Delivery
### Retry Queue
```python
import asyncio
from collections import defaultdict
class RetryQueue:
def __init__(self, max_retries: int = 3, base_delay: float = 60):
self.max_retries = max_retries
self.base_delay = base_delay
self.queue: list[tuple[str, CanonicalContent, int]] = []
async def add(self, platform: str, content: CanonicalContent, attempt: int = 0):
self.queue.append((platform, content, attempt))
async def process(self, distributor: POSSEDistributor):
while self.queue:
platform, content, attempt = self.queue.pop(0)
if attempt >= self.max_retries:
log.error("syndication_abandoned", platform=platform, content_id=content.id)
continue
delay = self.base_delay * (2 ** attempt)
await asyncio.sleep(delay)
target = distributor.targets.get(platform)
if not target:
continue
try:
adapted = target.adapter.adapt(content)
url = await target.adapter.publish(adapted)
content.syndications[platform] = SyndicationStatus.PUBLISHED
except Exception:
await self.add(platform, content, attempt + 1)
```
### Circuit Breaker per Platform
```python
class PlatformCircuitBreaker:
def __init__(self):
self.circuits: dict[str, CircuitBreaker] = {}
def get(self, platform: str) -> CircuitBreaker:
if platform not in self.circuits:
self.circuits[platform] = CircuitBreaker(
failure_threshold=3,
recovery_timeout=300, # 5 minutes
)
return self.circuits[platform]
async def publish(self, platform: str, adapter: PlatformAdapter, content: dict) -> str:
circuit = self.get(platform)
return await circuit.call(adapter.publish, content)
```
## Backfeed Collection
```python
async def collect_backfeed(syndication_urls: dict[str, str]) -> list[dict]:
backfeed = []
for platform, url in syndication_urls.items():
try:
adapter = get_adapter(platform)
metrics = await adapter.get_metrics(url)
backfeed.append({
"platform": platform,
"url": url,
"likes": metrics.get("likes", 0),
"reposts": metrics.get("reposts", 0),
"comments": metrics.get("comments", []),
})
except Exception:
pass # Backfeed is best-effort
return backfeed
```
## Syndication Manifest
```yaml
# syndication-manifest.yaml
content:
- id: essay-2026-03-20-architecture
canonical_url: https://example.com/essays/architecture
published_at: 2026-03-20T10:00:00Z
syndications:
bluesky:
status: published
url: https://bsky.app/profile/.../post/...
published_at: 2026-03-20T10:01:00Z
devto:
status: published
url: https://dev.to/author/article
published_at: 2026-03-20T10:02:00Z
newsletter:
status: published
campaign_id: "abc123"
published_at: 2026-03-20T10:05:00Z
backfeed:
total_likes: 42
total_reposts: 8
total_comments: 3
last_collected: 2026-03-20T22:00:00Z
```
## Anti-Patterns
- **Platform-first publishing** — Always publish on own site first; canonical URL is sacred
- **No canonical URL** — Every syndicated copy must link back to the original
- **Synchronous distribution** — Publish locally first, syndicate asynchronously
- **No retry logic** — Platforms have outages; queue and retry failed syndications
- **Identical content everywhere** — Adapt format and length per platform
- **Ignoring backfeed** — Engagement data from platforms enriches the canonical record
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.