distribution-strategy
Distribution Strategy
The strategic brain of ORGAN-VII – audience segmentation, channel strategy, content calendar, growth targets, engagement benchmarks, and distribution philosophy for the eight-organ creative-institutional system.
Distribution Strategy is the public-facing planning repository for ORGAN-VII (Kerygma), the marketing and distribution organ of the organvm ecosystem. This is where strategic intent is documented, audience segments are defined, channel performance is analyzed, and distribution decisions are made visible. It is the why and when behind every message the system sends into the world.
This repository is intentionally public. While announcement-templates and social-automation contain internal operational details, Distribution Strategy operates in the open because transparency about audience strategy is itself a portfolio asset. Grant reviewers evaluate whether applicants understand their audiences. Hiring managers assess whether candidates think strategically about reach and impact. Fellow creative technologists appreciate honest analysis of what works and what does not. Making this strategy public serves all three audiences simultaneously.
The core thesis: quality over quantity, POSSE over platform lock-in, evergreen over ephemeral. The organvm system does not chase viral moments. It builds sustained visibility with the specific audiences that matter for its portfolio, funding, and community goals – and it does so on infrastructure it controls.
Table of Contents
- Overview
- Distribution Philosophy
- Audience Segmentation
- Channel Strategy
- Content Calendar
- Growth Targets and Benchmarks
- Competitive Landscape
- Content Types and Formats
- Measurement Framework
- Strategic Risks and Mitigations
- Templates and Resources
- Metrics and Tracking
- Cross-Organ Dependencies
- Contributing
- License
- Author and Contact
Overview
Distribution strategy for a creative-institutional system differs fundamentally from product marketing or personal brand building. The organvm system is not selling a product, not building a personal following, and not optimizing for engagement metrics as ends in themselves. Instead, it is constructing a portfolio presence that serves three concurrent goals:
- Grant competitiveness. Demonstrating organizational capacity, technical depth, and community engagement to funding bodies (Knight Foundation, NEA, Mellon Foundation, NSF, Processing Foundation Fellowship, Google Creative Fellowship).
- Hiring signal. Providing evidence of systems thinking, production-quality engineering, and architectural reasoning to technical recruiters and engineering managers evaluating portfolio submissions.
- Community contribution. Sharing knowledge, tools, and process insights with the creative technology community in a way that generates goodwill, collaboration opportunities, and citation.
These three goals are not in tension – they are mutually reinforcing. The essay that demonstrates governance thinking to a grant reviewer also shows architectural maturity to a hiring manager and shares useful knowledge with the open-source community. Distribution strategy maximizes this triple-audience leverage by ensuring the right content reaches the right people through the right channels at the right time.
Distribution Philosophy
POSSE: Publish on Own Site, Syndicate Elsewhere
The organvm system adopts the POSSE principle as a foundational distribution commitment. The implications are structural:
- Canonical content lives on infrastructure we control. The ORGAN-V Jekyll site at
https://organvm-v-logos.github.io/public-process/hosts all essays, with an Atom RSS feed for subscribers. GitHub repositories host all documentation and code. These are platforms where content ownership is unambiguous and portability is guaranteed. - Social platforms receive syndicated copies, not originals. Mastodon posts, Discord embeds, and LinkedIn articles are derivative – they excerpt, summarize, and link back to canonical sources. If Mastodon disappears tomorrow, the content survives. If Discord changes its terms of service, no essays are lost.
- Syndication serves discovery, not dependency. Social platforms are discovery mechanisms that introduce audiences to the canonical content. The goal is to move people from platform feeds to owned-site engagement, not to build platform-specific audiences that exist only within walled gardens.
Quality Over Quantity
The organvm system publishes when it has something worth saying, not because a content calendar demands daily output. The publication rhythm is driven by genuine milestones – repository deployments, essay completions, system achievements – not by engagement algorithms that reward frequency over substance.
This is a strategic choice, not a limitation. In the audiences this system targets (academic researchers, grant reviewers, technical hiring managers), posting frequency has diminishing returns beyond a threshold. A weekly digest with substantive content outperforms daily posts with thin content. A single well-crafted essay with genuine insight generates more lasting impact than a dozen promotional posts.
Evergreen Over Ephemeral
The content strategy prioritizes artifacts that remain valuable over time:
- Essays explore ideas that are relevant beyond the news cycle. “Why Orchestrate Everything” is not a reaction to a trend – it is a position paper that remains useful whether read today or in two years.
- Repository documentation serves as permanent reference material. A 3,000-word README is a portfolio piece with indefinite shelf life.
- System documentation (governance rules, dependency models, orchestration specs) demonstrates institutional maturity regardless of when it is encountered.
Ephemeral content (event announcements, milestone celebrations) is produced as needed but is not the strategic center. The ratio target is 70% evergreen / 30% ephemeral.
Audience Segmentation
Segment 1: Academic Researchers and Digital Humanists
Profile: Faculty, postdocs, PhD students, and independent researchers in digital humanities, computational creativity, media studies, science and technology studies, and related fields. They discover work through academic social media (Mastodon is disproportionately popular in this segment), conference proceedings, and citation networks.
What they value: Theoretical rigor, methodological transparency, engagement with relevant literature, conceptual novelty, reproducibility. They evaluate work by its intellectual contribution, not its commercial viability.
How to reach them:
- Primary channel: Mastodon (many academics migrated from Twitter; Mastodon’s instance model creates concentrated communities in
scholar.social,hcommons.social, etc.) - Secondary channel: ORGAN-V essays (discoverable via RSS, search engines, and citation)
- Tertiary channel: Conference submissions and proceedings
Content strategy for this segment:
- Lead with theoretical frameworks and conceptual contributions
- Reference relevant thinkers and traditions (Deleuze, Haraway, Bratton, etc. where genuinely applicable)
- Share process insights (how the recursive engine models ontological layers, how governance structures encode institutional thinking)
- Avoid commercial framing entirely
Engagement metrics: Boosts and replies on Mastodon (especially from accounts with academic institutional affiliations), citations in papers and talks, invitations to speak or collaborate.
Segment 2: Grant Reviewers and Program Officers
Profile: Program staff at foundations and government agencies who evaluate funding applications. They read quickly, assess against rubrics, and look for evidence rather than claims. They are not regular social media consumers but do check applicants’ online presence during review periods.
What they value: Organizational capacity, sustainability planning, community impact, alignment with program priorities, evidence of professional infrastructure. They want to see that an applicant can execute at scale, not just ideate.
How to reach them:
- Primary channel: Direct (grant applications reference specific URLs – repos, essays, org profiles)
- Secondary channel: GitHub presence (org profiles, repository quality, documentation depth)
- Tertiary channel: LinkedIn (for professional visibility during review periods)
Content strategy for this segment:
- Ensure all public-facing assets are grant-reviewer-friendly at all times (not just during application windows)
- Emphasize system-level thinking: 8 organizations, 67 repositories, governance structures, quality processes
- Quantify everything: word counts, test counts, coverage metrics, repository counts
- Connect individual deliverables to broader systemic goals
- Maintain a “grant readiness” posture – any reviewer checking the system at any time should find professional-grade materials
Engagement metrics: Grant application outcomes, reviewer feedback, shortlist appearances. These are lag indicators with long feedback loops (6-12 months from application to decision).
Segment 3: Hiring Managers and Technical Recruiters
Profile: Engineering managers, technical leads, and recruiters at companies evaluating candidates’ portfolios. They spend 30-60 seconds on initial portfolio review and 5-10 minutes on deep dives for shortlisted candidates.
What they value: Production-quality code, architectural reasoning, testing discipline, documentation quality, systems thinking, evidence of shipping real work (not just tutorials and toy projects). They distinguish between “built a thing” and “built a thing that handles failure modes, scales, and is maintained.”
How to reach them:
- Primary channel: GitHub (org profiles, pinned repositories, README quality, commit history)
- Secondary channel: LinkedIn (professional positioning, portfolio links in profile)
- Tertiary channel: ORGAN-V essays (especially “Why Orchestrate Everything” and “Governance Without Bureaucracy” – these demonstrate the kind of thinking hiring managers value)
Content strategy for this segment:
- Repository READMEs are the primary instrument. Every README is written to withstand scrutiny from a senior engineer: specific, honest, technically detailed
- Architecture diagrams, test counts, and coverage metrics appear prominently
- Cross-organ coordination demonstrates project management and systems thinking
- The meta-system itself (orchestrating 67 repos across 8 orgs) is evidence of organizational capacity that most candidates cannot demonstrate
Engagement metrics: Profile views (GitHub analytics), repository stars and forks (lagging indicator), interview invitations (ultimate outcome metric).
Segment 4: Creative Technologists and Fellow Practitioners
Profile: Artists, designers, creative coders, and technologists working at the art-technology intersection. They discover work through Mastodon, conferences (SIGGRAPH, Ars Electronica, ISEA), creative coding communities (Processing, openFrameworks, TouchDesigner), and peer networks.
What they value: Aesthetic ambition, technical craft, conceptual depth, process transparency, generosity with knowledge, community contribution. They evaluate by “would I want to collaborate with this person” and “does this work expand my understanding of what is possible.”
How to reach them:
- Primary channel: Mastodon (strong creative technology community presence)
- Secondary channel: ORGAN-V essays (building-in-public content resonates deeply)
- Tertiary channel: Conference presence, community events
Content strategy for this segment:
- Share process, not just results. “Here is what I tried and what broke” is more valuable than “here is the polished output.”
- Foreground the creative vision – what is this system for, aesthetically and philosophically?
- Invite collaboration and contribution. Open-source is a community act, not just a licensing decision.
- Acknowledge influences and inspirations explicitly
Engagement metrics: Mastodon engagement (especially replies and conversations, not just boosts), collaboration requests, community event attendance, fork/contribution activity.
Segment 5: Open Source Community
Profile: Developers who discover, use, and contribute to open-source projects. They find work through GitHub trending, Hacker News, Reddit, Mastodon developer communities, and word of mouth.
What they value: Code quality, documentation completeness, maintainer responsiveness, issue triage speed, contribution guidelines, license clarity. They evaluate by “could I contribute to this project” and “would I trust this project as a dependency.”
How to reach them:
- Primary channel: GitHub (repository quality, issue response time, CONTRIBUTING.md, community health files)
- Secondary channel: Mastodon developer communities
- Tertiary channel: Hacker News, Reddit (for major releases and milestones only)
Content strategy for this segment:
- Maintain impeccable repository hygiene: clear READMEs, typed contribution guidelines, responsive issue management
- Release notes follow conventional changelog format
- Community health files (CODE_OF_CONDUCT.md, SECURITY.md, CONTRIBUTING.md) are present and substantive in all orgs
- Avoid “marketing speak” entirely – this audience has zero tolerance for promotional language in technical contexts
Engagement metrics: Stars, forks, issues filed, pull requests submitted, contributor count.
Channel Strategy
Mastodon (Primary Social Channel)
Rationale: Mastodon’s decentralized architecture and community culture align with the organvm system’s values. The academic and creative technology communities are strongly represented on Mastodon. The platform’s chronological timeline (no algorithmic suppression) means that well-timed, high-quality posts reach followers reliably.
Posting strategy:
- Frequency: 3-5 posts per week during active periods; 1-2 per week during quiet periods.
- Content mix: 40% essay promotion and system updates, 30% process insights and building-in-public notes, 20% community engagement (replies, boosts of related work), 10% event announcements.
- Threading: Long-form announcements use threaded posts (3-7 posts per thread). Each post is self-contained enough to be meaningful if encountered out of sequence.
- Hashtag strategy: 2-3 hashtags per post from controlled vocabulary. Never more than 5. No hashtag-stuffing.
- Engagement: Reply to every genuine response. Boost related work from peers. Follow back accounts in target audience segments.
Performance benchmarks (Year 1):
- Follower count: 200+ by month 6, 500+ by month 12
- Average engagement per post: 5+ boosts, 10+ favorites
- Click-through rate to canonical URLs: 3-5%
Discord (Community Channel)
Rationale: Discord provides a persistent, structured community space for deeper engagement than social media allows. It serves as the real-time communication layer for ORGAN-VI (Koinonia) community events and as a distribution channel for system announcements.
Posting strategy:
- Frequency: Announcements as events occur (not scheduled – Discord audiences expect immediacy).
- Format: Rich embeds for all announcements (visually distinct from conversation, scannable metadata fields).
- Channel structure: Separate channels for announcements (one-way broadcast), releases (technical updates), community-events (interactive), and general (conversation).
- Moderation: Active but light-touch. Community health files set expectations; enforcement is rare and proportionate.
Performance benchmarks (Year 1):
- Server members: 50+ by month 6, 150+ by month 12
- Average reactions per announcement: 3+
- Community event attendance: 5-10 participants per event
GitHub (Portfolio Channel)
Rationale: GitHub is not traditionally considered a “distribution channel,” but for the organvm system’s target audiences (hiring managers, grant reviewers, open-source community), it is the primary discovery surface. Repository quality, documentation depth, and organizational structure are evaluated directly.
Strategy:
- Organization profiles serve as landing pages – each org profile README is a curated entry point.
- Repository READMEs are the primary content format – each is a portfolio piece written for expert audiences.
- Pinned repositories on the personal profile and org profiles highlight flagships.
- GitHub Discussions (if enabled) provide a lightweight community interaction layer.
- Release tags for significant milestones generate activity signals that appear in follower feeds.
Performance benchmarks (Year 1):
- Total stars across all repos: 50+ by month 6, 200+ by month 12
- Unique profile visitors: 100+ per month
- Contribution from external contributors: 1+ pull request per quarter
LinkedIn (Professional Visibility)
Rationale: LinkedIn serves the hiring manager audience segment and provides professional credibility signals. It is not a primary engagement channel but an important visibility layer during job searches and grant application periods.
Strategy:
- Frequency: 1-2 posts per week during active job search periods; 1-2 per month otherwise.
- Content: Professional framing of system milestones, essay re-publications with business context, architecture insights.
- Profile optimization: Bio references the organvm system. Featured section links to key repositories and essays.
RSS / Atom Feed (Subscriber Channel)
Rationale: RSS feeds serve the long-tail audience – people who prefer to subscribe once and receive updates without platform dependency. This aligns perfectly with POSSE principles.
Implementation: The ORGAN-V Jekyll site publishes an Atom feed at https://organvm-v-logos.github.io/public-process/feed.xml with all essays. The feed is the canonical subscription mechanism.
Content Calendar
Calendar Principles
The content calendar is driven by external rhythms, not internal cadences:
- Grant deadline alignment. Major grant deadlines (Knight Foundation: typically March; NEA: various; Mellon: rolling; NSF: program-specific) trigger increased visibility 2-4 weeks beforehand. The goal is that any grant reviewer who checks the system during review season finds recent, high-quality activity.
- Conference seasons. SIGGRAPH (July-August), Ars Electronica (September), ISEA (June), NeurIPS (December), and other relevant conferences create attention windows. Submissions, presentations, and related content are timed to these windows.
- Academic calendar. Reduced posting during exam periods and holidays (December, May) when academic audiences are less engaged. Increased posting at the start of semesters (September, January) when researchers are forming new interests.
- Exhibition and residency cycles. Art residency applications cluster in the fall (September-November); exhibition proposals cluster in winter-spring (January-April). Content relevant to these audiences is timed accordingly.
Monthly Calendar Template
| Week | Content Focus | Channels | Audience Priority |
|---|---|---|---|
| Week 1 | System update / progress report | Mastodon, Discord, LinkedIn | All segments |
| Week 2 | Essay publication or re-promotion | Mastodon, Discord, RSS | Academic, Creative Tech |
| Week 3 | Technical deep-dive / process insight | Mastodon, GitHub | Hiring Managers, Open Source |
| Week 4 | Community engagement / event promotion | Discord, Mastodon | Creative Tech, Community |
Quarterly Strategic Themes
- Q1 (Jan-Mar): Grant season. Emphasize organizational capacity, system metrics, and institutional maturity. Publish sustainability-themed essays.
- Q2 (Apr-Jun): Conference preparation. Emphasize technical depth and creative vision. Submit to ISEA, prepare SIGGRAPH materials.
- Q3 (Jul-Sep): Conference season. Maximum visibility. Share talks, presentations, and conference connections. Ars Electronica and SIGGRAPH content.
- Q4 (Oct-Dec): Residency applications and year-end review. Emphasize creative vision and collaboration potential. Publish retrospective content.
Growth Targets and Benchmarks
Year 1 Targets
| Metric | 3-Month | 6-Month | 12-Month |
|---|---|---|---|
| Mastodon followers | 75 | 200 | 500 |
| Discord members | 20 | 50 | 150 |
| GitHub stars (total) | 20 | 50 | 200 |
| Monthly unique visitors (Jekyll site) | 100 | 300 | 1,000 |
| RSS subscribers | 10 | 30 | 100 |
| Essay page views (monthly) | 200 | 500 | 2,000 |
| External contributions (PRs) | 0 | 1 | 5 |
| Grant applications submitted | 1 | 3 | 6 |
| Conference submissions | 0 | 2 | 4 |
Engagement Quality Metrics
Raw follower counts are vanity metrics. The system tracks engagement quality:
- Audience segment composition: What percentage of followers are in target segments (academic, creative tech, hiring, open source) vs. general/bot accounts?
- Engagement depth: Are people clicking through to canonical content, or only engaging with syndicated excerpts?
- Conversation rate: What percentage of engagement generates meaningful conversation (replies, discussions) vs. passive acknowledgment (favorites)?
- Return rate: What percentage of site visitors return within 30 days?
Competitive Landscape
Comparable Creative-Institutional Presences
Understanding how similar practitioners distribute their work informs the organvm strategy:
Hundred Rabbits (Devine Lu Linvega & Rekka Bellum): Prolific documentation, radical transparency about tools and process. Distribution through personal website, Mastodon, and niche forums. Lesson: extreme documentation depth builds devoted community without scale.
Julian Oliver: Institutional-grade project documentation, selective publication, conference-centric visibility. Lesson: quality over quantity works for artist-engineer hybrid profiles.
Nicky Case: Highly polished interactive essays that spread through educational and technology communities. Lesson: format innovation (interactive, exploratory) drives organic distribution.
Processing Foundation: Organizational infrastructure (governance, community programs, documentation) treated as primary output. Lesson: meta-system documentation attracts institutional recognition.
Differentiation
The organvm system differentiates through:
- Scale of coordination: 8 organizations, 67 repositories, 230K+ words. No comparable individual-operated creative system operates at this organizational scale.
- Governance transparency: Published governance rules, dependency models, quality gates. Most creative projects operate on implicit governance; explicit governance is a competitive advantage for institutional credibility.
- POSSE commitment: Most creative technologists are platform-dependent. POSSE ownership provides resilience and credibility.
Content Types and Formats
| Content Type | Word Count | Frequency | Primary Channel | Shelf Life |
|---|---|---|---|---|
| Meta-system essay | 3,000-5,000 | Monthly | Jekyll/RSS, Mastodon | Evergreen |
| Process note | 500-1,000 | Weekly | Mastodon | 6 months |
| Release announcement | 200-500 | As needed | Mastodon, Discord | 3 months |
| Architecture deep-dive | 2,000-3,000 | Quarterly | Jekyll, LinkedIn | Evergreen |
| Community event post | 200-400 | As needed | Discord, Mastodon | Ephemeral |
| System metrics update | 300-500 | Monthly | Mastodon, Discord | 3 months |
| Grant supplement | 1,000-2,000 | Per application | Direct | Application-specific |
Measurement Framework
Leading Indicators (Weekly)
- New followers across platforms
- Engagement rate per post (boosts + favorites + replies / impressions)
- Click-through rate to canonical URLs
- RSS feed subscriber count
Lagging Indicators (Quarterly)
- Grant application outcomes
- Interview invitations attributable to portfolio
- External contributor activity
- Conference acceptance rate
- Citation mentions in academic work
Health Indicators (Monthly)
- Audience segment composition (% in target segments)
- Content mix ratio (evergreen vs. ephemeral)
- Channel health (circuit breaker status, delivery reliability)
- Calendar adherence (% of planned content published on schedule)
Strategic Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Mastodon instance shutdown | Low | High | Maintain account on well-established instance; all content canonical on own site |
| Algorithm changes (LinkedIn) | Medium | Medium | LinkedIn is tertiary channel; no strategic dependency |
| Audience fatigue | Medium | Medium | Quality-over-quantity principle; respect audience attention |
| Platform lock-in | Low | High | POSSE architecture prevents dependency on any single platform |
| Grant reviewer unfamiliarity with system | Medium | High | Self-explanatory entry points (org profiles, essay abstracts); avoid jargon |
| Content stagnation | Medium | Medium | Calendar cadence ensures minimum publication rhythm; evergreen content provides backfill |
Templates and Resources
Template artifacts for recurring content types are maintained in announcement-templates. This repository provides the strategic context that informs template design:
- Audience profiles (this document) determine template tone and framing
- Channel specifications (this document) determine template format constraints
- Calendar cadences (this document) determine template scheduling metadata
- Growth targets (this document) inform template performance evaluation
Metrics and Tracking
All metrics defined in this strategy are collected by the social-automation analytics pipeline and reported to the ORGAN-IV orchestration hub. The feedback loop:
- Strategy defines targets and benchmarks (this repository)
- Templates encode the strategy into content formats (announcement-templates)
- Automation executes distribution and collects metrics (social-automation)
- Metrics inform strategy refinement (back to this repository)
This closed loop ensures that distribution strategy evolves based on evidence rather than assumption.
Cross-Organ Dependencies
| Dependency | Direction | Purpose |
|---|---|---|
| ORGAN-IV orchestration-start-here | VII consumes IV | Workflow infrastructure, registry data |
| ORGAN-V public-process | VII consumes V | Essay content for distribution, Jekyll site as canonical platform |
| ORGAN-VI community repos | VII consumes VI | Community event data for promotion |
| announcement-templates | VII internal | Template library implements strategy |
| social-automation | VII internal | Automation infrastructure executes strategy |
| All organs (I-VIII) | VII serves all | Distribution amplifies work from every organ |
Contributing
This is a strategy document. Contributions are welcome in several forms:
- Audience insight: If you are a member of one of the target audience segments, your feedback on what resonates (and what does not) is invaluable.
- Channel expertise: If you have deep experience with a distribution channel, your recommendations for strategy refinement are welcome.
- Metric analysis: If you have analytics expertise, help refining the measurement framework and interpreting results.
- Competitive intelligence: If you know of comparable creative-institutional presences not listed in the competitive landscape, please share.
See CONTRIBUTING.md for general contribution guidelines.
License
MIT License. See LICENSE for full text.
Author and Contact
4444J99 – @4444J99
Part of the organvm eight-organ creative-institutional system. ORGAN-VII (Kerygma) – Marketing, Distribution, and Audience Building.