Public Process

Creative technologists face a structural problem: finished work is visible, but the reasoning that produced it disappears. Portfolios showcase polished artifacts while erasing the decision chains, false starts, and architectural debates that constitute the actual practice.^[1] Sennett argues that craft knowledge resides not in the finished object but in the iterative dialogue between maker and material — a dialogue that traditional portfolios systematically suppress. The same asymmetry haunts open-source culture: code is public, but the reasoning behind the code remains private, locked in Slack threads and whiteboard photos that no reviewer will ever see.^[2] Kelty's ethnography of free software communities reveals that the "recursive public" — people who maintain the very infrastructure through which they communicate — depends on transparent process documentation as a condition of participation. ORGAN V (LogosGreek: word/reason — the organ of essays, public discourse, and transparent process) was created to solve this problem: a dedicated organ within the eight-organ system whose sole purpose is making the work of building visible, structured, and citable.

The collection comprises 49 published essays totaling approximately 740,000 words, deployed as a static Jekyll site on GitHub Pages. These are not blog posts in the conventional sense — each essay is a structured, long-form account of a specific phase, decision, or methodology within the eight-organ system.^[3] Schön Donald Schön, educational theorist who distinguished reflection-in-action (thinking while doing) from reflection-on-action (thinking after doing) 's concept of reflection-in-action The practice of thinking critically about what you are doing while you are doing it, adjusting approach in real time rather than only in retrospect describes practitioners who think about what they are doing while doing it, and the essays follow this model: they were written during the sprints they describe, not after. The temporal proximity between action and documentation means the essays capture uncertainty, provisional reasoning, and the texture of real-time problem-solving that retrospective accounts inevitably smooth over.^[4] Polanyi's insight that "we can know more than we can tell" is precisely the challenge: these essays attempt to make tacit architectural knowledge explicit by documenting it at the moment it is still active, before it becomes embedded and invisible.

A single essay must address multiple audiences without becoming incoherent, and the collection was designed with explicit audience models from the start.^[5] Bakhtin's concept of heteroglossia — the coexistence of multiple voices and social registers within a single utterance — informs the writing strategy: each essay carries technical specificity for practitioners, evidential weight for grant reviewers, communicative clarity for hiring managers, and theoretical grounding for academics. This is not an accident of style but a deliberate rhetorical architecture. The essays are structured so that different readers can extract different value from the same text: a grant reviewer reads the metrics and timeline evidence, a hiring manager reads the communication skill and system-design thinking, a practitioner reads the tooling decisions and honest post-mortems, and an academic reads the epistemological commitments and citational apparatus.^[6] Bazerman's genre theory demonstrates that written forms are not neutral containers but active shapers of knowledge — the essay format itself signals sustained intellectual engagement in ways that tweet threads and README files cannot.

The publication infrastructure follows a deliberate pipeline: source material enters as Markdown files in a Git repository, passes through Jekyll's Kramdown processor, and exits as static HTML served from GitHub's CDN. The pipeline includes three automated layers beyond basic rendering. First, jekyll-feed generates an Atom XML feed A standardized syndication format that lets readers and automation tools subscribe to content updates without polling the website at /atom.xml enabling machine-readable syndication — any RSS reader or automation tool can subscribe to new essays without polling the HTML. Second, jekyll-seo-tag injects structured metadata (Open Graph, Twitter Cards, JSON-LD) into each essay's <head>, ensuring that when essays are shared on social platforms or indexed by search engines, the preview includes the title, abstract, and canonical URL rather than generic page text. Third, the YAML front matter encodes audience routing metadata that downstream tools can consume — the audiences array enables programmatic filtering for different distribution channels.^[11] Berners-Lee's principle that the web's value comes from machine-readable structure, not just human-readable presentation, applies directly: the YAML front matter transforms each essay from a document into a data object that automated systems can route, filter, and aggregate.

