levain 0.1.0

A portable cognitive-partnership memory + methodology kit. Ship the seed that grows a practice, not the practice.

Levain

A portable cognitive-partnership memory + methodology kit. You ship the seed that grows a practice, not the practice.

pip install levain
levain init

---

What this is

If you've been working with an AI partner long enough to feel the session-amnesia problem — every conversation starts over, every insight has to be re-explained, the quality of the partnership keeps resetting — Levain is the kit you'd otherwise build for yourself.

It packages four things that work together:

1. A four-layer memory substrate (episodic + continuity + Hebbian associations + limbic) via the anneal-memory library — your partner's hippocampus, neocortex, and lateral connections.
2. A methodology-core seed — a small set of files defining who the entity is, how partnership works, how memory accrues, who its operator is.
3. An activation mechanism — primacy-position posture + recency directives + session-boundary wrap discipline, wired through harness hooks.
4. A scripted onboarding interview — levain init walks you through filling the seed templates so the entity is uniquely yours from session one.

The kit installs into a Claude Code or Codex CLI workspace. Both harnesses are tier-1 supported at v1.

Why a seed, not a finished methodology

The load-bearing claim under the name levain (the sourdough starter you feed):

A grown cognitive-partnership methodology cannot be shipped as a methodology. Hand someone the artifact and they get a fossil — text describing practices that don't accrete in their substrate. Practice-encoded knowledge transfers through use, not specification.

So Levain ships the engine that grows a methodology: substrate + graduation mechanism + wrap discipline + reflection loop + minimal starting posture. Your own methodology accretes from your sessions. Which is why it sticks, and why it's yours.

A separate operator running Levain will not end up with this operator's continuity — different texture, different graduated patterns, different shape. That's the point.

Proof

See examples/accrual/growth_timeline.md — one continuity file rendered at four snapshots over five months. It started at 96 lines / 6 sections, locked into 9 sections around week 12, and has held that shape since while density grew inside it.

Your week 1 will look like the first snapshot. That's the right starting place — not the last snapshot, which is what this operator's partnership grew into. The trajectory is the proof; the endpoint is not the target.

Install

pip install levain
levain init

levain init runs the scripted interview, lays down the seed templates, registers the chosen adapter (Claude Code or Codex), and initializes the memory store at .levain/memory.db. One adapter per install at v1 — multi-adapter layering is a v1.1 candidate.

levain init --path /path/to/install [--adapter claude-code|codex] [--force]
levain doctor --path /path/to/install
levain verify-hooks --path /path/to/install

levain doctor is the loud in-environment health check — interpreter resolution, MCP server registration, store reachability, hook injection liveness.

levain verify-hooks actually invokes the activation hooks via stdin JSON and verifies they emit valid output. Closes the silent-skip class — particularly the Codex platform hook-reliability gap where the harness itself doesn't surface failures.

Audience

Operator-class developers — the ~5% who already sense session-amnesia is a real problem and would build their own fix. The ceiling isn't a crack; it's the shape of the correct audience.

If you've already built your own substrate-management scripts, you'll recognize the pieces. If "continuity file" and "wrap protocol" don't land, this isn't your tool yet.

What's in v1

• Methodology-core seed templates (harness-neutral, small, dense)
• Claude Code adapter (tier-1)
• Codex CLI adapter (tier-1)
• levain init / levain doctor / levain verify-hooks CLI
• Accrual demo showing the empirical growth trajectory

What's not in v1

• The framework (heartbeat, control pane) — a native flow-shaped framework is parked at v2, held off substitution-drift by one invariant: the human is the fan-in.
• The web-pane onboarding — the CLI interview is the only front-end at v1.0; the web pane absorbs into v1.1.
• Multi-adapter layering — one adapter per install at v1; two installs if you need both Claude Code and Codex.

Dependencies

Levain layers on anneal-memory — the four-layer memory library. Both ship to PyPI. Clean dependency direction: Levain depends on anneal-memory, never the reverse.

License

Apache 2.0. See LICENSE for full text and NOTICE for attribution.

The patent grant matters: as the kit accrues operator-class contributions, downstream operators are protected against future contributor patent ambush. The "second sourdough surface" — the activation layer that the operator edits — is the design intent. Apache 2.0 protects that surface.

---

Built inside the flow workspace; lives at levainhq.com.