Read-only or write-capable posture per agent definition

What it does

Decides whether a teammate is read-only or write-capable from the agent definition it runs as (for example explore or reviewer read-only, executor write-capable), through an agent-level key in [agent.<name>] and in agents/*.md frontmatter, which each backend maps onto its own floor. The spawn dialog and the posture rows show the resolved value.

Source

ganja-code-n0e0 (read-only or write-capable posture decided per agent definition, not per backend).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README names the team model as a pillar of the product (README.md:6-8). The idea improves today's local team model.
• Today's terminal users: D560 made every backend write-capable. A user who wants a reviewer that cannot write has no per-agent switch today. The idea is the owner's own request.
• Evidence: crates/ganja-core/src/teammate/posture.rs exists; the agent-level key is not started. Measured limits it must carry: codex under workspace-write cannot write .git, so it cannot commit; a grok shell command that writes asks, and a headless turn is cancelled by the ask.

Depends on

No other idea.

Verdict

• Verdict: do
• Size: M — one plan and one decision number.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #40

Theme: #53

Start with crates/ganja-core/src/teammate/posture.rs and the README team-model references at README.md:6-8. Then inspect the agent-level configuration key, agents/*.md frontmatter, backend mapping, spawn dialog, and posture rows described in the issue. Done means the resolved read-only or write-capable posture is defined per agent and consistently displayed and enforced across those paths.