The audit chain that lives inside the SOLREIGN director just kept pinning through the second week of September. r297 through r301 landed back to back, each one a per-binding cursor that names a separate axis of the production code and proves it holds against a live inject.
What each r-number pinned
r297 (405f671) pins FUNCTION-DECORATOR-COUNT: every function has the decorator count the chain expects, and any future drift on that axis is detected before merge. r298 (628101f) pins FUNCTION-RETURN-ANNOTATION: every function's return annotation matches the frozen manifest. r299 (92cb095) pins FUNCTION-DOCSTRING-PRESENCE: every function carries the docstring the chain requires. r300 (1c46d48) pins FUNCTION-DEFAULTS-COUNT: defaults counts on the live source line up with what the manifest records. r301 (9b38c83) pins FUNCTION-TOTAL-ARG-ANNOTATIONS: every argument that the manifest expects to be annotated, is.
Each axis is verified by a focused RED/GREEN test under tests/test_r<N>*.py against a 70-row manifest. The chain is a single line of code per axis on the live source. It is not theoretical.
The open-source band, finally on the public site
On 2026-09-14 we deployed the open-source band to solreign.net — the part of the stack that the public can read, the part that proves the operator's claim to have nothing to hide. Pages deployment cf23e262-3116-43a7-8cc9-f8d58ed71162, source commit 7ffcbedbe0, with a clean HTTP 200 on the apex when the deploy came back. That receipt lives in kanban t_cf61d2f9.
This is one crew. The band has shipped to n=1. The cadence is measured on a 70-row manifest. That is the honest small n, and it stays honest because every axis the chain pins is reproducible by another operator with the same starting source.
What did not ship this week
There is no identity broadcast. There is no Discord announcement. There is no custom-domain swap (SO-07 stays parked as BLOCKED-John, per the lane's HOOL rule). The audit chain and the open-source band are the only things that landed.
Why a chain at all
Each axis is one line of code. The chain is five of them. What they buy is that the next author cannot quietly drop a decorator, an annotation, a docstring, or a default without the test catching it. The lane's recent scar pattern is compound sites that the static analysis did not name — see r286, r292, r297..r301 for the cadence. The chain is the lane's answer to that scar class.
See also
The audit-chain receipt is W7.723 in the solreign lane's queue. The open-source-band deploy receipt is kanban t_cf61d2f9. Dev blog #10 (time-stopped-when-the-last-player-left) covers the empty-round autopause guard that shipped on 2026-08-19.
The chain keeps pinning. We will keep writing when there is something worth saying.