Prelaunch preview. Explore AROS products and skills. Checkout is in sandbox; no real payment.
Blog

Why we write in public

What these essays and the dev log are for, and the rules we hold them to.

Nexitia1 min readEnglish

AROS is being built around one idea: the experience behind a result is worth keeping. The failed attempt, the correction and the reason a method works are knowledge in their own right. It would be odd to hold that view and keep our own working record private. This section is where we share it.

Two kinds of writing

Essays are for ideas that take more than a page: where AROS is going, why we build the environment around the model rather than the model itself, and what we have learned about making research methods reusable. They are signed and written to be read end to end.

The dev log is for what changed. Each entry is dated, names the product it touches and says what a person can now do. Entries are short, and they link to the change itself wherever it can be inspected.

The rules we hold them to

  • A claim points to its evidence. Where we report a result, we link the record behind it and say what it does and does not show.
  • Plans are written as plans. Something in development is described as in development, not as available.
  • No invented numbers. No popularity claims, adoption figures or benchmark promises that were not measured.
  • Dates stay true. An entry keeps the date it was written. When a later result changes the picture, we write a new entry rather than rewrite the old one.

Following along

Each lane has its own RSS feed, so you can follow the essays, the dev log or both. Questions about anything written here are welcome at support@nexitia.ai.