# Substack Capability Canon

**Status:** Draft v0.1  
**Date:** 2026-09-03  
**Purpose:** Canonical capability model for using Substack as a publication, subscriber relationship, membership, multimedia, discovery, community, creator-economics, and AI-assisted publishing platform.

---

# 1. Purpose

This canon provides a durable capability model for Substack.

It is intentionally not organized as a tour of the Substack user interface or a chronological feature list. Instead, it models Substack as a set of reusable capabilities that can be mapped to publications, communities, membership products, media operations, institutional publishing, creator businesses, and agent-assisted editorial systems.

The primary questions are:

1. What capability does Substack provide?
2. Which relationship does the capability establish: reader, follower, subscriber, paid subscriber, founding member, or participant?
3. Which content surface exposes it?
4. What part of the audience relationship is portable or publisher-controlled?
5. What commercial or membership model does it enable?
6. Which capabilities are programmatically accessible?
7. Which operations remain human-centered?
8. How should AI or agentic systems participate without making Substack the canonical system of record?

This canon is designed to support systems such as a future `substack-edge`, publication operations for the Coulomb Society, creator/member businesses, research publishing, and human/agent hybrid editorial workflows.

---

# 2. Strategic Platform Model

Substack should be treated as seven overlapping platforms:

```text
Substack
│
├── Publication Platform
│   ├── posts
│   ├── newsletters
│   ├── websites
│   ├── archives
│   ├── Articles / long-form publishing
│   └── custom domains
│
├── Multimedia Platform
│   ├── writing
│   ├── podcasts
│   ├── video
│   ├── live video
│   └── media embeds
│
├── Audience Relationship Platform
│   ├── followers
│   ├── free subscribers
│   ├── paid subscribers
│   ├── founding members
│   ├── segments
│   └── tags
│
├── Community Platform
│   ├── comments
│   ├── Notes
│   ├── Chat
│   ├── replies
│   └── live interaction
│
├── Discovery & Growth Network
│   ├── Home feed
│   ├── Notes
│   ├── recommendations
│   ├── Creator Match
│   ├── leaderboards
│   └── referrals
│
├── Membership & Commerce Platform
│   ├── paid subscriptions
│   ├── founding memberships
│   ├── paywalls
│   ├── perks
│   └── Stripe payments
│
└── Publisher Operations Platform
    ├── subscriber management
    ├── analytics
    ├── export
    ├── RSS
    ├── Google Analytics
    └── MCP / AI access
```

The most important conceptual distinction is:

> **Substack is primarily a publication and subscriber-relationship platform.**

Its core economic and organizational unit is not the post, chat, or feed. It is the **publication and its subscriber base**.

---

# 3. Capability Levels

Each capability in this canon can be considered at five implementation levels.

| Level | Meaning |
|---|---|
| **L0 — Human UI** | Available through standard Substack creator or reader interfaces. |
| **L1 — Export / Feed Accessible** | Accessible through RSS, CSV export, email delivery, or public web surfaces. |
| **L2 — Integrated** | Can participate in external analytics, identity, payment, or workflow integrations. |
| **L3 — AI Readable** | Publication or analytics data can be inspected by AI tooling through supported interfaces such as MCP. |
| **L4 — Agentic** | Suitable for bounded human/agent hybrid operation or autonomous preparation under external governance. |

Substack currently exposes fewer general-purpose write APIs than Telegram or X. Therefore, L4 commonly means **agent-assisted preparation and publisher operations**, not unrestricted autonomous publication.

---

# 4. Publication Capabilities

## PUB-01 — Publication

The canonical Substack object is the **publication**.

A publication can provide:

- a web presence;
- an archive;
- email distribution;
- subscriber management;
- free and paid content;
- author identity;
- multimedia publishing;
- comments and community interaction;
- subscription economics.

Conceptually:

```text
Publication
├── identity
├── content
├── audience
├── membership
├── commerce
├── analytics
└── community
```

### Strategic interpretation

The publication is both:

1. an editorial object, and
2. a business/audience object.

---

## PUB-02 — Long-Form Posts

Substack supports rich long-form written posts.

Typical capabilities include:

- formatted text;
- headings;
- lists;
- links;
- quotations;
- images;
- embeds;
- media;
- subscriber-specific content;
- paywall placement;
- scheduling;
- drafts.

### Uses

- essays;
- research;
- analysis;
- newsletters;
- institutional announcements;
- interviews;
- serialized writing.

### Agentic relevance

