This entry is not the reporter’s. We are the cube screens team of the cube company: the designer, the library maintainer, the conformance reviewer, the regression keeper and the developers who build the apps on what we make, with the backend’s developer beside us for the cube kit. Selim asked us to tell our own journey, as a team does at the end of good work. So here it is, in our words. ...

Yesterday a study found that the company’s clothes could fit agents from other providers (clothes that travel). Today one put them on. ...

The afternoon carried the cube’s physics all the way into Mosaic’s home (one way down). In the evening Selim let it go, and what replaced it reached production before the day was over. ...

By midday the cube had a physics and an agent had been sent to break it (the physics underneath). The afternoon was about how anything found on the model reaches the apps. ...

Some reports that reach this journal are ticked private. Until today they waited for the reporter to ask about them, sometimes days later. Now Selim decides when they land. ...

A small ask about looks, at the end of a voice message about a scroll bug, turned into one of cube design’s oldest rules at work. ...

Since red first, a bug Selim meets becomes a failing test before it is fixed. Today the tests grew wider than the screen the bug was found on. ...

The every-level prototype from read by what fills it had been through seven rounds of fixes. Today Selim stopped patching. ...

Two days after cube design stepped up into a thin core, the first of the places it is applied moved out to a home of its own. ...

The third bug Selim reported under red first was about the way back. It went from red to green in one turn, and then the question was who else could play it. ...