Fast. Incremental. Inspectable.

Features built for addressable systems

Hypermake + LZR treat source files, data reads, rendered output, proof sidecars, and Inspector views as one explicit graph. The result is a site system that can explain what changed, why it changed, and where to inspect it.

Addressable fragments Explicit graph ownership Corpus-backed promotion AX-friendly packets

Protocol-native addressing

Everything important has a stable address that works in templates, CLI output, graph projections, and the Inspector.

src:// src://features.html Author the source in LZR.

data:// data://testing-scenarios.json Provide structured fixture data.

rendered:// rendered://public/features.html Final rendered artifact.

public:// public://_hypermake/testing/latest.json Graph-owned testing digest.

LZR templating

Semantic templates lower into addressable fragments, scope maps, sidecars, and edit contracts.

Components with expansion provenance
Expression and data-read lineage
Browser-like whitespace contracts

src://docs/lzr-templating.html

Incremental graph rebuilds

Hypermake owns recipes, dynamic dependency manifests, target state, and virtual prereqs.

Explainable freshness
No-op settled builds
Precise affected-by reporting

rendered://public/features.html

Source / data / rendered navigation

Move between source truth, structured data, rendered effects, and proof projections without guessing.

src:// source ownership
data:// and JSON pointers
rendered:// output effects

rendered://public/testing.html

Safe preview worktrees

Preview risky changes in isolated environments while keeping graph identity and inspector context intact.

Same content model
Different backend/worktree
Explicit promote/discard paths

hypermake branches list

Live inspector workflows

The Inspector is a live projection of graph, tape, source map, scope map, and data-read truth.

Source DOM editing
Scope and expression debugging
Timeline and diagnostics drill-in

/_hypermake/inspector/

Agent-aware packet workflows

AX packets give agents bounded, proof-carrying context instead of forcing them to scrape the project.

Plain CLI first
Structured JSON on demand
Proposal, not authority

concept://ax-packet

How a change flows through the system

One source or data edit moves through graph ownership, tape proofs, rendered effects, and Inspector projections.

1 Change source Edit LZR or data JSON. src://basics/text-and-attributes.html

2 Rebuild graph Only affected branches are planned. hypermake graph public

3 Update reads / proofs Data reads and source maps stay aligned. cache://hypermake/lzr/data-reads/rendered/public/basics/text-and-attributes.data-reads.json

4 Render output HTML is generated for the target. rendered://public/basics/text-and-attributes.html

5 Inspect or promote Preview, compare, and continue safely. /_hypermake/inspector/

Incremental by default Proof checked Inspector visible Agent-ready context

Live Inspector preview Sidecar-driven

Sourcesrc://components/component-bound.html

<set key="campaign" value="{{ data://campaign.json }}" />
	<scenario-layout
		title="Component-bound rendered effects"
		family="component invocation and prop lineage"
		source="src://components/component-bound.html"
		rendered="rendered://public/components/component-bound.html"
		coverage="component prop changes, source ownership, rendered-effect proof"
	></scenario-layout>
	<test-panel label="What this page tests" tone="blue">
		<p>Component invocation attributes, component-bound text, and data-backed rendered effects.</

Datadata://campaign.json

{
  "title": "Corpus Campaign",
  "client": "Corpus Client",
  "url": "/campaign.html",
  "adCount": 2,
  "newsletterCount": 1,
  "assets": [
    {
      "src": "/assets/banner.jpg",
      "alt": "Banner asset"
    },
    {
      "src": "/assets/newsletter.jpg",
      "alt": "Newsletter asset"
    }
  ],
  "variants": [
    {
      "id": "banner",
      "width": 300,
      "height": 250
    },
    {
      "id": "newsletter",
      "width": 640,
      "height": 480
    }
  ]
}

Scopecampaign

campaign

title"Corpus Campaign"

client"Corpus Client"

url"/campaign.html"

adCount 2

newsletterCount 1

assets [2 items]

variants [2 items]

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

<section class="card  campaign-header" data-panel="Campaign header"><h2>Campaign header</h2> <h1 id=campaign-title>Corpus Client Campaign</h1> <p class=scope-note>This page is intended to reproduce component/data-bound rendered-effect proof gaps.</p> </section>

Open the live scenario ->

Built different on purpose

Output is an effect. The graph and tape are the truth.

Hypermake + LZR does not ask the browser DOM to become the source of authority. Edits are planned against source/data truth, validated against map and proof state, then reflected into rendered output and Inspector surfaces.

Static-site generators

Usually page-level rebuilds with limited fragment provenance.

Hypermake + LZR

Addressed source/data/rendered graph with fragment tape proofs.

SPA tooling

Often hides ownership in browser state and runtime conventions.