The essays form a citation graph A directed network where nodes are documents and edges represent references between them, revealing the structure of intellectual dependency , not a flat list. Architectural essays reference sprint narratives for evidence of principles in practice; sprint narratives reference methodology essays for the frameworks that guided execution; reflective essays reference all three categories to examine what the frameworks predicted versus what actually happened. This cross-referencing is not decorative — it is the mechanism by which the collection demonstrates coherence rather than merely asserting it.^[7] Latour's actor-network theory reveals that claims gain authority from the density of the network supporting them. A single essay making claims about system architecture is an opinion; the same essay cross-referenced by sprint narratives with timestamped evidence, methodology essays with theoretical grounding, and reflective essays with honest failure analysis is a knowledge structure. The cross-reference density is itself evidence of the practice's integrity.

The critical distinction that separates this collection from conventional project documentation is its commitment to evidence over persuasion. Every essay contains timestamped decisions, concrete metrics, and honest acknowledgments of failure — not because transparency is morally superior, but because verifiable claims are more useful to every audience than polished narratives.^[7] Latour's actor-network theory reveals that scientific facts gain their authority not from correspondence with reality but from the density of the network that supports them — citations, instruments, institutions, replications. The essays apply this principle to creative practice: each claim about the system (116 repositories, 740K words, 2000 automated tests) is backed by traceable evidence in the registryA centralized, queryable data store that serves as the single source of truth for all entities and their relationships in a system, the CI logs, and the commit history. The methodology is exposed, not hidden.^[8] Kuhn's observation that paradigm shifts require making previously invisible assumptions visible applies here at the individual level: the essays make visible the assumptions, constraints, and tradeoffs that conventional portfolios treat as backstage work.

The reflective essays in the collection are not afterthoughts appended to the sprint narratives — they are a structural requirement enforced by the organ's governance rules. Every major sprint must produce both a narrative account and a separate reflective practice A disciplined habit of examining one's own decisions and assumptions after action, transforming experience into transferable knowledge essay that examines what went wrong, what was surprising, and what the practitioner would change with the benefit of hindsight.^[3] Schön distinguishes between "reflection-in-actionThe practice of thinking critically about what you are doing while you are doing it, adjusting approach in real time rather than only in retrospect" (thinking while doing) and "reflection-on-action" (thinking after doing) — the sprint narratives capture the former, and the reflective essays capture the latter, creating a layered documentation practice that addresses different temporal perspectives on the same events. This dual-mode documentation is unusual in both academic and industry contexts, where reflection tends to be either absent entirely or confined to post-project retrospectives that have lost access to the granular decision context.^[4] The goal is to counteract what Polanyi identifies as the inevitable loss of tacit knowledge once a practice becomes routine — by writing the reflective essay while the surprise is still fresh, the collection preserves knowledge that would otherwise become invisible.

The most significant claim this project makes is that building in public A practice of documenting and sharing the process of creating software or creative work as it happens, rather than only showing finished results can be a rigorous, structured methodology rather than a casual social media practice. The dominant model of "building in publicA practice of documenting and sharing the process of creating software or creative work as it happens, rather than only showing finished results" is the tweet thread: fragmentary, performative, optimized for engagement rather than evidence.^[9] Eghbal observes that open-source maintainers face a tension between community engagement and deep work — the tweet-thread model of building in publicA practice of documenting and sharing the process of creating software or creative work as it happens, rather than only showing finished results exacerbates this tension by demanding constant performance. The ORGAN-V model offers an alternative: structured, long-form documentation written on a deliberate cadence, published to infrastructure you own, and designed to serve multiple audiences simultaneously. This is reusable. Any practitioner or organization could adopt the same model — dedicated documentation practice, explicit audience models, YAML-structured metadata, static-site publication, POSSEPublish on your Own Site, Syndicate Elsewhere -- an IndieWeb principle where canonical content lives on infrastructure you control and copies flow outward distribution — without adopting the eight-organ system itself.^[10] The methodology is separable from the content, and that separability is what makes it a genuine contribution rather than a personal idiosyncrasy.