You want to know what shipped this fortnight. The honest answer is that the list lives in one place, and it is not this post.
The record is the changelog and the tracker on Atheron Progress. We do not retype it here. A second copy of a list can drift from the first, and then you have two answers and no way to know which is right. So this post shows you how to read the record yourself, quickly, across every project.
Start with the changelog
The changelog is the dated record of change. If something shipped, it shows up there. If it is not there, it did not ship, whatever anyone says in a meeting or a message.
When you read it for a fortnight, look at three things:
- The date. Only count entries inside the two weeks you care about.
- The project. Each entry belongs to a project, so you can read one at a time.
- What changed. An entry tells you what moved, not how hard it was to get there.
That last point matters. We do not reward effort in the record. We record outcomes.
Then check the tracker
The tracker splits each project into modules. Each module carries one mark: shipped, building, next or later.
Shipped has a strict meaning for us. It means somebody uses it today. Code that is finished but not in anyone's hands is not shipped. It stays at building until it is.
The percentage you see for each project is counted from those marks. Nobody types it in. When a module moves to shipped, the number moves with it. When nothing moves, the number stays still, and that is information too.
A percentage that did not change this fortnight is not a failure to report. It is a report.
Read it project by project
Here is what to keep in mind for each project as you read.
Atheron Trading. This project runs on paper only until launch. You will not find performance figures in the changelog or the tracker, and you will not find them here. What you can see is which modules are shipped and which are still building.
ATON Blockchain. Read its modules the same way. Look for any that moved from building to shipped inside the fortnight, and check the changelog for the matching entry.
ATON Desk. This one is marked coming soon. Expect most of its modules to sit at building, next or later. That is an accurate picture, not a gap in the data.
Atheron Network Labs. Labs is open for projects. Its tracker shows what is in use today and what is still ahead.
A quick method that takes five minutes
If you only have a few minutes, this is the order we use ourselves:
- Open the changelog and filter your eyes to the last two weeks.
- Note each entry by project.
- Open the tracker and find the module each entry belongs to.
- Confirm the module is marked shipped, not building.
- Check whether the project percentage moved.
If an entry and a mark disagree, trust the stricter one. A module is shipped when somebody uses it today, and not before.
Do not forget the status page
Shipping something is half the story. The other half is whether it stays up. The status page shows each public service with ninety days of history. Each day is coloured by its worst event in that day.
So after you check what shipped, glance at the status page for the same fortnight. A new module that shipped into a service with a rough week tells you something different from one that shipped into a quiet one.
Why we work this way
We could write a tidy summary every two weeks. It would be easier to read. It would also be a claim you have to take on trust.
We would rather you did not have to trust us. The changelog and the roadmap are the record. The tracker counts from the marks. The status page colours each day by what actually happened. You can check all of it yourself, any time, without waiting for us to tell you.
The list for this fortnight is waiting on Atheron Progress. Open it and read it in your own words.
