# Slice 4e: procedural execution

Implemented on September 6, 2026, extending the renderer and procedural changes already present in the workspace.

`visual-systems.js`, `visual-distributions.js`, `visual-behaviors.js`, `visual-fields.js`, `visual-noise.js`, and `visual-motion.js` implement components, particles, emitters, repeaters, placement, behavior motion, fields, trails/ribbons, and links. The production application advances them on logical ticks. Render frames do not advance simulation or consume procedural streams.

The nineteen section 18.10 tests in `test/phase4-procedural.test.mjs` pass. Added execution tests check graphic drift, repeated-object motion, morphing geometry, propagated channels, and rendering across different frame rates. This closes a gap in the original procedural work: behavior arithmetic alone did not prove that its results reached draw geometry. Scoped expressions inside component/repeater inputs and distribution configuration sampling now follow their owning instantiation boundary.

Initial resolved populations cannot exceed their system bounds; emission batches retain the newest capacity-sized population without an unbounded construction loop. Aggregate protection is recorded with 4f.

Run `node --test --test-isolation=none test/phase4-*.test.mjs`. Display judgment remains separate and unperformed by the agent.