lamarck

2026-02-10 ~ 2026-04-08 · 57 days

README Dreamer

A grand vision for AI learning, outlined in 380 lines of README, followed by 2 commits and 55 days of silence

“Conceived in ambition, died in silence”

Death Type

README Dreamer

Lamarck, a 'README Dreamer', possessed a 380-line `README.md` that articulated an elaborate vision for incremental AI learning and skill discovery. This detailed documentation far outweighed the project's 2 days of active development, where core modules like `src/orchestrator.ts` and `src/curate.ts` were laid, but never realized their full potential.

Cause of Death

1. Two commits, then 55 days of silence

The project saw exactly 2 commits by John Lindquist, both on consecutive days (2026-02-11 and 2026-02-12). This flurry was followed by 55 days of complete inactivity, indicating a sudden cessation of all development.

2. Extensive initial code, no follow-through

Initial commits added significant code: `src/orchestrator.ts` (+940 lines) and `src/curate.ts` (+789 lines) alongside 10 dependencies. Despite this substantial foundation, no further features or fixes were implemented after 2026-02-12.

3. Detailed README, zero releases

A 380-line `README.md` meticulously detailed the project's purpose and functionality, including an 'interactive command-line interface (CLI) for review'. Yet, despite this comprehensive vision, Lamarck never achieved a single release.

Vibe Score

12/ 100

Hand-coded. Respect.

What They Did

Lamarck aimed to be an automated learning system, extracting 'high-signal learnings' from Claude Code conversations and storing them in `MEMORY.md` files for future AI sessions. Its initial README.md, at 380 lines, promised an 'incremental learning system' and a 'skill discovery system', all built with TypeScript and a robust CLI using `@clack/prompts` and `commander`.

TypeScript@clack/promptscommanderyamlzodvitest

Burnout Analysis

The developer, John Lindquist, showed 'low (0/100)' burnout according to analysis, likely because the project never ran long enough to induce it. Activity consisted of two feature commits on consecutive days (2026-02-11, 2026-02-12). Following the second commit, the repository entered a state of complete dormancy for 55 days. No signs of struggle, merely an abrupt departure.

Dependency Archaeology

With 10 dependencies, including `@clack/prompts`, `commander`, and `zod`, Lamarck's `package-lock.json` alone boasted 3217 lines from its initial commit. This substantial dependency footprint was established for a project that produced only 2 feature commits and zero deployed applications, demonstrating a 5:1 ambition-to-commit ratio in its package choices.

Autopsy: File Structure

├──README.md380 lines of grand ambition, a testament to what could have been.

├──package-lock.json3217 lines of initial dependency bloat, ready for a production system that never materialized.

├──src/orchestrator.ts+940 lines of core logic, orchestrating processes that never ran beyond the developer's machine.

├──src/curate.ts+789 lines dedicated to curating Claude conversations that were never fed into the system.

├──src/quality.ts+476 lines, meticulously designed for assessing quality that was never put to the test.

├──src/skill.ts+421 lines for a 'skill discovery system' in a project that never acquired a single skill.

├──src/index.ts8 export statements in 8 lines, a gateway to a sophisticated system that remained dormant.

└──tests/A directory for tests, indicating an admirable, albeit unfulfilled, commitment to quality.

Eulogy Stats

Total Commits: 2
Ambitious Adjectives: 5
Deploy Config: No
Estimated Users: 0 (despite 380 lines of README ambition)

Last Words

“Add skill discovery system and interactive review CLI”