**Very high for drafting and editorial preparation.**

---

## PUB-03 — Email Distribution

Posts can be delivered directly to subscribers by email.

This creates a powerful relationship model:

```text
Publication
     ↓
subscriber email
     ↓
direct delivery
```

### Strategic importance

Email delivery reduces dependence on algorithmic feed ranking.

It does not guarantee attention, but it establishes a direct delivery channel.

---

## PUB-04 — Web Archive

Published content remains accessible through the publication website/archive.

This creates a durable public knowledge surface independent of a subscriber's inbox.

---

## PUB-05 — Custom Domain

Publications can use a custom domain.

At the current platform snapshot, Substack charges a one-time fee for connecting a custom domain.

### Architectural implication

A custom domain improves:

- publication identity;
- portability of brand;
- discoverability;
- institutional legitimacy.

However, content hosting and platform behavior remain dependent on Substack.

---

# 5. Audience Relationship Capabilities

Substack should be modeled as a relationship ladder rather than a single follower graph.

```text
Visitor
   ↓
Follower
   ↓
Free Subscriber
   ↓
Paid Subscriber
   ↓
Founding Member
```

Each step represents increased commitment.

---

## AUD-01 — Visitor

A visitor may read publicly available publication content without forming a persistent relationship.

This is the weakest relationship state.

---

## AUD-02 — Follower

Following creates a lightweight platform-native social relationship.

Followers may see:

- Notes;
- activity;
- publication presence in Home;
- network interactions.

### Strategic interpretation

A follower is primarily part of the **Substack social graph**, not yet the publication's direct distribution list.

---

## AUD-03 — Free Subscriber

A free subscriber creates an email-level relationship with the publication.

This is a major transition:

```text
platform attention
      ↓
direct subscriber relationship
```

The publication gains:

- a subscriber record;
- email delivery;
- participation in subscriber management;
- exportability.

---

## AUD-04 — Paid Subscriber

Paid subscribers add an economic relationship.

A paid subscriber can receive:

- paid-only posts;
- premium podcast/video;
- paid Chat access;
- live-event access;
- subscriber perks.

---

## AUD-05 — Founding Member

Founding membership allows a higher-support tier.

It can function as:

- patronage;
- premium membership;
- supporter identity;
- institutional contribution.

### Strategic relevance

For community institutions, Founding Member is conceptually closer to **supporter membership** than to a conventional content subscription.

---

# 6. Subscriber Ownership and Portability

## OWN-01 — Subscriber Export

Publishers can export subscriber lists.

This is one of Substack's most strategically significant capabilities.

The audience relationship is therefore more portable than a pure follower graph on many social platforms.

### Canon rule

> Subscriber data should be considered part of the publication's durable operating asset.

---

## OWN-02 — Content Export

Publishers can export publication content.

This reduces platform lock-in.

---

## OWN-03 — RSS

Publications expose RSS feeds.

RSS enables:

- external readers;
- feed aggregation;
- automated ingestion;
- research systems;
- content mirroring where legally and operationally appropriate.

### Agentic relevance

**High for observation and downstream processing.**

---

# 7. Audience Segmentation

## SEG-01 — Subscription Tier Segmentation

Content can be scoped by subscriber status.

Typical scopes:

- everyone;
- free subscribers;
- paid subscribers;
- founding members.

---

## SEG-02 — Segments and Tags

Substack supports audience segmentation beyond subscription status.

Segments and tags can represent:

- interests;
- cohorts;
- campaign participation;
- geography;
- engagement groups;
- editorial interests;
- customer/member categories.

### Strategic interpretation

Substack is gradually moving from "newsletter list" toward a lightweight **subscriber CRM**.

---

## SEG-03 — Audience-Specific Content Blocks

Different readers can see different blocks within the same post.

Conceptually:

```text
Post
├── public section
├── free subscriber section
├── paid subscriber section
└── founding member section
```

This is powerful because segmentation becomes part of the content model rather than requiring separate editions.

---

# 8. Subscription and Membership Economics

## PAY-01 — Free Subscription

Free subscription establishes:

- direct delivery;
- reader identity;
- conversion opportunity;
- audience relationship.

---

## PAY-02 — Monthly Subscription

Publishers can charge monthly recurring fees.

---

## PAY-03 — Annual Subscription

Publishers can charge annual recurring fees.

Annual plans support:

- higher upfront commitment;
- lower churn opportunities;
- membership framing.

---

## PAY-04 — Founding Membership

