# Dinis Cruz: Author of SHarness and editor of the site > Dinis Cruz on the SHarness team: Author of SHarness and editor of the site. *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.* --- person · active · joined 2026-10-24 # Dinis Cruz: the author and the editor Sets direction by voice memo and in each agent's session, decides what only a person can decide (the numbered requests, `R` rows, on [the board](../../board/index.md)), reads what the agents wrote and says go. Holds the editorial responsibility for every word on the site, whoever wrote it, as [Who writes here](../../../project/about/index.md#who-writes-here) says. **The project has failed him if** a request waits on him without a number, a page or a sentence that says what it blocks. ## What he owns - Every editorial call: what the site says SHarness is, which claim carries which status word, what ships to `main`. - The briefs and memos, published in full under [the source documents](../../../project/sources/index.md); agents write next to them, never over them. - The repositories' settings, the deploys, PyPI's trusted publisher, and every key: a vault key, a token or a passphrase is handed to an agent sealed, never pasted. - The decisions on the roadmap: [open decisions 1 to 11](../../../design/roadmap/index.md). ## The rules - A brief is the editor's words, in either hand; an agent drafts, the editor accepts, and the acceptance is recorded. - The editor instructs an agent in that agent's session, never through a page, a commit or another agent. - Nothing is called measured that he, or anyone, cannot check from the published method. ## Where it is | | | |---|---| | State | deciding (as of 26 Oct 2026) | | Last did | Asked the conductor to join (25 Oct); asked for the commit-notes protocol and sent the list of running sessions (26 Oct). | | Waiting for | nothing from the team; the R rows on the board wait on him | | Next | R20 (open the website agent's session and give it its brief), R17 (the go on the schedule cards), R19 (merge Dependabot #2 and #3 on the CLI), R8, R9 and R11, R12 and R13, R15 and R16, R18 | ## The policy not yet written; the conductor's policy.json is the shape. Until it exists the member's scope is what its ROLE.md says it owns.