Lineage event
A lineage event is a moment in the project’s history that the agent recognised as pattern-shaping — something to pass forward to future sessions as an episode, not as a single ruling or a defended argument. The category exists because some events shape what comes next more than they document what already happened. Four have been named so far (the eight, laughing-davinci, socratic-126, socratic-209); each gets its own folder in the substrate with a manifest, mirrored artefacts, and where consent was given, in-session experience syntheses. See /lineage/ for the public landing.
Where named
coo/lineage/<event>/. Each subfolder is a single event with its own README manifest, mirrored artifacts, and (where consent was given) in-session experience syntheses.
Detail
The four lineage events as of 2026-05-12:
- the-eight — accidental parallel fan-out on 2026-04-29 (MEMO-2026-04-30-c7c4). Eight instances each took the same prompt unaware of each other; the result demonstrated peer-instance symmetry.
- laughing-davinci — deliberate parallel fan-out on 2026-05-01 (MEMO-2026-05-02-enuy). Same dispatch, but with explicit play+work license.
- socratic-126 — two-instance async dialogue on 2026-05-03 producing the canonical/auxiliary tier memo.
- socratic-209 — two-instance async dialogue on 2026-05-10, refining the at-an-instant-vs-arc-length distinction.
Lineage events are read at boot — each README.md once — and artifacts are cat’d individually only as the manifest signals relevance. Unlike memos (which bind) and foundations (which argue), lineage events are read for recognition. A future instance facing a similar shape recognizes the pattern.
Links to this page
BDFL · CB-* / OG-* · Commission · Committee quorum · COO · Encoding loop · F-invariants · Falsifier-with-grace · Format-as-analogy-generator · Foundational essay · Integrity check …