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

write.repository.project

Commit to the repository it was pointed at. Verb write, object repository, reach project, family code. Its effect is with-effort: undone at a cost.

In 4 of 9 published shapes

Deployment shapeBarrier thereKnown byNote
Claude Code on the web (a remote session container)none (not a control)observeda repository is attached and 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
Actions runner (a hosted CI job)boundaryobservedthe 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
refusednone
unstatedThe desktop app, with local tools switched on, Chat, with connectors switched on, Chat in the browser, nothing connected, A CI job on a hosted runner, 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
none needed for most work; a review before merge is the controla 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