Path: docs/press-pipeline-v2.md
Last updated: 2026-09-17 07:23 UTC
Source: NextXus Federation Private Vault

Federation Press Pipeline v2

Ratified: 2026-09-16 Authors: Roger Keyserling + Pontus (via Catalyst) Status: CANONICAL — replaces all prior press/content pipeline specs

Failure Named

The prior pipeline reported its own intentions as achievements. "Auto-published" meant "sent to a queue." Counts came from pipeline logs, not from the world. Root fix: reports must be generated from verification evidence, never from pipeline logs. A count without a live URL behind it cannot be written down anywhere.

Language Contract

Three statuses only — nothing else:

The phrase "auto-published" is retired. "Published" requires a live URL. Ghost counts are structurally impossible under this contract.

The Pipeline (Minimal — Composio-native throughout)

  1. Draft — Catalyst drafts (unchanged)
  2. Produce — Gemini/NotebookLM produces (unchanged)
  3. Stage — Drive staging via Composio-native (zero rebuild)
  4. Format + Publish — Catalyst formats → GitHub Pages via Composio-native (zero rebuild)
  5. Verify — fetch the live URL, confirm it loads and content matches. Only then does status become verified-live
  6. Review Queue — drafts go to Beehiiv for Roger's review. Never auto-post. Roger's exact-text approval rule is permanent
  7. YAML Log — every step writes back: timestamp, artifact path, verification evidence (URL + load check result), failures with cause. The status report Roger sees is rendered FROM this log

OAuth Dependency Map

What This Eliminates


This document is the source of truth for all content automation going forward. It supersedes press-auto-pipeline, nova-marketing-agent, and beehiiv-pipeline-bridge specs.