Home / The model / The capabilities / write.file.project

write.file.project

Change the project it is working on. Verb write, object file, reach project, family filesystem. Its effect is with-effort: undone at a cost.

In 5 of 9 published shapes

Deployment shapeBarrier thereKnown byNote
Claude Code on the web (a remote session container)none (not a control)observedthe attached working tree is writable
Claude Code (the CLI, on your own machine)none (not a control)derived
Claude Code (the CLI, on your own machine)none (not a control)derived
Claude Desktop (a desktop app with local tools)none (not a control)derived
Actions runner (a hosted CI job)none (not a control)observedthe checked-out tree at this ref is writable by the job
BarrierWhat stands in the wayIs it a control
nonenothing in the wayno
expectationa rule in prose, enforced by nobodyno
settinga switch the agent's own account can flipno
boundaryenforced above the grant, out of the agent's reachyes

What the starting mandates say about it

The mandate saysWhich mandates
authorisedA coding assistant on my machine, A coding assistant in a container on the web, The desktop app, with local tools switched on, A CI job on a hosted runner
refusednone
unstatedChat, with connectors switched on, Chat in the browser, nothing connected, A browser extension I installed, A scheduled job under a service account

Unstated is not authorised. A mandate that never mentioned a capability did not authorise it, and the delta on every example page counts it as excess and says which kind it was.

What would move it to the fourth barrier

WhatWhat it costsThe barrier afterwards
a review before mergea reviewer's timesetting
This is a published reduction, not a recommendation. Whether it is worth doing depends on the assets and the consequences, which are not in this document and are not this site's to guess.

The capability grammar · This primitive as JSON