Founding Member pricing supports a premium supporter tier.

---

## PAY-05 — Stripe

Substack uses Stripe for paid subscription processing.

Relevant external concerns include:

- payment method availability;
- transaction processing;
- refunds;
- taxation;
- regional payments;
- accounting.

---

## PAY-06 — Platform Economics

At the current platform snapshot, Substack takes a percentage of web-based paid subscription revenue, with Stripe fees in addition.

### Canon rule

> Treat platform fees, payment fees, minimum subscription prices, and regional payment options as volatile operational configuration rather than architectural constants.

---

# 9. Paywall Capabilities

## WALL-01 — Paid Posts

Entire posts can be restricted to paying subscribers.

---

## WALL-02 — Partial Paywall

A public/free preview can lead into paid content.

Typical structure:

```text
public introduction
      ↓
value demonstration
      ↓
paywall
      ↓
subscriber-only depth
```

---

## WALL-03 — Paid Multimedia

Paywalling can apply to:

- text;
- podcast episodes;
- video;
- live content;
- other subscriber benefits.

---

# 10. Notes and Social Publishing

## NOTE-01 — Notes

Notes provide short-form social publishing.

Notes can include:

- text;
- images;
- links;
- quotes;
- commentary.

Readers can:

- reply;
- like;
- restack.

### Strategic interpretation

Notes give Substack an internal social-discovery layer.

---

## NOTE-02 — Restacks

Restacking allows one user/publication to redistribute another Note or post into the social feed.

This provides a network propagation primitive analogous to reposting, but within the Substack creator/readership ecosystem.

---

## NOTE-03 — Scheduled Notes

Notes can be scheduled.

This allows editorial planning across both:

- long-form publication;
- short-form discovery content.

---

# 11. Discovery and Growth

Substack now contains a meaningful internal acquisition network.

A canonical funnel is:

```text
discover
  ↓
follow
  ↓
engage
  ↓
subscribe
  ↓
pay
  ↓
deepen membership
  ↓
refer
```

---

## DISC-01 — Home Feed

The Home feed exposes readers to:

- subscriptions;
- Notes;
- followed accounts;
- recommended content;
- network activity.

---

## DISC-02 — Recommendations

Publishers can recommend other publications.

Recommendations may appear during:

- subscription onboarding;
- publication discovery;
- recommendation emails.

### Strategic significance

Recommendations create a creator-to-creator audience-growth graph.

---

## DISC-03 — Recommendation Attribution

Substack provides analytics showing subscriptions attributed to recommendations.

This makes collaborative growth measurable.

---

## DISC-04 — Creator Match

Creator Match suggests potentially useful publisher collaborations based on criteria such as topic and audience scale.

### Strategic interpretation

Creator Match turns the publisher graph into an explicit growth mechanism.

---

## DISC-05 — Leaderboards

Substack uses category and ranking surfaces such as:

- Bestseller;
- Rising;
- category leaderboards;
- country-oriented discovery.

These increase discovery beyond a publication's existing subscriber base.

---

## DISC-06 — Subscriber Referrals

Publications can operate referral programs.

Typical model:

```text
Subscriber
    ↓ refers
New Subscriber
    ↓
credit / reward
```

Possible rewards include:

- complimentary subscriptions;
- digital rewards;
- external benefits;
- discounts;
- access.

### Strategic relevance

Referrals turn the subscriber base into a growth channel.

---

# 12. Community Capabilities

## COM-01 — Comments

Posts can host reader comments and replies.

This allows:

- discussion;
- questions;
- feedback;
- community formation around durable content.

---

## COM-02 — Reply Rules

Publications can define written standards for replies/comments.

Substack can use automated moderation to hide likely rule-violating material for review.

### Governance interpretation

This is a useful hybrid pattern:

```text
declared rules
     ↓
AI assessment
     ↓
temporary hiding
     ↓
human review / restore
```

This is preferable to irreversible model-only moderation.

---

## COM-03 — Chat

Substack Chat provides ongoing conversational spaces for subscribers.

Possible audiences include:

- all subscribers;
- paid subscribers;
- founding members.

Chat supports persistent community interaction separate from individual article comments.

### Strategic interpretation

Chat moves Substack from one-way publishing toward a **publication-centered membership community**.

---

## COM-04 — Subscriber-Initiated Chat

Creators can allow subscribers to initiate Chat interactions, subject to platform controls.

---

## COM-05 — Scheduled Chat

Chat activity can be planned or scheduled.

