‹ examples

opening a cube on its rows, not its shape

outcomes: fixedapps: anlat, cubes, cube designbroken principles: 2, 16, 17

seen: 2026-10-30, cube design, anlat and cubes (the violations cube in cube-design#3; anlat's moments; the planets in the cubes app), on a phone. selim: "when i'm going into the violations, the first thing that i see, it's not violations themselves … similarly in anlat, when i go into the moments, the stories of the user, i don't land on them. i just land in the columns." and: "when i click on the planets, it was giving me the list of planets. no, that's not the idea. when i click on the planets, it's going to give me its columns first. it's not giving me its rows." it came up because the second build put "apps" beside the violations and a finding said principle 16 strains because apps has no app.

picture:

the violations cube on a phone, second build: the seven violations as tiles first, then apps and what happened to it beside them

breaks: 16 (every piece of a cube has the same shape), 2 (the cube is the viewfinder, not the data), 17 (journey one and journey many), and the screen shape of 05-patterns.md. the same mistake in three apps; no screenshot is kept for anlat and cubes.

why it feels wrong: a cube is first its shape: the columns every piece has. a table called violations has rows, each one a violation, and its first column is what a violation is pointed to by (its one line, its title), before anything else is known about it. opening the cube on its rows skips the shape and puts the pieces where their faces should be; adding a kind beside them then mixes a thing with a way of looking at things, and principle 16 seems to break ("apps has no app"). it does not break: the face shows a violation's shape (examples, apps, what happened to it, the principles it breaks, seen, pictures, why it feels wrong, how it could follow), and every violation has all of them, pale where nothing is known. the name of the cube (violations) and the name of its pieces (a violation) are the same word, which is where the confusion comes from; the first column needs a word of its own, and here it is examples.

how it could follow: going into a cube shows its faces first. the first face is the names (examples here, pieces for cube design itself, names in the cubes app); zooming into it shows the rows, each opening close up. zooming into a kind shows its values, and into a value the rows that hold it; zooming into a text face (why it feels wrong) shows every row's text, one at a time. anlat's hikâyem and the cubes app's cubes would open the same way.

status: fixed for cube design in cube-design#3 and made principle 29; seen in anlat and cubes, not changed there yet.