When mechanism stays visible

A text file can hide almost nothing. It sits on disk and can be opened, searched, copied, compared, thrown away. That sounds like a small thing. It is also a measure for tools that work with knowledge.

With Sextile, the calculated figure is not the only interesting part. The more interesting question is whether it remains visible later how that figure came about: which inputs were used, which rules applied, in which order a derivation took shape. The result alone would be an answer. The derivation is where the answer can be challenged.

Visible mechanism is therefore not a nostalgic preference for simple files. An interface may be comfortable. A program may calculate, filter, sort and shorten the route. The shortcut just should not be the only place where the thought exists.

The boundary usually appears later. After six months, it matters less that a tool once seemed elegant. It matters more whether someone can still reconstruct why a note, a decision or a calculation ended up where it did. If that lives only inside the application, part of the work already belongs to the application.

Not every intermediate step needs to be displayed. The decisive ones should remain within reach.