magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
2 min read

lease-claim

A deny rule by default: it refuses a leased write outside its write paths that magus proves belongs to the job, and names what to run instead.

What it catches

A leased write outside its write paths that magus proves belongs to the job.

Why

A write outside the write paths is still refused: the boundary is the declaration, and the guard never changes it inside a hook. When magus can prove the path belongs to the job, the refusal names the proof and serves the one magus job apply line that claims the path for the job, instead of sending the worker to its orchestrator. A proof is one of four: refs:, a Go file referencing a declaration the job's diff changed or removed inside its write paths; test:, a test beside a file the job changed (a _test file in its directory, or a file under its testdata) that names what the file defines; output::, a declared output of a target whose sources the job changed; and released, a path this attempt's holder released. The store proves the record again under its lock when it applies, and refuses a path another live job holds (MGS3032), a deny path, a path outside the checkout, and any claim past the job's max_claims (3 when unset), which jobs.max_claims in magus.yaml (default 10) caps. A write no proof covers stays lease-write. Every message is rendered by magus from the row and the tree; no model is asked.

Default and override

By default this rule takes the decision deny. A workspace sets it by name, in its root magusfile, to deny, advise or off:

magus\guard.builtins({"lease-claim": "advise"})

A loosening takes effect once it is committed; a tightening applies at once.

Seeing it

A verdict names its rule in brackets, which is how you got here:

deny [lease-claim]: ...

A workspace that sets this rule to advise sees advise [lease-claim]: ... instead.

magus describe rule lease-claim prints the same entry at a terminal, and magus describe rules lists every rule this workspace enforces.

See also

ReferencePages in this section. check-timeout: a bound worker's magus run whose timeout is shorter than the target's last real run allows forA deny rule by default: it refuses a bound worker's magus run whose timeout is shorter than the target's last real run allows for, and names what to run instead. human-only: a magus run reaching a human_only target: the person is asked, a leased worker refusedA deny rule by default: it refuses a magus run reaching a human_only target: the person is asked, a leased worker refused, and names what to run instead. raw-tool: a toolchain command a spell already wraps, run outside the cacheA deny rule by default: it refuses a toolchain command a spell already wraps, run outside the cache, and names what to run instead.
guardruleslease-claimdeny
Last updated (61fd39a7)
Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. Workspace in full.

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. Project in full.

Magusfile

The magusfile.buzz that declares a project's targets (as export funs) and binds its spells. Magusfile in full.

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. Target in full.

Buzz

The language magusfiles are written in (the .buzz engine). Buzz in full.

CI

An ordinary target you compose yourself with ctx.needs; magus does not hardcode its stages. It is the anchor magus affected ci keys off, and ci strips the rw charm. CI in full.

Agent

A model working through an agent host such as Claude Code, Codex, Cursor or OpenCode. magus treats an agent as one more caller of its CLI, MCP tools and console, held to the same checks as a person. Agent in full.

Job

The unit of delegated work, and one row of the job store: what an orchestrating agent handed out, with its goal, the checkpoint it was cut against, the paths it may write or must not touch, and the one check it runs. A job's holder is either a session, for work an orchestrator handed out, or the daemon, for its own maintenance. The store records; the agent guard is what reads those facts back when grading a write. Job in full.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate. Run in full.

Lease

The grant a holder takes on a job: the write and read paths that job declared, enforced in the checkout that took it with magus job exec. A job is the piece of work; a lease is permission over it. Lease in full.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.