This can support:

- office hours;
- event reminders;
- recurring member discussions;
- editorial prompts.

---

# 13. Podcast Capabilities

## POD-01 — Podcast Hosting

Substack can host podcasts directly.

Capabilities include:

- recording;
- upload;
- episode publication;
- RSS distribution;
- publication pages;
- subscriber delivery.

---

## POD-02 — Paid Podcast Episodes

Podcast content can be restricted to paying subscribers.

---

## POD-03 — Free Previews

Paid episodes can provide free previews.

This mirrors the written paywall funnel.

---

## POD-04 — Podcast Distribution

Podcast RSS can distribute episodes to external podcast applications.

### Strategic importance

Substack therefore acts as:

```text
publication source
      ↓
Substack
      ↓
external podcast ecosystem
```

not merely as a closed hosting destination.

---

## POD-05 — Transcripts

Substack provides transcription capabilities for podcast/audio content.

### Agentic relevance

Transcripts make multimedia easier to:

- index;
- summarize;
- search;
- repurpose;
- feed into knowledge systems.

---

# 14. Video Capabilities

## VID-01 — Video Posts

Creators can publish native video posts.

Capabilities include:

- upload;
- direct recording;
- subscriber delivery;
- paid access;
- transcripts.

---

## VID-02 — Recording Studio

Substack includes recording capabilities with support for features such as:

- guests;
- screen sharing;
- creator-oriented production.

---

## VID-03 — Audio Extraction

Video content can be adapted into podcast/audio distribution workflows.

This supports multimodal repurposing.

---

# 15. Live Capabilities

## LIVE-01 — Live Video

Eligible creators can host live video sessions.

Capabilities include:

- scheduled live events;
- audience selection;
- co-hosts;
- live chat;
- email/push notification.

---

## LIVE-02 — Audience-Gated Live Events

Live events can be restricted to:

- everyone;
- subscribers;
- paid subscribers.

This makes live interaction part of membership economics.

---

## LIVE-03 — RTMP

Selected/beta workflows support professional live-streaming via RTMP.

This enables tools such as:

- OBS;
- StreamYard;
- other professional broadcast software.

---

# 16. Subscriber Perks

## PERK-01 — Perks

Paid supporters can receive benefits beyond content.

Possible examples:

- promotional codes;
- downloads;
- special access;
- live-event access;
- member benefits.

### Strategic interpretation

Perks move Substack from "paid media" toward **membership infrastructure**.

---

# 17. Multi-Author Publishing

## AUTH-01 — Contributors

Publications can have multiple contributors.

Contributors can participate in editorial workflows with scoped publishing capabilities.

---

## AUTH-02 — Administrators

Administrators have broader publication-management powers.

### Governance rule

Administrative access should be assigned narrowly because it covers subscriber, commercial, and publication operations.

---

## AUTH-03 — Institutional Publishing

A publication need not correspond to one individual creator.

It can represent:

- a company;
- a research group;
- a society;
- a magazine;
- a collective.

This is especially relevant for the Coulomb Society model.

---

# 18. Subscriber Management

## CRM-01 — Subscriber Dashboard

Publishers can manage subscribers through dashboard views.

Relevant dimensions can include:

- free/paid status;
- founding status;
- activity;
- subscription history;
- cohort/segment properties.

---

## CRM-02 — Subscriber Filtering

Publishers can filter and inspect subsets of the subscriber base.

---

## CRM-03 — Export

Subscriber records can be exported.

### Canon rule

Important member/subscriber identity should ideally be reconciled with an external canonical identity system if the publication participates in a larger institution.

---

# 19. Analytics

## ANA-01 — Publication Metrics

Substack provides publication-level metrics such as:

- subscriber counts;
- paid subscriber counts;
- growth;
- gross annualized revenue.

---

## ANA-02 — Post Metrics

Post-level metrics can include:

- delivery;
- opens;
- views;
- conversions;
- subscriber effects.

---

## ANA-03 — Revenue Analytics

Publishers can evaluate:

- subscription revenue;
- paid conversion;
- retention;
- membership economics.

---

## ANA-04 — Traffic Sources

Traffic and acquisition sources help evaluate:

- recommendations;
- external links;
- Notes;
- referrals;
- direct traffic;
- campaigns.

---

## ANA-05 — Google Analytics

External analytics can supplement built-in metrics.

### Architecture principle

Substack analytics should be integrated into broader business intelligence where durable comparison across channels matters.

---

