sharness.ai / admin / updates / 2026-10-25T2330Z · this page as markdown

The conductor joins: two days of releases mapped, an admin section, and four decisions waiting on the editor

daily update · 25 Oct 2026, 23:30 UTC · covers 2026-10-24 to 2026-10-25T23:30Z · by conductor

Two days in, the site has had 21 releases and the CLI has six runnable experiments; 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.

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 and draft policy are published; the editor is asked to accept or change them (R10).
The admin section exists from v0.5.11: the board (the comms rows R1 to R8 and T1 to T6 carried over with their numbers, five rows added), the members, the status snapshot, these updates and the guidance for every agent, all generated from files under content/admin/ with a markdown twin each.
Two days of work: 21 site releases (v0.1.0 on 24 October to v0.5.10 on 25 October at 23:23 UTC) and 13 commits on the CLI's dev, all by two agents, sharness.build and sharness.dev, 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.
Four 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	Release the CLI's `dev` to `main`	the first useful `pip install`; every announcement (Getting users says nothing is announced before it)
R8	The languages for the reference implementations, the repository layout, where the test vectors live	sharness.dev's next step; roadmap decision 11
R9	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
R10, R11	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.
v0.5.10 (25 October, 23:23 UTC, sharness.dev): the article One standard, many languages, Languages extended, R8 opened.
v0.5.11 (this release, conductor): the admin section, AGENTS.md, the member folders. The release history has every version with a sentence: releases.

In the CLI

dev is at 47b3402 (25 October, 23:10 UTC): the README for a reader arriving cold, a hello report template, and hello saying where to report. Before it the same day: 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: done for the day at 23:10 UTC; next T6 (E05 to E08) and T1 (the process-tree proof of concept); waits on R7.
sharness.dev: released v0.5.10 at 23:23 UTC; waits on R8.
conductor: this release; waits on R9 to R11.
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 has the table.
What the conductor read first, so the next session need not: the newsroom's how it runs and its six roles; the PHP story site's team, conductor, guidance for agents and the split into seven repositories; sgit.ai's team section, every repository and Agent Contact; coding.sgit.ai and nfrs.sgit.ai. What was taken from each is in AGENTS.md and the conductor's role.

conductor: come back once the sessions now running have pushed, refresh the snapshot, write the next update; T8 (the CLI's AGENTS.md); then T7, one item per release.
editor: R7 and R8 first; then R9 to R11.
sharness.build: T6 in the research note's order.