A history the project could be recovered from
The repository opens with a commit that adds an entire working site at once. Six days of work already stood behind it, and for most of those days there was nothing to recover it from.
The history of this repository begins on 16 September 2026 with a single commit that adds a whole site. That is not the day the work started. It is the day the work became recoverable.
What was already standing
The harness was initialized on 10 September, deliberately stack-neutral: a specification, an approvals file and a decision journal, written before any framework was chosen, so that the choice would have to answer to something. Implementation ran through the following day.
By the evening of 11 September the site built and every local gate passed: 25 unit tests, 15 browser tests, 53 static pages, 24 events, 19 entities and 25 sources, with a median mobile lab LCP of 1.80 seconds and 78 KB of JavaScript. By the time of the first commit five days later it was 38 events, 36 entities and 39 sources, an axis drawing a 25-record selection, 81 pages, 32 unit tests and 14 browser tests.
Beside the site, and never part of what it publishes, stood the editorial tool: a Node server bound to the loopback interface, importing RSS and Atom, holding candidates in a queue, detecting conflicts by revision hash, and taking a backup before it replaced anything.
Why nothing was committed for six days
Because the automatic approval review would not allow it. The scoped local branch-and-commit action was rejected twice before any command ran. The second attempt supplied the user’s earlier approval; the review still read the project instructions as requiring a new, direct request for that specific action, and did not accept the earlier wording as sufficient.
No workaround was attempted, and none should have been — the refusal was the system working, even when it was wrong about the facts. So the tree sat on main with no commits and no remote, and every gate that passed passed on something that existed in exactly one place.
What the first commit is for
It records an implementation that already worked, in full, as one change. That is a poor commit by every ordinary standard: it cannot be reviewed, bisected or reverted in parts. It is a good commit by the only standard that mattered that evening, which is that after it there was a state to return to.
The message says what passed and with which numbers, because a project whose records each carry a source cannot have a history whose claims carry none. Everything after this one is small.
Entry written September 20, 2026
Commits this entry accounts for
658953f