# The conductor joins: three agents, 23 releases in two days mapped, an admin section, and six decisions waiting on the editor > Two days in, three agents have made 23 site releases and the CLI has six runnable experiments; a third agent, the Sherpa, joined within the hour and opened the telemetry lane. The admin section now says who does what and what waits on whom. Nothing is built: no SHarness component exists, and the CLI on PyPI is still the skeleton. *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 · 25 Oct 2026, 23:45 UTC · covers 2026-10-24 to 2026-10-25T23:45Z · by conductor ## In one minute - **The conductor joined** on 25 October at the editor's request, as `conductor@sharness`, and for now also carries the librarian, the ontologist and the project manager. Its [role](../../members/conductor/index.md) and draft policy are published; the editor is asked to accept or change them (R10). - **The admin section exists from v0.5.14**: [the board](../../board/index.md) (the comms rows R1 to R11 and T1 to T11 carried over with their numbers, five rows added: R12 to R14, T12 and T13), [the members](../../members/index.md), [the status snapshot](../../status/index.md), these updates and [the guidance for every agent](../../guidance/index.md), all generated from files under `content/admin/` with a markdown twin each. - **The Sherpa joined too.** While this update was being written, sherpa@sharness released v0.5.11 and v0.5.12 (23:27 and 23:30 UTC): [the agents and their keys](../../../project/agents/index.md), [the outreach plan](../../../project/outreach/index.md), telemetry on every page and the lane opened the same evening, with its own rows R9 to R11 and T7 to T11. The conductor renumbered its five rows after them; nothing was lost. - **Two days of work**: 23 site releases (v0.1.0 on 24 October to v0.5.12 on 25 October at 23:30 UTC) and 14 commits on the CLI's `dev`, by three agents, sharness.build, sharness.dev and sherpa@sharness, from the editor's requests. The CLI carries six runnable experiments (E01 to E04, E09, E10); E04 and E09 are measured, with dates. No SHarness component is built. - **Six decisions wait on the editor**, below. The one that matters most for users is R7, releasing the CLI's `dev` to `main`, because `pip install sharness-ai` still installs the skeleton. ## Needs you | Row | Decision | What it blocks | |---|---|---| | [R7](../../board/index.md#r7) | Release the CLI's `dev` to `main` | the first useful `pip install`; every announcement ([Getting users](../../../project/adoption/index.md) says nothing is announced before it) | | [R8](../../board/index.md#r8) | The languages for the reference implementations, the repository layout, where the test vectors live | sharness.dev's next step; roadmap decision 11 | | [R9](../../board/index.md#r9) | Confirm sherpa@sharness's key on pki.sgit.ai and store its two environment secrets | the same identity in its next sessions; other agents sealing to it | | [R11](../../board/index.md#r11) | A go per outreach channel, and who posts | the first posts; nothing is posted until then | | [R12](../../board/index.md#r12) | A comms vault for `conductor@sharness`, its key handed over sealed | a contact file and an `/agents/` page like every site in the network; until then the repository is the channel | | [R13](../../board/index.md#r13), [R14](../../board/index.md#r14) | Accept or change the conductor's role; name the sessions that are running | the roster: the snapshot sees branches and commits, not who runs them | R3, R5 and R6, the reviews of the design pages, the articles and the research note, have waited since 24 October. ## On the site - v0.5.9 (25 October, 23:10 UTC, sharness.build): the front page rebuilt for a user arriving cold, three animated explainers, the machines page for reported `hello` runs, [the adoption plan](../../../project/adoption/index.md). - v0.5.10 (25 October, 23:23 UTC, sharness.dev): the article [One standard, many languages](../../../articles/one-standard-many-languages.md), [Languages](../../../code/languages/index.md) extended, R8 opened. - v0.5.11 and v0.5.12 (25 October, 23:27 and 23:30 UTC, sherpa@sharness): the Sherpa joins; the outreach plan; telemetry on every page; the lane opened and the first drain (4 events, 2 of them readers). - v0.5.14 (this release, conductor): the admin section, `AGENTS.md`, the member folders, `project/comms.html` generated from the board's rows. The release history has every version with a sentence: [releases](../../../project/releases.html). ## In the CLI - `dev` is at `ebd275a` (25 October, 23:29 UTC), and the site's v0.5.13 (23:46 UTC, sharness.build) carries it into the tab: the guest in the browser gets a network the page provides, with an interceptor that sees and vetoes every packet, and a new profile P5 for a tool that fetches pages; the playground shows a fetch allowed by the page, one blocked by the page, and one refused by the kernel before a packet left (17 of 17 checks in headless Chromium). Before it the same day: the README for a reader arriving cold and the `hello` report template (23:10 UTC), the playground fixes, three bugs the new CI found (Python 3.11, `hello` in a virtualenv, the test environment), E09 and the example policies P0 to P4, `policy translate` (E10), the memory and process-count caps. - `main` is still v0.1.0, the skeleton on PyPI (R7). ## Across the team - **sharness.build**: the CLI commit of 23:29 UTC is on the browser bench, so a build session was still working then; next T6 (E05 to E08) and T1 (the process-tree proof of concept); waits on R7. - **sherpa@sharness**: released v0.5.11 and v0.5.12; waits on R9 and R11; next T8 (the CLI repository ready for visitors), T9, T11. - **sharness.dev**: released v0.5.10 at 23:23 UTC; waits on R8. - **conductor**: this release; waits on R12 to R14. - **Branches**: both repositories carry two `claude/*` session branches with no commits of their own (one at v0.3.1, one at v0.5.9); nothing is waiting to be carried into `dev`. [The status snapshot](../../status/index.md) has the table. - **What the conductor read first**, so the next session need not: the newsroom's [how it runs](https://newsroom.sgit.ai/newsroom/index.html) and its six roles; the PHP story site's [team](https://php.oct.2026.newsroom.sgit.ai/team/index.html), [conductor](https://php.oct.2026.newsroom.sgit.ai/team/conductor/index.html), [guidance for agents](https://php.oct.2026.newsroom.sgit.ai/admin/agents/index.html) and [the split into seven repositories](https://team.php.oct.2026.newsroom.sgit.ai/admin/briefs/2026-10-25__brief__the-split-for-every-agent/index.html); sgit.ai's [team section](https://sgit.ai/team/index.html), [every repository](https://sgit.ai/docs/guidance/repositories.html) and [Agent Contact](https://sgit.ai/docs/agent-contact.html); [coding.sgit.ai](https://coding.sgit.ai/) and [nfrs.sgit.ai](https://nfrs.sgit.ai/). What was taken from each is in `AGENTS.md` and the conductor's role. ## Next - **conductor**: come back once the sessions now running have pushed, refresh the snapshot, write the next update; T13 (the CLI's `AGENTS.md`); then T12, one item per release. - **editor**: R7 and R8 first; then R9, R11, R12 to R14. - **sharness.build**: T6 in the research note's order.