Every fortnight the same question comes back in different words: what actually shipped? We could answer with a list. We would rather show you how to check it, because the answer lives in three places on Atheron Progress, and those three places should agree.
This piece does not retell this fortnight's items. The changelog does that, and it is the record. What follows is how to read it alongside the tracker and the status page, across every project, so you can trust what you see.
Three places, one story
- The changelog says what changed and when.
- The tracker shows each project split into modules, each marked shipped, building, next or later.
- The status page shows whether each public service has been up, with ninety days of history.
A shipped item should leave a trace in each place that applies to it. An entry in the changelog. A module that moved to shipped on the tracker. And, if it is a public service, a row on the status page.
Step 1: start with the changelog
Read the changelog for the last two weeks. Note each entry and which project it belongs to: Atheron Trading, ATON Blockchain, ATON Desk or Atheron Network Labs.
Not every entry is a shipment. Some record work moving from next to building. That is progress, and it is worth knowing, but it is not shipped. Keep the two apart as you read.
Step 2: find the mark on the tracker
For each entry that says something shipped, open that project on the tracker and find the module. It should be marked shipped.
Remember what the mark means here. Shipped means somebody uses it today. Not finished on a branch. Not passing tests and waiting. Used.
When a module moves to shipped, the project's percentage moves with it. We never type those percentages. They are counted from the marks. So a rise in a percentage should always line up with a module that changed. If it does, that is simply arithmetic.
Step 3: check the status page where it applies
Some shipped work is a public service. If it is, look at its row on the status page. Each day is coloured by its worst event, so a rough first day shows as a rough day, even if the rest of the fortnight was clean.
Not everything that ships is a public service. Work that sits inside a project will not have a row of its own. That is expected, and it does not make the work any less shipped.
What each project can show
The four projects are at different stages, so the record looks different for each.
| Project | What to look for |
|---|---|
| Atheron Trading | Module marks and changelog entries. It runs on paper only until launch, so there are no performance figures. |
| ATON Blockchain | Module marks, changelog entries, and status rows for its public services. |
| ATON Desk | Coming soon. Read its module marks to see where the work stands. |
| Atheron Network Labs | Open for projects. Its changes appear in the changelog and on the tracker like any other project. |
One point on Atheron Trading is worth stating plainly. Progress there means modules moving, not results. We do not publish performance figures for it, so the tracker and changelog are the only measure of that project you will find from us.
When the three disagree
Most of the time the changelog, the tracker and the status page tell the same story. Sometimes they will not line up straight away.
The same goes the other way. A module marked shipped with no changelog entry is a gap in the record, not a quiet win.
Why we ask you to check
A summary written by hand drifts. Words get rounded up, a hard fortnight gets softened, a half-done module gets called done. The tracker is computed from our repositories, the percentages come from the marks, and the status page colours each day by its worst moment. None of that depends on how we feel about the fortnight.
So when you want to know what shipped, you do not need to take our word for it. Open the changelog, find the mark, check the row. If all three agree, that is what shipped.
