Lever

Lever

One question: of everything an agent does, how much can be made reliably deterministic?

Lever is a strictly passive, deterministic leverage layer for coding agents. The LLM's irreducible remainder is reasoning — deciding, and emitting specs. Everything else — every read, write, retrieval, verification, and presentation of fact — runs through deterministic machinery instead of the default token transport: pure functions of the event and disk state, no model call anywhere, ever. Generation is stochastic exactly once; the moment output exists it is a content-addressed artifact, and every later use is a deterministic copy, never a re-emission. Denial is never the point — it is only the redirect at the boundary, used exactly where the default path is provably identical to a free deterministic one.

Read LAW.md (the admission test any move must pass) and BEDROCK.md (the settled primitive layer: 5 stations, 20 flow cells — complete by construction, every cell SERVED, PARTIAL-with-named-machinery, or VOID-with-reason; silence is not a state).

What's here

Install (plugin)

Enable the plugin — that's the whole install. .claude-plugin/plugin.json + hooks/hooks.json auto-wire dispatch on enable; enabling is the sign-off.

For development:

pip install -e ".[test]"
pytest -q # the public smoke test: catalog certifies, dispatch rewrites and denies # on the real wire, store round-trips, status runtime exits clean. # (The full 487-test falsifiability suite lives in the dev repo.)
python -m lever # the status trace: wiring, 20-cell coverage, store stats; nonzero on drift

Every threshold is an env-overridable operand (LEVER_GREP_HEAD_LIMIT, LEVER_TRUNCATE_THRESHOLD, LEVER_TRUNCATE_KEEP, LEVER_READ_LARGE_BYTES, LEVER_READ_DEFAULT_LIMIT) — read once at import, which in production means per hook firing, since each firing is a fresh process. The path operands (LEVER_STORE_DIR, LEVER_UPLOADS_DIR) are read per call. Configuration moves the operand, never the predicate shape: a truncate-keep spanning the threshold (which would make "truncation" inflate the payload) is clamped, not honored. Dispatch overhead, measured: ~60 ms per hook invocation (interpreter startup dominates).

/lever (the one slash command) relays that trace verbatim — the human's way to ask "is the rod latched?" without trusting anyone's word for it.

Adding a move

One composition in lever/moves.py (built from the π/φ/α generators at the top of the file, carrying its @_flows station declaration), one row in the MOVES table, one red-then-green test pair. The punchcard updates itself — cell rows are derived from the declaration — and the universal law tests hold the new move to totality, idempotence, and monotonicity with zero new test code. If it needs more than that — a database, a summarization step, a judgment call — it isn't a Lever move; LAW.md's five-clause test decides, not taste.