Every two weeks we look at the same two sources and write down what they say. The changelog is the record of what changed. The tracker is the record of where each module stands. Nothing in this report comes from anywhere else. If a point is not in one of those two places, it is not here.
This time we go project by project, so you can see the fortnight the way the tracker shows it rather than as one long list.
How to read this
Each project on Atheron Progress is split into modules. Each module carries one of four marks: shipped, building, next or later. The percentages you see on a project are counted from those marks. Nobody types a number in.
Shipped has a narrow meaning. It means somebody uses the module today. Building means we are working on it now. Next means it is queued. Later means it is on the list but not scheduled.
When a module moves between marks, that move appears in the changelog. So a fortnight report is really a report of moves. A module going from building to shipped is the one we care about most, because it changes what you can use.
Atheron Trading
Atheron Trading is paper only until launch. That is the single most important fact about this project and it has not changed. Paper only means the system runs on simulated positions. No real money, no real orders.
Because of that, you will not find performance figures anywhere on the tracker, in the changelog, or in this report. We do not publish returns from a paper system, and we will not quote them to you in a progress note either. A number from a simulation says very little about a live market, and a number we cannot stand behind is worse than no number.
What you can read for Trading is the module list and its marks. Shipped modules there are modules somebody runs today in paper mode. Building and next tell you what has to move before launch is possible.
ATON Blockchain
ATON Blockchain is tracked the same way: modules, marks, a percentage counted from the marks. Where it differs from Trading is that it has public services, and public services appear on the status page.
The status page shows each public service with ninety days of history. Each day is coloured by its worst event. One bad hour colours the whole day. We chose that rule because it is harder on us than a daily average would be, and because it is the rule you would want if you were relying on the service.
So for ATON Blockchain, read two things together. The tracker tells you what has shipped. The status page tells you whether what has shipped stayed up. A shipped module with a run of clean days is the result we are aiming for every fortnight.
ATON Desk
ATON Desk is marked coming soon. Read that plainly: it is not available to use yet. Its modules are on the tracker, so you can see which are building, which are next and which are later, and you can see the counted percentage move as marks change.
We do not pre-announce a date for Desk here. The tracker and changelog are the record, and until a module there is marked shipped, nothing about Desk is something you can use today.
Atheron Network Labs
Labs is open for projects. It is the part of Atheron where work can begin that does not yet belong to one of the three named products. Because it is open, its module list is the one most likely to gain new entries rather than only move existing ones.
A new entry in Labs usually starts at later or next. It earns building when work begins and shipped when somebody uses it. Watch the changelog for new names appearing under Labs. That is the earliest signal of a direction, well before any percentage changes.
Reading the fortnight as a whole
Table: What to read for each project this fortnight
| Project | Where the fortnight shows up | What to watch for |
|---|---|---|
| Atheron Trading | Tracker marks, changelog | Moves to shipped, in paper mode only |
| ATON Blockchain | Tracker, changelog, status page | Shipped modules and clean days together |
| ATON Desk | Tracker marks, changelog | First modules reaching shipped |
| Atheron Network Labs | Changelog, tracker | New module names, then marks moving |
A few honest limits. The tracker only knows what the repositories tell it, so work that has not reached a repository does not appear. The status page only covers public services, so internal services are not on it. And a percentage is a count of marks, not a measure of difficulty. A project at a high percentage can still have its hardest module ahead of it.
If you want the fortnight in one sentence: open the changelog, read the moves, then check the status page to see whether what shipped stayed up. Everything we would tell you is already there, and it is computed, not typed.
