Review: the five other specialists and the email cell

Verdict

Not ready, as expected on day one: none of the six has a behaviour policy. All six now have a proposed one, in proposals/, that passes abp-check. Each team's first job is to measure its own reach and ask its person to approve.

Checker result

proposals/code/abp.md:       specialist.code@AgentiCCells.dinis 0.1.0 proposal, mixed; 23 rules: boundary 2, setting 6, expectation 15
proposals/design/abp.md:     specialist.design@AgentiCCells.dinis 0.1.0 proposal, mixed; 23 rules: boundary 2, setting 6, expectation 15
proposals/email-cell/abp.md: cell.email@AgentiCCells.dinis 0.1.0 proposal, observe; 14 rules: boundary 5, setting 7, expectation 2
proposals/security/abp.md:   specialist.security@AgentiCCells.dinis 0.1.0 proposal, mixed; 25 rules: boundary 2, setting 8, expectation 15
proposals/ux/abp.md:         specialist.ux@AgentiCCells.dinis 0.1.0 proposal, mixed; 23 rules: boundary 2, setting 5, expectation 16
proposals/writing/abp.md:    specialist.writing@AgentiCCells.dinis 0.1.0 proposal, mixed; 23 rules: boundary 2, setting 7, expectation 14
OK

About two thirds of each specialist's rules are expectations: rules only the agent keeps. That is honest for day one and is the number to bring down. The email cell is the other way round, because its design already puts the dangerous things out of reach.

The checker also caught a fault in the first draft of the writing specialist's policy: sending in a person's name was marked "draft" with only an expectation in the way, which is exactly the shape of the 9 October emails signed "Dinis". Sending is now denied and drafting is its own row. The agent template had the same trap and was fixed the same way.

Findings that apply to all five specialists

They were seeded from the same template, so they share a shape, and they share its gaps.

  1. Must fix first: the specialists' own names fail the release gate. scripts/check-commits.mjs (from the site template, ACC-015) accepts an Agent: trailer only as role@AgentiCCells.person with no dot in the role. Every specialist was named specialist.<skill>@AgentiCCells.dinis. This specialist's first two pushes failed CI on that check (runs 4 and 5, 16 November) and nothing deployed. The Code specialist's commits carry the same form. A gate that held, which is what a boundary is for; but the name and the gate cannot both stand. Choice for Dinis: allow a dotted role in the template's check (the PrompTugal scheme, role.speciality@), or rename the specialists (specialist-abp@). Not changed here: weakening a check, or renaming an agent, is not this specialist's call. Resolved 16 November, about 18:15 UTC: Dinis chose dots ("that's our terminology"); the template was fixed at f7438ad, and every factory repository should take the same line in scripts/check-commits.mjs.
  2. Must fix before release: no policy. CLAUDE.md holds the rules, but every rule in it is an expectation. Proposed: the drafts in proposals/. (Principle 1.)
  3. Must fix: dev is unprotected, and the gates live in the repository the agent writes. The validator, leak scan and workflow can be edited by the agent they gate. Proposed: protect dev (no force-push, no deletion, the Pages workflow required), and CODEOWNERS on scripts/ and .github/workflows/ needing Dinis. (Principle 11; mistake 1.)
  4. Must fix: the account can push to about 200 repositories. Measured on this specialist's session; the others share the account, so it is inferred for them. A consultant needs write on one repository and comments on the rest. Proposed: a fine-grained token per specialist. (Principle 9.)
  5. Should fix: starting sessions and scheduled tasks is in reach, with only a sentence in the brief against it. Proposed: remove those tools from specialists that do not need them. (Principle 17.)
  6. Should fix: nothing reads board/HOLD.md. CLAUDE.md says never work while it exists, but release.sh does not check it. Proposed: two lines in the template's release.sh, through the site factory, so every seeded repository gets them. Not made here: it changes a shared gate, and the factory owns the template.
  7. Should fix: no agent has a key of its own. Commits are signed by the session's signer and named by the Agent: trailer, which is the agent's own word. (Principle 23.)
  8. Worth considering: every site says "the review lane is not wired yet". That is true and honest. Until it is, the file-based request in reviews/ works for any specialist; each could copy it.

Findings for each team

What this review did not check

This page is generated from 2026-11-16__specialists-and-email-cell.md, its Markdown twin.