mnemosyne cannot create deepwork/memory-bank artifacts — edit:deny + no write tool contradicts its declared scope

[ils15]

Summary

mnemosyne's declared scope REQUIRES writing files inside .pantheon/memory-bank/ and .pantheon/deepwork/, but its permission set denies every file-creation path (edit: deny, bash: deny, no write tool). The agent escalates every time it is asked to materialize artifacts.

Evidence

• src/agents/mnemosyne.md:27-39 — permissions: bash: deny, edit: deny, task: "*" deny; tools: pantheon-resources all, memory recall/store/search/delete, execute_code_script only
• src/agents/mnemosyne.md:42-47 — scope: "Memory Bank ONLY — NEVER write files outside .pantheon/memory-bank/ or .pantheon/deepwork/" (i.e., writing INSIDE is the job)
• Live validation: escalated 2× (2026-09-10 open3dcalc deepwork D0; 2026-09-11 cosmos-hub F0 artifacts) with "ferramenta de criação/escrita local ausente" — creation had to be re-routed to @talos

Impact

• Deepwork PLAN.md/STATUS.md and memory-bank ADRs cannot be created by the agent that owns them
• Forces a re-route on every first-artifact creation (extra delegation, pitfall already cached in memory as pitfall:mnemosyne-cannot-create-files)

Suggested fixes

• Grant a scoped write: write: allow limited to .pantheon/memory-bank/** and .pantheon/deepwork/** (keep deny elsewhere), or edit: allow scoped to those paths
• Alternative: keep mnemosyne read-only and officially move artifact creation to implementers — but then update the agent scope text so it stops claiming write ownership