Distribution Strategy

The Distribution Problem

You can build 116 repositories with 739,000 words of documentation and it means nothing if nobody encounters the work. Distribution is the most systematically underthought problem in creative technology: engineers and artists invest enormous energy in building, then treat the question of who sees the work as an afterthought — a tweet after launch, a link in a Slack channel, a conference talk if they happen to know someone on the program committee.^[1]

The POSSE Principle

The distribution strategy is built on the POSSE principle: Publish on your Own Site, Syndicate Everywhere. I directed the architectural commitment to long-term content ownership, where all content originates in the organ system's own repositories — the canonical source lives in infrastructure the practitioner controls — and gets syndicated outward through defined channels.^[3]

name: Distribute Content (POSSE)
on:
  workflow_dispatch:
    inputs:
      content_type:
        description: 'Type of content to distribute'
        required: true
        type: choice
        options:
          - essay
          - launch-announcement
          - milestone-update
      target_channels:
        description: 'Distribution channels'
        required: true
        type: choice
        options:
          - all
          - mastodon-only
          - discord-only

jobs:
  distribute:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Extract canonical content
        run: python scripts/extract-content.py
      - name: Adapt for Mastodon
        if: contains(inputs.target_channels, 'mastodon') || inputs.target_channels == 'all'
        run: python scripts/adapt-mastodon.py
        env:
          MASTODON_TOKEN: ${{ secrets.MASTODON_TOKEN }}
      - name: Adapt for Discord
        if: contains(inputs.target_channels, 'discord') || inputs.target_channels == 'all'
        run: python scripts/adapt-discord.py
        env:
          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK }}

Audience Segmentation

The distribution strategy identifies four distinct audiences, each requiring a different framing of the same underlying content. This is not a marketing persona exercise — it is a rhetorical analysis of how the same work carries different significance for different communities of practice.^[5]

Channel-Native Adaptation

The critical distinction in this distribution strategy is between cross-posting and channel-native adaptation. Cross-posting takes a single piece of content and copies it to multiple platforms unchanged — a practice that violates the norms of every platform simultaneously. I implemented a genuine re-framing process for each channel's discourse conventions, audience expectations, and technical affordances.^[7]

Automated Distribution Infrastructure

The distribution system is not a manual checklist but an automated pipeline implemented as GitHub Actions workflows. The distribute-content.yml workflow extracts canonical content from the organ repositories, applies channel-specific adaptation scripts, and publishes to each target platform through authenticated API calls. Mastodon distribution was verified with HTTP 200 responses; Discord distribution was verified with HTTP 204 responses.^[1]

def adapt_for_mastodon(essay: Essay) -> list[str]:
    """Transform a canonical essay into a Mastodon thread.

    Rules:
    - First post: hook + essay title + canonical URL
    - Middle posts: 1-2 key insights, max 500 chars each
    - Final post: call-to-action + canonical URL
    - Always link back to the canonical source (POSSE)
    """
    thread = []

    # Opening post: hook the audience
    thread.append(
        f"{essay.hook}\n\n"
        f"New essay: {essay.title}\n"
        f"{essay.canonical_url}\n\n"
        f"#BuildingInPublic #CreativeInfrastructure"
    )

    # Key insight posts (2-3 per essay)
    for insight in essay.extract_key_insights(max=3):
        thread.append(
            f"{insight.summary}\n\n"
            f"Full context: {essay.canonical_url}"
        )

    # Closing post
    thread.append(
        f"Read the full {essay.word_count:,}-word essay: "
        f"{essay.canonical_url}\n\n"
        f"Part of the Public Process collection: "
        f"21 essays on building creative infrastructure."
    )

    return thread

Distribution as Organ: Governance Protection

The most unusual aspect of this project is that distribution has its own organ — ORGAN VII (Kerygma) — rather than being a feature of marketing or a task on a project board. This is not organizational vanity but a governance decision with real consequences.^[9]

Content Calendar Architecture

The content calendar is driven by external rhythms rather than internal cadences. Grant deadlines (Knight Foundation, NEA, Mellon Foundation, NSF) trigger increased visibility 2-4 weeks beforehand. Conference seasons (SIGGRAPH in July-August, Ars Electronica in September, ISEA in June) create attention windows for submissions and related content. The academic calendar shapes posting density: reduced during exam periods, increased at the start of semesters when researchers form new interests.^[4]

The content mix targets a 70/30 ratio of evergreen to ephemeral content. Essays exploring ideas beyond the news cycle, repository documentation with indefinite shelf life, and governance specifications demonstrating institutional maturity form the evergreen core. Event announcements and milestone celebrations serve as ephemeral supplements but are not the strategic center.^[6]

Strategic Risks and Mitigations

risks:
  - name: Mastodon instance shutdown
    likelihood: low
    impact: high
    mitigation: >
      All content canonical on own site.
      Maintain account on well-established instance.

  - name: Platform lock-in
    likelihood: low
    impact: high
    mitigation: >
      POSSE architecture prevents dependency on any
      single platform. Syndicated copies are derivative.

  - name: Grant reviewer unfamiliarity
    likelihood: medium
    impact: high
    mitigation: >
      Self-explanatory entry points (org profiles,
      essay abstracts). Avoid internal jargon.

  - name: Audience fatigue
    likelihood: medium
    impact: medium
    mitigation: >
      Quality-over-quantity principle.
      Publish only when there is something worth saying.

Measuring Distribution Without Vanity Metrics

The distribution strategy deliberately avoids vanity metrics — follower counts, like ratios, impression numbers — in favor of metrics that indicate whether the content reached the intended audiences and served the intended purposes.^[2] The measurement framework tracks leading indicators weekly (new followers, engagement rate per post, click-through rate to canonical URLs), lagging indicators quarterly (grant application outcomes, interview invitations, conference acceptance rate), and health indicators monthly (audience segment composition, content mix ratio, channel reliability). Raw follower counts are explicitly excluded from success criteria — what matters is whether the right people encountered the right content through the right channels.