Skip to content

Doctrine identity & the soma/dendrite model

Doctrine identity & the soma/dendrite model

How the general doctrine of the Industrial Nonprofit understands itself — distinct from the category’s definition, which this page assumes. Where that page answers “what is an Industrial Nonprofit?”, this one answers “what is the doctrine, and how does it grow without corrupting the instance it generalizes from?”

Contents

What the doctrine is

The general doctrine names the form that one specific building is an instance of. Its conviction is the category’s core (see the definition page): the quality that makes an institution last and the ownership that keeps it honest are one decision at two scales — materials and governance. The doctrine exists to make that form nameable, because an unnamed thing cannot be funded, permitted, taught, or repeated. Naming it is the work.

Why a separate home

The generalizable form does not belong inside the planning record of any single building. Kept together, both corrupt: the instance leaks into the doctrine, and the doctrine dilutes the instance. So the specific must stay specific and the general must stay free to branch — two records, one boundary between them.

The soma/dendrite model

The organizing metaphor for how general doctrine relates to a specific instance:

MetaphorMeaning
Somathe single, specific, irreplaceable instance (the cell body) — e.g. 601 Delaware
Dendritethis doctrine — it reaches the idea outward without creating a second soma
Arborizationgrowth = branching (more reach, more connection), not photocopying
Worked examplea specific instance carried beside every general claim as proof, cited by link

The direction of flow is fixed: specific → general by abstraction, never general → specific by templating. New instances are new dendrites — each linked, none reproduced. The goal is recognition of the form, not replication of an instance.

Operational invariants

  • The category is defined by two simultaneous constraints (industrial scale and community ownership), held together always — never by tax status alone.
  • No exit and a multi-generation horizon are part of the definition, not optional governance flavor.
  • The instance is cited by link, never copied into the doctrine.
  • Content flows specific → general by abstraction.
  • The friction in the name is preserved — the category is never quietly reassigned to a familiar slot.

Drift guards (theory violations)

Changes that “work” but conceptually corrupt the doctrine:

  • Importing instance-specific doctrine — link instead.
  • Defining by tax status alone — drops the industrial half, dissolves the category.
  • Producing a franchise / replication kit — betrays “recognition, not replication.”
  • Resolving the name’s friction — destroys its most useful property.
  • Softening a constraint — drifting “industrial” toward “cultural center,” or treating “no exit” as negotiable, collapses into a failure mode.
  • Doctrine without a worked example — general claims floating free of any real, linked instance.
  • Copy-paste between sibling repos — any direction. Abstraction in, links out.

Signals of health

  • Every general claim is traceable to a worked example by link, not copy.
  • The name still makes people pause and resolve it.
  • New instances arrive as dendrites — linked, distinct, never reproduced.
  • The two constraints stay coupled; no page argues for one without the other.
  • Instance-specific material stays out without enforcement.
  • The doctrine stays usable by all three audiences at once — builder, funder, culture.

See also