newest first. date · project · decision · why · what it replaced.
| date | project | decision | replaced |
|---|---|---|---|
| 2026-10-30 | cubes | letting go is hiding: one move (selim picked it over two moves and over "let go only from hidden"). there is no delete; hiding a cube, piece or face of yours is kept with your data and hidden on every phone, the library's stays on the phone. a look and a change turned out to be one move kept in two places. places the finding "letting go and hiding are close" as a piece of principle 20. cubes decision 30. | a separate let go with its own fold (mockup boards 4 and 5) |
| 2026-10-30 | cubes | press and hold changes what is yours (selim: "we are touching it, holding it, pressing it to change it"; three dots fit anlat, not a cube). a cube, piece, face or colour of yours raises its sheet; the library only whispers that it is read-only. a rename keeps the old name (principle 18), shown as "once mars" beside the title. letting go (removing) waits until it is compared with hide (finding below). cubes decision 29. | everything but adding done by hand in notion |
| 2026-10-30 | cube design, cubes | a cube first; a list or a table only as a rare fallback (principle 30). first use: the words of the cubes app became a cube (faces names, meanings, examples, code names; each word a piece with its example and code name), violation 11. | lists of cards and tables wherever knowledge was explained |
| 2026-10-30 | cube design, cubes, anlat, mosaic | every app keeps its own cube in cubes, kept true by the sessions that build it (selim): what the app is made of, what is asked of it, what happens to it. cubes holds itself first (cubes-app, private for now). the shape is shared (proposed by the session, following principles 1, 17, 22, 29): the app's pieces with features first, faces places and stages; features opens with faces uses, states, sources, days. a feature request is a feature in state asked, seen from afar by turning features to its states, not a cube of its own. first request: reading the library without a key. the app-cube skill (skill/app-cube/) carries it. |
anlat alone keeping a cube (anlat-cube skill, 30 oct morning); requests and what happened to an app living only in chats and threads |
| 2026-10-30 | cube design, cubes | cubes becomes the home of cube design: the "cube design" library cube in the cubes app is where cube design is read and grown, so what feels off there pushes the design of cubes and the other way round. the website shrinks to a door (an intro and a way into the cube) once cubes can carry it; until then it stays. first step: anyone can read the library cubes in cubes without the api key (the key only for writing), a feature request of cubes. then pictures and long text on a piece, versions as a cubes feature, and only then the website's own cube views go. | the website re-building cube views, zoom and versions beside cubes |
| 2026-10-30 | cube design | versions are a face of cube design (versions › a version › cube design as it was, its faces first); what each version brought is a face of it (changes: new, grown, the same). the newest is also shown inside versions (/v/<id>/). violation 10. |
the version picker in the top corner and the "how it grew" page |
| 2026-10-30 | cube design | principle 29: a cube opens on its shape, not its rows. faces are named by their answers in the plural: violations › examples, apps, outcomes, broken principles, sightings, pictures, reasons, adaptations; cube design › pieces, layers, stages, readers. | the pieces first; faces named as questions or labels: what happened to it, principles it breaks, seen, why it feels wrong, how it could follow; layer, how settled, first reader |
| 2026-10-30 | cube design | on the website a cube opens on its shape: its faces first (the names, then every kind), the pieces inside the names face (violations › examples, cube design › pieces). text fields are faces too, a piece's text one at a time. violation 9. | the pieces first, with the kinds beside them |
| 2026-10-30 | cube design | a kind is a piece of the cube it groups: on the website the kinds sit on the face beside the pieces (folded corner) and are zoomed into (kind › its values › the pieces holding one); no turning buttons, colour key, caption line or sideways links. violations 7 and 8. | turning with ‹ › and a key; a second grouping written under every tile |
| 2026-10-30 | cube design | the website follows cube design: a file whose sections are numbered opens as a cube of its own (the violations first, turned by where each was seen and what happened to it, from cube.json insides); every face is a complete square; two fingers together, ctrl and the wheel, a trackpad's pinch and escape go one level out on every page (principle 25). violation 6. |
the violations as one numbered text; tiles three across; only the ‹ to go out |
| 2026-10-30 | anlat, cube design | principle 28: everything in an app is the user's and the app does nothing it was not asked for. anlat's "seninle ilgili" became "benimle ilgili", in four pieces (how I'd like to be called, about myself, tercihlerim (first ayarlarım) with language, colours, words and the three dots as its own face, rehberim); "şimdilik değil" became "vazgeçtim" (anlat R61, anlat#86, #87); no conditional or permission language ("istersen", "-ebilirsin") on the user's own screens. | "seninle ilgili" with seven pieces; "sana nasıl seslenirim"; "şimdilik değil" |
| 2026-10-30 | anlat, cube design | a face is read in rows by what its pieces are for (principle 27 reworded): anlat's main screen puts looking at the cube first (hikâyem, yan yana), then adding to it (share, help), then the app and its user (seninle ilgili, rehberim); the rows are not named. "principles serve the person" becomes "principles serve, they do not rule" (violation 5: the person set users apart from makers). | the whole face ordered by use alone; "principles serve the person" |
| 2026-10-30 | anlat, cube design | anlat's main screen is one face of the app's offers on one level (share, hikâyem, help, yan yana, seninle ilgili, rehberim), a complete square with open places the makers fill, ordered by use with the guide last (violation 1, anlat R59, anlat#83). principles 26 (alike is not a must) and 27 (then: the most used comes first); philosophy: principles serve the person (renamed the same day, violation 5). | the first proposal: four pieces, yan yana inside hikâyem, help inside the share sheet |
| 2026-10-30 | cube design, anlat | going out of a piece is zooming out, wherever the hands allow it (principle 25): every screen inside another steps out one level when two fingers come together, to where its back arrow goes; the back arrow always stays as the backup. anlat's settings, rehberim, yan yana and the trial's pages take it (R56, anlat#80); logged as violation 4. | zoom out only on some screens (anlat: hikâyem's layers), the corner button the only way out elsewhere |
| 2026-10-30 | cube design, anlat | violations are a piece of their own (12-violations.md): each keeps a picture, the principles it breaks, why it feels wrong, how it could follow and its status; never fixed away from the page. first three: anlat's main screen (five doors side by side, proposed), rehberim not a square (fixed, anlat#78), ne zaman's date picker (moved in from the findings). | bad examples only in findings and threads |
| 2026-10-30 | cube design, anlat | a face is always a complete square (principle 24), from the cubes decision and the finding of the same day; anlat's faces follow it (R54). | the screen's width deciding how many sit across |
| 2026-10-30 | cube design | the app and the person walk the cube together: they look at it and build it together, see it differently and influence each other (philosophy). | not written down |
| 2026-10-30 | cube design, anlat | language is its own piece (principle 23): the words an app speaks are designed apart from the code and with the same attention; every line has a key and may have several wordings side by side, one in use, the others kept. anlat's lines moved out of its code into a table of their own (notion "lines"), with turkish and english on one row and a tick for the wording in use. | lines written inside the code, one text per button |
| 2026-10-30 | cube design | principle 22 widened: names others own go small too (notion, github, google, claude), since no law or courtesy asks running text to copy a brand's capitals; only abbreviations, codes a machine reads and single letters keep capitals. the data each app brings goes small as well (cubes' library, anlat's offered details); a person may still write capitals in their own. | brand names kept their owners' capitals |
| 2026-10-30 | cubes | four from selim's play: (1) from afar too a colour is where the journey ends; it names its pieces and opens nothing, as in anlat (opening it onto its pieces is parked); (2) nothing is counted: a tile names its first pieces instead of "14 pieces"; (3) a wide screen puts the cube on the left and the square beside it, a phone keeps it on top; (4) a face that holds pieces is named in the plural, like names (parts, tastes, colours), and every word is in small letters (principle 22), labels and badges included. | a colour from afar opened the cube again; counts beside every title; the cube on top on a desktop; face names in the singular and title case |
| 2026-10-30 | cube design | small letters first (principle 22): an app's own words, its installed name and the data it brings itself are written in small letters; capitals only for abbreviations, codes, single letters standing for something and names others own; what a person types is never changed. applied to cube design's own documents, website and skill, and to cubes, anlat and mosaic. | title case and sentence case, each app its own way |
| 2026-10-30 | cubes | a grid is always a complete square: the smallest n × n that holds the pieces, places not filled yet outlined, zooming out a step by itself as it fills; tiles say less as they shrink, the square keeps its size, the cube stays on top on a desktop too. the grid is a slice of the cube; making the two represent each other is kept for later. | the 2/3 columns button and a list that grew downwards |
| 2026-10-29 | cubes | a cube of your own is named first (mockup A): your own box (white, warm border, a plus; anlat's design language) ends yours and every cube of yours, always after the pale offers, and opens a sheet to name a cube, a piece or a face. mockup B (find a piece first, the cube later) is anlat's way and stays there: two projects may share a design language without sharing their content. | a pale dashed "something new" tile and an inline naming card |
| 2026-10-29 | cubes | the library is read-only: its cubes (the daily cube too) are fixed knowledge to look at, turn and learn from; a viewer may hide pieces but changes nothing. cubes to change are yours, so the cube design cubes moved from the library to yours. who may change a cube (a lock) is kept as a possible face for later. | every library cube could grow from the app |
| 2026-10-29 | cubes | the navigation is a cube: / is cubes, as far out as anything is known, with library (public), yours (private), words, and pieces found from what the viewer does (lately, hidden, today's cube); a swipe turns it to "who can see it". no tab bar; every top screen steps out to it. |
the tab bar library / yours / words (kept as an option, principle 18) |
| 2026-10-29 | cube design | every app says when it was last built (principle 21): the date and time of the last deploy, quiet, where the app keeps things about itself. anlat shows it at the end of seninle ilgili, cubes at the end of words; mosaic already knows its build (BUILD_INFO) but shows it only on dev and in bug reports. |
nothing said; no way to tell from the app whether a change had arrived |
| 2026-10-29 | cubes | pieces and faces can be hidden under "hidden" (principle 20), the page uses a desktop's width with two or three tiles across on a phone (principle 19), and the lines telling the viewer where to start are gone for now (kept as a later idea). | every piece always shown; a phone-wide column on every screen; "start anywhere", "start yours" |
| 2026-10-29 | cube design | mobile first, not mobile only (principle 19); hide, never delete (principle 20). | nothing said about wide screens; a viewer saw every piece |
| 2026-10-29 | cube design | nothing found is thrown away (principle 18): every name, suggestion, option and finding is a piece of the cube, chosen or not; competing ones are kept side by side and compared. first use: every name of the two journeys is kept in the words cube (journey one/many, A/B, close up/from afar, into a piece/across the cube, zoom in/turn). | only the chosen name was written down |
| 2026-10-29 | cube design | the two journeys of principle 17 are called, for now, journey one (one piece, close up: piece › face › colour, placed) and journey many (the whole cube from afar: cube › face › colour › pieces; a cube opens this way, names first). they replace anlat's journey A and B. | journey A and journey B |
| 2026-10-29 | cubes | a cube opens from afar, as its faces, and names is the first face (every piece by its name, as a database's first column is the name). names opens as the plain list; a piece opens close up. with principle 17 the two journeys are now both in the app: from afar (cube › face › colour › pieces) and close up (piece › face › colour, placed, never opened). | a cube opened straight onto the plain list of its pieces' names |
| 2026-10-29 | cube design | two journeys, and the other side only from afar (principle 17): close up a value is where the journey ends (a tap places it, it never opens); every piece with that value is seen only by turning the whole cube to its face. close up never leads out to afar. cubes takes it: no "turn ... to this face" from a piece's face, no value screen close up, the cube itself turns to its faces. | close up and afar linked both ways, so zooming in could walk in a circle (open question 12) |
| 2026-10-29 | cube design | every piece of a cube has the same shape (principle 16): every face and inside its siblings have, shown pale as not known yet in the domain's words. in cubes: mars shows continents because earth has them; a cube's screen shows only its pieces, no faces section; a piece's colour on one face is its sticker. | insides shown only on the pieces that had them |
| 2026-10-29 | cube design | each project speaks its own domain's words and never mixes domains in one place; a domain without its own words borrows cube and piece until it finds them. the cubes app takes a rubik's cube's words: cube, piece, face, colour. | "each project picks its own words, mapped" (same day), which allowed mixing |
| 2026-10-29 | cubes | every cube grows from its last tile, library cubes too (a piece, a kind with its question, a value, a new cube), and a cube turns by a kind seen from afar: each value a cube of its pieces, plus "not known yet" (anlat's journey B, taken into cubes). | only cubes of yours could grow; a kind was seen only close up, inside one piece |
| 2026-10-29 | cube design | each project picks its own words as long as they are mapped in the words cube; a new domain maps its things before naming them. new principle 15 and a words dial. which variable a thing is depends on the distance it is seen from. | one word set for every project |
| 2026-10-29 | cube design | say zoom in and zoom out, never "pinch": zoom out is bringing two fingers together (thumb and index closing along the diagonal), zoom in is spreading them. | "pinch out" / "pinch in", heard opposite ways |
| 2026-10-29 | cube design | the words become a cube of their own (11-words.md): each concept is a variable with a description until a name fits every domain, and every domain's words are mapped onto it. working words for now: row, column, option (X, Y, Z). new principle: understand once. | one word set to pick (open question #1) |
| 2026-10-29 | cube design | every session that changes this repo logs a row in the notion table cube design contributions (what, why, where it is placed), so selim follows the evolution there, not in PRs or git history. small changes go straight to main. |
reading PRs and commits |
| 2026-10-29 | cube design | every project follows cube design: cubes, anlat and mosaic say so in their CLAUDE.md, and so does this repo. every project is a cube. | cube design read only when remembered |
| 2026-10-29 | cube design | 0.2 released ("the way of looking"); 0.3 starts. | — |
| 2026-10-29 | cube design | a public website shows cube design: the text, the visuals, the cube drawings, and every version to choose from. built from this repo (site/). |
files read on github only |
| 2026-10-29 | cube design | findings are collected, not fixed away: each is placed as a piece, a cube of its own or a new axis, and settled later. | fixing drift as soon as it is seen |
| 2026-10-29 | cube design | cube design is approached with its own principles (recursive); a living philosophy explains it to anyone curious. | a design system written about other projects only |
| 2026-10-29 | cube design | cube design becomes its own project: repo as source, skill as messenger, weekly review. | ideas spread across three projects |
| 2026-10-29 | anlat | "yüz" dropped from the app; a value opens the stories that carry it. | yüz / taraf vocabulary; values as last level |
| 2026-10-29 | anlat | own box back to a plain square. | filled apricot box ("felt like a button") |
| 2026-10-28 | cubes | built on the cubes sub-app of mosaic's backend, data in notion under mosaic › cubes. yours can bring in a library piece, find a kind on a piece and pick its values, start from a library cube, and name a new cube or piece. naming your own kinds and values comes next. |
mockups only |
| 2026-10-28 | cubes | the tabs library, yours and words stay; words explains each word with a "show me". | — |
| 2026-10-28 | cubes | building uses the same navigation, with things missing: yours looks like the library with fewer pieces, pale tiles are what to find next, the library's own answer is marked ("the library says so"). adding a kind drops you into it; growth says "this cube grew." | a separate building screen |
| 2026-10-28 | cubes | everything named is a piece and a cube, and every cube is a piece of a bigger one. a cube is never seen whole or complete. a value is the one complete piece: one colour on every face. | "not a cube yet" |
| 2026-10-28 | cubes | mockup 5 shipped: zoom at every distance; naming a thing makes it a cube. | table-like v0; "not a cube yet" seed state |
| 2026-10-28 | cubes | one screen shape at every distance (from anlat's rows, columns, values). a cube opens as the plain list of its pieces, never grouped by a property. back is always one step out. | opening grouped by a property ("rocky", "gas giant") |
| 2026-10-28 | cubes | a question is a hint, not part of the cube. | question as a face |
| 2026-10-28 | cubes | two modes, the library and yours: the library is public, searchable, one web; yours is what you know, compared with the library, which offers what you have not met. same moves in both. | one undivided space |
| 2026-10-28 | cubes | built a little at a time, never dumped: one next move with suggestions; the cube grows 1, 2³, 3³ like a puzzle. | everything shown at once (viewfinder mockup alone) |
| 2026-10-28 | cubes | the cube shows, the data stays readable: the cube pictures the thinking, names and text sit readable underneath, never on stickers. a list is already a cube. | data on the stickers (mockup 1) |
| 2026-10-28 | cubes | zoom in and out is the navigation, animated as a change of distance, as far out as anything is known (planets › solar system › … › local group). | page changes |
| 2026-10-28 | mosaic | puzzle cube becomes the home screen; fill / each once / twist / upright kept as switches. | tile dashboard; themed faces |
| 2026-10-28 | anlat | every piece is a cube: rows → columns → values, one screen shape. | separate piece, side and colour-shelf screens |
| 2026-10-27 | anlat | "the cube was always solved" replaces solving language. | "the cube nobody hands you" |
| 2026-10-27 | cube problem | the viewfinder: faces are axis ends; a look shows ≤ 3 dimensions. | faces as dimensions |