Decision 0007 establishes a derivation order for the endeavor philosophy: work through the source domains from most foundational to most accessible (TCCC → insurgent → disaster → western military → medicine → FOSS → business), then present in roughly the reverse order. This text traces what each domain contributes to the theory as written in semiotic-endeavor v0.7.0, making the derivation chain explicit.
The spec itself is written in its own vocabulary — neutral, formal, self-standing (per content neutrality). This text is the companion that says where the ideas came from.
The derivation chain
1. Relationality and semiotics (prior to the chain)
The formal foundation — Heyting algebras, closure operators, the j/G interaction, the semiotic hierarchy — precedes the domain chain. These provide the mathematical vocabulary: closure pressure, fixed points, flow-nucleus compatibility, ComonadCurvature. The domains below provide the empirical content that the mathematics formalizes.
2. TCCC (Tactical Combat Casualty Care)
TCCC contributes three concepts to the endeavor theory:
Context-determined practice. TCCC makes the tactical situation part of the clinical problem. The same injury is a different problem under fire vs. in a field hospital vs. during evacuation. The endeavor theory’s insistence that practice is situated (not abstract) and that method must be context-responsive comes from this: the environment determines what is admissible, not the protocol alone. In the spec, this appears as the temporal constraint concept (temporality §4) and the method-practice gap diagnostic.
Attention allocation under degradation. MARCH/PAWS locks teams to a priority sequence when cognitive load is highest. This is the empirical source for the spec’s appetite-bounded cycles and the claim that time in an endeavor is iteration-time, not clock-time. When resources are scarce, you iterate through priorities, not through a calendar.
Layered scope as safety boundary. TCCC layers scope: self-aid, buddy-aid, trained responder, medical personnel, evacuation team. Each layer has a bounded scope — overreach harms the patient and the team. The spec’s region declarations and the non-interference theorem formalize this: safe multi-agent coordination comes from bounded scope, not from communication between unbounded agents.
3. Insurgent military practice
Insurgent and anarchist organizing contribute:
Informal organization as anti-capture. Affinity groups (3–15 people, mutual trust, no membership list, no constitution) resist both external repression and internal bureaucratization. The endeavor theory’s anarchic governance (no project manager, no authority chain) inherits from this: formal organizations develop self-preservation instincts that compete with stated aims. The spec avoids this by making governance emerge from closure pressure rather than from institutional position.
Theory-practice unity. Insurrectionary praxis treats action as the site where analysis is produced, not the implementation of pre-existing analysis. The endeavor theory’s claim that purpose is immanent — found from within, not declared from outside — inherits from this: you discover what the endeavor is for by doing the work, not by writing a mission statement.
Federation without subordination. Spokescouncils coordinate autonomous groups through delegates with specific mandates. The spec’s multi-agent coordination section formalizes this: agents coordinate through shared method (the specification family) rather than through hierarchy. Each agent reads the same specs and follows the same policies; their work composes without direct agent-to-agent communication, like affinity groups coordinating through shared analysis rather than through a command structure.
4. Emergent disaster response
Disaster sociology contributes:
Observational priority. Emergent disaster response starts from what affected people actually do, not from institutional categories. Emergent citizen groups arise around new tasks that existing organizations fail to handle. The spec’s practice-before-method direction inherits from this: when the world presents a situation that method doesn’t cover, the first response is to observe what practice is doing, then codify it — not to impose method from above.
Elite panic as diagnostic. Officials often respond to survivor self-organization with fear and suppression rather than recognition. The spec’s reification-by-noun warning (in the endeavor identity section) inherits from this: naming something an organization does not make it one; binding commitments do. An endeavor that claims to be an organization without having method, governance, or closure conditions is performing the same reification that platforms perform when they confuse a Discord server with a political organization.
Sustained coordination without institution. COVID-19 mutual aid showed that emergent coordination can persist across prolonged crises — not just acute events. The spec’s claim that an endeavor persists through dormancy and resumes (lifecycle phases) inherits from this: sustained effort does not require continuous institutional support, only continuity of repository, method, closure conditions, and governance.
5. Western military practice
Military command contributes:
Campaigns as time-binding. A campaign sequences many local actions into a coherent strategic effect. The recurring failure mode is cumulative drift — plans unchanged while situations shift. The spec’s method evolution section (what drives change, what constrains it) inherits from this: the endeavor must ask what must become true first for later actions to matter, what must be sustained for the sequence to continue, and which assumptions collapse the whole logic.
Mission command as delegation. Commander’s intent allows subordinates to act without paralysis. The spec’s governance model inherits this: emsenn provides intent (goals, policies, decisions); agents exercise initiative to accomplish the work. The method (specs, skills, policies) is the standing intent that enables autonomous agent operation.
Doctrine as shared language. Doctrine reduces coordination costs by providing agreed-upon vocabulary. The spec’s insistence on the specification family (every convention traceable to a named spec) is the same move: shared method replaces per-interaction negotiation.
Staff work as shared picture. Staffs turn ambiguous situations into operational pictures. The assessment skill, review-plans skill, and situational assessment are the endeavor’s equivalent: they produce a shared picture of what the situation is, so that leverage analysis can select the next action.
6. Western medicine (beyond TCCC)
Medical practice contributes:
Reflective practice cycles. FOAM (Free Open-Access Medicine) operates with explicit update rhythms: weekly capture, monthly review, guideline retirement. The spec’s temporal structure (cycles with cool-down periods, retrospectives at cycle boundaries) inherits this rhythmic updating. Knowledge has a freshness constraint — it can become stale if not actively maintained.
Evidence-gated transitions. Clinical practice advances through evidence levels, not authority. The spec’s plan lifecycle (draft → proposed → accepted → active → completed) with evidence gates at each transition inherits this: a plan advances when evidence supports it, not when someone with authority decides.
7. FOSS (Free/Open Source Software)
FOSS contributes:
Architecture Decision Records. ADRs create an immutable, append-only decision log. When circumstances change, teams write new ADRs that supersede old ones rather than editing the original. The spec’s decision records and policy 005 (accrete, don’t replace) directly inherit from this practice.
RFC processes. Written proposals, structured review, and defined decision-makers separate design-phase reasoning from implementation. The spec’s plan lifecycle mirrors this: plans are proposed, reviewed, accepted, then executed.
Contributor coordination through format. Open-source projects coordinate hundreds of contributors through shared formats (pull request templates, commit conventions, CI checks). The spec’s semiotic-markdown and shared carrier declarations formalize the same insight: coordinate through format, not through meetings.
8. Business practice
Business contributes the least to the derivation but the most to the presentation vocabulary. Terms like “backlog,” “sprint,” “retrospective,” “stakeholder” are accessible because they are familiar. The spec reinterprets them:
- Backlog = computable semantic gap (not curated list)
- Goal = closure condition (not aspiration)
- Milestone = named closure state (not calendar date)
- Retrospective = categorical review (not process improvement)
- WIP limit = concurrency bound on closure (not arbitrary number)
These reinterpretations are documented in the semiotic-project- management spec’s comparison table.
The derivation-presentation dual
Decision 0007 identifies this as another instance of the structuration-interface dual:
-
Derivation is internal structuration: how the philosophy organizes itself, from the most empirically grounded sources. TCCC and insurgent practice have the deepest grounding in coordination under uncertainty without guaranteed hierarchy.
-
Presentation is external interface: how the philosophy meets the reader, using vocabulary they already have. Business and FOSS vocabulary is familiar; military and medical vocabulary is not.
The dual inverts the ordering. The spec is written in formal vocabulary (closure operators, fixed points, method-practice gaps) that is neutral to all domains. This text traces the derivation chain that produced that vocabulary. The published site, when it exists, will present in the reversed order — leading with familiar concepts and progressively revealing the deeper sources.
What has been integrated (v0.8.0)
Three domain concepts identified in the initial derivation have been integrated into semiotic-endeavor v0.8.0:
-
Constraint-forcing epistemology — INTEGRATED. New “Method validation” subsection in Method evolution. Distinguishes greenfield validation (internal consistency) from constraint-forcing validation (testing against resistant reality). Maps to the draft → candidate lifecycle transition. Grounded in the constraint-forcing demonstrations text and platform invariants analysis.
-
Intelligence cycle as recursive process — INTEGRATED. New “Recursive process structure” subsection in Temporality. Makes explicit the structural parallel between the intelligence cycle (direction → collection → processing → analysis → dissemination) and the encoding loop (inputs → texts → terms → research → skills). Both are recursive processes that converge toward closure.
-
Trust as coordination medium — INTEGRATED. New “Trust as coordination precondition” subsection in Multi-agent coordination, plus new term file at terms/trust.md. Trust is the interpersonal precondition that makes method-based coordination viable rather than a compliance regime. Grounded in affinity group research, disaster response, and counterinsurgency analysis of trust destruction as organizational attack.
What is not yet integrated
Two domain concepts remain as candidates for future enrichment:
-
Organic intellectuals: disaster response and insurgent practice show that people embedded in struggle produce theoretical coherence from experience. The spec’s “purpose is immanent” claim gestures at this but doesn’t cite the sociological grounding (Gramsci, Freire, Hampton). This would enrich the closure conditions section’s account of how purpose is discovered.
-
Long-haul coordination: COVID-19 mutual aid shows that emergent coordination can be sustained for years, not just weeks. The spec’s lifecycle phases could be enriched with this evidence, particularly the dormancy-to-active-conduct transition and the conditions under which emergent coordination persists without institutional support.
These gaps are candidates for future enrichment as the spec matures toward candidate stability.
Practice derivation: MUD heritage
The domain derivation chain above operates at the level of
organizational theory — what an endeavor IS. A separate derivation
axis operates at the level of implementation practice — how an
endeavor’s tools WORK. This axis draws primarily from MUDs,
especially LPMUDs and their descendants. See the companion text
mud-heritage-as-practice-derivation.md for the full treatment.
Key contributions from the MUD tradition:
- Driver/mudlib separation: infrastructure (scripts, MCP server) provides a standard interaction surface; content (specs, skills, terms) builds on that surface
- World-building as programming: content is code, code is content — the same convergence the semiotic framework formalizes
- Object inheritance: the type system (term, concept, text, etc.) works like mudlib base classes
- Permission models: region declarations parallel LPC sandboxing
This is another instance of the derivation-presentation dual: the practice derives from MUD architecture internally, but presents in modern software engineering vocabulary externally.