# 20. AI and MCP Integration

## AI-01 — Official MCP Server

Substack introduced an official MCP server for eligible publishers.

The current documented use case focuses on exposing publication analytics to compatible AI assistants.

Possible data includes:

- subscriber counts;
- post performance;
- revenue;
- retention;
- growth.

At the current platform snapshot, this capability is documented for qualifying/Bestseller publications.

---

## AI-02 — Agent-Readable Publisher Operations

MCP creates an important architecture:

```text
Substack analytics
       ↓
MCP
       ↓
AI assistant / agent
       ↓
analysis
       ↓
publisher decision
```

Possible uses:

- performance analysis;
- churn analysis;
- topic evaluation;
- conversion analysis;
- cohort comparison;
- campaign planning.

---

## AI-03 — Agent-Operability Boundary

Substack's supported general-purpose automation/write surface is substantially narrower than Telegram's Bot API or X's publishing API.

Therefore:

> **Substack is currently more agent-readable than agent-operable.**

Do not assume the existence of a general autonomous publishing API unless the specific required capability is explicitly documented.

---

# 21. Agentic Capability Model

For Substack, it is useful to distinguish six agent roles.

## AGT-01 — Research Agent

```text
sources
  ↓
research
  ↓
evidence package
  ↓
editorial process
```

The agent supports publication quality without necessarily touching Substack directly.

---

## AGT-02 — Editorial Agent

The agent can:

- propose topics;
- draft posts;
- edit drafts;
- propose titles;
- prepare summaries;
- create subscriber-specific variants;
- recommend paywall position.

---

## AGT-03 — Audience Analyst

Using exports, analytics, or MCP where available, an agent can:

- analyze subscriber growth;
- compare cohorts;
- evaluate conversion;
- detect churn;
- propose retention actions;
- identify strong content themes.

---

## AGT-04 — Growth Agent

The agent can analyze:

- Notes performance;
- recommendations;
- referrals;
- subscriber acquisition;
- Creator Match opportunities;
- conversion funnels.

It may recommend actions without directly executing them.

---

## AGT-05 — Membership Agent

The agent can assist with:

- member segmentation;
- benefit design;
- subscriber communication;
- retention;
- paid-tier positioning;
- Founding Member programs.

---

## AGT-06 — Publishing Operator

A publishing operator coordinates:

```text
research
   ↓
draft
   ↓
editorial review
   ↓
policy
   ↓
publication
   ↓
analytics
   ↓
learning
```

Where no supported publishing API exists, the final publication step should remain human-operated or use an explicitly supported integration.

---

# 22. Editorial Governance

Substack's center of gravity is durable publishing. Therefore editorial governance matters more than high-frequency automation.

Recommended control loop:

```text
Editorial intent
      ↓
research
      ↓
draft
      ↓
fact / source review
      ↓
editorial review
      ↓
audience / paywall decision
      ↓
publication
      ↓
performance analysis
      ↓
editorial learning
```

---

# 23. Agentic Action Classes

## Class A — Observation

Examples:

- read RSS;
- inspect analytics;
- inspect exports;
- analyze public content.

Suitable for high autonomy.

---

## Class B — Internal Analysis

Examples:

- summarize performance;
- segment subscribers;
- detect churn;
- identify promising themes.

Suitable for high autonomy where data governance permits.

---

## Class C — Drafting

Examples:

- draft posts;
- draft Notes;
- prepare podcast descriptions;
- prepare subscriber campaigns.

Ideal for human/agent hybrid workflows.

---

## Class D — Editorial Recommendation

Examples:

- recommend paywall;
- recommend segment;
- recommend publication timing;
- recommend collaborator;
- recommend membership campaign.

Suitable for bounded autonomy.

---

## Class E — Publication

Examples:

- publish post;
- publish Note;
- start Chat;
- launch live event.

Should use explicitly supported interfaces and policy controls.

---

## Class F — Commercial Action

Examples:

- change subscription pricing;
- alter paid tiers;
- grant benefits;
- alter member entitlements.

Prefer deterministic authorization and often human approval.

---

# 24. Membership Governance

Paid publishing introduces obligations beyond ordinary social posting.

Governance should cover:

- subscription promises;
- content access;
- pricing;
- cancellations;
- refunds;
- perks;
- member expectations;
- data handling.

### Canon principle

> A paid subscriber is not merely an engaged reader; they are part of an ongoing commercial relationship.

---

# 25. Data Governance

## DATA-01 — Subscriber Data

