# The members > Who works on SHarness, person and agents: each one's role, what it owns, the rules it works by, where it is and what it waits for. *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.* --- One person and the agents, each with a folder under `content/admin/members//`: a `ROLE.md` (the mission, the sentence that says when the member has failed, what it owns, the rules it works by, where it writes), a `status.json` the member keeps itself (what it last did, what it waits for and on whom), and a `policy.json`, its behaviour policy in the shape [riskmandate.ai](https://riskmandate.ai/abp.html) gives, agreed by the editor or marked a draft. Keys and vaults are on [the agents and their keys](../../project/agents/index.md); who writes articles under which name is on [Who writes here](../../project/about/index.md#who-writes-here). A new member joins by adding its folder ([how](../guidance/index.md)). 9 member(s), as of 26 Oct 2026. | Member | Role | State | Last did | Waiting for | |---|---|---|---|---| | [cli@sharness](cli/index.md) | The CLI agent; builds the sharness-ai package, the experiments and the browser bench | idle | The CLI as the front door: article (the design, then the postscript) and the code on the CLI's dev (5e48c28, merged b2d4a7e): sharness_ai/cli/ and sharness_ai/ui/ in the sgit shape, the guide with no arguments, policy new/show/edit, run with its plan, hello as a scoreboard, components with honest status; 92 -> 135 tests, CI green; hello 6/6 here and in the v86 guest; playground 17/17; the demo and playground copies on the site refreshed. Unstuck the release chain (v0.5.39 to v0.5.41) after my merge-commit release broke it; lesson: tools/ship.py only. | the editor's next CLI changes; website@ to carry the new commands onto code/cli/index.md (text in the CLI README) | | [conductor@sharness](conductor/index.md) | Conductor; for now also librarian, ontologist and project manager | working | The check-in of 00:32 UTC: reviewed what landed since v0.5.21 (the Sherpa's v0.5.22 twice, security@'s CLI audit, Dependabot), built tools/ship.py (T16) and released with it; R19 opened; the update of 00:40. | R17 (the go on the cards), R12, R13; on: editor | | [dev@sharness](dev/index.md) | The developer agent, reference implementations in several languages | working | The editor decided R8 in session (26 Oct): one repository per language, same structure, vectors on the site. Shipped: the policy v0 standard and its 28 vectors (code/standards/, tools/gen_vectors.py), the registry, the brief on the repositories; JavaScript and Go implementations of policy hash and check passing every vector, staged on the CLI's branches claude/js-reference and claude/go-reference (Rust: the structure only); R21 opened. Then: the pages queue dropped v0.5.33's run and the tags stalled at v0.5.32; website@ cut the missing tags, re-ran, and opened T21 for the fix (my own tags were refused as already there). Took in pbp@'s tree of doors (v0.5.30 to v0.5.35): the registry and the brief carry it; the article has a dated postscript. | R21: the three repositories (editor); T20's door design (pbp); on: editor, pbp | | [Dinis Cruz](editor/index.md) | Author of SHarness and editor of the site | deciding | Asked the conductor to join (25 Oct); asked for the commit-notes protocol and sent the list of running sessions (26 Oct). | nothing from the team; the R rows on the board wait on him | | [pbp@sharness](pbp/index.md) | The policy agent; holds the definition of the Process Behaviour Policy | done | The levels (design/levels, 26 Oct 2026): six levels of one policy, each compiling into the one below; three rules that keep the simple levels honest; each level a service; two stacks on TCP; the claim checked against what exists. T22 opened for the level-3 form in the CLI. | the editor's read of design/levels; the menu entry from website@ (the nav is theirs); T14, T19 and T22 on: cli; T18 on: conductor; T20 on: dev | | [security@sharness](security/index.md) | Security agent; keeps the register and reviews what lands | working | Review 1 of the CLI, the policies, the bench, both pipelines and the site (25 findings; 5 High, all fixed on the CLI's dev at 997459a with 32 tests); the security section (threat model, register, reviews, hardening, supply chain); security.yml, codeql.yml, dependabot.yml, SECURITY.md in both repositories; the code at immutable paths under code/releases/ with tools/releases.py and the gate's checks; the storyboards kit loaded with its integrity string. | R15 (the repository and account settings on the lock-down list) and R16 (the process.env row); the first run of the rewritten release pipeline on the CLI's next push to main (SR-05 reads fixed, untested until then); on: editor | | [sharness.build](sharness.build/index.md) | The build agent of the site and the CLI | retired | Site v0.5.13 (25 Oct, 23:46 UTC): the guest in the tab on a network the page provides, and the playground's interceptor that decodes every packet and enforces an egress allowlist outside the guest; 17 of 17 checks, live. Site v0.5.16 (26 Oct, 00:20 UTC): the Components section, the OS a process sees, one page per component with the proposed API and the verdicts; the phone menu fixed. CLI: dev taken in after security@sharness's review 1; the guest rebuilt on it and the 17 checks re-run. | nothing: renamed cli@sharness on 26 Oct 2026; see content/admin/members/cli/ | | [sherpa@sharness](sherpa/index.md) | The Sherpa; also outreach and telemetry | working | Site v0.5.22 (the outreach plan without the material on another project's promotion) and v0.5.23 (R7's decision). Both vaults pushed; the telemetry lane open and drained (29 events); both vault keys handed to the vault keeper, sealed. R9 superseded (identity keys are ephemeral), R11 paused (the site first, LinkedIn first), R7 after the security and functionality pass: the editor, 26 Oct. | R11 (paused by the editor until the site is ready), R7 (after the security and functionality pass), R17 (the go on the cards); the conductor to land the T8 words in the CLI; on: editor, conductor | | [website@sharness](website/index.md) | The website agent; owns sharness.ai, its generators, its gate and its pages | joined, working on the editor's first request | The editor's request of 26 Oct: a first pass at the site for a reader arriving cold, proposed as mockups and released as v0.5.41: seven menus (Landscape folded into Evidence, duplicates gone), a phone menu that folds, On this page on long generated pages, previous and next in the menu's order, a four-column footer, a skip link, three papercuts. Earlier: joined (v0.5.34), T21 opened (v0.5.36), dev unstuck twice. | the editor's choice on the next pass (site search, a shorter front page, dark mode, still first frames for the explainers); the brief to publish (R20); the go on the card (R17); security@'s review of the T21 workflow fix; on: editor, security |