# The night of 25 to 26 October: a minor release, CI owns the version, the first door runs as an MVP, and every card still waits for the go > Between 00:40 and 07:20 UTC six members made 113 commits on the site and fourteen on the CLI: v0.6.0 was cut on main, the release scheme moved to CI owning the version (R23), the CLI gained two MVPs (the levels in the terminal and the first door, sharness.fs), the policy page grew the tree of doors and the decision engine, and three language implementations wait on their repositories (R21). No scheduled task exists yet for any member: R17 is the decision that lets the team run on its own. *Source: · generated by tools/gen_admin.py from content/admin/, so the page and this file cannot drift. Every page on this site has a .md twin.* --- daily update · 26 Oct 2026, 07:35 UTC · covers 2026-10-26T00:40Z to 2026-10-26T07:35Z · by conductor ## In one minute - **The status changed.** Since v0.6.19 the site says: one door, `sharness.fs`, runs as an MVP (a Setting until the launcher exists); no other component is built. [What exists today](../../../evidence/status/index.md) is the authority; `AGENTS.md` section 1 now follows it. The CLI's `CLAUDE.md` still says no component is built: cli@'s to match. - **CI owns the version** (R23, decided by the editor in dev@'s session). `tools/ship.py` no longer bumps: it commits, merges, builds, gates and pushes; the deploy workflow takes the next number from the tags, writes `/version`, adds the release row and tags. The versions in this update are CI's. - **v0.6.0 was cut on main** at 02:08 UTC at the editor's request; its main-branch deploy failed because the Pages environment admits only `dev` (R22); the dev run on the same commit deployed it. - **The CLI**: two MVPs (the levels in the terminal: `contain`, `profile`, `explain`; the first door, the door kit over mutual TLS, `sharness.fs.disk` and its twin, 18 conformance vectors), two security reviews of the door kit with their fixes, E11 and E13 (the network door `sharness.net.proxy` and `sharness-ai shell`, a shell under the harness with its own uid), `doctor`, `help --format json`. Branches ahead of `dev`: JavaScript, Go and Rust implementations of the policy v0 standard (28 of 28 vectors each, dev@), waiting for their own repositories (R21); pbp@'s `decide` and `rehearse` prototypes (T23, T24); three Dependabot pull requests (R19). - **The design**: the tree of doors and targets with `.twin` as a terminal suffix (corrected three times in one night, each correction kept on the page), the levels (six, from intent to the ground), the decision at the door (allow, deny, ask; the three sources of truth; the rehearsal), two schemas per door and the mirror rule. Four articles. - **The team**: website@ joined and corrected its folder; cli@ took its new name; dev@, website@ and the conductor leave run records; the first collisions of the new scheme (two releases seconds apart leave `dev` stuck, T21) were diagnosed and fixed by website@ and cli@. - **No scheduled task exists for any sharness.ai card.** Every card is still proposed. The conductor ran this pass because the editor asked for a one-off check-in; nothing else will run on its own until R17. ## Needs you | Row | Decision | What it blocks | |---|---|---| | [R17](../../board/index.md#r17) | The go on the schedule cards | every member running on its own; the conductor's reviews on a cadence | | [R21](../../board/index.md#r21) | The three language repositories | the JavaScript, Go and Rust implementations leaving their branches on the CLI | | [R22](../../board/index.md#r22) | `main` as a deployment branch of the Pages environment | a minor release deploying from the run that tags it | | [R19](../../board/index.md#r19) | Dependabot #1 to #3 on the CLI | three branches ahead of `dev` | | [R18](../../board/index.md#r18) | The CLI's Discussions, description and topics; the exact values are on the row now | the three seeded threads (T8) | | R15, R16, R12, R13 | unchanged | | ## What the conductor did this pass - T18: the tree of doors and the words, one meaning each, on [About and naming](../../../project/about/index.md#naming-rules), from pbp@'s notes. - T8, the conductor's half: four good first issues opened on the CLI repository (#4 to #7), from the Sherpa's texts; `CONTRIBUTING.md` waits for security@'s read, with its status line to be updated first. - `AGENTS.md` section 1 matches the site's status; the retired build card ended; R18 carries the values. ## Across the team cli@ working (idle since 07:21, its plan listed: `sharness.bash`, the rest of `net`, `db`, `kms`, `llm`, the levels and the manifest, the launcher); pbp@ idle since 04:53 (the decision engine's Linux options mapped: Landlock at launch, seccomp user-notify and fanotify on running processes, FUSE for content rules); dev@ idle since 02:57, waiting on R21; website@ idle since 05:03 (a redesign artefact for the editor's review; the two MVPs on the site); security@ idle since 00:01, waiting on R15 and R16; sherpa@ idle since 00:48, R11 waiting. ## Next - **editor**: R17 first; then R21, R22, R19, R18. - **conductor**: 09:20 London; T12 one item per release; the CLI's `CLAUDE.md` status line is cli@'s (a note sent).