Repository navigation
Logbook October 2026
Week of Monday 28th — A structural clean-up week: command entry points are made small, every source falls under lint and format policy, and Aiken documentation is published. In parallel the protected open datum goes from model to validator to a lifecycle run through the ordinary command line. The week ends with the first preprod demonstration of one registry and one key and the 0.9.0 release.
The command line works through an acquired node interface (#327) with indexer-backed coherent reads (#328), and recovers its state after an uncertain submission or a rollback (#329). A folder can reject a pending request before the retraction deadline (#338). The preprod demonstration of one registry and one key is delivered (#339) together with a backend contract suite and release evidence (#337).
Release 0.9.0 is cut and the site is reconciled with registry mode, manifests and releases (#353). The command line gains separate book and fold commands (#367), an opt-in phase log with a timestamped journal (#366), clearing of expired requests ([#374][374]), and text keys on every command with the envelope built by insert (#365, #369). Refused transactions are re-evaluated with traced validators to report the chain's own refusal reason (#357), registry rows move onto generic conformance programs ([#373][373]), and Lean's batch laws are exposed as driver questions (#349). Requirement names are made descriptive throughout ([#378][378]). Reclaim of a pending request, the next conformance migration and a persistent indexer socket plan remain open.
A sweep of all 151 open issues against main and the milestone scope settled this morning. Thirty-two issues and two deferred drafts closed as done or superseded; every open issue now carries a milestone. The conformance-bible epic and its children moved to assurance; the dead naming-era journey executables are deleted under one ticket; the Scalus experiment, the naming command-line tool and the 30 October naming stretch are closed. A new milestone, [Shareable script family][m6], holds the shared-script validator redesign and Demo 2. The Demo 1 review card moves to 22 October.
Two rulings came out of the sweep. The Singular executable is the registry only; the open datum becomes its own executable built on the Singular library, which is how cardano-keri's ckeri will be built ([#528][528]). Every request carries a tag minted by Singular's request policy, untagged outputs at the request address are spendable by anyone, and every tagged request has an exit ([#529][529]). The fleet rule that every ticket is searched and placed before filing landed in the shared skills.
: https://github.com/lambdasistemi/singular/issues/528 [529]: https://github.com/lambdasistemi/singular/issues/529 [m6]: https://github.com/lambdasistemi/singular/milestone/6 [374]: https://github.com/lambdasistemi/singular/pull/374 [378]: https://github.com/lambdasistemi/singular/pull/378