a violation is a screen, a word or a move in a live project that goes against cube design. it is collected, not hidden: a bad example teaches what the principles mean as much as a good one, and often more. each one keeps a picture of how it looked, why it feels wrong (worked out against the principles, not only felt), how it could follow cube design, and what happened to it. like a finding it is never fixed away from this page: when the project changes, the violation stays here, marked fixed, with the change linked.
how a violation is written (every project, every session):
## <n>. <one line>, numbered in order; the picture isviolations/<nn>-<project>-<screen>.png.- seen: when, in which project and screen, and who saw it.
- picture: the screen as it was.
- breaks: the principles it goes against, by number.
- why it feels wrong: the reasoning, in the project's own words.
- how it could follow: the adaptation proposed; nothing is built until selim says so, unless he asked for it.
- status: seen, proposed, or fixed (with the change linked).
a violation is also a row in the notion table cube design contributions, kind violation.