Repository navigation
v1.23.0
Pre-release
Pre-release
A testing build. It is the build that ran as the beta from 2026-09-11 to 2026-09-16 (1.22.0-test4), promoted unchanged. Everything below is what changed for a user since v1.22.0.
Your project's shape
- Setup asks what your project's parts are. A new project is set up with the product in its own folder and repository, and the planning documents kept privately around it. Setup now asks roughly what the moving parts are, gives each its own folder, and writes a small SPEC per part; a build reads only the spec of the part it is working in.
- A project that already has a public repository is wrapped, not moved. Setup tells the two conversions apart by whether the repository has a remote, and where it does, keeps that repository whole and creates the private outer around it.
- A
temp/folder for what the project does not keep. Fetched transcripts, one-read downloads and drafts you edit land there, ignored by git, so nothing has to record when to delete them.
Cycles
- A cycle can chain its rituals into a close calendar. A weekly release, say, names the rituals that lead up to it and how many days before the anchor each falls due, and the planning opening computes which one is due today. A later ritual can carry a gate that refuses to run while an earlier one's output is unfinished.
- Every ritual step names what fires it and who performs it. A definition missing either is refused when it is written.
- Due cycle work now comes first at planning, ahead of ordinary captures.
The safety check and the hooks
- A door through a refusal, on your word. Where the safety check refuses an edit in a session with no build running, asking for the same change again in your own words opens that one path for the session, and the close records the edit.
- Every decision is logged. The safety check keeps a log of what it allowed and refused in the project's working folder, so a write that passed with no line is a check that never ran.
- Time words need a source. A record that says "an hour ago" or "yesterday" with nothing to read the time from is refused once, and so is a clock time later than the clock actually reads. The finished reply gets the same check.
- Every command tells you when the hooks are not running, and what to check:
python --versionmust print a version, not the Windows Store placeholder. - A step of yours says how many things are waiting on it, read off the queue, and says nothing where nothing is.
Planning and closing
- Handing work to another project for completion closes the item here. The walkthrough ends at the send, and anything depending on the outcome is filed as its own item first, so a clean close drops nothing.
- Held work says what it rests on. When a hold lifts, the offer says what the item's design was assuming and whether anything has checked it since.
- Drafts you edit are handed over as a link that opens in the side panel, in the project's
temp/folder. - Rules trimmed. Several passes removed reasoning and history from the always-loaded rules and the procedure docs, so the same instructions are carried in fewer words.
For porters
The port-facing changelog is attached (63 entries over v1.22.0..v1.23.0). It says what changed inside which shipped file; the mapping stays yours.
Install and update: see the README. Report a problem by asking Claude to file a GitHub issue on this repository, or on the Discord.