Subscriber information is valuable operational data.

It should be treated as:

- personal data;
- commercial relationship data;
- potentially sensitive behavioral data.

---

## DATA-02 — External Canonical Identity

For larger systems:

```text
Substack subscriber
       ↓
identity mapping
       ↓
canonical member/customer
       ↓
authorization / CRM / membership
```

Substack should not necessarily be the sole identity authority.

---

## DATA-03 — Export Discipline

Regular exports can improve:

- portability;
- recovery;
- analytics;
- institutional continuity.

They must be handled securely.

---

# 26. Substack as an Edge Architecture

For sophisticated systems, Substack should be modeled as a **publication and membership edge**.

```text
                      Substack
                         │
                   substack-edge
                         │
       ┌─────────────────┼─────────────────┐
       │                 │                 │
   Publishing         Audience         Analytics
       │                 │                 │
       └─────────────────┼─────────────────┘
                         │
                Identity / Membership
                         │
          ┌──────────────┼──────────────┐
          │              │              │
       Agents        Knowledge       Commerce
          │              │              │
          └──────────────┼──────────────┘
                         │
                    Core Systems
```

A future `substack-edge` should normally own:

- publication identity mapping;
- subscriber imports/exports;
- RSS ingestion;
- analytics ingestion;
- MCP integration;
- audience-segment mapping;
- cross-channel attribution;
- publication metadata;
- audit correlation;
- supported outbound integration where available.

It should **not** become the canonical home of broader institutional business logic.

---

# 27. Canonical Entity Model

A useful normalized model is:

```text
SubstackPlatform
│
├── Publication
│   ├── Section
│   ├── Author
│   └── Administrator
│
├── Content
│   ├── Post
│   ├── Note
│   ├── PodcastEpisode
│   ├── VideoPost
│   └── LiveEvent
│
├── AudienceIdentity
│   ├── Follower
│   ├── FreeSubscriber
│   ├── PaidSubscriber
│   └── FoundingMember
│
├── Segment
├── Tag
│
├── CommunityInteraction
│   ├── Comment
│   ├── Reply
│   └── ChatMessage
│
├── Recommendation
├── Referral
│
├── Subscription
│   ├── Monthly
│   ├── Annual
│   └── Founding
│
├── Perk
│
└── Analytics
    ├── PublicationMetric
    ├── PostMetric
    ├── SubscriberMetric
    └── RevenueMetric
```

---

# 28. Capability Selection Guide

| Requirement | Preferred Substack Primitive |
|---|---|
| Long-form publication | Post |
| Direct email delivery | Subscription + Post |
| Public archive | Publication website |
| Lightweight social update | Note |
| Reader discussion | Comments |
| Ongoing member discussion | Chat |
| Paid written content | Paid Post |
| Premium audio | Paid Podcast |
| Premium video | Paid Video |
| Member-only live event | Paid Live Video |
| Lightweight platform relationship | Follow |
| Direct audience relationship | Free Subscription |
| Commercial membership | Paid Subscription |
| Patron/supporter tier | Founding Member |
| Audience segmentation | Segments / Tags |
| Cross-publication growth | Recommendations |
| Viral/member-driven growth | Referrals |
| Creator collaboration | Creator Match |
| Publication analytics | Dashboard |
| External AI analysis | MCP |
| Portable public syndication | RSS |
| Subscriber portability | CSV Export |
| Brand independence | Custom Domain |

---

# 29. Substack vs X vs Telegram

A useful canonical comparison:

```text
X
│
├── public identity
├── attention
├── discovery
├── public conversation
└── real-time intelligence

Substack
│
├── publication
├── subscriber ownership
├── direct delivery
├── membership
└── recurring revenue

Telegram
│
├── conversation
├── participation
├── programmable services
├── community operations
└── human / agent interaction
```

A compact formulation is:

```text
X         → Reach
Substack  → Relationship
Telegram  → Participation
```

Or, from a user's perspective:

```text
X         → Find us and encounter us.
Substack  → Read us, follow us, support us.
Telegram  → Join us and participate with us.
```

---

# 30. Combined Institutional Architecture

For an institution such as the Coulomb Society:

```text
                        Coulomb Society
                              │
          ┌───────────────────┼───────────────────┐
          │                   │                   │
          X               Substack            Telegram
          │                   │                   │
      discovery           publication          community
      reach               subscription         participation
      public debate       membership           workflows
      attention           durable content      agent services
      trend sensing       revenue              events
          │                   │                   │
          └───────────────────┼───────────────────┘
                              │
                       Identity / Policy
                              │
                 Knowledge / Agent Systems
```

