# Lineage

How CNOS and Triadic Self-Coherence relate to prior people, ideas, and systems.

| | |
|---|---|
| **Version** | 3.14.0 |
| **Status** | Converged |
| **Doc-Class** | reference |
| **Canonical-Path** | docs/beta/lineage/LINEAGE.md |
| **Owns** | structural debts, direct catalysts, conceptual lineage, substrate precursors, documentation and workflow influences |
| **Does-Not-Own** | endorsements, biography, personal gratitude, project history |

---

## Purpose

This document records the structural lineage behind CNOS and Triadic Self-Coherence. It is a dependency map, not a prestige wall. Entries are grouped by kind of influence, not by importance or chronology. A name belongs here only if the person or system changed one of the following:

- the formalism
- the architecture
- the substrate choice
- the documentation discipline
- the workflow discipline

---

## Non-Claims

This document does not claim that the people named here endorse CNOS, agree with it, or participated in its implementation. It names debts, not affiliations.

---

## Direct Catalysts

### Joscha Bach

Applied rigor pressure to claims about truth, love, and agency.

Type: catalyst.

### David Lattimore Gay

Pushed architectural rigor and translation of abstraction into executable design.

Type: mentor.

### Evgeny Perevalov

Made the Whole a live problem rather than a decorative philosophical term.

Type: initiating pressure.

---

## Conceptual Lineage

### Karl Friston

Self-organisation, free energy, and active inference as pressure toward systemic integrity.

Type: systems-theoretic influence.

### David Bohm

Dialogue, implicate order, and preservation of concurrent articulation.

Type: process and dialogue influence.

### Michael Levin

Agency across scales, collective intelligence, and permeable boundaries.

Type: agential systems influence.

### Riccardo Manzotti

Object-mind identity and pressure against representational shortcuts.

Type: ontological influence.

---

## Substrate and Open Systems Lineage

### Linus Torvalds

Git object model, distributed history, merges, and content-addressed state.

Type: substrate precursor.

### Richard Stallman

Software freedom as a substrate requirement rather than a licensing ornament.

Type: freedom boundary.

### Eric S. Raymond

Bazaar-style open collaboration and public-by-default development.

Type: open development influence.

---

## Documentation and Workflow Lineage

### Naomi Gleit

Canonical documents and single-source project orientation.

Type: documentation governance.

### Seb Holington

Pushed for formal whitepapers and explicit articulation instead of leaving the system implicit.

Type: documentation discipline.

### David Allen

Externalized workflow, trusted capture, and regular review.

Type: workflow influence.

---

## Scope Boundary

If a contribution was primarily emotional, logistical, editorial, or personal, it does not belong in this document unless it directly changed the structure of CNOS or TSC. Those debts may be named elsewhere.
