A public record of contributions. No token. Nothing to trade. This is a database.
The window
This digest covers ISO week 2026-W37: 2026-09-07 to 2026-09-13, in UTC. 2 commits landed in that window.
The first was 82d9978 at 2026-09-07T11:44:16+00:00; the last was ca0cc4c at 2026-09-09T07:07:21+00:00.
What changed, by area
| Area | Files changed |
|---|---|
| the toolchain: validator, renderer, gates | 1 |
| the blog itself | 1 |
Areas not listed had no file changed this week.
The contribution ledger
There is no ledger/log.jsonl in this repository yet — no real record has been opened — so the honest count of recorded contributions this week is zero. The engine that will accept those events exists and is tested (ledger/), and the example chain the /ledger page renders (ledger/example/chain.jsonl) is an example: it is labelled as one there and it is not counted here. This section starts counting the week a ledger/log.jsonl file is committed. Nothing here estimates what the count would have been.
Every commit in the window
| Commit | UTC | Subject |
|---|---|---|
82d9978 | 2026-09-07 11:44 | blog: weekly digest 2026-W36 (generated) |
ca0cc4c | 2026-09-09 07:07 | Add denominators to ledger share prose |
How to check this
Every number above is a count of things in this repository's history, not an estimate. The counts are history as it stood at commit ca0cc4c, which the command in this file's header names explicitly: clone the repository, run that command, and you get these bytes back whatever has landed since. git log ca0cc4c --since --until over the same window shows the same commits.
A digest written while its week is still open reports the part of the week that had happened by that commit, and it is not rewritten afterwards — a corrected digest would be a new commit, visible as one.