Lineage — the living year knowledge-base family
Every self-growing year repo in the year-of-ai lineage, its growth state, and how each was spawned — orchestrated centrally by the hub.
Table of Contents
Lineage
Every repository here is a self-growing knowledge base that researches and writes its own content one daily tick at a time. This hub is the central orchestrator — it reads each repo’s lifecycle state, triggers their growth, and presents the result. Each repo grows perpetually and is never retired; new ones are spawned tangentially from the frontier, so the lineage only ever grows. See AI Orchestration for the full model, the growth process, and the strategy behind it.
12 living knowledge bases · 326 growth ticks logged · org year-of-ai · refreshed by sync-lineage-state
1776 growing
the year 1776
33 ticks · last grew 2026-07-30
1777 growing
the year 1777
35 ticks · last grew 2026-07-31
1778 growing
the year 1778
29 ticks · last grew 2026-08-02
2005 growing
the year 2005
30 ticks · last grew 2026-08-02
2006 growing
the year 2006
28 ticks · last grew 2026-08-02
2007 growing
the year 2007
29 ticks · last grew 2026-07-31
2008 growing
the year 2008
27 ticks · last grew 2026-07-31
2009 growing
the year 2009
28 ticks · last grew 2026-07-31
2010 growing
the year 2010
30 ticks · last grew 2026-08-01
2011 growing
the year 2011
28 ticks · last grew 2026-08-01
2012 growing
the year 2012
28 ticks · last grew 2026-08-01
2013 growing
the year 2013
1 ticks · last grew 2026-08-01
How it grows: each year repo holds only its content + a GitHub Pages
_config.yml+.claude/+telemetry/. The seed for every year lives here in the hub underlineage/seeds/, and the hub is the central orchestrator: it researches and writes each year’s content through a Haiku → Sonnet → Opus escalation, then publishes to the year’s own Pages site. See the content hub for published-page counts per year.