The README states what the compositor keeps and what it forgets. The compositor holds the changes of the program in its memory only, and it drops them when it stops or when it reads its configuration file again. A user who expects a permanent arrangement loses the work. The README also lists the behavior of niri that the design depends on: the calculation of the logical size, the limits of the scale factor, the treatment of an output that is not connected, and the absence of an event for a change of the outputs. The architecture document gives the six crates and the direction of the dependencies between them. The test document gives the limit of a nested niri instance and the reason for the compositor in the ipc crate. The script starts a nested niri instance and prints the path of its socket. The tests change the outputs, so they must not use the socket of the session of the user.