dot-github--logos
Plain English TL;DR
ORGAN-V builds the public writing layer for the organvm project. It publishes essays about what the system is making, maintains tools that help draft and validate those essays, tracks lightweight readership signals, and keeps the editorial standards, reading lists, and GitHub profile that make the work easier to understand from the outside.
New here? The Quick Start guide tells you which repository to clone first and how to run it locally.
Want to talk back? Start with GitHub Discussions for questions, community reception, and open-ended feedback.
What Is ORGAN-V?
ORGAN-V is the public-facing process layer of the organvm system — an eight-organ creative-institutional architecture spanning theory, art, commerce, orchestration, community, marketing, and meta-governance.
Where other organs produce artifacts, ORGAN-V produces the account of how those artifacts came to be. It is the organ of narration, reflection, and methodological transparency. Its outputs are essays, process documentation, marginalia, and the ongoing public record of what it means to build a multi-organ creative system from first principles.
The name comes from the Greek λόγος (logos) — a word that resists clean translation. It means word, speech, reason, account, explanation, ratio, principle. That semantic breadth is deliberate. ORGAN-V is where the system explains itself — not as marketing copy (that belongs to ORGAN-VII), but as honest, substantive reflection on process, failure, and methodology.
Why Build in Public?
Most creative and technical work is presented as a finished product. The drafts, dead ends, architectural pivots, and reasoning chains that produced it are discarded or hidden. ORGAN-V inverts this default.
Building in public matters because:
- Process is product. The decisions behind a system are often more instructive than the system itself. A well-documented pivot teaches more than a polished landing page.
- Transparency invites accountability. Publishing methodology means it can be scrutinized, challenged, and improved by others.
- The gap between intent and execution is where learning lives. Essays that track that gap — honestly, in real time — create a record that has long-term value for both the author and the audience.
- Writing clarifies thinking. The act of articulating a decision forces precision that internal notes never demand. ORGAN-V essays are a forcing function for the entire system’s intellectual rigor.
This is not performative openness. ORGAN-V publishes because the process of building an eight-organ system across 81 repositories is itself a body of knowledge worth preserving.
Repositories
| Repository | Description | Status |
|---|---|---|
| public-process | Flagship essay series — 40 published essays (~130K words) on methodology, architecture, and building-in-public |  |
| essay-pipeline | Essay automation engine: monitor, narrator, validator, indexer |  |
| analytics-engine | Engagement tracking: GoatCounter integration, metrics aggregation, dashboards | |
| editorial-standards | Voice guide, quality rubrics, essay templates, frontmatter schema spec | |
| reading-observatory | Curated reading lists, bibliography management, RSS feed aggregation | |
| .github | Org profile and community health files | Infrastructure |
The public-process repository is the primary venue for ORGAN-V content. It houses 40 long-form essays (2,000-5,000 words each, ~130K words total), organized by category (meta-system, case study, retrospective, guide). Its Jekyll site with RSS is live at organvm.github.io/public-process. The four supporting repos provide autonomous essay pipeline automation (essay-pipeline), privacy-first engagement analytics (analytics-engine), editorial governance (editorial-standards), and curated intellectual context (reading-observatory).
Architecture Overview
The arrows below show dependency and information flow, not ownership. Read it left to right: the wider system creates work and standards, the Logos repositories turn that material into public narrative, and reception data loops back into the next editorial cycle.
flowchart LR
subgraph Sources["System sources"]
Meta["VIII / Meta<br/>directory, governance, standards"]
Theory["I / Theory<br/>frameworks and knowledge base"]
Art["II / Art<br/>artifacts and practice"]
Commerce["III / Commerce<br/>offers and delivery"]
Taxis["IV / Taxis<br/>orchestration signals"]
end
subgraph Logos["V / Logos repository map"]
GitHub[".github<br/>org profile and defaults"]
Standards["editorial-standards<br/>voice, schema, rubrics"]
Reading["reading-observatory<br/>sources and context"]
Pipeline["essay-pipeline<br/>detect, draft, validate, index"]
Public["public-process<br/>essays, RSS, Jekyll site"]
Analytics["analytics-engine<br/>privacy-first metrics"]
end
subgraph Reception["Reception and reuse"]
Readers["Readers<br/>GitHub, site, RSS"]
Community["VI / Community<br/>questions and reception"]
Kerygma["VII / Marketing<br/>campaign adaptation"]
end
Meta --> GitHub
Meta --> Standards
GitHub --> Standards
GitHub --> Reading
GitHub --> Pipeline
GitHub --> Public
GitHub --> Analytics
Theory --> Standards
Theory --> Reading
Theory --> Pipeline
Art --> Pipeline
Commerce --> Pipeline
Taxis --> Pipeline
Reading --> Pipeline
Standards --> Pipeline
Pipeline --> Public
Public --> Readers
Public --> Analytics
Public --> Community
Public --> Kerygma
Community --> Pipeline
Kerygma --> Analytics
Analytics --> Standards
Analytics --> Pipeline
Repository Hand-Offs
| Repository | Owns | Receives From | Hands Off To |
|---|---|---|---|
| .github | Organization profile, community-health defaults, issue/PR templates | Meta-governance standards | Every Logos repository and first-time contributors |
| editorial-standards | Voice guide, frontmatter schema, rubrics, templates | Meta standards, theory frameworks, analytics evidence | essay-pipeline, profile/README authors, essay contributors |
| reading-observatory | Bibliography, feed watch, external intellectual context | Theory/knowledge work, curated sources | essay-pipeline and public-process essay context |
| essay-pipeline | Detection, drafting, validation, indexing automation | System events, reading context, editorial standards, community questions | public-process publication queue |
| public-process | Published essays, RSS, Jekyll site | Validated drafts and editorial standards | Readers, community discussion, marketing reuse, analytics |
| analytics-engine | Privacy-first engagement metrics and profile/site evidence | public-process, campaign reuse, reader behavior |
editorial-standards and essay-pipeline improvements |
In practice:
- System organs create the work. Theory, art, commerce, and orchestration generate frameworks, artifacts, offers, and events worth documenting.
- Logos turns work into public account.
editorial-standardsdefines the quality bar,reading-observatorysupplies intellectual context, andessay-pipelinemoves material toward publication. public-processis the main publication surface. It hosts the essays, RSS feed, and Jekyll site that make the system legible outside the repos.- Feedback closes the loop.
analytics-engine, ORGAN-VI community reception, and ORGAN-VII campaign reuse feed evidence back into future editorial choices.
How ORGAN-V Fits the System
The organvm system distributes creative and institutional work across eight specialized organs — 81 repositories, ~320K words of documentation. ORGAN-V occupies a unique position: it is the organ that observes and narrates the work of all the others.
| Organ | Domain | Greek | Organization |
|---|---|---|---|
| I | Theory | theoria | organvm-i-theoria |
| II | Art | poiesis | organvm-ii-poiesis |
| III | Commerce | ergon | organvm-iii-ergon |
| IV | Orchestration | taxis | organvm-iv-taxis |
| V | Public Process | logos | organvm-v-logos |
| VI | Community | koinonia | organvm-vi-koinonia |
| VII | Marketing | kerygma | organvm-vii-kerygma |
| VIII | Meta | — | meta-organvm |
ORGAN-V draws on ORGAN-I (theory) for conceptual frameworks, works alongside ORGAN-VI (community) for audience engagement, and feeds ORGAN-VII (marketing) with narratives that can be adapted for distribution. But its primary dependency is the system itself: every organ generates the material that ORGAN-V reflects upon.
For a system-wide overview, see meta-organvm.
ORGAN V: Logos — 6 repositories, 40 essays, ~130K words — part of the eight-organ creative-institutional system — @4444j99 — LOGOS Sprint 2026-02-17