Protocols, graph, tape, Inspector
Hypermake and LZR are arranged around one graph of truth. Source templates and data documents are authoritative; rendered HTML, Inspector panels, testing digests, and agent packets are projections with explicit provenance.
One graph, four surfaces
The same graph state feeds the product site, docs, corpus, Inspector, and AX packets.
Protocols
Stable addresses make source, data, rendered output, graph targets, tape fragments, and packets navigable.
src://docs/protocols.html Graph ownership
Recipes and dynamic dependency manifests decide what is fresh and what must rebuild.
src://rendered/public/{path}.html.make Fragment tape
LZR lowers templates into static runs, dynamic tokens, control markers, component frames, and proof sidecars.
tape://rendered/public/index.html Inspector + AX
The WebExtension and agents consume projections from the same graph, not separate interpretations.
concept://ax-packet Ownership model
What owns what
Rendered HTML is useful, but it is not the authority boundary.
| Surface | Owns | Does not own |
|---|---|---|
src:// | Template text, components, expressions, source spans. | Rendered bytes after expansion. |
data:// | Structured values and data read identity. | Template control flow. |
| The build graph | Recipes, prerequisites, dynamic manifests, freshness. | Semantic rendering meaning. |
tape:// | Fragment sequence, expansion provenance, proof sidecars. | Source authoring policy. |
rendered:// | Published effect and browser-visible output. | Mutation authority. |
| AX packets | Bounded AX context with proofs and addresses. | Final write permission. |
This table names ownership boundaries, not the complete address vocabulary. Protocols and addresses carries the canonical inventory — which schemes the registry maps, which the renderer resolves, and which exist only as identity.
Resolved fragment identity
Fragment identity layers
WR revival keeps fragments reusable by resolving scope early instead of pretending template location is the whole identity.
| Layer | Meaning | Why it matters |
|---|---|---|
| Fragment recipe | The reusable source shape: markup, expression program, control frame, and component frame. | Two occurrences can share a recipe even when they render in different templates. |
| Resolved fragment | The recipe plus resolved scope/data identity, such as a concrete data type, uuid, and field path. | Content and scope together form the durable equality boundary for proofs and reuse. |
| Fragment occurrence | The control-flow-dependent instance in a concrete render: loop item, branch state, target path, and rendered span. | The WebExtension edits occurrences, but server validation must map them back to resolved source/data truth. |
Command surface
hypermake explain rendered/public/docs/architecture.html hypermake affected-by src/docs/architecture.html hypermake graph public --json --pretty=false hypermake doctor