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

MGS3039: a job nothing would grade

magus job fork, magus job apply and magus\job.put refused a job record that nothing would grade:

[MGS3039] job wave/docs writes and declares no check or goal: declare the check
  that proves the change, such as {"target": "test", "project": "."}

Nothing was written to the job store.

What fires it

  • A record with write paths and neither a check nor a goal. Its worker could report done with no recorded run behind it.
  • A record with no write paths that is not read_only. Empty write paths are correct only on a job that gathers evidence and writes nothing.

What to do

  • For a job that writes, add the check that proves its change, or a goal.
  • For a job that writes nothing, set "read_only": true.
  • Otherwise, list the files the job edits as its write paths.

See also

  • Leases: checks, goals and read-only jobs.
MGS3039jobsleasesforkapplyagentsvalidationgoals
Last updated (29d8b3de)
Glossary

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.

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.

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.