Module worked 

What an act touched: the scope its author was standing in and the entities its ops named.

One derivation of “what did this change touch”, consumed twice — the camera aims at it and the canvas rings it — so the two cannot disagree about where a change was. The names come from the manifest row the act wrote (docs/log-vs-snapshot.md §10.1), so nothing here has to guess which coordinate space a pin belongs to; a session with no rows reads its own commit instead.

Structs

Step

The two documents a commit stands between. A subject is read from before — a step frames where the thing was, which is what the camera has to reach before the change is drawn — and from after only where the commit itself brought it into being. Between them they hold every subject a commit can name, which is what a delete’s footprint needs now that a delete removes rather than tombstones.

Worked

What an act named and where it was standing — a manifest row’s own two advisory fields, or the same pair read off a commit for a session that keeps no rows.

Functions

container 🔒

The block a subject sits inside: a shape’s owner, a block’s parent, a wire label’s wire’s owner. The document itself and an asset sit in nothing.

parent_of 🔒

The scope a block is a child of. The root’s own parent is the root.

scope_of

The scope a subject is drawn in, read across a step, in the wire spelling. A pin is the exception: it shows at its slot anchor, which is on its owner’s outside, so it belongs to the scope the owner is a child of.