Anahadh

Writam is spatial thinking. Notes, sources and unfinished ideas keep the positions you give them, so the arrangement becomes something you can read later.

Swaya is adaptive planning. It works from the capacity you actually have on a given day, and treats repairing a plan as a designed path rather than cleanup.

Bokta is connected food and pantry management. Scan what came in, say what went out, and pantry, recipes, meal planning and shopping stay one loop.

You should be able to tell where a piece of information came from: whether you entered it, whether the software observed it, whether it was calculated from other things, or whether it is a prediction.

In Swaya that is literal. Every figure carries a badge showing its origin, so a number you typed in last week and a number the app worked out this morning never look alike. In Writam it takes a different form: the position of a note is information you put there, and the canvas is never rearranged on your behalf, because a layout you did not choose would be telling you something you never said.

The same applies to results and recommendations. When the software shows you a conclusion, you can ask why it is showing it, at the thing showing it, and the answer is about that specific thing.

Swaya is the clearest example. That you slept five hours on Tuesday is a fact. That your Tuesdays tend to run short is a pattern. That tomorrow may be tight is a prediction.

Those three are not interchangeable, so they are not presented as though they were. They differ in wording and in appearance, every time, with no exceptions for the ones that would look tidier merged.

The general form of the rule: software should not present uncertainty as certainty. A guess set in the same confident type as a measurement is a guess that will get acted on as though it were one.

Hiding something should not silently delete it. Switching a feature off removes it from view and leaves the underlying data recoverable.

Previewing a change should accurately represent what will happen. If a preview and the result can disagree, the preview is decoration.

An action should not have surprising side effects somewhere unrelated. Turning off one part of Swaya does not quietly rewrite your history in another part of it.

These read as obvious, and they are also the rules most easily broken by accident, usually while adding something else. So they are written down as rules the products are checked against rather than left as good intentions. {{TODO: Is there a specific invariant you would rather name here in the product's own words? — CONTENT-TODO #34}}

Bokta is the clearest case. Pantry, recipes, meal planning and shopping are useful because they form one loop: what you have shapes what you can cook, what you plan determines what you buy, and what you buy updates what you have. Split into four apps, each one makes you re-enter what the other three already know.

Writam works the same way at a smaller scale. Position, movement and clustering are not three organisation features bolted together, they are one spatial model. You do not group things and then separately arrange them — grouping is what arranging produces.

Products in beta may change substantially. Things break, features get reworked, and some parts are visibly incomplete.

Feedback is useful at this stage because the workflows are still being tested, not just the code. If something felt wrong to use, that is the report worth sending.