clearcontext is an independent build and research log about AI tools, developer workflows, and the systems behind this site. Each article starts with firsthand work or a question that can be checked, not an announcement rewritten for volume.
I'm a developer who's happiest in a terminal. Most of what I build lives there: command-line tools and text interfaces. On the side, I work on games. I like software that's small enough to understand completely, and I'd rather ship a focused tool that does one thing than a framework that does everything.
Every article has an evidence boundary. Tested claims come from a saved run or artifact. Calculated claims show their inputs and arithmetic. Documented comparisons stay tied to dated primary sources and say plainly what I could not test. News is useful when it creates something to measure or compare, not when it only supplies a headline.
AI helps with research, code, images, and editing, but it does not get the final decision. I approve the topic before drafting, verify primary sources and saved evidence, inspect the article and images, and approve the publication packet. Future-dated articles re-check the exact source claims on release day and fail closed if a source has drifted.
Email rafael.b.moraes@gmail.com to report an error, challenge an evidence label, ask how a result was produced, or suggest a problem worth testing. Material corrections are checked against the underlying source or artifact before the article is changed.