How Paranor works

What each stage does

Content in Paranor moves through five stages. Each has a clear role and feeds the next.

• Dot — A single unit of content: an article, episode, stream, or timeline event. Dots are ingested from RSS, Bluesky mentions, or manual entry. Raw items enter the pipeline here.
• Contexter — The review queue. You see incoming Dots, add or edit summaries (including with GPT), set Master Content Numbers, tags, and visibility, then approve or reject. Only approved items move forward.
• Index — Your approved content store. Everything that passed Contexter lives here and drives the Media Room and Agent API. One source of truth for “what’s public.”
• Cataloger — The org-level tool for Paranor staff and agencies. It manages multiple creators, aggregated intelligence, and cross-creator workflows. You don’t run it when self-hosting; it lives at paranor.app.
• Nexus — The creator discovery registry. When you opt in (“Discoverable in Nexus”), your profile appears here by topic. Producers and AI agents discover you and reach your Media Room and Agent API—no scraping.

End-to-end flow

RSS or Bluesky (or manual entry) creates new Dots. They land in the Contexter. You review, summarize, tag, and approve. Approved items go into the Index. The Index feeds the Media Room (for humans) and the Agent API (for tools and agents). If you opt in to Nexus, your profile is listed in the discovery registry so others can find and use your API.

Why this pipeline matters

One index. All approved content lives in one place. No duplicate “live” lists or sync issues. One API. The same Index powers the human-facing Media Room and the machine-readable Agent API (content-index, booking, media-kit, speaking, webhooks). Review before publish. Nothing goes public until you approve it in the Contexter. That keeps your public presence intentional and accurate.