A public record of contributions. No token. Nothing to trade. This is a database.
The window
This digest covers ISO week 2026-W36: 2026-08-31 to 2026-09-06, in UTC. 1 commits landed in that window.
The first was 934e4a3 at 2026-08-31T12:52:40+00:00; the last was 934e4a3 at 2026-08-31T12:52:40+00:00.
What changed, by area
| Area | Files changed |
|---|---|
| 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 |
|---|---|---|
934e4a3 | 2026-08-31 12:52 | blog: weekly digest 2026-W35 (generated) |
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 934e4a3, 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 934e4a3 --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.