Intent

Why lzr/hypermake exists

Most content systems treat the final HTML as the primary artifact: dependencies stay implicit, rebuilds are coarse, and understanding why output appeared requires tribal knowledge. lzr/hypermake starts from a different premise.

Addressability everywhere

Every piece of content has a stable protocol address that works from the CLI, the graph, the Inspector, and templates.

src://components/component-bound.html

Incremental and safe by default

The system knows exactly what a change affects. Repeated work becomes a no-op; previews happen in isolated worktrees.

hypermake affected-by src/components/component-bound.html

Inspectable at every layer

Source maps, scope maps, tape ledgers, and data-read sets make the "why" visible instead of hidden in a black-box render.

cache://hypermake/lzr/tape-ledgers/rendered/public/components/component-bound.tape-ledger.json

AX over pure DX

The surfaces that make the system pleasant for developers — explicit dependencies, provenance, bounded mutations, plain output — are the same surfaces that make it tractable for agents.

hypermake agent-brief rendered/public/components/component-bound.html

Legible substrate

Recipes are path-local.make files; dynamic edges live in explicit.d manifests; the graph is the single source of ownership and impact.

src://rendered/public/{path}.html.make

Rendered output is an effect

The graph, tape, source, and data are the truth; the final HTML is a proof-carrying consequence, never the authority.

rendered://public/components/component-bound.html

What it is not

It is not	Because
A general-purpose framework for everyone.	It optimizes for content-heavy sites where source/data/output relationships must stay understandable over time.
Primarily a static site generator.	It can produce static output, but the graph, proofs, and inspectability are the product.
"Make plus some plugins."	The protocol model, fragment tape, proof-carrying rendering, and Inspector/AX layer are first-class.

Verify this yourself shell

hypermake status
hypermake explain rendered/public/docs/intent.html
hypermake affected-by src/docs/intent.html