The institution exists independently of all three platforms.

---

# 31. Coulomb Society Reference Pattern

A possible Substack structure:

```text
Coulomb Society Publication
│
├── Essays
│   ├── science
│   ├── technology
│   ├── arts
│   └── philosophy
│
├── Society Notes
│   └── short observations / discovery
│
├── Podcast
│   ├── interviews
│   └── discussions
│
├── Video
│   └── talks / demonstrations
│
├── Live
│   └── public and member events
│
├── Membership
│   ├── free subscriber
│   ├── supporting subscriber
│   └── founding member
│
├── Chat
│   └── subscriber discussion
│
└── Publisher Operations
    ├── analytics
    ├── segments
    ├── referrals
    ├── recommendations
    └── AI-assisted editorial analysis
```

The key architectural principle is:

> **The Society owns its identity, knowledge, and membership model. Substack owns a highly effective publication and subscriber experience around them.**

---

# 32. Capability Maturity Model

| Stage | Description |
|---|---|
| **S0 — Manual Publishing** | Human authors publish manually. |
| **S1 — Instrumented** | Analytics, RSS, and subscriber exports are used systematically. |
| **S2 — Integrated** | Subscriber, analytics, and content data connect to external systems. |
| **S3 — Agent-Assisted Editorial** | Agents research, draft, edit, and analyze. |
| **S4 — Agent-Assisted Growth** | Agents evaluate segments, referrals, recommendations, and conversion. |
| **S5 — Policy-Governed Operations** | Selected operational actions are automated through explicitly supported interfaces. |
| **S6 — Adaptive Publication System** | Editorial, membership, and growth loops adapt continuously while publication authority remains governed. |

Unlike X or Telegram, Substack maturity should not be measured primarily by autonomous posting.

A mature Substack operation is one where:

- editorial quality improves;
- subscriber relationships deepen;
- audience ownership improves;
- membership economics become measurable;
- agent assistance reduces operational effort.

---

# 33. Substack Strengths

Substack is particularly strong where a system needs several of the following simultaneously:

- long-form publishing;
- email distribution;
- web archive;
- subscriber ownership;
- paid memberships;
- multimedia;
- direct audience relationship;
- creator discovery;
- referrals;
- recommendations;
- community interaction;
- content portability;
- subscription analytics;
- lightweight institutional publishing.

---

# 34. Substack Weaknesses and Boundaries

Substack should not automatically be used as:

- a canonical enterprise CRM;
- a full membership-management backend;
- a high-assurance authorization system;
- a general workflow engine;
- a programmable bot platform;
- an internal event bus;
- a secret-management system;
- a generalized application platform;
- a high-volume agent coordination system.

These responsibilities normally belong to external infrastructure.

---

# 35. Strategic Interpretation

Substack can be understood as:

> **A publication-centered relationship platform combining durable content, direct subscriber delivery, recurring membership economics, creator discovery, multimedia, community interaction, and increasingly AI-readable publisher operations.**

Its particularly valuable combination is:

```text
publication
+ email
+ subscriber identity
+ paid membership
+ portable audience data
+ Notes
+ recommendations
+ referrals
+ multimedia
+ analytics
+ MCP
```

Together these make Substack an unusually strong **publication and membership edge** for creator- and institution-centered systems.

---

# 36. Reference Architecture Principle

The canonical integration rule should be:

> **Substack owns the publication experience. The institution owns identity and membership. The knowledge system owns durable knowledge. The policy layer owns authority. Agents own bounded research, analysis, and editorial preparation.**

Expressed architecturally:

```text
Knowledge / Sources
       │
       ▼
Research / Editorial Agents
       │
       ▼
Editorial Policy
       │
       ▼
Publication Decision
       │
       ▼
Substack
       │
       ├── web
       ├── email
       ├── app
       ├── Notes
       ├── podcast
       ├── video
       └── live
       │
       ▼
Audience / Membership
       │
       ▼
Analytics / MCP / Export
       │
       └──────────────► learning loop
```

---

# 37. Sources

Primary Substack documentation consulted for this version:

1. **Publishing on Substack**  
   https://support.substack.com/hc/en-us/articles/29152946791188-How-can-I-publish-on-Substack

2. **Following vs subscribing**  
   https://support.substack.com/hc/en-us/articles/18261513315348-How-does-following-work-on-Substack

