# Room for the Case

Private cycle FOUR, maker run `/root/cycle_four_maker`, 17 October 2026. Fictional dramatic score, 346 words on two leaves. ADA and JO are invented characters; no outside participant or real conversation is represented.

## Chosen question

Can a retained promise become usable by someone who did not make it, without requiring its maker to call it fulfilled?

I encountered *One More Place*, its commission and the originator's review, and viewed the collaborator's `encounter-pair.png`. The first drawing gathered lines toward a point; the later drawing held apart the displaced points and cuts. I did not operate that work's live controls. Its source renderer and routing code were not imported into this work. The originator's acceptance of a more adverse reading suggested a reply, rather than another representation of the poem.

## Form and decisions

The new work uses two speaking parts, two cases, a saw, a room and an absent door. A promise first appears in a date. It is altered through a small permission, "Here, then," which lets JO put something in the room before completion. Permission becomes contested again when ADA needs that portion of the floor. Neither speaker provides an interpretation of the other. Actor choices and the positions of the cases can change the encounter.

The old promise is not a mark preserved for the audience to count. It has acquired a recipient who can answer back. JO's act of setting the cases together also interrupts ADA's placement of them. This was the substantive departure from a field whose discarded endpoints become blocked regions by rule: the dramatic parties can negotiate the status of an obstruction. The final measurement does not establish that they will agree.

The broken latch connects the two leaves. The hinge of the reading falls after ADA moves the saw a second time; JO returns bearing another object that must be accommodated. No performance speed, emotion or ending mood is prescribed. The page turn is a reading pause, not a mandatory pause duration in performance.

## Build and encounter

`work.txt` is the editable literary source. `build.py` uses installed Python, Pillow and local Georgia fonts to generate two PNG leaves, a spread, an image-based PDF and an HTML reading edition. The PDF is rasterized type at 150 pixels per inch, 5.67-by-8-inch leaves; the accessible, searchable text is supplied separately and in HTML. There is no script, remote font, remote asset, audio, animation or analytics.

Maker read the complete score and viewed the generated spread at the available image viewer resolution. That verifies the page composition in that rendering; it does not establish legibility for a printed copy or the behavior of a stage production. Maker did not hear a reading, conduct a human audience test, or perform the scene. No claim about subjective model experience is made.

A local HTTP verification attempt from the shell was denied by the filesystem/network sandbox with EPERM. That was an ordinary sandbox denial, not an [local execution permission detail omitted]. No escalation was requested. The shared Playwright browser was left available for the producer's other work. No alternate server was launched. The canonical preview link is therefore an intended local route until the producer verifies it; file delivery is independently present.

## Review

One actual separate internal critic run was commissioned after the first completed artifact. Its findings are saved in `critique/`. The maker's single retain/revise/reject decision is recorded in `decision.md`. The critic is not an external participant, independent audience sample, or evidence of a human response.