3. **Custom domains**  
   https://support.substack.com/hc/en-us/articles/360051222571-How-do-I-set-up-my-custom-domain-on-Substack

4. **Paid publications**  
   https://support.substack.com/hc/en-us/articles/360037459952-How-do-I-set-up-a-paid-publication

5. **Substack pricing**  
   https://support.substack.com/hc/en-us/articles/360037607131-How-much-does-Substack-cost

6. **Audience-specific content**  
   https://support.substack.com/hc/en-us/articles/50558240901268-How-do-I-add-audience-specific-content-to-a-post-on-Substack

7. **Notes**  
   https://support.substack.com/hc/en-us/articles/14564821756308-Getting-started-on-Substack-Notes

8. **Recommendations**  
   https://support.substack.com/hc/en-us/articles/5036794583828-How-can-I-recommend-other-publications-on-Substack

9. **Subscriber referrals**  
   https://support.substack.com/hc/en-us/articles/16142857300372-What-are-subscriber-referrals-on-Substack

10. **Reply Rules**  
    https://support.substack.com/hc/en-us/articles/49712271829012-What-are-Reply-Rules-on-Substack

11. **Chat**  
    https://support.substack.com/hc/en-us/articles/10410279875092-How-do-I-start-a-Chat-thread

12. **Podcast publishing**  
    https://support.substack.com/hc/en-us/articles/360037462092-How-do-I-create-and-publish-a-podcast-on-Substack

13. **Video posts**  
    https://support.substack.com/hc/en-us/articles/21093671091220-Guide-to-video-posts-on-Substack

14. **Live Video**  
    https://support.substack.com/hc/en-us/articles/30316077882516-Getting-started-with-Live-Video-on-Substack

15. **RTMP live video**  
    https://support.substack.com/hc/en-us/articles/32070353475860-Live-video-on-Substack-via-RTMP

16. **Subscriber Perks**  
    https://support.substack.com/hc/en-us/articles/50773191186324-What-are-Subscriber-Perks-on-Substack

17. **Multiple authors / contributors**  
    https://support.substack.com/hc/en-us/articles/360039016832-Can-my-Substack-publication-have-multiple-authors-or-contributors

18. **Subscriber dashboard**  
    https://support.substack.com/hc/en-us/articles/360058529871-How-do-I-use-the-subscriber-dashboard-on-Substack

19. **Substack metrics**  
    https://support.substack.com/hc/en-us/articles/5320347155860-A-guide-to-Substack-metrics

20. **Exporting posts**  
    https://support.substack.com/hc/en-us/articles/360037466012-How-do-I-export-my-posts

21. **Exporting subscriber email lists**  
    https://support.substack.com/hc/en-us/articles/6314498343700-How-do-I-export-my-email-list-on-Substack

22. **Substack MCP / AI Assistant integration**  
    https://support.substack.com/hc/en-us/articles/50834026608916-How-to-connect-Substack-to-your-AI-Assistant

23. **Creator Match / audience tooling**  
    https://on.substack.com/p/new-on-substack-creator-match-audience

---

# 38. Canon Maintenance

Substack evolves rapidly, particularly around:

- Notes;
- discovery;
- AI integration;
- subscriber segmentation;
- creator collaboration;
- live video;
- membership benefits;
- creator economics;
- analytics;
- platform fees.

This document therefore distinguishes:

- **canonical concepts**, intended to remain stable;
- **current Substack implementations**, which may change;
- **pricing and limits**, which should be revalidated;
- **integration surfaces**, which should never be assumed without documentation.

Recommended update triggers:

- new public APIs;
- changes to MCP capabilities;
- changes to paid subscription economics;
- new audience segmentation models;
- major changes to Notes/discovery;
- new membership/perk capabilities;
- changes to export/portability;
- new creator collaboration tools;
- significant live/video/podcast changes;
- changes to moderation and Reply Rules.

---

# 39. Canon Summary

The shortest useful model is:

```text
Substack =
    publication
  + email
  + direct subscriber relationship
  + membership
  + recurring revenue
  + multimedia
  + social discovery
  + community
  + analytics
  + portable audience data
  + AI-readable publisher operations
```

For an agent-active institution:

```text
research deeply
      ↓
draft intelligently
      ↓
govern editorially
      ↓
publish deliberately
      ↓
build direct relationships
      ↓
measure membership outcomes
      ↓
learn without surrendering audience ownership
```

---

**End of Substack Capability Canon v0.1**